[Touch-packages] [Bug 1502717] [NEW] wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()
Public bug reported: wpa_supplicant crashed with SIGSEGV when removing kernel module brcmfmac. rsalveti@evapro:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Wily Werewolf (development branch) Release:15.10 Codename: wily Linux evapro 4.2.0-14-generic #16-Ubuntu SMP Fri Oct 2 05:14:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux MacBook Pro Retina 13' 12,1 43557 Oct 4 18:02:56 evapro kernel: [ 86.406354] usbcore: deregistering interface driver brcmfmac 43558 Oct 4 18:02:57 evapro avahi-daemon[950]: Withdrawing workstation service for wlp3s0. 43559 Oct 4 18:02:57 evapro NetworkManager[936]: devices removed (path: /sys/devices/pci:00/:00:1c.2/:03:00.0/net/wlp3s0, iface: wlp3s0) 43560 Oct 4 18:02:57 evapro NetworkManager[936]: (wlp3s0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36] 43561 Oct 4 18:02:57 evapro NetworkManager[936]: (wlp3s0): failed to disable userspace IPv6LL address handling 43562 Oct 4 18:02:57 evapro gnome-session[2190]: (nm-applet:2346): GLib-CRITICAL **: Source ID 190 was not found when attempting to remove it 43563 Oct 4 18:02:57 evapro NetworkManager[936]: radio killswitch /sys/devices/pci:00/:00:1c.2/:03:00.0/ieee80211/phy0/rfkill0 disappeared 43564 Oct 4 18:02:57 evapro kernel: [ 86.947963] show_signal_msg: 39 callbacks suppressed 43565 Oct 4 18:02:57 evapro kernel: [ 86.947968] wpa_supplicant[1330]: segfault at 0 ip 7f835170fcba sp 7fffc00140c8 error 4 in libc-2.21.so[7f835167+1c] 43566 Oct 4 18:02:57 evapro NetworkManager[936]: wpa_supplicant stopped 43567 Oct 4 18:02:57 evapro NetworkManager[936]: (wlx048d38ab601a): supplicant interface state: completed -> down 43568 Oct 4 18:02:57 evapro NetworkManager[936]: (NetworkManager:936): GLib-CRITICAL **: Source ID 167 was not found when attempting to remove it 43569 Oct 4 18:02:57 evapro NetworkManager[936]: Failed to GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.30 was not provided by any .service files: remove network. 43570 Oct 4 18:02:57 evapro dbus[969]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' 43571 Oct 4 18:02:57 evapro NetworkManager[936]: (wlx048d38ab601a): device state change: activated -> unavailable (reason 'supplicant-failed') [100 20 10] 43572 Oct 4 18:02:57 evapro systemd[1]: Started WPA supplicant. 43573 Oct 4 18:02:57 evapro NetworkManager[936]: (wlx048d38ab601a): canceled DHCP transaction, DHCP client pid 1915 43574 Oct 4 18:02:57 evapro NetworkManager[936]: (wlx048d38ab601a): DHCPv4 state changed bound -> done 43575 Oct 4 18:02:57 evapro avahi-daemon[950]: Withdrawing address record for 192.168.1.17 on wlx048d38ab601a. 43576 Oct 4 18:02:57 evapro avahi-daemon[950]: Leaving mDNS multicast group on interface wlx048d38ab601a.IPv4 with address 192.168.1.17. 43577 Oct 4 18:02:57 evapro avahi-daemon[950]: Interface wlx048d38ab601a.IPv4 no longer relevant for mDNS. 43578 Oct 4 18:02:57 evapro avahi-daemon[950]: Withdrawing address record for fe80::68d:38ff:feab:601a on wlx048d38ab601a. 43579 Oct 4 18:02:57 evapro avahi-daemon[950]: Leaving mDNS multicast group on interface wlx048d38ab601a.IPv6 with address fe80::68d:38ff:feab:601a. 43580 Oct 4 18:02:57 evapro avahi-daemon[950]: Interface wlx048d38ab601a.IPv6 no longer relevant for mDNS. 43581 Oct 4 18:02:57 evapro NetworkManager[936]: Writing DNS information to /sbin/resolvconf 43582 Oct 4 18:02:57 evapro dnsmasq[1607]: setting upstream servers from DBus 43583 Oct 4 18:02:57 evapro dnsmasq[1607]: using nameserver fe80::e6f4:c6ff:fe0b:5c4d#53 43584 Oct 4 18:02:57 evapro whoopsie[994]: [18:02:57] Cannot reach: https://daisy.ubuntu.com 43585 Oct 4 18:02:57 evapro whoopsie[994]: [18:02:57] offline 43586 Oct 4 18:02:57 evapro whoopsie[994]: [18:02:57] Cannot reach: https://daisy.ubuntu.com 43587 Oct 4 18:02:57 evapro NetworkManager[936]: Writing DNS information to /sbin/resolvconf 43588 Oct 4 18:02:57 evapro dnsmasq[1607]: setting upstream servers from DBus 43589 Oct 4 18:02:57 evapro NetworkManager[936]: NetworkManager state is now CONNECTED_LOCAL 43590 Oct 4 18:02:57 evapro NetworkManager[936]: NetworkManager state is now DISCONNECTED 43591 Oct 4 18:02:57 evapro nm-dispatcher: Dispatching action 'down' for wlx048d38ab601a 43592 Oct 4 18:02:57 evapro systemd[1]: wpa_supplicant.service: Main process exited, code=dumped, status=11/SEGV 43593 Oct 4 18:02:57 evapro systemd[1]: wpa_supplicant.service: Unit entered failed state. 43594 Oct 4 18:02:57 evapro systemd[1]: wpa_supplicant.service: Failed with result 'core-dump'. 43595 Oct 4 18:02:58 evapro gnome-session[2190]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. 43596 Oct 4 18:02:58 evapro org.freedesktop.Notifications[2012]: ** Message: resizing pixbuf to 44 ProblemType: Crash
Re: [Touch-packages] [Bug 1458694] Re: [vivid-overlay] unity8 fails to start on the emulator
On Fri, Aug 21, 2015 at 6:52 AM, Timo Jyrinki
timo.jyri...@canonical.com wrote:
As per QA report:
Needs a fix in unity8 so we can get past edges demo and confirm there are no
further issues with the silo before landing.
Sorry, but why do we need to disable the edge demo? It's still useful
during the first boot. If needed we could extend the flashing tool to
offer an option for that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1458694
Title:
[vivid-overlay] unity8 fails to start on the emulator
Status in Canonical System Image:
Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Status in unity8 package in Ubuntu:
Fix Committed
Bug description:
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 140
device name: generic_x86
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2015-05-25 12:02:10
version version: 140
version ubuntu: 20150525
version device: 20150210
version custom: 20150525
When starting unity8 (this started at image 136, probably when mir
0.13 landed):
phablet@ubuntu-phablet:~$ cat ./.cache/upstart/unity8.log
()
[1432595001.896139] mirplatform: Found graphics driver: dummy
[1432595001.898447] mirplatform: Found graphics driver: android
qtmir.mir: MirServer created
[1432595003.675225] Server: Starting
[1432595003.679331] Loader: Loading modules from:
/usr/lib/i386-linux-gnu/mir/server-platform
[1432595003.679501] Loader: Loading module:
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
[1432595003.680673] Loader: Loading module:
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
[1432595003.681107] WARNING Loader: Failed to load module:
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
[1432595003.684868] Loader: Loading module:
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
[1432595003.685014] mirplatform: Found graphics driver: dummy
[1432595003.685211] mirplatform: Found graphics driver: android
[1432595003.685416] Platform Loader: Selected driver: android (version 0.13.0)
qtmir.mir: PromptSessionListener::PromptSessionListener - this=
PromptSessionListener(0x9679764)
qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x9676d24)
qtmir.mir: MirShell::MirShell
[1432595003.883766] DisplayServer: Mir version 0.13.0
QtCompositor::setAllWindowsExposed true
qtmir.clipboard: D-Bus registration successful.
Mode argument was not provided or was set to an illegal value. Using default
value of --mode= full-greeter
Cannot create window: no screens available
With version 135 it starts fine, but not fully functional, giving this
error:
QOpenGLShader::compile(Fragment): 0:2(12): warning: extension
`GL_OES_standard_derivatives' unsupported in fragment shader
0:2(1): error: #extension directive is not allowed in the middle of a shader
*** Problematic Fragment shader source code ***
#extension GL_OES_standard_derivatives : enable // Enable dFdy() on OpenGL
ES 2.
#define lowp
#define mediump
#define highp
// Copyright © 2015 Canonical Ltd.
//
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU Lesser General Public License as published by
// the Free Software Foundation; version 3.
//
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU Lesser General Public License for more details.
//
// You should have received a copy of the GNU Lesser General Public License
// along with this program. If not, see http://www.gnu.org/licenses/.
//
// Author: Loïc Molinari loic.molin...@canonical.com
// Static flow control (branching on a uniform value) is fast on most GPUs
(including ultra-low
// power ones) because it allows to use the same shader execution path for an
entire draw call. We
// rely on that technique here (also known as uber-shader solution) to
avoid the complexity of
// dealing with a multiple shaders solution.
// FIXME(loicm) Validate GPU behavior with regards to static flow control.
uniform sampler2D shapeTexture;
uniform sampler2D sourceTexture;
uniform lowp vec2 dfdtFactors;
uniform lowp vec2 opacityFactors;
uniform lowp float sourceOpacity;
uniform lowp float distanceAA;
uniform bool textured;
uniform mediump int aspect;
varying mediump vec2 shapeCoord;
varying mediump vec4 sourceCoord;
varying lowp vec4 backgroundColor;
const mediump int FLAT = 0x08; // 1 3
const mediump int INSET = 0x10; // 1 4
void main(void)
{
lowp
[Touch-packages] [Bug 1460152] Re: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates)
** Changed in: snappy/15.04 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1460152 Title: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates) Status in Snappy: Fix Released Status in Snappy 15.04 series: Fix Released Status in apparmor package in Ubuntu: Fix Released Bug description: The apparmor cache gets confused easily on upgrade. Here is what happens: - boot stable, /etc/apparmor.d/cache/usr.bin.ubuntu-core-launcher is mtime of now because we generate the cache on boot - upgrade to edge, /etc/apparmor.d/usr.bin.ubuntu-core-launcher is updated and has the mtime of T (yesterday) when the file was put into the package - on the next reboot the apparmor_parser compares the mtime of the cache/usr.bin.ubuntu-core-launcher (very very recent) with the mtime of the souce usr.bin.ubuntu-core-launcher (much older) - cache does is *not* re-generate Possible solution: - clear cache on upgrade - make apparmor_parser store mtime of the source file in the header - make apparmor_parser use set the cache file to the mtime of the source file used to generate the cache and re-generate if those get out-of-sync Original description: -- Rick Spencer ran into the situation that he ended up with a snappy image that gave the following error: apparmor=DENIED operation=mkdir profile=/usr/bin/ubuntu-core-launcher name=/tmp/snap.0_pastebinit.mvo_em33Zz/ pid=1092 comm=ubuntu-core-lau requested_mask=c denied_mask=c fsuid=0 ouid=0 Running: $ sudo apparmor_parser --skip-cache -r /etc/apparmor.d/usr.bin.ubuntu-core-launcher fixes it. This strongly indicates that the cache has the old content and did not get re-generated on upgrade or image build. I also managed to reproduce this via: 15.04/stable-15.04/edge The image is here: https://drive.google.com/open?id=0B1sb5ymdUGiLa0tUR0pGV3lzR1kauthuser=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1460152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460152] Re: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates)
** Changed in: snappy/15.04 Status: Fix Released = Fix Committed ** Changed in: snappy/15.04 Milestone: 15.04.1 = 15.04.2 ** Changed in: snappy Status: Fix Committed = Fix Released ** Changed in: apparmor (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1460152 Title: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates) Status in Snappy Ubuntu: Fix Released Status in Snappy 15.04 series: Fix Committed Status in apparmor package in Ubuntu: Fix Released Bug description: The apparmor cache gets confused easily on upgrade. Here is what happens: - boot stable, /etc/apparmor.d/cache/usr.bin.ubuntu-core-launcher is mtime of now because we generate the cache on boot - upgrade to edge, /etc/apparmor.d/usr.bin.ubuntu-core-launcher is updated and has the mtime of T (yesterday) when the file was put into the package - on the next reboot the apparmor_parser compares the mtime of the cache/usr.bin.ubuntu-core-launcher (very very recent) with the mtime of the souce usr.bin.ubuntu-core-launcher (much older) - cache does is *not* re-generate Possible solution: - clear cache on upgrade - make apparmor_parser store mtime of the source file in the header - make apparmor_parser use set the cache file to the mtime of the source file used to generate the cache and re-generate if those get out-of-sync Original description: -- Rick Spencer ran into the situation that he ended up with a snappy image that gave the following error: apparmor=DENIED operation=mkdir profile=/usr/bin/ubuntu-core-launcher name=/tmp/snap.0_pastebinit.mvo_em33Zz/ pid=1092 comm=ubuntu-core-lau requested_mask=c denied_mask=c fsuid=0 ouid=0 Running: $ sudo apparmor_parser --skip-cache -r /etc/apparmor.d/usr.bin.ubuntu-core-launcher fixes it. This strongly indicates that the cache has the old content and did not get re-generated on upgrade or image build. I also managed to reproduce this via: 15.04/stable-15.04/edge The image is here: https://drive.google.com/open?id=0B1sb5ymdUGiLa0tUR0pGV3lzR1kauthuser=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1460152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1458681] Re: [gst-hybris] FTBFS in wily/vivid (armhf/i386)
On Mon, Jun 15, 2015 at 11:56 AM, Iain Lane i...@orangesquash.org.uk wrote: Requires: mirclient on data/ubuntu-platform-api.pc.in is needed on the platform-api side I think gst-plugins-bad1.0 needs updating to use platform-api's CFLAGS and LIBS from pkg-config. Right, that once we're able to build platform-api again :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to platform-api in Ubuntu. https://bugs.launchpad.net/bugs/1458681 Title: [gst-hybris] FTBFS in wily/vivid (armhf/i386) Status in gst-plugins-bad1.0 package in Ubuntu: New Status in platform-api package in Ubuntu: New Bug description: When building gst-plugins-bad1.0 1.4.5-1ubuntu3 ... /bin/bash ../../libtool --tag=CC --tag=disable-static --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -D_FORTIFY_SOURCE=2 -I../../gst-libs -I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DGST_USE_UNSTABLE_API -DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Wno-multichar -Wnested-externs -g-I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I /usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/libusb-1.0 -DGST_USE_UNSTABLE_API -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-error -c -o libgstuvch264_la-gstuvch264_mjpgdemux.lo `test -f 'gstuvch264_mjpgdemux.c' || echo './'`gstuvch264_mjpgdemux.c /bin/bash ../../libtool --tag=CC --tag=disable-static --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -D_FORTIFY_SOURCE=2 -I../../gst-libs -I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DGST_USE_UNSTABLE_API -DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Wno-multichar -Wnested-externs -g-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-error -c -o libgstdvb_la-gstdvbsrc.lo `test -f 'gstdvbsrc.c' || echo './'`gstdvbsrc.c /bin/bash ../../libtool --tag=CC --tag=disable-static --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -D_FORTIFY_SOURCE=2 -I../../gst-libs -I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DGST_USE_UNSTABLE_API -DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Wno-multichar -Wnested-externs -g-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-error -c -o libgstdvb_la-dvbbasebin.lo `test -f 'dvbbasebin.c' || echo './'`dvbbasebin.c In file included from /usr/include/ubuntu/application/ui/window.h:31:0, from gstamc.h:35, from gstamchybris.c:27: /usr/include/ubuntu/application/instance.h:28:44: fatal error: mir_toolkit/mir_client_library.h: No such file or directory #include mir_toolkit/mir_client_library.h ^ compilation terminated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1458681/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store
Basically we need to change pulseaudio in a way it can ask trusty store for the right permission when starting the recording process. Please ping tvoss to know more about how that can be done at the trust-store level, since there are some examples in the trust-store project. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1224756 Title: Pulseaudio should integrate with trust-store Status in the base for Ubuntu mobile products: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Currently the 'audio' policy group allows access to pulseaudio which allows apps to use the microphone and eavesdrop on the user. Pulseaudio needs to be modified to use trust-store, like location- service does. Integrating with trust-store means that when an app tries use the microphone via pulseaudio, pulseaudio will contact trust-store, the trust-store will prompt the user (Foo wants to use the microphone. Is this ok? Yes|No), optionally cache the result and return the result to pulseaudio. In this manner the user is given a contextual prompt at the time of access by the app. Using caching this decision can be remembered the next time. If caching is used, there should be a method to change the decision in settings. Targeting to T-Series for now, since the trust-store is not in a reusable form yet. Original description: David and the security team (inspired by an observation from Rick) discussed that when recording, pulseaudio should somehow unobtrusively show the user that it is recording. The easiest thing to do would be for pulseaudio to alert indicator-sound which would then turn its icon red (similar to indicator-message turning blue with new messages). Marking 'high' because apps with access to pulseaudio can currently eavedrop on users. If the app is allowed to do networking (the default for apps), then it can ship that information off to a server somewhere. Note 1, the alert to indicator-sound must happen via the out of process pulseaudio server and not the confined app itself to be effective. Note 2, we should consider how to enforce this for foreground apps only. Application lifecycle should probably handle this for 13.10 (apps are suspended if not in foreground or if the screensaver is on), but we don't want an app on the converged device to record in the background when the user isn't paying attention. Example eavesdropping attack: start recording only when the screensaver is on (perhaps inhibiting the screensaver during recording would be enough). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1224756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450642] Re: seccomp missing many new syscalls
** Changed in: snappy/15.04 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1450642 Title: seccomp missing many new syscalls Status in Snappy Ubuntu: Fix Released Status in Snappy 15.04 series: Fix Released Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Vivid: Fix Released Status in libseccomp source package in Wily: Fix Released Bug description: [Impact] Several syscalls were discovered to be missing when using the launcher on snappy. These should be added so we may properly support seccomp filtering. [Test Case] seccomp itself has a comprehensive testsuite, and while it doesn't fail the build, regressions can be seen by looking at the build log. Eg: Regression Test Summary tests run: 6494 tests skipped: 52 tests passed: 6494 tests failed: 0 tests errored: 0 Furthermore, on a snappy system, perform: $ sudo snappy install hello-world $ hello-world.env It should show the environment. On an arm system with 2.1.1-1 from the archive, this will fail due to a seccomp denial: audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 pid=1491 comm=env exe=/bin/bash sig=31 arch=4028 syscall=983045 compat=0 ip=0xb6fb0bd6 code=0x0 (note, snappy images have a ppa fix for this, see notes below). To test the segfault fix, do: $ scmp_sys_resolver 1024 Segmentation fault It should return: $ scmp_sys_resolver 1024 UNKNOWN For the new 3.19 syscalls: $ scmp_sys_resolver getrandom -1 it should return something like (actual number depends on arch, this is on armhf): $ scmp_sys_resolver getrandom 384 autopkgtests for libseccomp have been added as part of this update to verify that the library recognizes all the syscalls from 3.19 and the private syscalls. These tests can be run like so (assuming you are in the unpacked source and the binaries are in ../binary): $ export REL=vivid $ adt-run `for i in ../binary/*.deb ; do echo -n -B $i ; done` --source ../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot autopkgtest-$REL-amd64 || echo ** AUTOPKGTESTS FAILED Alternatively, if you don't have autopkgtest setup, you can do: $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp $ export ADTTMP=/tmp/foo ; mkdir -p $ADTTMP ; sh ./debian/tests/test-filter ... PASS $ export ADTTMP=/tmp/foo ; mkdir -p $ADTTMP ; sh ./debian/tests/test-scmp_sys_resolver ... PASS Lastly, seccomp is used by lxc. lxc can be tested by using the test case as outlined in step 4 of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only. [Regression Potential] If the above tests, regression potential is considered low. Unknown syscalls will continue to be handled as before. Description of changes: add finit_module: https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15 sync the syscall table entries - 3.16 https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75 https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4 https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718 https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a sync the syscall table entries - 3.17 https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9 sync the syscall table entries - 3.19 https://github.com/seccomp/libseccomp/commit/7b80fb2fb683cafaf5dc9ff7692437ba86e598a3 This should also be applied (fix a segfault for invalid syscall numbers): https://github.com/seccomp/libseccomp/commit/2d09a74c7f04d29ae740db1e2187ff1a1886b2c3 In addition, add-missing-arm-private-syscalls.patch is add to add 5 private ARM syscalls. These are absolutely required on snappy. This portion of the patch has been well tested and is included by default in stable snappy images via the snappy image PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1450642/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460152] Re: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates)
** Changed in: snappy/15.04 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1460152 Title: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates) Status in Snappy Ubuntu: In Progress Status in Snappy 15.04 series: Fix Released Status in apparmor package in Ubuntu: New Bug description: The apparmor cache gets confused easily on upgrade. Here is what happens: - boot stable, /etc/apparmor.d/cache/usr.bin.ubuntu-core-launcher is mtime of now because we generate the cache on boot - upgrade to edge, /etc/apparmor.d/usr.bin.ubuntu-core-launcher is updated and has the mtime of T (yesterday) when the file was put into the package - on the next reboot the apparmor_parser compares the mtime of the cache/usr.bin.ubuntu-core-launcher (very very recent) with the mtime of the souce usr.bin.ubuntu-core-launcher (much older) - cache does is *not* re-generate Possible solution: - clear cache on upgrade - make apparmor_parser store mtime of the source file in the header - make apparmor_parser use set the cache file to the mtime of the source file used to generate the cache and re-generate if those get out-of-sync Original description: -- Rick Spencer ran into the situation that he ended up with a snappy image that gave the following error: apparmor=DENIED operation=mkdir profile=/usr/bin/ubuntu-core-launcher name=/tmp/snap.0_pastebinit.mvo_em33Zz/ pid=1092 comm=ubuntu-core-lau requested_mask=c denied_mask=c fsuid=0 ouid=0 Running: $ sudo apparmor_parser --skip-cache -r /etc/apparmor.d/usr.bin.ubuntu-core-launcher fixes it. This strongly indicates that the cache has the old content and did not get re-generated on upgrade or image build. I also managed to reproduce this via: 15.04/stable-15.04/edge The image is here: https://drive.google.com/open?id=0B1sb5ymdUGiLa0tUR0pGV3lzR1kauthuser=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1460152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460152] Re: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates)
Let's land on wily, test and then make push to our PPA (so we can also test it there, and also revert the workaround), we can include this at our next stable release :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1460152 Title: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates) Status in Snappy Ubuntu: In Progress Status in Snappy 15.04 series: Fix Released Status in apparmor package in Ubuntu: New Bug description: The apparmor cache gets confused easily on upgrade. Here is what happens: - boot stable, /etc/apparmor.d/cache/usr.bin.ubuntu-core-launcher is mtime of now because we generate the cache on boot - upgrade to edge, /etc/apparmor.d/usr.bin.ubuntu-core-launcher is updated and has the mtime of T (yesterday) when the file was put into the package - on the next reboot the apparmor_parser compares the mtime of the cache/usr.bin.ubuntu-core-launcher (very very recent) with the mtime of the souce usr.bin.ubuntu-core-launcher (much older) - cache does is *not* re-generate Possible solution: - clear cache on upgrade - make apparmor_parser store mtime of the source file in the header - make apparmor_parser use set the cache file to the mtime of the source file used to generate the cache and re-generate if those get out-of-sync Original description: -- Rick Spencer ran into the situation that he ended up with a snappy image that gave the following error: apparmor=DENIED operation=mkdir profile=/usr/bin/ubuntu-core-launcher name=/tmp/snap.0_pastebinit.mvo_em33Zz/ pid=1092 comm=ubuntu-core-lau requested_mask=c denied_mask=c fsuid=0 ouid=0 Running: $ sudo apparmor_parser --skip-cache -r /etc/apparmor.d/usr.bin.ubuntu-core-launcher fixes it. This strongly indicates that the cache has the old content and did not get re-generated on upgrade or image build. I also managed to reproduce this via: 15.04/stable-15.04/edge The image is here: https://drive.google.com/open?id=0B1sb5ymdUGiLa0tUR0pGV3lzR1kauthuser=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1460152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460152] Re: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates)
** Changed in: snappy Assignee: (unassigned) = Michael Vogt (mvo) ** Changed in: snappy/15.04 Assignee: (unassigned) = Michael Vogt (mvo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1460152 Title: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable - 15.04/edge updates) Status in Snappy Ubuntu: In Progress Status in Snappy 15.04 series: In Progress Status in apparmor package in Ubuntu: New Bug description: The apparmor cache gets confused easily on upgrade. Here is what happens: - boot stable, /etc/apparmor.d/cache/usr.bin.ubuntu-core-launcher is mtime of now because we generate the cache on boot - upgrade to edge, /etc/apparmor.d/usr.bin.ubuntu-core-launcher is updated and has the mtime of T (yesterday) when the file was put into the package - on the next reboot the apparmor_parser compares the mtime of the cache/usr.bin.ubuntu-core-launcher (very very recent) with the mtime of the souce usr.bin.ubuntu-core-launcher (much older) - cache does is *not* re-generate Possible solution: - clear cache on upgrade - make apparmor_parser store mtime of the source file in the header - make apparmor_parser use set the cache file to the mtime of the source file used to generate the cache and re-generate if those get out-of-sync Original description: -- Rick Spencer ran into the situation that he ended up with a snappy image that gave the following error: apparmor=DENIED operation=mkdir profile=/usr/bin/ubuntu-core-launcher name=/tmp/snap.0_pastebinit.mvo_em33Zz/ pid=1092 comm=ubuntu-core-lau requested_mask=c denied_mask=c fsuid=0 ouid=0 Running: $ sudo apparmor_parser --skip-cache -r /etc/apparmor.d/usr.bin.ubuntu-core-launcher fixes it. This strongly indicates that the cache has the old content and did not get re-generated on upgrade or image build. I also managed to reproduce this via: 15.04/stable-15.04/edge The image is here: https://drive.google.com/open?id=0B1sb5ymdUGiLa0tUR0pGV3lzR1kauthuser=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1460152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450642] Re: seccomp missing many new syscalls
** Also affects: snappy/15.04 Importance: Undecided Status: New ** Changed in: snappy/15.04 Milestone: None = 15.04.1 ** Changed in: snappy/15.04 Assignee: (unassigned) = Jamie Strandboge (jdstrand) ** Changed in: snappy/15.04 Status: New = Fix Committed ** Changed in: snappy Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1450642 Title: seccomp missing many new syscalls Status in Snappy Ubuntu: Fix Released Status in Snappy 15.04 series: Fix Committed Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Vivid: Fix Released Status in libseccomp source package in Wily: Fix Released Bug description: [Impact] Several syscalls were discovered to be missing when using the launcher on snappy. These should be added so we may properly support seccomp filtering. [Test Case] seccomp itself has a comprehensive testsuite, and while it doesn't fail the build, regressions can be seen by looking at the build log. Eg: Regression Test Summary tests run: 6494 tests skipped: 52 tests passed: 6494 tests failed: 0 tests errored: 0 Furthermore, on a snappy system, perform: $ sudo snappy install hello-world $ hello-world.env It should show the environment. On an arm system with 2.1.1-1 from the archive, this will fail due to a seccomp denial: audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 pid=1491 comm=env exe=/bin/bash sig=31 arch=4028 syscall=983045 compat=0 ip=0xb6fb0bd6 code=0x0 (note, snappy images have a ppa fix for this, see notes below). To test the segfault fix, do: $ scmp_sys_resolver 1024 Segmentation fault It should return: $ scmp_sys_resolver 1024 UNKNOWN For the new 3.19 syscalls: $ scmp_sys_resolver getrandom -1 it should return something like (actual number depends on arch, this is on armhf): $ scmp_sys_resolver getrandom 384 autopkgtests for libseccomp have been added as part of this update to verify that the library recognizes all the syscalls from 3.19 and the private syscalls. These tests can be run like so (assuming you are in the unpacked source and the binaries are in ../binary): $ export REL=vivid $ adt-run `for i in ../binary/*.deb ; do echo -n -B $i ; done` --source ../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot autopkgtest-$REL-amd64 || echo ** AUTOPKGTESTS FAILED Alternatively, if you don't have autopkgtest setup, you can do: $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp $ export ADTTMP=/tmp/foo ; mkdir -p $ADTTMP ; sh ./debian/tests/test-filter ... PASS $ export ADTTMP=/tmp/foo ; mkdir -p $ADTTMP ; sh ./debian/tests/test-scmp_sys_resolver ... PASS Lastly, seccomp is used by lxc. lxc can be tested by using the test case as outlined in step 4 of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only. [Regression Potential] If the above tests, regression potential is considered low. Unknown syscalls will continue to be handled as before. Description of changes: add finit_module: https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15 sync the syscall table entries - 3.16 https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75 https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4 https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718 https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a sync the syscall table entries - 3.17 https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9 sync the syscall table entries - 3.19 https://github.com/seccomp/libseccomp/commit/7b80fb2fb683cafaf5dc9ff7692437ba86e598a3 This should also be applied (fix a segfault for invalid syscall numbers): https://github.com/seccomp/libseccomp/commit/2d09a74c7f04d29ae740db1e2187ff1a1886b2c3 In addition, add-missing-arm-private-syscalls.patch is add to add 5 private ARM syscalls. These are absolutely required on snappy. This portion of the patch has been well tested and is included by default in stable snappy images via the snappy image PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1450642/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434143] Re: boot script should run aa-profile-hook in addition to aa-clickhook
** Changed in: snappy Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1434143 Title: boot script should run aa-profile-hook in addition to aa-clickhook Status in Snappy Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Bug description: Summary says it all. aa-profile-hook does the same sort of thing as aa-clickhook and is used on snappy. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1434143/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1458680] Re: platform-api FTBFS in wily (2.9.0+15.04.20150326-0ubuntu1)
On Tue, May 26, 2015 at 2:56 PM, Robert Carr rac...@canonical.com wrote:
https://code.launchpad.net/~mir-team/platform-api/delete-
deprecations/+merge/254170 needed to land
Thanks.
Can we please coordinate such landings next time we change something
on mir that breaks the reverse build-deps?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1458680
Title:
platform-api FTBFS in wily (2.9.0+15.04.20150326-0ubuntu1)
Status in platform-api package in Ubuntu:
New
Bug description:
sbuild -A --dist=wily --arch=i386 -c wily-proposed-i386-sbuild
platform-api_2.9.0+15.04.20150326-0ubuntu1.dsc
[ 26%] Building CXX object
src/ubuntu/application/common/mircommon/CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o
cd
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/src/ubuntu/application/common/mircommon
/usr/bin/i686-linux-gnu-g++-4.9-g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2 -fvisibility=hidden -fPIC
--std=c++11 -I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/include
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/android/include
-I/usr/include/mirclient -I/usr/include/mircommon
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/include
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/../../bridge
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common
-o CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o -c
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:
In function 'bool ubuntu::application::ui::mir::event_to_ubuntu_event(const
MirEvent*, WindowEvent)':
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:28:22:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
switch (mir_event-type)
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward
declaration of 'const MirEvent {aka const union MirEvent}'
typedef union MirEvent MirEvent;
^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:32:44:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
ubuntu_ev.key.device_id = mir_event-key.device_id;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward
declaration of 'const MirEvent {aka const union MirEvent}'
typedef union MirEvent MirEvent;
^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:33:44:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
ubuntu_ev.key.source_id = mir_event-key.source_id;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward
declaration of 'const MirEvent {aka const union MirEvent}'
typedef union MirEvent MirEvent;
^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:34:41:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
ubuntu_ev.key.action = mir_event-key.action;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
[Touch-packages] [Bug 1458681] [NEW] [gst-hybris] FTBFS in wily/vivid (armhf/i386)
Public bug reported: When building gst-plugins-bad1.0 1.4.5-1ubuntu3 ... /bin/bash ../../libtool --tag=CC --tag=disable-static --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -D_FORTIFY_SOURCE=2 -I../../gst-libs -I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DGST_USE_UNSTABLE_API -DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Wno-multichar -Wnested-externs -g-I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/u sr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/libusb-1.0 -DGST_USE_UNSTABLE_API -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-error -c -o libgstuvch264_la-gstuvch264_mjpgdemux.lo `test -f 'gstuvch264_mjpgdemux.c' || echo './'`gstuvch264_mjpgdemux.c /bin/bash ../../libtool --tag=CC --tag=disable-static --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -D_FORTIFY_SOURCE=2 -I../../gst-libs -I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DGST_USE_UNSTABLE_API -DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Wno-multichar -Wnested-externs -g-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-error -c -o libgstdvb_la-gstdvbsrc.lo `test -f 'gstdvbsrc.c' || echo './'`gstdvbsrc.c /bin/bash ../../libtool --tag=CC --tag=disable-static --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -D_FORTIFY_SOURCE=2 -I../../gst-libs -I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DGST_USE_UNSTABLE_API -DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Wno-multichar -Wnested-externs -g-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-error -c -o libgstdvb_la-dvbbasebin.lo `test -f 'dvbbasebin.c' || echo './'`dvbbasebin.c In file included from /usr/include/ubuntu/application/ui/window.h:31:0, from gstamc.h:35, from gstamchybris.c:27: /usr/include/ubuntu/application/instance.h:28:44: fatal error: mir_toolkit/mir_client_library.h: No such file or directory #include mir_toolkit/mir_client_library.h ^ compilation terminated. ** Affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: platform-api (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1458681 Title: [gst-hybris] FTBFS in wily/vivid (armhf/i386) Status in gst-plugins-bad1.0 package in Ubuntu: New Status in platform-api package in Ubuntu: New Bug description: When building gst-plugins-bad1.0 1.4.5-1ubuntu3 ... /bin/bash ../../libtool --tag=CC --tag=disable-static --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -D_FORTIFY_SOURCE=2 -I../../gst-libs -I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DGST_USE_UNSTABLE_API -DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Wno-multichar -Wnested-externs -g-I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I
[Touch-packages] [Bug 1458681] Re: [gst-hybris] FTBFS in wily/vivid (armhf/i386)
gst-plugins-bad doesn't use mir directly, and the mir_toolkit header gets included because of platform-api. I believe the right fix would be for platform-api to export the right include path as part of the pc file that it exports. ** Also affects: platform-api (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1458681 Title: [gst-hybris] FTBFS in wily/vivid (armhf/i386) Status in gst-plugins-bad1.0 package in Ubuntu: New Status in platform-api package in Ubuntu: New Bug description: When building gst-plugins-bad1.0 1.4.5-1ubuntu3 ... /bin/bash ../../libtool --tag=CC --tag=disable-static --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -D_FORTIFY_SOURCE=2 -I../../gst-libs -I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DGST_USE_UNSTABLE_API -DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Wno-multichar -Wnested-externs -g-I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I /usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/libusb-1.0 -DGST_USE_UNSTABLE_API -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-error -c -o libgstuvch264_la-gstuvch264_mjpgdemux.lo `test -f 'gstuvch264_mjpgdemux.c' || echo './'`gstuvch264_mjpgdemux.c /bin/bash ../../libtool --tag=CC --tag=disable-static --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -D_FORTIFY_SOURCE=2 -I../../gst-libs -I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DGST_USE_UNSTABLE_API -DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Wno-multichar -Wnested-externs -g-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-error -c -o libgstdvb_la-gstdvbsrc.lo `test -f 'gstdvbsrc.c' || echo './'`gstdvbsrc.c /bin/bash ../../libtool --tag=CC --tag=disable-static --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -D_FORTIFY_SOURCE=2 -I../../gst-libs -I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DGST_USE_UNSTABLE_API -DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Wno-multichar -Wnested-externs -g-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-error -c -o libgstdvb_la-dvbbasebin.lo `test -f 'dvbbasebin.c' || echo './'`dvbbasebin.c In file included from /usr/include/ubuntu/application/ui/window.h:31:0, from gstamc.h:35, from gstamchybris.c:27: /usr/include/ubuntu/application/instance.h:28:44: fatal error: mir_toolkit/mir_client_library.h: No such file or directory #include mir_toolkit/mir_client_library.h ^ compilation terminated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1458681/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452386] Re: [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32m color format.
Tried to land this fix but then got blocked by bug 1458681 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1452386 Title: [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32m color format. Status in gst-plugins-bad1.0 package in Ubuntu: In Progress Status in gst-plugins-bad1.0 package in Ubuntu RTM: New Bug description: COLOR_QCOM_FormatYVU420SemiPlanar32m is essentially GST_VIDEO_FORMAT_NV12, but with stride and plane heights aligned to 32. Adding support is as simple as adding android-gst color format mapping, and using same code as COLOR_QCOM_FormatYUV420SemiPlanar to handle software conversion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1452386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452386] Re: [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32m color format.
** Also affects: gst-plugins-bad1.0 (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1452386 Title: [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32m color format. Status in gst-plugins-bad1.0 package in Ubuntu: In Progress Status in gst-plugins-bad1.0 package in Ubuntu RTM: New Bug description: COLOR_QCOM_FormatYVU420SemiPlanar32m is essentially GST_VIDEO_FORMAT_NV12, but with stride and plane heights aligned to 32. Adding support is as simple as adding android-gst color format mapping, and using same code as COLOR_QCOM_FormatYUV420SemiPlanar to handle software conversion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1452386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458680] [NEW] platform-api FTBFS in wily (2.9.0+15.04.20150326-0ubuntu1)
Public bug reported:
sbuild -A --dist=wily --arch=i386 -c wily-proposed-i386-sbuild platform-
api_2.9.0+15.04.20150326-0ubuntu1.dsc
[ 26%] Building CXX object
src/ubuntu/application/common/mircommon/CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o
cd
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/src/ubuntu/application/common/mircommon
/usr/bin/i686-linux-gnu-g++-4.9-g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2 -fvisibility=hidden -fPIC
--std=c++11 -I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/include
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/android/include
-I/usr/include/mirclient -I/usr/include/mircommon
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/include
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/../../bridge
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common
-o CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o -c
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:
In function 'bool ubuntu::application::ui::mir::event_to_ubuntu_event(const
MirEvent*, WindowEvent)':
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:28:22:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
switch (mir_event-type)
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward
declaration of 'const MirEvent {aka const union MirEvent}'
typedef union MirEvent MirEvent;
^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:32:44:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
ubuntu_ev.key.device_id = mir_event-key.device_id;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward
declaration of 'const MirEvent {aka const union MirEvent}'
typedef union MirEvent MirEvent;
^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:33:44:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
ubuntu_ev.key.source_id = mir_event-key.source_id;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward
declaration of 'const MirEvent {aka const union MirEvent}'
typedef union MirEvent MirEvent;
^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:34:41:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
ubuntu_ev.key.action = mir_event-key.action;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward
declaration of 'const MirEvent {aka const union MirEvent}'
typedef union MirEvent MirEvent;
^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:35:40:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
ubuntu_ev.key.flags = mir_event-key.flags;
^
In file included from
[Touch-packages] [Bug 1453163] Re: [Ubuntu Phone BQ] Wrong brightness after a few minutes with Never sleep
*** This bug is a duplicate of bug 1437510 *** https://bugs.launchpad.net/bugs/1437510 ** This bug has been marked a duplicate of bug 1437510 Screen dim is not following the lock screen timeout (always dimming after 50 seconds) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1453163 Title: [Ubuntu Phone BQ] Wrong brightness after a few minutes with Never sleep Status in Ubuntu Touch System Settings: New Status in uNAV: New Status in indicator-network package in Ubuntu: Invalid Bug description: Hi! Steps: 1. Set in the Battery preferences: Sleep when idle = Never 2. Set in the Brightness preferences: Adjust automatically = Disabled 3. Set in the Brightness preferences: Display brightness bar = Max. brightness 4. Leave the mobile in a web BUG: After ~2' the brightness is changing to a lower brightness. This is annoying in special with the GPS application Here, when you're driving and you want the max brightness in the mobile all the time. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings/+bug/1453163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435088] Re: Crash of media-hub opening a .avi file
** Also affects: media-hub (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1435088 Title: Crash of media-hub opening a .avi file Status in the base for Ubuntu mobile products: Confirmed Status in Media Hub: Fix Committed Status in media-hub package in Ubuntu: Fix Released Status in mediaplayer-app package in Ubuntu: Fix Released Status in qtubuntu-media package in Ubuntu: Fix Released Status in media-hub package in Ubuntu RTM: New Bug description: I tried to open two .avi videos on BQ Aquaris E4.5 running Ubuntu Touch using the Media Player app: one simply prints Video format not supported while the second shows only a black screen. Then if I close the player I can't open any video and I get the error: Error playing video Fail to connect with playback backend. and trying to play some audio files simply doesn't do anything. I uploaded the second video here: http://uz.sns.it/~ilario/utouch-media-hub.avi ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: media-hub 2.0.0+15.04.20150120~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Sun Mar 22 23:32:09 2015 InstallationDate: Installed on 2015-03-12 (10 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150312-002053) SourcePackage: media-hub UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458689] [NEW] [vivid-overlay] input-stub.so fails to load on i386
Public bug reported: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 140 device name: generic_x86 channel: ubuntu-touch/rc-proposed/ubuntu last update: 2015-05-25 12:02:10 version version: 140 version ubuntu: 20150525 version device: 20150210 version custom: 20150525 When starting unity8: [1432591771.427440] Server: Starting [1432591771.427679] Loader: Loading modules from: /usr/lib/i386-linux-gnu/mir/server-platform [1432591771.427824] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so [1432591771.428143] WARNING Loader: Failed to load module: /usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij) [1432591771.428520] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so [1432591771.428875] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2 [1432591771.429008] mirplatform: Found graphics driver: dummy [1432591771.429180] mirplatform: Found graphics driver: android [1432591771.429324] Platform Loader: Selected driver: android (version 0.13.1) ** Affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1458689 Title: [vivid-overlay] input-stub.so fails to load on i386 Status in mir package in Ubuntu: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 140 device name: generic_x86 channel: ubuntu-touch/rc-proposed/ubuntu last update: 2015-05-25 12:02:10 version version: 140 version ubuntu: 20150525 version device: 20150210 version custom: 20150525 When starting unity8: [1432591771.427440] Server: Starting [1432591771.427679] Loader: Loading modules from: /usr/lib/i386-linux-gnu/mir/server-platform [1432591771.427824] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so [1432591771.428143] WARNING Loader: Failed to load module: /usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij) [1432591771.428520] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so [1432591771.428875] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2 [1432591771.429008] mirplatform: Found graphics driver: dummy [1432591771.429180] mirplatform: Found graphics driver: android [1432591771.429324] Platform Loader: Selected driver: android (version 0.13.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1458689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458043] Re: can't connect to adb in emulator and swipe doesn't appear to work
Adb issue fixed in wily, the other issues are bug 1458689 and bug
1458694.
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
** Package changed: goget-ubuntu-touch (Ubuntu) = lxc-android-config
(Ubuntu RTM)
** Changed in: lxc-android-config (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1458043
Title:
can't connect to adb in emulator and swipe doesn't appear to work
Status in lxc-android-config package in Ubuntu:
Fix Released
Status in lxc-android-config package in Ubuntu RTM:
New
Bug description:
On vivid with:
ubuntu-emulator 0.21-1+173~ubuntu15.04.1build1
ubuntu-emulator-runtime 20141117-0039-0ubuntu11
I generated an image like so:
$ sudo ubuntu-emulator create --channel=ubuntu-touch/devel-proposed/ubuntu
--arch=i386 devel-proposed.x86
and started with:
$ ubuntu-emulator run --scale=0.75 devel-proposed.x86
then I see a lot of output, but some of it doesn't look right:
[4.944791] init: ureadahead-touch main process (469) terminated with
status 5
[ 12.865870] init: /dev/hw_random not found
[ 12.865870] init: cannot open '/initlogo.rle'
[ 12.887030] init: /dev/hw_random not found
[ 12.945132] init: cannot find '/system/etc/install-recovery.sh', disabling
'flash_recovery'
[ 12.945132] init: cannot find '/system/bin/ubuntuappmanager.disabled',
disabling 'ubuntuappmanager'
[ 12.945132] init: property 'sys.powerctl' doesn't exist while expanding
'${sys.powerctl}'
[ 12.945132] init: powerctl: cannot expand '${sys.powerctl}'
[ 12.945132] init: property 'sys.sysctl.extra_free_kbytes' doesn't exist
while expanding '${sys.sysctl.extra_free_kbytes}'
[ 12.945132] init: cannot expand '${sys.sysctl.extra_free_kbytes}' while
writing to '/proc/sys/vm/extra_free_kbytes'
[ 12.945132] init: cannot find '/sbin/adbd', disabling 'adbd'
[ 12.945132] init: property 'persist.sys.usb.config' doesn't exist while
expanding '${persist.sys.usb.config}'
[ 12.945132] init: cannot expand '${persist.sys.usb.config}' while
assigning to 'sys.usb.config'
* Setting up X socket directories...[ OK
]
/lib/init/init-d-script: 12: /etc/rc2.d/S02whoopsie: -c: not found
basename: missing operand
Try 'basename --help' for more information.
* Starting virtual private network daemon(s)...
[ 47.445560] systemd-logind[1146]: Failed to start user service: Unknown
unit: user@32011.service
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1458043/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458694] [NEW] [vivid-overlay] unity8 fails to start on the emulator
Public bug reported:
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 140
device name: generic_x86
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2015-05-25 12:02:10
version version: 140
version ubuntu: 20150525
version device: 20150210
version custom: 20150525
When starting unity8 (this started at image 136, probably when mir 0.13
landed):
phablet@ubuntu-phablet:~$ cat ./.cache/upstart/unity8.log
()
[1432595001.896139] mirplatform: Found graphics driver: dummy
[1432595001.898447] mirplatform: Found graphics driver: android
qtmir.mir: MirServer created
[1432595003.675225] Server: Starting
[1432595003.679331] Loader: Loading modules from:
/usr/lib/i386-linux-gnu/mir/server-platform
[1432595003.679501] Loader: Loading module:
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
[1432595003.680673] Loader: Loading module:
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
[1432595003.681107] WARNING Loader: Failed to load module:
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
[1432595003.684868] Loader: Loading module:
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
[1432595003.685014] mirplatform: Found graphics driver: dummy
[1432595003.685211] mirplatform: Found graphics driver: android
[1432595003.685416] Platform Loader: Selected driver: android (version 0.13.0)
qtmir.mir: PromptSessionListener::PromptSessionListener - this=
PromptSessionListener(0x9679764)
qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x9676d24)
qtmir.mir: MirShell::MirShell
[1432595003.883766] DisplayServer: Mir version 0.13.0
QtCompositor::setAllWindowsExposed true
qtmir.clipboard: D-Bus registration successful.
Mode argument was not provided or was set to an illegal value. Using default
value of --mode= full-greeter
Cannot create window: no screens available
With version 135 it starts fine, but not fully functional, giving this
error:
QOpenGLShader::compile(Fragment): 0:2(12): warning: extension
`GL_OES_standard_derivatives' unsupported in fragment shader
0:2(1): error: #extension directive is not allowed in the middle of a shader
*** Problematic Fragment shader source code ***
#extension GL_OES_standard_derivatives : enable // Enable dFdy() on OpenGL ES
2.
#define lowp
#define mediump
#define highp
// Copyright © 2015 Canonical Ltd.
//
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU Lesser General Public License as published by
// the Free Software Foundation; version 3.
//
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU Lesser General Public License for more details.
//
// You should have received a copy of the GNU Lesser General Public License
// along with this program. If not, see http://www.gnu.org/licenses/.
//
// Author: Loïc Molinari loic.molin...@canonical.com
// Static flow control (branching on a uniform value) is fast on most GPUs
(including ultra-low
// power ones) because it allows to use the same shader execution path for an
entire draw call. We
// rely on that technique here (also known as uber-shader solution) to avoid
the complexity of
// dealing with a multiple shaders solution.
// FIXME(loicm) Validate GPU behavior with regards to static flow control.
uniform sampler2D shapeTexture;
uniform sampler2D sourceTexture;
uniform lowp vec2 dfdtFactors;
uniform lowp vec2 opacityFactors;
uniform lowp float sourceOpacity;
uniform lowp float distanceAA;
uniform bool textured;
uniform mediump int aspect;
varying mediump vec2 shapeCoord;
varying mediump vec4 sourceCoord;
varying lowp vec4 backgroundColor;
const mediump int FLAT = 0x08; // 1 3
const mediump int INSET = 0x10; // 1 4
void main(void)
{
lowp vec4 shapeData = texture2D(shapeTexture, shapeCoord);
lowp vec4 color = backgroundColor;
// FIXME(loicm) Would be better to use a bitfield but bitwise ops have only
been integrated in
// GLSL 1.3 (OpenGL 3) and GLSL ES 3 (OpenGL ES 3).
if (textured) {
// Blend the source over the current color.
// FIXME(loicm) sign() is far from optimal. Call texture2D() at
beginning of scope.
lowp vec2 axisMask = -sign((sourceCoord.zw * sourceCoord.zw) -
vec2(1.0));
lowp float mask = clamp(axisMask.x + axisMask.y, 0.0, 1.0);
lowp vec4 source = texture2D(sourceTexture, sourceCoord.st) *
vec4(sourceOpacity * mask);
color = vec4(1.0 - source.a) * color + source;
}
// Get screen-space derivative of texture coordinate t representing the
normalized distance
// between 2 pixels. dFd*() unfortunately have to be called outside of
branches in order to work
// correctly with VMware's
[Touch-packages] [Bug 1455107] Re: Creating and destroying SoundEffects causes crashes
** Also affects: qtmultimedia-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1455107 Title: Creating and destroying SoundEffects causes crashes Status in pulseaudio package in Ubuntu: Confirmed Status in qtmultimedia-opensource-src package in Ubuntu: New Bug description: I keep on receiving bug reports about Machines vs. Machines being crashy on Ubuntu Phones and I tracked it down to the SoundEffect item. When playing without sound effects enabled, the game seems very stable. To get to the bottom of this I created an app that simulates a bit how a game works with sound effects. It's a bit more aggressive than Machines-vs-Machines (still not really far fetched from a real game scenario) and reliably triggers some crashers in less than a minute here. So far I've seen crashes in creating SoundEffects items as well as removing them from the scene. Please find the example here: lp:~mzanetti/+junk/soundcrasher You should be able to run it on any vivid powered device by just opening the .pro file in QtCreator and hit the play button. The logs vary a lot between crashes. Sometimes I get some PulseAudio messages, sometimes it just crashes without any. Probably some raciness. Anyhow, this example app should be give the system a hard time and reveal most of the crashes eventually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1455107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378048] Re: Make music controls work in the sound indicator
Adding task for indicator-sound again as the new UX spec requires changes for the indicator as well. ** Changed in: indicator-sound (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1378048 Title: Make music controls work in the sound indicator Status in the base for Ubuntu mobile products: Confirmed Status in indicator-sound package in Ubuntu: Confirmed Status in media-hub package in Ubuntu: Confirmed Bug description: Steps: 1. Play an album in the music player 2. Pull down sound indicator 3. Click forward button Observed: the music does not advance Expected: the music advances To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1378048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452300] Re: Reboot takes too long
** Also affects: powerd (Ubuntu) Importance: Undecided Status: New ** Also affects: powerd (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1452300 Title: Reboot takes too long Status in the base for Ubuntu mobile products: New Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Status in powerd package in Ubuntu RTM: New Bug description: Test case. - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452300] Re: Reboot takes too long
** Description changed: Test case. + - Without usb cable connected - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1452300 Title: Reboot takes too long Status in the base for Ubuntu mobile products: New Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Status in powerd source package in Vivid: New Status in powerd package in Ubuntu RTM: New Bug description: Test case. - Make sure phone is not plugged in. - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452300] Re: Reboot takes too long
Problem is that we can only reproduce this issue without a usb cable, as that makes the kernel to acquire a wakelock. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1452300 Title: Reboot takes too long Status in the base for Ubuntu mobile products: New Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Status in powerd source package in Vivid: New Status in powerd package in Ubuntu RTM: New Bug description: Test case. - Make sure phone is not plugged in. - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425880] Re: location settings doesn't persist upon reboot
** Changed in: lxc-android-config (Ubuntu RTM) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1425880 Title: location settings doesn't persist upon reboot Status in the base for Ubuntu mobile products: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Status in lxc-android-config package in Ubuntu RTM: Fix Released Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-25 15:06:29 version version: 122 version ubuntu: 20150225 version device: 20150210-95b6a9f version custom: 20150225 Test Case 1. Open System-Settings = Security Privacy = Location Access 2. Select 'Not at all' option from the list to turn the location access off 3. Close the system settings and reboot the phone Verify that location settings changes are persistent after the boot Actual Result Location is enabled after reboot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Thu Feb 26 10:54:26 2015 InstallationDate: Installed on 2015-02-25 (1 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425880] Re: location settings doesn't persist upon reboot
** Also affects: lxc-android-config (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1425880 Title: location settings doesn't persist upon reboot Status in the base for Ubuntu mobile products: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Status in lxc-android-config package in Ubuntu RTM: New Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-25 15:06:29 version version: 122 version ubuntu: 20150225 version device: 20150210-95b6a9f version custom: 20150225 Test Case 1. Open System-Settings = Security Privacy = Location Access 2. Select 'Not at all' option from the list to turn the location access off 3. Close the system settings and reboot the phone Verify that location settings changes are persistent after the boot Actual Result Location is enabled after reboot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Thu Feb 26 10:54:26 2015 InstallationDate: Installed on 2015-02-25 (1 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1426923] Re: Allow ubuntu-system-settings to set a device's firmware
** Package changed: wpasupplicant (Ubuntu) = lxc-android-config (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1426923 Title: Allow ubuntu-system-settings to set a device's firmware Status in lxc-android-config package in Ubuntu: In Progress Bug description: Background: To do Wi-Fi hotspots on krillin, we need to poke wifi by doing a call to wpa_supplicant's (undocumented/local) SetInterfaceFirmware method. See [1] for details. Rationale: Ubuntu System Settings needs to do the same things as aforementioned script, but via dbus [2], as phablet/current non-privileged user and unconfined. What happens: If phablet runs [2], this error message [3] is produced, which I interpret to be equivalent with you're not welcome here. What should happen instead: Ubuntu System Settings should be able to make the call to wpa. [1] http://bazaar.launchpad.net/~mathieu-tl/+junk/touch-hotspot/view/head:/hotspot.py [2] gdbus call --system -d fi.w1.wpa_supplicant1 -o /fi/w1/wpa_supplicant1 -m fi.w1.wpa_supplicant1.SetInterfaceFirmware / ap [3] http://pastebin.ubuntu.com/10489519/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1426923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425880] Re: location settings doesn't persist upon reboot
** Changed in: canonical-devices-system-image Status: Confirmed = Fix Released ** Changed in: lxc-android-config (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1425880 Title: location settings doesn't persist upon reboot Status in the base for Ubuntu mobile products: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-25 15:06:29 version version: 122 version ubuntu: 20150225 version device: 20150210-95b6a9f version custom: 20150225 Test Case 1. Open System-Settings = Security Privacy = Location Access 2. Select 'Not at all' option from the list to turn the location access off 3. Close the system settings and reboot the phone Verify that location settings changes are persistent after the boot Actual Result Location is enabled after reboot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Thu Feb 26 10:54:26 2015 InstallationDate: Installed on 2015-02-25 (1 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449580] Re: [arale] photos taken by camera are corrupt
** Changed in: canonical-devices-system-image Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1449580 Title: [arale] photos taken by camera are corrupt Status in the base for Ubuntu mobile products: Fix Released Status in camera-app package in Ubuntu: Invalid Status in qtubuntu-camera package in Ubuntu: Invalid Bug description: This is arale specifc bug Took pictures with camera Go to photo roll Photo is black, spinner keeps spinning The photo is written to disk, but is corrupt when opening I am attaching photo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449580] Re: photos taken by camera are corrupt
I think this is basically the same issue we had with krillin, which I just pushed to arale. I already triggered a new build including this fix on the device side, so next image should have it. ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: camera-app (Ubuntu) Status: New = Invalid ** Changed in: qtubuntu-camera (Ubuntu) Status: New = Invalid ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Ricardo Salveti (rsalveti) ** Summary changed: - photos taken by camera are corrupt + [arale] photos taken by camera are corrupt ** Changed in: canonical-devices-system-image Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1449580 Title: [arale] photos taken by camera are corrupt Status in the base for Ubuntu mobile products: In Progress Status in camera-app package in Ubuntu: Invalid Status in qtubuntu-camera package in Ubuntu: Invalid Bug description: This is arale specifc bug Took pictures with camera Go to photo roll Photo is black, spinner keeps spinning The photo is written to disk, but is corrupt when opening I am attaching photo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449576] Re: embedded thumbnails not generated correctly
I think this is basically the same issue we had with krillin, which I just pushed to arale. I already triggered a new build including this fix on the device side, so next image should have it. ** Package changed: qtubuntu-camera (Ubuntu) = canonical-devices- system-image ** Changed in: canonical-devices-system-image Status: New = In Progress ** Summary changed: - embedded thumbnails not generated correctly + [arale] embedded thumbnails not generated correctly -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-camera in Ubuntu. https://bugs.launchpad.net/bugs/1449576 Title: [arale] embedded thumbnails not generated correctly Status in the base for Ubuntu mobile products: In Progress Bug description: This is arale only bug Open camera-app and take picture Go to photo roll Notice the thumbnails are not at the correct aspect ration use exiv2 to extract thumbnail out of jpeg and you can see the embedded thumbnail is not correct To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425880] Re: location settings doesn't persist upon reboot
** Package changed: location-service (Ubuntu) = lxc-android-config (Ubuntu) ** Changed in: lxc-android-config (Ubuntu) Assignee: Manuel de la Peña (mandel) = Ricardo Salveti (rsalveti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1425880 Title: location settings doesn't persist upon reboot Status in the base for Ubuntu mobile products: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-25 15:06:29 version version: 122 version ubuntu: 20150225 version device: 20150210-95b6a9f version custom: 20150225 Test Case 1. Open System-Settings = Security Privacy = Location Access 2. Select 'Not at all' option from the list to turn the location access off 3. Close the system settings and reboot the phone Verify that location settings changes are persistent after the boot Actual Result Location is enabled after reboot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Thu Feb 26 10:54:26 2015 InstallationDate: Installed on 2015-02-25 (1 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447606] [NEW] incoming call ringtone is not played repeatedly
Public bug reported: Mako/arale/krillin device, r196, ubuntu-touch/vivid-proposed Steps 1. Call the ubuntu phone from another phone 2. Don't answer it Expect Incoming call ringtone should be played repeatedly Result Ringtone is only played once. ** Affects: canonical-devices-system-image Importance: Critical Assignee: Bill Filler (bfiller) Status: Confirmed ** Affects: telephony-service (Ubuntu) Importance: Critical Assignee: Tiago Salem Herrmann (tiagosh) Status: Confirmed ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1447606 Title: incoming call ringtone is not played repeatedly Status in the base for Ubuntu mobile products: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: Mako/arale/krillin device, r196, ubuntu-touch/vivid-proposed Steps 1. Call the ubuntu phone from another phone 2. Don't answer it Expect Incoming call ringtone should be played repeatedly Result Ringtone is only played once. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447376] Re: obexd fails to stop
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1447376 Title: obexd fails to stop Status in the base for Ubuntu mobile products: New Status in ubuntu-touch-session package in Ubuntu: New Bug description: Current obexd job fails to stop/restart, as the upstart job is expecting daemon instead of fork. This affect the shutdown process. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425625] Re: Vivid image 121: Gps tag is permanently turn off on krillin when the custom tarball is installed
We landed a change in indicator-location that should help fixing this issue. Can you try reproducing again but using the channel ubuntu-touch /vivid-proposed-customized-here instead? ** Changed in: indicator-location (Ubuntu) Status: New = Incomplete ** Changed in: canonical-devices-system-image Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1425625 Title: Vivid image 121: Gps tag is permanently turn off on krillin when the custom tarball is installed Status in the base for Ubuntu mobile products: Incomplete Status in indicator-location package in Ubuntu: Incomplete Bug description: STEPS: 1. Install image 121 and install the krillin custom tarball 2. Boot the device and use the recommend here location check box in the location page 3. Drag down the location indicator 4. Enable gps 5. drag down the indicator 6. enable gps a second time 7. reboot the device once gps stays on 8. check the locations indicator again EXPECTED: I expect to see happen what happens on rtm ACTUAL: Gps is turned off on reboot, and doesn't function when enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442166] Re: Calendar alarms rings forever if Low Battery dialog visible
** Changed in: canonical-devices-system-image Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1442166 Title: Calendar alarms rings forever if Low Battery dialog visible Status in the base for Ubuntu mobile products: In Progress Status in indicator-datetime package in Ubuntu: Invalid Status in usensord package in Ubuntu: Confirmed Bug description: I'm on rtm build 258 on krillin Steps to reproduce: - let battery run down on phone (was sitting unplugged for 1 or 2 days) - in the morning, a calendar alarm starting ringing/vibrating and would not stop - when I looked at the phone, the screen was on and I see the Low Battery dialog - after dismissing the dialog, then I see the notification for the alarm, and only after 5-10 more seconds does the ringing stop Seems like while the Low Battery dialog is displayed it keeps the alarm ringing forever To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447376] [NEW] obexd fails to stop
Public bug reported: Current obexd job fails to stop/restart, as the upstart job is expecting daemon instead of fork. This affect the shutdown process. ** Affects: ubuntu-touch-session (Ubuntu) Importance: Undecided Status: New ** Description changed: Current obexd job fails to stop/restart, as the upstart job is expecting daemon instead of fork. + + This affect the shutdown process. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1447376 Title: obexd fails to stop Status in ubuntu-touch-session package in Ubuntu: New Bug description: Current obexd job fails to stop/restart, as the upstart job is expecting daemon instead of fork. This affect the shutdown process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-session/+bug/1447376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store
Please move this to ww21. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1224756 Title: Pulseaudio should integrate with trust-store Status in the base for Ubuntu mobile products: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Currently the 'audio' policy group allows access to pulseaudio which allows apps to use the microphone and eavesdrop on the user. Pulseaudio needs to be modified to use trust-store, like location- service does. Integrating with trust-store means that when an app tries use the microphone via pulseaudio, pulseaudio will contact trust-store, the trust-store will prompt the user (Foo wants to use the microphone. Is this ok? Yes|No), optionally cache the result and return the result to pulseaudio. In this manner the user is given a contextual prompt at the time of access by the app. Using caching this decision can be remembered the next time. If caching is used, there should be a method to change the decision in settings. Targeting to T-Series for now, since the trust-store is not in a reusable form yet. Original description: David and the security team (inspired by an observation from Rick) discussed that when recording, pulseaudio should somehow unobtrusively show the user that it is recording. The easiest thing to do would be for pulseaudio to alert indicator-sound which would then turn its icon red (similar to indicator-message turning blue with new messages). Marking 'high' because apps with access to pulseaudio can currently eavedrop on users. If the app is allowed to do networking (the default for apps), then it can ship that information off to a server somewhere. Note 1, the alert to indicator-sound must happen via the out of process pulseaudio server and not the confined app itself to be effective. Note 2, we should consider how to enforce this for foreground apps only. Application lifecycle should probably handle this for 13.10 (apps are suspended if not in foreground or if the screensaver is on), but we don't want an app on the converged device to record in the background when the user isn't paying attention. Example eavesdropping attack: start recording only when the screensaver is on (perhaps inhibiting the screensaver during recording would be enough). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1224756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445580] Re: Impossible to end a call after switching to airplane mode
** Changed in: canonical-devices-system-image Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1445580 Title: Impossible to end a call after switching to airplane mode Status in the base for Ubuntu mobile products: In Progress Status in dialer-app package in Ubuntu: Incomplete Status in indicator-network package in Ubuntu: New Status in ofono package in Ubuntu: Fix Committed Bug description: As I described here https://lists.launchpad.net/ubuntu-phone/msg12177.html I accidentally switched the phone to the airplane mode while having an active incoming call. As a result it is impossible to end a call - the red button does not end the call. The bug is easy to reproduce: 1. Make a call to your Ubuntu phone and answer it. 2. Switch on 'airplane mode' 3. As a result you get unusable phone. Of course switching gsm off while having an active call is not a typical use of the phone, but still the phone should react to this situation differently. Another thing is that I somehow switched gsm off while holding my phone to my ear (which may suggest some issue with the top panel) - but I don't know how to reproduce this, hence currently I treat this as an very unfortunate accident. Workaround for ending the call: make another incoming call to your phone. BQ (r21) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445080] Re: Cellular data not activated after exiting flight mode
Yup, modem is online just fine, the side effect is the same described by Alfonso (and you at comment #5). Modem is online, powered and attached, without any active context. current build number: 179 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2010-01-01 01:29:38 version version: 179 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1445080 Title: Cellular data not activated after exiting flight mode Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: Cellular data is not activated in ~50% of the cases in arale after setting then unsetting flight mode. I obtained the attached log this way: 1. Disabled wifi (to have less noise) and removed syslog (to make smaller the attached one) 2. Reboot 3. See cellular data is on: route is right, I have network access 4. Set flight mode 5. Unset flight mode 6. Data is not restored even after waiting for a few minutes. ccmni0 interface is down. list-modems shows that the modem is data-attached list-contexts output shows that no IP context has been activated Doing usr/share/ofono/scripts/activate-context 1 sudo ip route add default dev ccmni0 ping 8.8.8.8 works and I receive the ping responses. $ system-image-cli -i current build number: 12 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-16 08:06:39 version version: 12 version ubuntu: 20150416.0 version device: a17b9320788e7215ddf123544a3a2b5a4fa61f0d5add83f393866e8c7a9155b0 version custom: 20150416.0 + NetworkManager 0.9.10.0-4ubuntu15~mtrudel1 (silo 29 atm) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437633] Re: Choosing not to report crashes and errors setting reverts
About patch in comment #8, a few things: 1 - Nothing provides /etc/whoopsie, who should be creating it? 2 - Disabling works fine, but enabling doesn't work: 2.1 - Whoopsie is not started when enabling 'app crashes and errors' 2.2 - Even after reboot, there is still a 'manual' entry at /etc/init/whoopsie.override -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1437633 Title: Choosing not to report crashes and errors setting reverts Status in the base for Ubuntu mobile products: Fix Released Status in lxc-android-config package in Ubuntu: Confirmed Status in whoopsie package in Ubuntu: Invalid Status in lxc-android-config package in Ubuntu RTM: Confirmed Bug description: Possibly related to bug 1389407 Reported on Askubuntu [1] and confirmed here on a retail bq handset with no modifications (no app installs, only OTA updates). Steps to reproduce:- System Settings - Security Privacy - Diagnostics - Untick box next to App crashes and errors Leave system settings. Wait some time - the AU report suggests an hour, I waited less than that Go back into System Settings - Security Privacy - Diagnostics Not the tick box is ticked again. I would expect the tickbox to remain at whatever I set it to. [1] http://askubuntu.com/questions/602365/permanently-disable-error- reports-on-aquaris-e4-5-ubuntu-edition To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1437633/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445080] Re: Cellular data not activated after exiting flight mode
Just tested again and was again able to reproduce on mako:
phablet@ubuntu-phablet:/usr/share/ofono/scripts$ ./list-modems
[ /ril_0 ]
Revision = M9615A-CEFWMAZM-2.0.1700.98
Serial = 353918052313257
Online = 1
Type = hardware
Features = ussd net gprs sms rat sim
Emergency = 0
Model = Fake Modem Model
Lockdown = 0
Powered = 1
Interfaces = org.ofono.CallBarring org.ofono.CallSettings
org.ofono.SupplementaryServices org.ofono.NetworkRegistration
org.ofono.ConnectionManager org.ofono.Phonebook org.ofono.CallForwarding
org.ofono.SmartMessaging org.ofono.PushNotification org.ofono.MessageManager
org.ofono.NetworkTime org.ofono.MessageWaiting org.ofono.RadioSettings
org.ofono.SimManager org.ofono.CallVolume org.ofono.VoiceCallManager
Manufacturer = Fake Manufacturer
[ org.ofono.CallBarring ]
VoiceIncoming = disabled
VoiceOutgoing = disabled
[ org.ofono.CallSettings ]
CallingLineRestriction = off
CalledLinePresentation = disabled
CallingLinePresentation = enabled
HideCallerId = default
ConnectedLineRestriction = unknown
ConnectedLinePresentation = unknown
VoiceCallWaiting = enabled
CallingNamePresentation = unknown
[ org.ofono.SupplementaryServices ]
State = idle
[ org.ofono.NetworkRegistration ]
CellId = 3198203
Technology = umts
MobileCountryCode = 724
LocationAreaCode = 40248
Status = registered
MobileNetworkCode = 06
Mode = auto
Name = VIVO
Strength = 45
[ org.ofono.ConnectionManager ]
Attached = 1
Powered = 1
RoamingAllowed = 0
Bearer = hspa
Suspended = 0
[ org.ofono.Phonebook ]
[ org.ofono.CallForwarding ]
ForwardingFlagOnSim = 0
VoiceNoReplyTimeout = 30
VoiceNoReply = +550174891818716
VoiceUnconditional =
VoiceBusy = +550174891818716
VoiceNotReachable = +550174891818716
[ org.ofono.SmartMessaging ]
[ org.ofono.PushNotification ]
[ org.ofono.MessageManager ]
ServiceCenterAddress = +550112102010
Alphabet = default
Bearer = cs-preferred
UseDeliveryReports = 0
[ org.ofono.NetworkTime ]
[ org.ofono.MessageWaiting ]
VoicemailMailboxNumber = *555
VoicemailMessageCount = 0
VoicemailWaiting = 1
[ org.ofono.RadioSettings ]
TechnologyPreference = umts
FastDormancy = 0
ModemTechnologies = gsm umts
[ org.ofono.SimManager ]
BarredDialing = 0
CardIdentifier = 89551090318161348308
FixedDialing = 0
MobileNetworkCode = 06
Retries =
LockedPins =
SubscriberIdentity = 724064900113482
PinRequired = none
MobileCountryCode = 724
ServiceNumbers = [Policia] = '190' [Defesa Civil] = '199' [Bombeiros] =
'193' [Vivo no Mundo] = '+551139598262' [Vivo] = '*8486' [Ambulancia] = '192'
SubscriberNumbers = +554891818716
Present = 1
PreferredLanguages = pt es en
[ org.ofono.CallVolume ]
SpeakerVolume = 0
MicrophoneVolume = 0
Muted = 1
[ org.ofono.VoiceCallManager ]
EmergencyNumbers = 08 000 999 110 112 911 118 119
phablet@ubuntu-phablet:/usr/share/ofono/scripts$ ./list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Active = 0
Password = vivo
Preferred = 0
MessageCenter = http://termnat.vivomms.com.br:8088/mms
MessageProxy = 200.142.130.104:80
IPv6.Settings = { }
AccessPointName = mms.vivo.com.br
Protocol = dual
Name = Vivo MMS
Username = vivo
Settings = { }
Type = mms
[ /ril_0/context2 ]
AccessPointName = zap.vivo.com.br
Protocol = dual
Active = 0
Name = Vivo Internet
Username = vivo
Preferred = 0
Type = internet
Settings = { }
Password = vivo
IPv6.Settings = { }
phablet@ubuntu-phablet:/usr/share/ofono/scripts$ ifconfig
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1039 errors:0 dropped:0 overruns:0 frame:0
TX packets:1039 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:109170 (109.1 KB) TX bytes:109170 (109.1 KB)
phablet@ubuntu-phablet:/usr/share/ofono/scripts$ system-image-cli -i
current build number: 180
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-21 19:27:48
version version: 180
version ubuntu: 20150421.1
version device: 20150210
version custom: 20150421.1
phablet@ubuntu-phablet:/usr/share/ofono/scripts$ dpkg -l | grep network-manager
ii network-manager 0.9.10.0-4ubuntu15
[Touch-packages] [Bug 1445080] Re: Cellular data not activated after exiting flight mode
It seems NM was trying to connect, but that never actually succeeded: Apr 21 21:47:01 ubuntu-phablet NetworkManager[1518]: debug [1429652821.190832] [nm-modem-manager.c:205] poke_modem_cb(): Requesting to (re)launch modem-manager... Apr 21 21:49:01 ubuntu-phablet NetworkManager[1518]: debug [1429652941.287746] [nm-modem-manager.c:205] poke_modem_cb(): Requesting to (re)launch modem-manager... Apr 21 21:51:01 ubuntu-phablet NetworkManager[1518]: debug [1429653061.188103] [nm-modem-manager.c:205] poke_modem_cb(): Requesting to (re)launch modem-manager... Apr 21 21:53:01 ubuntu-phablet NetworkManager[1518]: debug [1429653181.282422] [nm-modem-manager.c:205] poke_modem_cb(): Requesting to (re)launch modem-manager... ** Attachment added: syslog on mako, after reproducing the issue https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+attachment/4380844/+files/syslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1445080 Title: Cellular data not activated after exiting flight mode Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: Cellular data is not activated in ~50% of the cases in arale after setting then unsetting flight mode. I obtained the attached log this way: 1. Disabled wifi (to have less noise) and removed syslog (to make smaller the attached one) 2. Reboot 3. See cellular data is on: route is right, I have network access 4. Set flight mode 5. Unset flight mode 6. Data is not restored even after waiting for a few minutes. ccmni0 interface is down. list-modems shows that the modem is data-attached list-contexts output shows that no IP context has been activated Doing usr/share/ofono/scripts/activate-context 1 sudo ip route add default dev ccmni0 ping 8.8.8.8 works and I receive the ping responses. $ system-image-cli -i current build number: 12 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-16 08:06:39 version version: 12 version ubuntu: 20150416.0 version device: a17b9320788e7215ddf123544a3a2b5a4fa61f0d5add83f393866e8c7a9155b0 version custom: 20150416.0 + NetworkManager 0.9.10.0-4ubuntu15~mtrudel1 (silo 29 atm) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446703] Re: Receiving a USSD while phone on mute shows sound OSD
** Changed in: canonical-devices-system-image Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1446703 Title: Receiving a USSD while phone on mute shows sound OSD Status in the base for Ubuntu mobile products: In Progress Status in indicator-sound package in Ubuntu: New Bug description: Version: ubuntu-touch/devel-proposed/krillin.en r59 krillin Steps to reproduce: * set sound on phone to minimum (mute) * perform an action that results in delivery of a USSD (e.g. request some info from the operator - I get a USSD from giffgaff giving balance info after sending a SMS for example) Expected result: - get the USSD pop up with no audible notification Actual result: - get the USSD and the sound OSD pops up show sound level To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1446703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434379] Re: GPS always active when a scope that uses location is in the background
** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1434379 Title: GPS always active when a scope that uses location is in the background Status in the base for Ubuntu mobile products: Fix Released Status in unity-scopes-shell package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: current build number: 256 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-13 11:19:04 version version: 256 version ubuntu: 20150312 version device: 20150310-3201c0a version custom: 20150216-561-29-186 (same for arale/vivid as well) If you happen to have a scope that uses location data in background, your GPS will always be active, doesn't matter what is in the foreground. This is a an issue with krillin (standard channel) as the main scope (Today's) can easily on background when you're using other apps. If you move to the apps scopes, then GPS will automatically be disabled, and this won't happen (same for any other scope that doesn't use location data). This is only when the user is actively using the phone, as the GPS gets automatically disabled once the screen turns off. And there is no timeout at all, it stays there until you move to another scope or turn off the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1434379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446636] Re: [Scopes] Photos sometimes shows popular Flickr photos instead of those belonging to user
** Tags added: bq -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1446636 Title: [Scopes] Photos sometimes shows popular Flickr photos instead of those belonging to user Status in unity8 package in Ubuntu: Invalid Bug description: Pulling down to refresh doesn't help but rebooting the phone does. It's easy to reproduce this bug as it happens every other day, it seems. Updated to r21 already on BQ Aquaris. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1446636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1264493] Re: No Paste option in web page entries
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Tags added: bq -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1264493 Title: No Paste option in web page entries Status in the base for Ubuntu mobile products: New Status in Web Browser App: Confirmed Status in webbrowser-app package in Ubuntu: Triaged Bug description: It's not possible to copy/paste passwords between two silo'd webapps. Open twitter webapp Open separate web browser which goes to password remembering site (such as lastpass) Copy password by longpress Switch to twitter webapp Try to paste into password field, discover no Paste option, only Copy. I would expect to be able to copy/paste between browser windows ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: webbrowser-app 0.22+14.04.20131107-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.7-0ubuntu3 Architecture: armhf Date: Fri Dec 27 11:01:32 2013 InstallationDate: Installed on 2013-12-20 (7 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20131220) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set SHELL=/bin/bash SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1264493/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422309] Re: Today's scope doesn't refresh automatically and indicates wrong day
** Tags added: bq -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1422309 Title: Today's scope doesn't refresh automatically and indicates wrong day Status in the base for Ubuntu mobile products: New Status in unity8 package in Ubuntu: Confirmed Bug description: Not sure if that's rather something for unity8 or the today, but that page should auto-refresh on day changes. Otherwise when you pick your phone in the morning and unlocks it you get welcomed with the wrong date info until you pull down to manually refresh the view To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1422309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433563] Re: QAudioRecorder recording hangs
** Package changed: pulseaudio (Ubuntu) = gst-plugins-good0.10 (Ubuntu) ** Also affects: qtmultimedia-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1433563 Title: QAudioRecorder recording hangs Status in gst-plugins-good0.10 package in Ubuntu: New Status in qtmultimedia-opensource-src package in Ubuntu: New Bug description: Recording audio with QAudioRecorder intermittently fails for me. Another user even reported that it only works 1 out of 5-10 times. QAudioRecorder seems to hang on requesting the audio to be recorded (status QMediaRecortder::StartingStatus). When it actually works, it properly goes from starting to recording and then it's possible to record audio and playback. QAudioRecorder has an error() method, but it returns QMediaRecorder::NoError Since it was confirmed by two people (victorp, karni) we suspect it's a bug in the middleware rather than the apps. A test click has been sent to Ricardo's e-mail by Victor. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 20 device name: krillin channel: (the BQ channel) last update: 2015-02-26 17:06:15 version version: 20 version ubuntu: 20150219 version device: 20150225-b67e0b6 version custom: 20150216-561-29-186 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1433563/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433563] Re: QAudioRecorder recording hangs
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtmultimedia-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1433563 Title: QAudioRecorder recording hangs Status in the base for Ubuntu mobile products: New Status in gst-plugins-good0.10 package in Ubuntu: Confirmed Status in qtmultimedia-opensource-src package in Ubuntu: Confirmed Bug description: Recording audio with QAudioRecorder intermittently fails for me. Another user even reported that it only works 1 out of 5-10 times. QAudioRecorder seems to hang on requesting the audio to be recorded (status QMediaRecortder::StartingStatus). When it actually works, it properly goes from starting to recording and then it's possible to record audio and playback. QAudioRecorder has an error() method, but it returns QMediaRecorder::NoError Since it was confirmed by two people (victorp, karni) we suspect it's a bug in the middleware rather than the apps. A test click has been sent to Ricardo's e-mail by Victor. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 20 device name: krillin channel: (the BQ channel) last update: 2015-02-26 17:06:15 version version: 20 version ubuntu: 20150219 version device: 20150225-b67e0b6 version custom: 20150216-561-29-186 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1433563/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445080] Re: Cellular data not activated after exiting flight mode
I could also easily reproduce that with mako/arale 173, without any custom network manager packages. ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1445080 Title: Cellular data not activated after exiting flight mode Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: New Bug description: Cellular data is not activated in ~50% of the cases in arale after setting then unsetting flight mode. I obtained the attached log this way: 1. Disabled wifi (to have less noise) and removed syslog (to make smaller the attached one) 2. Reboot 3. See cellular data is on: route is right, I have network access 4. Set flight mode 5. Unset flight mode 6. Data is not restored even after waiting for a few minutes. ccmni0 interface is down. list-modems shows that the modem is data-attached list-contexts output is fine too Doing usr/share/ofono/scripts/activate-context 1 sudo ip route add default dev ccmni0 ping 8.8.8.8 works and I receive the ping responses. $ system-image-cli -i current build number: 12 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-16 08:06:39 version version: 12 version ubuntu: 20150416.0 version device: a17b9320788e7215ddf123544a3a2b5a4fa61f0d5add83f393866e8c7a9155b0 version custom: 20150416.0 + NetworkManager 0.9.10.0-4ubuntu15~mtrudel1 (silo 29 atm) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445134] [NEW] Network manager never scanning for new access points
Public bug reported: While trying to reproduce another bug related with the last seen value from the access points, I noticed that network manager is never really scanning for new access points on my desktop, not even when not connected. $ sudo nmcli g logging level debug domains wifi_scan Then powered an access point, but was never really able to see it. From syslog, noticed that there is never really a scan, which explains why the ap never goes away and why it is not able to find it in the first place. If I force a scan via cmdline it works as expected (and I noticed a scan also happens when changing connections). Was also able to reproduce this issue on mako, with the following image: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 173 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-16 14:58:58 version version: 173 version ubuntu: 20150416 version device: 20150210 version custom: 20150416 In the mako case, I booted with a known connection in place, it connected successfully but it never really scans for other access points. Scan works fine after disconnecting though. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu14 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 14:21:42 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-29 (534 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev lxcbr0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.16 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2013-10-31 (532 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-04T02:19:36.923463 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1445134 Title: Network manager never scanning for new access points Status in network-manager package in Ubuntu: New Bug description: While trying to reproduce another bug related with the last seen value from the access points, I noticed that network manager is never really scanning for new access points on my desktop, not even when not connected. $ sudo nmcli g logging level debug domains wifi_scan Then powered an access point, but was never really able to see it. From syslog, noticed that there is never really a scan, which explains why the ap never goes away and why it is not able to find it in the first place. If I force a scan via cmdline it works as expected (and I noticed a scan also happens when changing connections). Was also able to reproduce this issue on mako, with the following image: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 173 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-16 14:58:58 version version: 173 version ubuntu: 20150416 version device: 20150210 version custom: 20150416 In the mako case, I booted with a known connection in place, it connected successfully but it never really scans for other access points. Scan works fine after disconnecting though. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu14 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 14:21:42 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-29 (534 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev lxcbr0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.16 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2013-10-31 (532 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-04T02:19:36.923463 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm']
[Touch-packages] [Bug 1444937] Re: QML cache gets stale too easily
Yeah, while disabling cache when the image is writable is a useful workaround, that could have the bad side effect you described, so probably better to not disable it for now. Proper fix would be improve the way it encodes library versions and magic header, like ricmm described. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1444937 Title: QML cache gets stale too easily Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Bug description: It's happened many times now that after looking for an issue the source of it ended up to be stale QML cache. We need the cache to be cleared more aggressively, likely on any QML- related package installation. App-specific cache should be (if it's not) cleared on install (or maybe better - removal) and upgrade. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libqt5qml5 5.4.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 12:25:21 2015 SourcePackage: qtdeclarative-opensource-src SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1444937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429887] Re: Pressing power button to resume does not turn on screen
This bug is not in powerd itself, it's usually caused by the amount of events that are either on hold before suspending, or that are triggered after resuming back (which makes the device to take a while to fully resume back). We landed quite a few changes as part of OTA3 that reduced such events (battery, console, etc), which improved quite a bit. I still saw this happening once, but then wasn't really able to reproduce it anymore. ** Changed in: powerd (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1429887 Title: Pressing power button to resume does not turn on screen Status in the base for Ubuntu mobile products: New Status in powerd package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Confirmed Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330770] Re: click packages rely upon tls for integrity and authenticity
** Changed in: canonical-devices-system-image Assignee: Ricardo Salveti (rsalveti) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1330770 Title: click packages rely upon tls for integrity and authenticity Status in the base for Ubuntu mobile products: In Progress Status in Click Package metadata search service: Fix Released Status in Online service used by software center: Fix Released Status in click package in Ubuntu: Fix Released Status in ubuntu-download-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: In Progress Status in unity-scope-click package in Ubuntu: Fix Released Bug description: Hello, I just completed a quick review of the click source and the unity-scope-click source and behaviours, and found some opportunities for improvement. Debian, and Ubuntu, rely upon signed repository files with cryptographic hashes of packages to provide both integrity and authenticity checks for the packages hosted on that repository. The click framework and the unity-scope-click discovery and installation tool do not use signed repository files, nor do they have signatures of any sort on downloaded packages. The only integrity and authenticity checks are provided by the use of HTTPS. The click verify command will check files within the archive against MD5sums stored inside the archive but the click verify command is not used during package installation. (This is suitable for validating integrity against accidental changes only.) While it appears that unity-scope-click properly uses HTTPS to download package metadata and packages, HTTPS alone is insufficient for our needs: - Someone in a position to create new certificates at any of several hundred certificate authorities could create certificates purporting to be our update servers. This actual problem has been discovered in the wild with several certificate authorities issuing wild-card certificates or even certificates with signing authority. - X.509 is extremely complicated; TLS is extremely complicated. Flaws in both are inevitable. - HTTPS prevents the use of caching. - HTTPS only 'works' for data-in-motion; it is useless for data-at- rest integrity and authenticity checks. I have not yet reviewed the tools that application authors will use to upload their packages to our distribution servers but note in passing that most of these issues are also issues for adding packages to our update servers -- packages in flight within our network can be corrupted for many reasons, packages on disk can be corrupted for many reasons. A signature mechanism can protect against internal network faults, storage faults, and provide assurance months or years later that an uploaded package was uploaded by someone in control of a corresponding private key. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1330770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432788] Re: Race in vivid means sometimes bluetooth is no available
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1432788 Title: Race in vivid means sometimes bluetooth is no available Status in the base for Ubuntu mobile products: New Status in bluez package in Ubuntu: New Bug description: STEPS: 1. Flash a fresh image of vivid on a krillin device 2. Check if bluetooth is on 3. Reboot EXPECTED: I always expect bluetooth to be on ACTUAL: Bluetooth was turned off, I couldn't tur it on, when I rebooted it was on how ever it wouldn't connect to anything. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1432788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420395] Re: [mako] upower consuming over 17% cpu when in idle
** Changed in: canonical-devices-system-image Assignee: Ricardo Salveti (rsalveti) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1420395 Title: [mako] upower consuming over 17% cpu when in idle Status in the base for Ubuntu mobile products: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: From the meta battery bug # 1372413 mako running 191 As device was not suspending and battery level running down, upower is reported at 17%+ cpu by the cpustat tool mpdecision and systemd-udevd also change their behavior. The upower cpu consumption is just a side effect of the amount of battery related events the kernel send, and specific to mako. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420395/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361864] Re: add Tag property to ConnectionContext interface
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1361864 Title: add Tag property to ConnectionContext interface Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Status in nuntium package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Fix Committed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: To implement system-settings APN editor reliably there has to be a Tag field with is an arbitrary non user-visible string that can be set for any Context. We also need org.ofono.ConnectionManager.AddContext which takes a variant map with prepopulated values for the context to be created, so we can have a function in QOfono QOfonoConnectionManager::addContextWithTag(QString tag). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1361864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443244] [NEW] [touch] small cracking sound when changing volume
Public bug reported: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 169 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 20:38:14 version version: 169 version ubuntu: 20150412 version device: 20150210 version custom: 20150412 Just change the volume quickly when playing a sound, and you can hear really small cracking sounds as the volume increases/decreases. This is even more noticeable with Pathwind's (touch game) soundtrack. Not critical for the user experience but can be a bit annoying. Remember that here pulse is only changing the volume for the multimedia role itself (or any other active role used when reproducing the bug). Not really touching the hardware. ** Affects: canonical-devices-system-image Importance: Undecided Assignee: Canonical Phone Foundations (canonical-phonedations-team) Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1443244 Title: [touch] small cracking sound when changing volume Status in the base for Ubuntu mobile products: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 169 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 20:38:14 version version: 169 version ubuntu: 20150412 version device: 20150210 version custom: 20150412 Just change the volume quickly when playing a sound, and you can hear really small cracking sounds as the volume increases/decreases. This is even more noticeable with Pathwind's (touch game) soundtrack. Not critical for the user experience but can be a bit annoying. Remember that here pulse is only changing the volume for the multimedia role itself (or any other active role used when reproducing the bug). Not really touching the hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443244] Re: [touch] small cracking sound when changing volume
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Description changed: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 169 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 20:38:14 version version: 169 version ubuntu: 20150412 version device: 20150210 version custom: 20150412 Just change the volume quickly when playing a sound, and you can hear really small cracking sounds as the volume increases/decreases. This is even more noticeable with Pathwind's (touch game) soundtrack. + + Not critical for the user experience but can be a bit annoying. + + Remember that here pulse is only changing the volume for the multimedia + role itself (or any other active role used when reproducing the bug). + Not really touching the hardware. ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1443244 Title: [touch] small cracking sound when changing volume Status in the base for Ubuntu mobile products: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 169 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 20:38:14 version version: 169 version ubuntu: 20150412 version device: 20150210 version custom: 20150412 Just change the volume quickly when playing a sound, and you can hear really small cracking sounds as the volume increases/decreases. This is even more noticeable with Pathwind's (touch game) soundtrack. Not critical for the user experience but can be a bit annoying. Remember that here pulse is only changing the volume for the multimedia role itself (or any other active role used when reproducing the bug). Not really touching the hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443178] [NEW] Accounts Service always relies on language fallback if never set by the user
Public bug reported:
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-sound,
as that will cause a sync to accountsservice in order to sync the
volume. Once that sync happens, it will request the user properties, and
in case the user doesn't have a valid language at
/var/lib/AccountsService/users/user, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any language
when the wizard shows up, run top and then change the volume by pressing
volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66
accounts-daemon
And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
guint param_id,
GValue *value,
GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user-language)
g_value_set_string (value, user-language);
else
g_value_set_string (value, user_get_fallback_value
(user, Language));
break;
case PROP_FORMATS_LOCALE:
if (user-formats_locale)
g_value_set_string (value, user-formats_locale);
else
g_value_set_string (value, user_get_fallback_value
(user, FormatsLocale));
break;
user_set_property never gets called unless the user changes the system
language from system-settings or wizard.
Once you change the language, it will set a valid language at
/var/lib/AccountsService/users/user, causing this behavior to stop.
Another bad side effect of this issue is that it takes quite a while for
accountsservice to reply back to indicator-sound when the sync happens,
possibly causing sync aborts (as indicator-sound only waits 1 second
before triggering another sync).
Some possible ways to fix this issue:
1) Make wizard to set language even when the selected language is already the
default one;
2) Change accountsservice to save the fallback value at the first time it gets
that from the system;
** Affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
** Affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1443178
Title:
Accounts Service always relies on language fallback if never set by
the user
Status in the base for Ubuntu mobile products:
New
Status in accountsservice package in Ubuntu:
New
Status in unity8 package in Ubuntu:
New
Bug description:
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-
sound, as that will cause a sync to accountsservice in order to sync
the volume. Once that sync happens, it will request the user
properties, and in case the user doesn't have a valid language at
/var/lib/AccountsService/users/user, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any
language when the wizard shows up, run top and then change the volume
by pressing volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0
[Touch-packages] [Bug 1443005] [NEW] Indicator shouldn't set volume on pulse/account service if the volume didn't change
Public bug reported: current build number: 168 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 03:49:09 version version: 168 version ubuntu: 20150411 version device: 20150210 version custom: 20150411 This is a regression from RTM. The current logic doesn't check for the volume value before calling pulseaudio and account service when updating the volume variable. The consequence is that it will set the volume at least twice after you change it, since it will get a callback from account service, and that will result in another volume set with the exact same volume. ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1443005 Title: Indicator shouldn't set volume on pulse/account service if the volume didn't change Status in indicator-sound package in Ubuntu: New Bug description: current build number: 168 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 03:49:09 version version: 168 version ubuntu: 20150411 version device: 20150210 version custom: 20150411 This is a regression from RTM. The current logic doesn't check for the volume value before calling pulseaudio and account service when updating the volume variable. The consequence is that it will set the volume at least twice after you change it, since it will get a callback from account service, and that will result in another volume set with the exact same volume. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1443005/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437633] Re: Choosing not to report crashes and errors setting reverts
2 issues with the current RTM silo: 1) +++ lxc-android-config-0.208rtm10/etc/system-image/writable-paths 2015-03-31 11:47:37.0 +0100 +# need to write to this file to toggle crash reporting +/etc/default/whoopsie autopersistent nonenone It should be 'persistent transition none' instead, otherwise the file will be empty (not respecting the previous content). 2) Even with the right writable path, it will still fail to save the configuration because whoopsie-preferences is using g_file_set_contents, which will first create a tmp file under the same path, and that will not work because /etc/default is not writable: open(/etc/default/whoopsie.YJXSWX, O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = -1 EROFS (Read-only file system) write(1, Could not write configuration: F..., 107) = 107 So either we make /etc/default rw (or create a writable directory to save whoopsie config), or change whoopsie-preference to first create the new file under /tmp and then copy it over the previous one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1437633 Title: Choosing not to report crashes and errors setting reverts Status in the base for Ubuntu mobile products: In Progress Status in lxc-android-config package in Ubuntu: Confirmed Status in whoopsie package in Ubuntu: Invalid Status in lxc-android-config package in Ubuntu RTM: Confirmed Bug description: Possibly related to bug 1389407 Reported on Askubuntu [1] and confirmed here on a retail bq handset with no modifications (no app installs, only OTA updates). Steps to reproduce:- System Settings - Security Privacy - Diagnostics - Untick box next to App crashes and errors Leave system settings. Wait some time - the AU report suggests an hour, I waited less than that Go back into System Settings - Security Privacy - Diagnostics Not the tick box is ticked again. I would expect the tickbox to remain at whatever I set it to. [1] http://askubuntu.com/questions/602365/permanently-disable-error- reports-on-aquaris-e4-5-ubuntu-edition To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1437633/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440852] [NEW] Need a way to tell our userspace if GPS is currently active or not
Public bug reported: As a result of bug 1434379, QA wanted to check if there could be a way (cmdline/API) to know, from the location-service itself, when the GPS hardware is active or not. Basically the only reliable way to know that is by checking /system/bin/logcat, and retrieving the GPS HAL logs. Having such call could allow us to create regression tests that could check for bug 1434379 (and similar ones). ** Affects: location-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1440852 Title: Need a way to tell our userspace if GPS is currently active or not Status in location-service package in Ubuntu: New Bug description: As a result of bug 1434379, QA wanted to check if there could be a way (cmdline/API) to know, from the location-service itself, when the GPS hardware is active or not. Basically the only reliable way to know that is by checking /system/bin/logcat, and retrieving the GPS HAL logs. Having such call could allow us to create regression tests that could check for bug 1434379 (and similar ones). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1440852/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness
Device tarball was validated by QA already, waiting for John to publish it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in the base for Ubuntu mobile products: In Progress Status in indicator-power package in Ubuntu: In Progress Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
Just to compare, on both iphone and android the AP disappear in no more than 30 seconds. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in the base for Ubuntu mobile products: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
** Summary changed: - Network indicator lists the non-exist AP (timeout for the AP to be removed is too big) + Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in the base for Ubuntu mobile products: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big)
** Summary changed: - Network indicator lists the non-exist AP + Network indicator lists the non-exist AP (timeout for the AP to be removed is too big) ** Description changed: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. + + The main issue is that the timeout for the AP to be removed from the + known AP list is too big when comparing with other phones. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big) Status in the base for Ubuntu mobile products: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420395] Re: upower consuming over 17% cpu
After profiling upower, this is actually not an issue in there, as the only thing it is doing is getting the battery change event from the kernel, updating the internal struct and sending another dbus message so the clients could see the changes. The main issue here is that the kernel is sending a big amount of battery events (all valid, and different changes), which results in udev, upower and dbus consuming a bit of your cpu. Verified this bug against both krillin and arale and that is not the case there, as I already did the profiling and reduced the amount of battery events. As this bug is just specific to mako, and would require a kernel change to reduce the amount of events, we can lower the priority and fix in vivid only. ** Summary changed: - upower consuming over 17% cpu + [mako] upower consuming over 17% cpu when in idle ** Description changed: From the meta battery bug # 1372413 mako running 191 As device was not suspending and battery level running down, upower is reported at 17%+ cpu by the cpustat tool - mpdecision and systemd-udevd also change their behavior. + mpdecision and systemd-udevd also change their behavior. + + The upower cpu consumption is just a side effect of the amount of + battery related events the kernel send, and specific to mako. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1420395 Title: [mako] upower consuming over 17% cpu when in idle Status in the base for Ubuntu mobile products: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: From the meta battery bug # 1372413 mako running 191 As device was not suspending and battery level running down, upower is reported at 17%+ cpu by the cpustat tool mpdecision and systemd-udevd also change their behavior. The upower cpu consumption is just a side effect of the amount of battery related events the kernel send, and specific to mako. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420395/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434379] Re: GPS always active when a scope that uses location is in the background
Any progress on this one? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1434379 Title: GPS always active when a scope that uses location is in the background Status in the base for Ubuntu mobile products: In Progress Status in unity-scopes-shell package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: In Progress Bug description: current build number: 256 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-13 11:19:04 version version: 256 version ubuntu: 20150312 version device: 20150310-3201c0a version custom: 20150216-561-29-186 (same for arale/vivid as well) If you happen to have a scope that uses location data in background, your GPS will always be active, doesn't matter what is in the foreground. This is a an issue with krillin (standard channel) as the main scope (Today's) can easily on background when you're using other apps. If you move to the apps scopes, then GPS will automatically be disabled, and this won't happen (same for any other scope that doesn't use location data). This is only when the user is actively using the phone, as the GPS gets automatically disabled once the screen turns off. And there is no timeout at all, it stays there until you move to another scope or turn off the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1434379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436018] Re: No sound for incoming calls
It could be just another one that got affected by the glibc regression we had, need to check again with latest to see if it's still an issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1436018 Title: No ringtone sound for incoming calls Status in the base for Ubuntu mobile products: Invalid Status in telephony-service package in Ubuntu: Invalid Bug description: vivid-proposed image 158, krillin 1. Call your Ubuntu phone from another device and make sure ringtone plays 2. Reject the call from Ubuntu phone 3. repeat step 1 and 2 On third retry there is no sound played for the incoming call, only the vibration ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20150227-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.2-0ubuntu4 Architecture: armhf Date: Tue Mar 24 23:57:01 2015 InstallationDate: Installed on 2015-03-24 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150324-020203) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436084] Re: bluetooth pairing impossible BQ phone
** Tags added: bq -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1436084 Title: bluetooth pairing impossible BQ phone Status in bluez package in Ubuntu: New Bug description: the bluetooth activation seem to be OK but no device were listed on the BQ aquaris ubuntu phone :( the test have been done with different bluetooth headset with the same result : no device detected by the phone. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: bluez 4.101-0ubuntu24 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity CurrentDmesg: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Mar 24 22:40:19 2015 InstallationDate: Installed on 2015-03-12 (12 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150312-002053) Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' ProcKernelCmdLine: console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 fixrtc lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=456 bootprof.lk_t=1690 printk.disable_uart=1 boot_reason=0 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JU001083 � lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=456 bootprof.lk_t=1690 printk.disable_uart=1 boot_reason=0 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JU001083 � ProcModules: SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) hciconfig: hci0:Type: BR/EDR Bus: UART BD Address: 4C:74:03:5F:13:48 ACL MTU: 1021:4 SCO MTU: 184:1 DOWN RX bytes:5489 acl:0 sco:0 events:338 errors:0 TX bytes:6152 acl:0 sco:0 commands:302 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1436084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398560] Re: Music playback randomly stops working
I was finally able to reproduce the issue I saw before with media-hub,
following the steps described by comment 14. After recording a few
videos and trying to play one of them, I got media-hub to consume 100%
of my cpu, blocking the loop and blocking any new connections as
consequence.
Strace shows it's busy in epoll_wait:
epoll_wait(6, {}, 128, 0) = 0
sendmsg(4, {msg_name(0)=NULL,
msg_iov(2)=[{l\2\1\1\20\0\0\0T\5\0\0\37\0\0\0\6\1s\0\6\0\0\0:1.107\0\0...,
48}, {\1x\0\0\0\0\0\0\0\0\0\0\0\0\0\0, 16}], msg_controllen=0, msg_flags=0},
MSG_NOSIGNAL) = 64
epoll_wait(6, {{EPOLLIN, {u32=33486680, u64=33486680}}}, 128, -1) = 1
recvmsg(4, {msg_name(0)=NULL,
msg_iov(1)=[{l\1\0\0011\0\0\0\25\5\0\0\247\0\0\0\1\1o\0%\0\0\0/core/ub...,
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 233
recvmsg(4, 0xbe938130, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily
unavailable)
epoll_ctl(6, EPOLL_CTL_MOD, 4, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP|EPOLLET,
{u32=33486680, u64=33486680}}) = 0
epoll_wait(6, {}, 128, 0) = 0
sendmsg(4, {msg_name(0)=NULL,
msg_iov(2)=[{l\2\1\1\20\0\0\0U\5\0\0\37\0\0\0\6\1s\0\6\0\0\0:1.107\0\0...,
48}, {\1x\0\0\0\0\0\0\0\0\0\0\0\0\0\0, 16}], msg_controllen=0, msg_flags=0},
MSG_NOSIGNAL) = 64
epoll_wait(6, {{EPOLLIN, {u32=33486680, u64=33486680}}}, 128, -1) = 1
recvmsg(4, {msg_name(0)=NULL,
msg_iov(1)=[{l\1\0\0011\0\0\0\26\5\0\0\247\0\0\0\1\1o\0%\0\0\0/core/ub...,
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 233
recvmsg(4, 0xbe938130, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily
unavailable)
epoll_ctl(6, EPOLL_CTL_MOD, 4, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP|EPOLLET,
{u32=33486680, u64=33486680}}) = 0
epoll_wait(6, {}, 128, 0) = 0
sendmsg(4, {msg_name(0)=NULL,
msg_iov(2)=[{l\2\1\1\20\0\0\0V\5\0\0\37\0\0\0\6\1s\0\6\0\0\0:1.107\0\0...,
48}, {\1x\0\0\0\0\0\0\0\0\0\0\0\0\0\0, 16}], msg_controllen=0, msg_flags=0},
MSG_NOSIGNAL) = 64
epoll_wait(6, {{EPOLLIN, {u32=33486680, u64=33486680}}}, 128, -1) = 1
recvmsg(4, {msg_name(0)=NULL,
msg_iov(1)=[{l\1\0\0011\0\0\0\27\5\0\0\247\0\0\0\1\1o\0%\0\0\0/core/ub...,
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 233
recvmsg(4, 0xbe938130, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily
unavailable)
epoll_ctl(6, EPOLL_CTL_MOD, 4, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP|EPOLLET,
{u32=33486680, u64=33486680}}) = 0
epoll_wait(6, {}, 128, 0) = 0
sendmsg(4, {msg_name(0)=NULL, msg_iov(2)=[{l\2
Getting dbg symbols now to get a trace.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1398560
Title:
Music playback randomly stops working
Status in the base for Ubuntu mobile products:
In Progress
Status in Media Hub:
Invalid
Status in QT Ubuntu Camera:
New
Status in pulseaudio package in Ubuntu:
In Progress
Bug description:
While listening to music media-hub stops randomly. Restart of the job
and reboots don't fix it. Video works fine. Also, 320 kbps music
pauses randomly, might be related. I have also talked about this on
the mailing list.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398560] Re: Music playback randomly stops working
Backtrace when attaching with gdb:
#0 0xb62c9712 in epoll_wait () at ../sysdeps/unix/syscall-template.S:81
No locals.
#1 0xb6ee93fa in boost::asio::detail::epoll_reactor::run (this=0x1fef6e8,
block=block@entry=true, ops=...) at
/usr/include/boost/asio/detail/impl/epoll_reactor.ipp:392
timeout = optimized out
events = {{events = 0, data = {ptr = 0x0, fd = 0, u32 = 0, u64 = 0}}
repeats 38 times, {events = 0, data = {ptr = 0x0, fd = 0, u32 = 0, u64 =
141392522407575552}}, {events = 32920512, data = {ptr = 0x1f5a0d0, fd =
32874704, u32 = 32874704, u64 = 32874704}}, {
events = 32872688, data = {ptr = 0x4, fd = 4, u32 = 4, u64 = 4}},
{events = 32920512, data = {ptr = 0x0, fd = 0, u32 = 0, u64 = 0}}, {events =
32920512, data = {ptr = 0x0, fd = 0, u32 = 0, u64 = 141392522407575552}},
{events = 32874704, data = {
ptr = 0x1f598f0, fd = 32872688, u32 = 32872688, u64 =
13176978892729456880}}, {events = 3068944384, data = {ptr = 0xb6e459c5, fd =
-1226548795, u32 = 3068418501, u64 = 13181015765591284165}}, {events = 0, data
= {ptr = 0xaa903f48, fd = -1433387192,
u32 = 2861580104, u64 = 13178762878944034632}}, {events = 0, data
= {ptr = 0x1f5ef58, fd = 32894808, u32 = 32894808, u64 = 32894808}}, {events =
3197337120, data = {ptr = 0x1f5ef58, fd = 32894808, u32 = 32894808, u64 =
14429902988664}}, {
events = 33597384, data = {ptr = 0x0, fd = 0, u32 = 0, u64 =
13732458124168658944}}, {events = 33607216, data = {ptr = 0xbe937e20, fd =
-1097630176, u32 = 3197337120, u64 = 13177003737984761376}}, {events = 0, data
= {ptr = 0x0, fd = 0, u32 = 0, u64 = 0}}, {
events = 0, data = {ptr = 0x2, fd = 2, u32 = 2, u64 =
145269464831623170}}, {events = 2, data = {ptr = 0x22b0ddc, fd = 36376028, u32
= 36376028, u64 = 8626310620}}, {events = 36376028, data = {ptr = 0xbe937e4c,
fd = -1097630132, u32 = 3197337164,
u64 = 13123924874283417164}}, {events = 36376028, data = {ptr =
0x2c, fd = 44, u32 = 44, u64 = 193273528364}}, {events = 3069841168, data =
{ptr = 0x2d, fd = 45, u32 = 45, u64 = 45}}, {events = 1, data = {ptr = 0x1, fd
= 1, u32 = 1,
u64 = 145246894778482689}}, {events = 2, data = {ptr = 0x3, fd =
3, u32 = 3, u64 = 18161629713510957059}}, {events = 36376028, data = {ptr =
0x6c, fd = 108, u32 = 108, u64 = 145246894778482796}}, {events = 36376028, data
= {ptr = 0xbe937f38,
fd = -1097629896, u32 = 3197337400, u64 = 13732460669986635576}},
{events = 103, data = {ptr = 0x1, fd = 1, u32 = 1, u64 = 463856467969}},
{events = 3197337416, data = {ptr = 0x0, fd = 0, u32 = 0, u64 =
13732459361119240192}}, {events = 0, data = {
ptr = 0x76, fd = 118, u32 = 118, u64 = 13732459567277670518}},
{events = 103, data = {ptr = 0xbe937f38, fd = -1097629896, u32 = 3197337400,
u64 = 13732459639194484536}}, {events = 3197337400, data = {ptr = 0x67, fd =
103, u32 = 103,
u64 = 13123673752938217575}}, {events = 3197337368, data = {ptr =
0xb6fa0f10 __stack_chk_guard, fd = -1225126128, u32 = 3069841168, u64 =
13123673481130151696}}, {events = 43, data = {ptr = 0xbe937fec, fd =
-1097629716, u32 = 3197337580,
u64 = 13123643665594679276}}, {events = 3197337400, data = {ptr =
0x0, fd = 0, u32 = 0, u64 = 13732459361119240192}}, {events = 3197337444, data
= {ptr = 0xbe937f58, fd = -1097629864, u32 = 3197337432, u64 = 7492304728}},
{events = 9, data = {ptr = 0x1,
fd = 1, u32 = 1, u64 = 1}}, {events = 4, data = {ptr =
0xbe937f58, fd = -1097629864, u32 = 3197337432, u64 = 11787272024}}, {events =
4, data = {ptr = 0xbe937f58, fd = -1097629864, u32 = 3197337432, u64 =
13128831883009032024}}, {events = 3055657113,
data = {ptr = 0x20419a0, fd = 33823136, u32 = 33823136, u64 =
206192253344}}, {events = 36376152, data = {ptr = 0x0, fd = 0, u32 = 0, u64 =
0}}, {events = 3197337416, data = {ptr = 0xb6235398, fd = -1239198824, u32 =
3055768472, u64 = 13124425637263791000}}, {
events = 33519408, data = {ptr = 0x1feceb0, fd = 33476272, u32 =
33476272, u64 = 156233833471987376}}, {events = 36376108, data = {ptr =
0x1fec7c0, fd = 33474496, u32 = 33474496, u64 = 143772277920417728}}, {events =
64, data = {ptr = 0x22b0e18,
fd = 36376088, u32 = 36376088, u64 = 13184867420510817816}},
{events = 16, data = {ptr = 0x0, fd = 0, u32 = 0, u64 = 13184867420474441728}},
{events = 3069841168, data = {ptr = 0x0, fd = 0, u32 = 0, u64 =
156233850618380288}}, {events = 36376088, data = {
ptr = 0x0, fd = 0, u32 = 0, u64 = 143771865570082816}}, {events =
3069841168, data = {ptr = 0x20, fd = 32, u32 = 32, u64 = 143771865570082848}},
{events = 3069841168, data = {ptr = 0x20, fd = 32, u32 = 32, u64 =
13732461216545112096}}, {events = 3069841168,
data = {ptr = 0xbe938174, fd = -1097629324, u32 = 3197337972, u64 =
13123867742628446580}}, {events = 3197304832, data = {ptr = 0x1fec7c0, fd =
33474496,
[Touch-packages] [Bug 1398560] Re: Music playback randomly stops working
As before, pulse was fine after a reboot. Will now try to manually corrupt the database and see what I can get (wondering if this is related with the mute issue we have with pathwind). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: In Progress Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398560] Re: Music playback randomly stops working
Trying to reproduce but I'm still unable to get the issue described at comment #14. I was able to get the system to hang for a bit, but that was because mediascanner crashed. It seems that at one point media-hub wasn't able to accept new connections (couldn't play music via music- app). The problem is that it worked fine after a reboot, so not really pulse specific. I also tested the pulseconfig described by comment #16, but audio is also working as expected (if the file was corrupted or with the multimedia role muted, it would show up when using such configs). Will keep trying to reproduce the issue (this is latest RTM/krillin). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: In Progress Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435776] Re: NM does not activate a valid ofono context
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1435776 Title: NM does not activate a valid ofono context Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: Device: Krillin Software: Vivid r157 NM does not activate a valid ofono context which is present in the gprs file (context_1 in this case) I was able to activate the context manually using ./activate-context /ril_0 1 You can find syslog, list-modems and list-contexts attached To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398560] Re: Music playback randomly stops working
** Attachment added: media-hub-taabtfull.txt https://bugs.launchpad.net/media-hub/+bug/1398560/+attachment/4361422/+files/media-hub-taabtfull.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: In Progress Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401563] Re: Playing a video from the photo roll exhibits odd behaviour if a video is currently loaded in the media player
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1401563 Title: Playing a video from the photo roll exhibits odd behaviour if a video is currently loaded in the media player Status in Camera App: Invalid Status in the base for Ubuntu mobile products: New Status in libhybris: New Status in Media Hub: Triaged Status in camera-app package in Ubuntu: Invalid Status in media-hub package in Ubuntu: Confirmed Bug description: Prerequisites: There must be two videos loaded on the phone, at least one which must have been taken with the phones camera and stored in the photo roll Steps to reproduce: 1. Navigate to the Videos scope 2. Tap on a video 3. Tap on the Play button 4. Let the video play for some time and then open the camera application 5. Swipe left to get to the photo roll and swipe to any video in the photo roll 6. Tap on the play button Expected result: The video from the photo roll plays properly in the media player Actual result: The video is corrupted in some way - usually the video that was already loaded is shown as a still but with the sound of the video from the photo roll. Sometimes the correct video will be played but in the wrong aspect ratio. current build number: 176 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-12-11 14:44:52 version version: 176 version ubuntu: 20141211 version device: 20141209-cae2b5f version custom: 20141119-442-21-160 To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1401563/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438486] [NEW] Turning off sound in Pathwind mutes other apps too
Public bug reported: current build number: 260 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-30 18:17:44 version version: 260 version ubuntu: 20150330 version device: 20150327-f7072d0 version custom: 20150216-561-29-186 In Pathwind (part of the custom tarball installed with newer flashes but also in the store) one can toggle sound on/off. If set to off sound won't be heard in youtube playbacks in the browser, cut the rope, media player. It still works for keyboard press sounds if enabled, and ringtones work as well. This may be intentional, but at least on one occasion it persisted even after pathwind quit, and sound did not work in the rest of the apps. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: pulseaudio (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1438486 Title: Turning off sound in Pathwind mutes other apps too Status in the base for Ubuntu mobile products: New Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu RTM: New Bug description: current build number: 260 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-30 18:17:44 version version: 260 version ubuntu: 20150330 version device: 20150327-f7072d0 version custom: 20150216-561-29-186 In Pathwind (part of the custom tarball installed with newer flashes but also in the store) one can toggle sound on/off. If set to off sound won't be heard in youtube playbacks in the browser, cut the rope, media player. It still works for keyboard press sounds if enabled, and ringtones work as well. This may be intentional, but at least on one occasion it persisted even after pathwind quit, and sound did not work in the rest of the apps. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1438486/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398560] Re: Music playback randomly stops working
Opened bug 1438491 for the issue I had with media-hub. For this bug I'll just force pulse to not store/restore any mute or device related value for the multimedia role. I think the original issue is that the multimedia role stream got muted, causing the blocking issue just for multimedia related apps (ringtone and alarms were playing fine). This is probably a similar issue as described by bug 1438486 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: In Progress Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438486] Re: Turning off sound in Pathwind mutes other apps too
** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1438486 Title: Turning off sound in Pathwind mutes other apps too Status in the base for Ubuntu mobile products: New Status in pulseaudio package in Ubuntu: Confirmed Status in ubuntu-touch-session package in Ubuntu: New Status in pulseaudio package in Ubuntu RTM: New Status in ubuntu-touch-session package in Ubuntu RTM: New Bug description: current build number: 260 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-30 18:17:44 version version: 260 version ubuntu: 20150330 version device: 20150327-f7072d0 version custom: 20150216-561-29-186 In Pathwind (part of the custom tarball installed with newer flashes but also in the store) one can toggle sound on/off. If set to off sound won't be heard in youtube playbacks in the browser, cut the rope, media player. It still works for keyboard press sounds if enabled, and ringtones work as well. This may be intentional, but at least on one occasion it persisted even after pathwind quit, and sound did not work in the rest of the apps. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1438486/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435776] Re: NM does not activate a valid ofono context
** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1435776 Title: NM does not activate a valid ofono context Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: Device: Krillin Software: Vivid r157 NM does not activate a valid ofono context which is present in the gprs file (context_1 in this case) I was able to activate the context manually using ./activate-context /ril_0 1 You can find syslog, list-modems and list-contexts attached To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398560] Re: Music playback randomly stops working
** Description changed: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. + + This is probably a side effect of bug 1438486 (or similar), as pulse is + working but without sound just for the multimedia related roles. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: In Progress Status in ubuntu-touch-session package in Ubuntu: New Status in ubuntu-touch-session package in Ubuntu RTM: New Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. This is probably a side effect of bug 1438486 (or similar), as pulse is working but without sound just for the multimedia related roles. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436084] Re: bluetooth pairing impossible BQ phone
Can you check, from a terminal, to see if your driver is able to find out other devices? Please call '$ sudo hcitool -i hci0 scan' and see if it's able to see at least one device. Would be good to double check with another device to make sure the range is fine and others can indeed see what your bq phone can't. If you open system settings - bluetooth, it should naturally try to scan other devices, and should have similar results as done with hcitool. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1436084 Title: bluetooth pairing impossible BQ phone Status in bluez package in Ubuntu: New Bug description: the bluetooth activation seem to be OK but no device were listed on the BQ aquaris ubuntu phone :( the test have been done with different bluetooth headset with the same result : no device detected by the phone. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: bluez 4.101-0ubuntu24 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity CurrentDmesg: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Mar 24 22:40:19 2015 InstallationDate: Installed on 2015-03-12 (12 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150312-002053) Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' ProcKernelCmdLine: console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 fixrtc lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=456 bootprof.lk_t=1690 printk.disable_uart=1 boot_reason=0 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JU001083 � lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=456 bootprof.lk_t=1690 printk.disable_uart=1 boot_reason=0 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JU001083 � ProcModules: SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) hciconfig: hci0:Type: BR/EDR Bus: UART BD Address: 4C:74:03:5F:13:48 ACL MTU: 1021:4 SCO MTU: 184:1 DOWN RX bytes:5489 acl:0 sco:0 events:338 errors:0 TX bytes:6152 acl:0 sco:0 commands:302 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1436084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness
That's weird as I can't reproduce this with my device, but I'm still using a prototype. Asking someone with a final device to give another try, but we can for sure try to change the minimal value as required. You can restore back the brightness if you have access to a terminal, by doing the following: sudo echo 10 /sys/devices/platform/leds-mt65xx/leds/lcd-backlight/brightness Can you play with the values and find out what is the minimum you get that is still able to see visualize unity8? Our minimum is currently 5, so would be great if you could play with that bit and give us the feedback. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in indicator-power package in Ubuntu: New Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437418] Re: Add NFC settings
Currently the missing piece is the platform glue layer that can hook up the kernel/android HAL layer in our stack. It's in our roadmap, but the first thing to do is properly understand what are the missing pieces and how than can work together. ** Summary changed: - Add NFC settings + Add NFC support ** Also affects: platform-api (Ubuntu) Importance: Undecided Status: New ** Also affects: android (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to platform-api in Ubuntu. https://bugs.launchpad.net/bugs/1437418 Title: Add NFC support Status in android package in Ubuntu: New Status in platform-api package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: There are no NFC settings. I don't know if it's a limitation of UT, but a lot of devices have NFC capabilities and this should be included in the settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1437418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436045] Re: (Krillin) Keyboard layout suggests wrong national domain as shortcut
** Tags added: bq -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1436045 Title: (Krillin) Keyboard layout suggests wrong national domain as shortcut Status in ubuntu-keyboard package in Ubuntu: New Bug description: On BQ Aquaris HD4.5 Ubuntu Edition I found the following bug concerning Croatian (hrvatski) keyboard layout, when using the keyboard with browser it has a key that suggests domain name shortcuts, it suggests .com which is ok, but that key also suggests .ba domain as shortcut which is a Bosnian, and not Croatian national domain, the key should suggest .com and .hr which is Croatian domain. Not a major issue but still it would be nice if it can be fixed. Device is fully updated and running 14.10 (r20). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1436045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437425] Re: Flight mode broken
Please check this again with image 152, as we believe the reason is that the proper ofono package wasn't part of the previous image. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1437425 Title: Flight mode broken Status in indicator-network package in Ubuntu: New Bug description: Test case. - Open indicator network. - Enable flight mode. Expected result. - Wifi and phone goes offline. Actual result. - Both wifi and phone remain online. current build number: 163 device name: krillin channel: ubuntu-touch/devel-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1437425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437510] [NEW] Screen dim is not following the lock screen timeout (always dimming after 50 seconds)
Public bug reported: current build number: 258 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-26 16:39:52 version version: 258 version ubuntu: 20150326 version device: 20150310-3201c0a version custom: 20150216-561-29-186 Go to system settings, security, lock when idle, and change to any value higher than 1 minute. Now wait and you will see that the screen will dim after 50 seconds, no matter what value you set. The screen should only dim 10 seconds before reaching the screen lock value. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: unity-system-compositor (Ubuntu) Importance: Undecided Status: New ** Affects: unity-system-compositor (Ubuntu RTM) Importance: Undecided Status: New ** Tags: bq ** Tags added: bq ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: unity-system-compositor (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1437510 Title: Screen dim is not following the lock screen timeout (always dimming after 50 seconds) Status in the base for Ubuntu mobile products: New Status in unity-system-compositor package in Ubuntu: New Status in unity-system-compositor package in Ubuntu RTM: New Bug description: current build number: 258 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-26 16:39:52 version version: 258 version ubuntu: 20150326 version device: 20150310-3201c0a version custom: 20150216-561-29-186 Go to system settings, security, lock when idle, and change to any value higher than 1 minute. Now wait and you will see that the screen will dim after 50 seconds, no matter what value you set. The screen should only dim 10 seconds before reaching the screen lock value. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1437510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness
I proposed a change to change minimum from 5 to 10, which should cover your issue specifically. If you want a workaround until next OTA is out (1-2 weeks), do the following (from your host): 1 - Download the attached config file and save as config-krillin.xml 2 - adb push config-krillin.xml /tmp/ 3 - adb shell: $ sudo mount -o remount,rw / $ sudo cp /tmp/config-krillin.xml /usr/share/powerd/device_configs/config-krillin.xml $ sudo reboot Also opened bug 1437510 for the dim issue, as that is indeed a problem. ** Attachment added: config-krillin.xml https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1436538/+attachment/4358308/+files/config-krillin.xml -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in indicator-power package in Ubuntu: Incomplete Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436971] Re: calendar alarm would not stop sounding
*** This bug is a duplicate of bug 1436162 *** https://bugs.launchpad.net/bugs/1436162 ** This bug has been marked a duplicate of bug 1436162 [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1436971 Title: calendar alarm would not stop sounding Status in indicator-datetime package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: vivid-proposed on mako I had a calendar alarm notification sound at 9:00am this morning and it keep ringing/vibrating and did not go away until I swiped it. At that point, I think something crashed because my datetime indicator is stuck at 9:01am and I cannot launch Time and Date settings from the menu. I do have a crash file (with an earlier timestamp, so not sure if it's the same or different crash). Attaching that and the indicator- datetime log files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1436971/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436998] [NEW] Keyboard not showing up again when switching back to the accounts page (system-settings)
Public bug reported: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 257 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-25 19:42:36 version version: 257 version ubuntu: 20150324 version device: 20150310-3201c0a version custom: 20150216-561-29-186 To reproduce: - Open system-settings - Go to accounts - Add account - Select Evernote (can happen with any other) - Keyboard will show up fine when touching the form - Swipe right-left, go to the home scopes - Swipe back to system-settings - Unable to bring up the keyboard anymore To continue you basically need to cancel and try to create the account again. ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New ** Tags: bq ** Tags added: bq -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1436998 Title: Keyboard not showing up again when switching back to the accounts page (system-settings) Status in ubuntu-keyboard package in Ubuntu: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 257 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-25 19:42:36 version version: 257 version ubuntu: 20150324 version device: 20150310-3201c0a version custom: 20150216-561-29-186 To reproduce: - Open system-settings - Go to accounts - Add account - Select Evernote (can happen with any other) - Keyboard will show up fine when touching the form - Swipe right-left, go to the home scopes - Swipe back to system-settings - Unable to bring up the keyboard anymore To continue you basically need to cancel and try to create the account again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1436998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398560] Re: Music playback randomly stops working
** Changed in: pulseaudio (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: Confirmed Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: In Progress Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21
So this issue is a combination of the following patches: https://sourceware.org/git/?p=glibc.git;a=commit;h=47c5adebd2c864a098c3af66e61e1147dc3cf0b4 https://sourceware.org/git/?p=glibc.git;a=commit;h=03d41216fe09fc71a2750946af8fe2892bf4feb5 Basically the main problem is that futex_atomic_cmpxchg_inatomic got disabled, even though we have that well supported in our kernels. I just did another build (in canonical-arm-dev) including the patch bellow, and with that I'm unable to reproduce this bug: Index: glibc-2.21/sysdeps/unix/sysv/linux/arm/kernel-features.h === --- glibc-2.21.orig/sysdeps/unix/sysv/linux/arm/kernel-features.h +++ glibc-2.21/sysdeps/unix/sysv/linux/arm/kernel-features.h @@ -37,8 +37,10 @@ /* The ARM kernel before 3.14.3 may or may not support futex_atomic_cmpxchg_inatomic, depending on kernel configuration. */ +/* #if __LINUX_KERNEL_VERSION 0x030E03 # undef __ASSUME_FUTEX_LOCK_PI # undef __ASSUME_REQUEUE_PI # undef __ASSUME_SET_ROBUST_LIST #endif +*/ ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: Confirmed = Invalid ** Changed in: pulseaudio (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1436162 Title: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21 Status in glibc package in Ubuntu: Confirmed Status in gst-plugins-good1.0 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: current build number: 146 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-03-24 13:57:03 version version: 146 After libc 2.21 landed, pulsesink fails constantly when pausing or seeking the active pipeline. Abort message: Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock(). Aborting. This is basically happens when it tries to unlock a mutex that is already unlocked. This issue doesn't happen with libc 2.19. To reproduce the issue: GST_DEBUG=*pulse*:5 gst-launch-1.0 playbin uri=file:///tmp/foobar.mp3 Then when playing, just hit control+c, which will then pause the pipeline, causing the crash. The crash happens with most of the times you pause or seek the pipeline. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1436162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21
SMP support for futex_atomic_cmpxchg_inatomic was added in 2.6.38, but it required !CPU_USE_DOMAINS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1436162 Title: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21 Status in glibc package in Ubuntu: Confirmed Status in gst-plugins-good1.0 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: current build number: 146 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-03-24 13:57:03 version version: 146 After libc 2.21 landed, pulsesink fails constantly when pausing or seeking the active pipeline. Abort message: Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock(). Aborting. This is basically happens when it tries to unlock a mutex that is already unlocked. This issue doesn't happen with libc 2.19. To reproduce the issue: GST_DEBUG=*pulse*:5 gst-launch-1.0 playbin uri=file:///tmp/foobar.mp3 Then when playing, just hit control+c, which will then pause the pipeline, causing the crash. The crash happens with most of the times you pause or seek the pipeline. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1436162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
