[Touch-packages] [Bug 1375837] Re: Popovers must close when rotating screen
** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid)
Status: New = Fix Released
--
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/1375837
Title:
Popovers must close when rotating screen
Status in Ubuntu UI Toolkit:
Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Status in webbrowser-app package in Ubuntu:
Triaged
Status in ubuntu-ui-toolkit source package in Vivid:
Fix Released
Status in webbrowser-app package in Ubuntu RTM:
Triaged
Bug description:
After rotating the device a few times while an overflow menu is open,
the menu will be placed in the wrong position on the screen. The
number of rotations before this happens appears to be quite random,
but it will eventually happen.
Below is a minimal example that should trigger the bug by rotating the
device after opening the overflow menu:
import QtQuick 2.0
import Ubuntu.Components 1.1
MainView {
id: mainView
applicationName: com.ubuntu.developer.ken-vandine.hub-importer
automaticOrientation: true
useDeprecatedToolbar: false
width: units.gu(100)
height: units.gu(75)
Page {
title: Test
head.actions: [
Action { name: Item 1 },
Action { name: Item 2 },
Action { name: Item 3 },
Action { name: Item 4 }
]
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1375837/+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 1369640] Re: Disabled menu items in header overflow don't look disabled
** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid) Status: New = Fix Released -- 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/1369640 Title: Disabled menu items in header overflow don't look disabled Status in Ubuntu UI Toolkit: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: Fix Released Bug description: If there is a disabled menu item in the header overflow menu, it will appear as if it was enabled but clicking on it will have no effect. Disabled items should be greyed out or have some visual clue that they are disabled. (Bug confirmed by Tim, stating the code to handle this case hasn't been implemented by mistake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1369640/+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 1382121] Re: test_hide_osk_when_pickerpanel_opens fails with Qt 5.3.2 on x86
** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid) Status: New = Fix Released -- 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/1382121 Title: test_hide_osk_when_pickerpanel_opens fails with Qt 5.3.2 on x86 Status in Ubuntu UI Toolkit: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu RTM: In Progress Bug description: See https://launchpadlibrarian.net/187504867/buildlog_ubuntu-utopic- amd64.ubuntu-ui- toolkit_1.1.1279%2B14.10.20141007-0ubuntu2%2Bdisabletest~~1_UPLOADING.txt.gz --- FAIL! : components::FocusingTests::test_hide_osk_when_pickerpanel_opens() 'OSK is hidden' returned FALSE. () Loc: [/build/buildd/ubuntu-ui-toolkit-1.1.1279+14.10.20141007/tests/unit_x11/tst_components/tst_focus.qml(187)] --- All Qt 5.3(.2) bugs https://bugs.launchpad.net/bugs/+bugs?field.tag=qt5.3 Info about Qt 5.3.2 testing https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1382121/+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 1468792] Re: various apparmor denials when using ubuntu-account-plugin template
This bug was fixed in the package ubuntu-system-settings-online-accounts
- 0.6+15.10.20150715-0ubuntu1
---
ubuntu-system-settings-online-accounts (0.6+15.10.20150715-0ubuntu1) wily;
urgency=medium
[ Alberto Mardegan ]
* Inject the APP_ID into the child process's environment. (LP:
#1468792)
[ CI Train Bot ]
* New rebuild forced.
* Resync trunk.
-- CI Train Bot ci-train-...@canonical.com Wed, 15 Jul 2015 11:13:52
+
** Changed in: ubuntu-system-settings-online-accounts (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-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1468792
Title:
various apparmor denials when using ubuntu-account-plugin template
Status in Online Accounts setup for Ubuntu Touch:
In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
Fix Released
Status in click-reviewers-tools package in Ubuntu:
Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
Fix Released
Bug description:
This is a new bug for the problems seen in bug #1219644. Specifically:
1. There is a denial to create this directory if it does not exist already:
Jun 24 17:02:55 ubuntu-phablet kernel: [44001.684473] type=1400
audit(1435183375.362:404): apparmor=DENIED operation=mkdir
profile=com.ubuntu.developer.rmescandon.asana_account-plugin_1.0.0
name=/home/phablet/.cache/QML/Apps/online-accounts-ui/ pid=15145
comm=QQmlThread requested_mask=c denied_mask=c fsuid=32011 ouid=32011
2. If you create that directory, the next denial is not application specific
(ie, it doesn't use the APP_ID):
Jun 24 17:12:00 ubuntu-phablet kernel: [44546.645041] type=1400
audit(1435183920.324:495): apparmor=DENIED operation=mknod
profile=com.ubuntu.developer.rmescandon.asana_account-plugin_1.0.0
name=/home/phablet/.cache/QML/Apps/online-accounts-ui/ea1df0af2467507eb3888f68100da073
pid=17998 comm=QQmlThread requested_mask=c denied_mask=c fsuid=32011
ouid=32011
3. The apparmor policy has rules for this:
owner @{HOME}/.cache/online-accounts-ui/id-*-@{APP_PKGNAME}_@{APP_APPNAME}/
rw,
owner
@{HOME}/.cache/online-accounts-ui/id-*-@{APP_PKGNAME}_@{APP_APPNAME}/** mrwkl,
but *not* for:
owner @{HOME}/.cache/QML/Apps/online-accounts-ui/.../ rw,
owner @{HOME}/.cache/QML/Apps/online-accounts-ui/.../** mrwkl,
It is not clear if '3' will be fixed if '2' is or if the policy will need
this added after '2' is fixed:
# Allow writes to application-specific QML cache directories
owner @{HOME}/.cache/QML/Apps/@{APP_PKGNAME}_@{APP_APPNAME}_@{APP_VERSION}/
rw,
owner
@{HOME}/.cache/QML/Apps/@{APP_PKGNAME}_@{APP_APPNAME}_@{APP_VERSION}/** mrwkl,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1468792/+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 1360101] Re: Toggling an alarm status right after editing it results in the alarm status being reverted
** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid) Status: New = Fix Released -- 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/1360101 Title: Toggling an alarm status right after editing it results in the alarm status being reverted Status in Ubuntu UI Toolkit: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: Fix Released Bug description: Steps to reproduce: 1. Create an alarm and save it. 2. Edit that alarm and change any property and then save it again. 3. Change the status of the alarm to disabled. What happens: Notice that the alarm status is reverted back to enabled What should happen: The alarm status stays disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1360101/+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 1361702] Re: clock-app alarms need to be handled differently from other VTODO events
** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid) Status: New = Fix Released -- 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/1361702 Title: clock-app alarms need to be handled differently from other VTODO events Status in Canonical System Image: Fix Released Status in Indicator Date and Time: Fix Released Status in Ubuntu Calendar App: Invalid Status in Ubuntu UI Toolkit: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: Fix Released Bug description: When you disable an alarm in the new clock app (with white background), it causes the alarm to show up as a calendar event. The expected behaviour is to not show up at all. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1361702/+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 1449080] Re: Starting bluetooth service fails in 15.04
This seems to be related to the package sixad When sixad is installed, it will autostart and it removes execution permissions on /usr/sbin/bluetoothd on start. This prevents bluetooth.service from starting. -- Unit bluetooth.service has begun starting up. jul 16 21:17:56 mainframe systemd[5337]: Failed at step EXEC spawning /usr/sbin/bluetoothd: Permission denied -- Subject: Process /usr/sbin/bluetoothd could not be executed johan@mainframe:~$ ls -la /usr/sbin/bluetoothd -rw-r--r-- 1 root root 946920 apr 13 19:05 /usr/sbin/bluetoothd If I manually set execute permissions on /usr/sbin/bluetoothd bluetooth.service will start properly but will fail at next reboot. I can start and stop the service as many times as I want to, but when I start sixad (sixad --start) it will remove execution permission on /usr/sbin/bluetoothd causing bluetooth.service to fail. I have not yet found a solution to this. -- 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/1449080 Title: Starting bluetooth service fails in 15.04 Status in bluez package in Ubuntu: Confirmed Bug description: This is an upgrade from 14.10 to 15.04 on a laptop using a dell 370 bluetooth minicard. Starting the bluetooth service (4.101-0ubuntu25) produces this error: Job for bluetooth.service failed. See systemctl status bluetooth.service and journalctl -xe for details. journalctl -xe shows: systemd[1]: Unit bluetooth.service entered failed state. systemd[1]: bluetooth.service failed. systemd[1]: bluetooth.service holdoff time over, scheduling restart. systemd[1]: start request repeated too quickly for bluetooth.service systemd[1]: Failed to start Bluetooth service. journalctl -u bluetooth shows: systemd[1]: Starting Bluetooth service... systemd[2561]: Failed at step EXEC spawning /usr/sbin/bluetoothd: Permission denied systemd[1]: bluetooth.service: main process exited, code=exited, status=203/EXEC systemd[1]: Failed to start Bluetooth service. systemd[1]: UnitApr 27 10:18:10 mobile bluetooth.service entered failed state. systemd[1]: bluetooth.service failed. Bluetooth works when the laptop is booted into Windows and worked on 14.10. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluetooth 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Mon Apr 27 10:44:30 2015 InstallationDate: Installed on 2015-03-10 (47 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) InterestingModules: btusb bluetooth MachineType: Dell Inc. Latitude E6400 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=dc3060f2-ea09-43a5-912a-45040afffd37 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A34 dmi.board.name: 0U692R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0U692R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 70:1A:04:1D:D9:2F ACL MTU: 1021:8 SCO MTU: 64:8 DOWN RX bytes:501 acl:0 sco:0 events:22 errors:0 TX bytes:329 acl:0 sco:0 commands:22 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1449080/+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 1474891] Re: USC crash on multimonitor unplug [std::exception::what: error during hwc prepare()]
So, what seems to be happening on these drivers is that the hotplug- unplug event comes in while the driver is doing work in hwc::set() with an external list. Since the driver cannot post the list to the display anymore (as its physically disconnected), hwc::set() returns -1. At that point, mir throws up the compositor thread (which is trying to be shut down anyways at this point), and the exception is caught, which terminates the server. Given that the thread that gets the throw is shutting down anyways, we can ignore the exception. ** Branch linked: lp:~kdub/mir/fix-1474891 -- 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/1474891 Title: USC crash on multimonitor unplug [std::exception::what: error during hwc prepare()] Status in Mir: In Progress Status in Unity System Compositor: New Status in mir package in Ubuntu: New Bug description: I've a slightly customized USC built in Silo0. On top of that, a multimonitor-aware unity8 is running. http://people.canonical.com/~platform/citrain_dashboard/#?q=ubuntu/landing-000 On Android devices, Nexus 4 7, I occasionally get a crash on external monitor unplug. Here is the relevant log: ERROR: /build/mir-UAyS26/mir-0.13.4+15.04.20150709.2/src/platforms/android/server/real_hwc_wrapper.cpp(123): Throw in function virtual void mir::graphics::android::RealHwcWrapper::set(const std::arrayhwc_display_contents_1*, 3u) const Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error std::exception::what: error during hwc prepare(). rc = To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474891/+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 1474891] Re: USC crash on multimonitor unplug [std::exception::what: error during hwc prepare()]
Attached my branch that should avert it, doing some more testing on it before proposing. -- 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/1474891 Title: USC crash on multimonitor unplug [std::exception::what: error during hwc prepare()] Status in Mir: In Progress Status in Unity System Compositor: New Status in mir package in Ubuntu: New Bug description: I've a slightly customized USC built in Silo0. On top of that, a multimonitor-aware unity8 is running. http://people.canonical.com/~platform/citrain_dashboard/#?q=ubuntu/landing-000 On Android devices, Nexus 4 7, I occasionally get a crash on external monitor unplug. Here is the relevant log: ERROR: /build/mir-UAyS26/mir-0.13.4+15.04.20150709.2/src/platforms/android/server/real_hwc_wrapper.cpp(123): Throw in function virtual void mir::graphics::android::RealHwcWrapper::set(const std::arrayhwc_display_contents_1*, 3u) const Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error std::exception::what: error during hwc prepare(). rc = To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474891/+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 1361919] Re: PageStack::push() should return the object that was pushed
** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid) Status: New = Fix Released -- 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/1361919 Title: PageStack::push() should return the object that was pushed Status in Ubuntu UI Toolkit: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Bug description: This way the caller can connect to any signals the pushed Component might have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1361919/+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 1363112] Re: StateSaver is not working on devices
** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1363112 Title: StateSaver is not working on devices Status in Ubuntu UI Toolkit: Fix Released Status in apparmor-easyprof-ubuntu package in Ubuntu: Fix Released Status in camera-app package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: Fix Released Bug description: build 212 The StateSaver is not working anymore on devices, so apps saved state is no longer restored when they are relaunched after being killed by oom killer (or manually via kill -2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1363112/+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 1367907] Re: Segfault in gc with cyclic trash
This issue is still biting us on the OpenStack CI. The py34 test job of the Oslo Messaging project is crashing randomly, even after disabling the test using trollius (the bug was initially found on an asyncio example, and trollius code is very close to asyncio). Please fix it, Trusty is a LTS version! Python 3.4 matters for us! The bug was fixed in Python in May 2014 and was reported here in September 2014. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1367907 Title: Segfault in gc with cyclic trash Status in oslo.messaging: Invalid Status in Python: Fix Released Status in python3.4 package in Ubuntu: Fix Released Status in python3.4 source package in Trusty: Triaged Bug description: Trusty's python3.4 package is affected by python bug http://bugs.python.org/issue21435. This bug was fixed in http://hg.python.org/cpython/rev/64ba3f2de99c. Trusty should pull this fix into the python3.4 package. Note this definitely affects some python projects. `git clone https://git.openstack.org/openstack/oslo.messaging cd oslo.messaging edit tox.ini file, copy py33 target and rename to py34 tox -repy34` will segfault due to this bug. With previous versions of python unaffected by this bug there is no segfaulting. Now for details, broken using: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy python3.4 python3.4: Installed: 3.4.0-2ubuntu1 Candidate: 3.4.0-2ubuntu1 Version table: *** 3.4.0-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status If I install the following python3.4 packages for Unicorn on Trusty this bug is corrected. The Unicorn packages here on lp for python3.4 are python3.4.1 which includes the bug fix for this bug. libpython3.4_3.4.1-10ubuntu1_amd64.deb libpython3.4-dev_3.4.1-10ubuntu1_amd64.deb libpython3.4-stdlib_3.4.1-10ubuntu1_amd64.deb python3.4-dbg_3.4.1-10ubuntu1_amd64.deb python3.4-minimal_3.4.1-10ubuntu1_amd64.deb libpython3.4-dbg_3.4.1-10ubuntu1_amd64.deb libpython3.4-minimal_3.4.1-10ubuntu1_amd64.deb python3.4_3.4.1-10ubuntu1_amd64.deb python3.4-dev_3.4.1-10ubuntu1_amd64.deb Note I installed the -dbg packages too just in case I needed to use gdb but that wasn't necessary as the test case works with these newer versions of python. $ apt-cache policy python3.4 python3.4: Installed: 3.4.1-10ubuntu1 Candidate: 3.4.1-10ubuntu1 Version table: *** 3.4.1-10ubuntu1 0 100 /var/lib/dpkg/status 3.4.0-2ubuntu1 0 500 http://az2.clouds.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages [Impact] This python bug can cause python processes that tickle it to segfault python. This means there could be a significant number of python packages that are broken when run under this interpreter. The fix for this bug should be backported to avoid seemingly random and hard to debug segfaults from happening when users use python. Unicorn's 3.4.1 packages fix this bug by including the patch at http://hg.python.org/cpython/rev/64ba3f2de99c. [Test Case] There is a test case detailed in the upstream bug http://bugs.python.org/issue21435, though I have been doing the following instead: git clone https://git.openstack.org/openstack/oslo.messaging cd oslo.messaging git fetch https://review.openstack.org/openstack/oslo.messaging refs/changes/90/118790/2 git checkout FETCH_HEAD tox -repy34 # This should end with segfaulting test runners. Note if you don't have tox installed you will need to install version 1.7.2 or greater. `sudo pip install tox==1.7.2` will do this. [Regression Potential] The patch in question is small. If we go straight to python 3.4.1 the diff will be larger but that isn't necessary to fix this particular issue. The biggest regression potential would be that the garbage collector is newly broken by the this bug fix. Considering that the garbage collector is already broken and this patch comes with test cases to check it is less broken the risk of regression here is less than the pain of dealing with this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/oslo.messaging/+bug/1367907/+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 1365674] Re: On the swipe autopilot helpers, accept a default value for containers
** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid) Status: New = Fix Released -- 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/1365674 Title: On the swipe autopilot helpers, accept a default value for containers Status in Ubuntu UI Toolkit: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Bug description: We made public the swipe helpers as can be seen here: https://code.launchpad.net/~canonical-platform-qa/ubuntu-ui-toolkit/make_flickable_methods_public/+merge/229354 But some methods still receive a containers argument, that can be get only from a private helper. We need to make that argument optional, and if not passed, call get_containers to initialize it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1365674/+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 1359167] Re: test_edit_event_with_default_values gets stuck clearing description field
** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid) Status: New = Fix Released -- 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/1359167 Title: test_edit_event_with_default_values gets stuck clearing description field Status in Ubuntu Calendar App: Fix Released Status in Ubuntu UI Toolkit: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: Fix Released Bug description: No logs for this one unfortunately because it prevents the tests from completing. Basically what happens is that when this test tries to clear the description field, it selects the middle of the field, then the cursor does not move to the end of the text. Subsequently the logic used to delete the text gets stuck in an infinite loop. It looks like: while not field.empty: press delete field.empty will never be true because the cursor will always have text on the right hand side To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1359167/+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 1456697] Re: [Favorite contacts] First entered number dialed
Like march already mentioned: A workaround would be if the users are able to change the order of a the phone numbers of a contact (see bug #1469508). Then, the user can at least influence which number is used as favorites. Up to now it is always the first one. But which number is placed on top isn't deterministic. Another solution would be to open the address book's detail page if a favorite has more than one number. Then the user can select which number he likes to dial. But this increases the time and complexity for dialing a favorite number. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1456697 Title: [Favorite contacts] First entered number dialed Status in address-book-app: Confirmed Status in Ubuntu UX: New Status in address-book-app package in Ubuntu: Confirmed Bug description: There should be an option which number should be dialed when a favourite contact is chosen from Today's Scope. At the moment the first number entered in adress-book-app is shown (here: Tux@work). If a contact has more than one number you can edit the details but it would be more user friendly to get a checkbox (e.g. [*]) to define the number which should be dialed. Tux 123321 [ ] Work 123456 [ ] Mobile 654321[*] Home Another option could be the possibility to sort contact details in edit mode like sorting pages in Today Scope. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1456697/+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 1473714] Re: WPA Wlan Password Lost after one day
I'm using a Aquaris 4.5 where I can observe a similar behavior. When I'm leaving my house I disable WiFi and enable it again when coming home. The WiFi connection (WPA/WPA2 encryption) isn't automatically restored. The network isn't even displayed (maybe because my SSID isn't visible). After reentering the settings everything works fine. -- 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/1473714 Title: WPA Wlan Password Lost after one day Status in indicator-network package in Ubuntu: Confirmed Bug description: Hi Guys, hope this is the right Place. Device is Meizu MX4 ubuntu touch edition of course running the latest Update available OTA Upate. If i setup my wireless Lan one after arround one Day the Password Dialog Pops up again and i'm discconected. rebooting the device doesn't help. Right after the setting up the Network everything is working normal. I'm using a pretty long WPA Passphrase (45 Digits) with WPA2 and AES Encryption. reagard Stefan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1473714/+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 1466002] Re: Clock display not using the same format as the indicator
** Changed in: ubuntu-clock-app Status: New = Confirmed -- 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/1466002 Title: Clock display not using the same format as the indicator Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Triaged Bug description: Environment: mako on latest rc proposed (17.06.2015) Reproduce: 1. Set Norwegian locale 2. Open Clock App What happens: Clock app says 11.06 and the indicator says 11:06. What should have happened: Both should use the same format. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1466002/+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 1421559] Re: Should be able to snooze alarm using power button
** Summary changed: - Should be able to silence alarm using power button + Should be able to snooze alarm using power button -- 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/1421559 Title: Should be able to snooze alarm using power button Status in Ubuntu Clock App: Confirmed Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: New Bug description: krillin @rtm #16 Reproduce: 1. Set alarm 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface, wait until the screen goes black 3. Try to disable alarm What happens: You need to turn on screen, press OK on alarm What should have happened: I should be able to snooze the alarm using the power button—like on iOS and Android. Rationale: I set two alarms on weekdays, one at 07:07 and one at 09:07. When I wake up at 07:07 and go to school, the 09:07 alarm goes off during class. Removing the phone from my pocket, swiping, unlocking and dismissing the alarm, always takes about 3-4 rings. Also when someone forget phone in the office, then it will be no possibility to disable alarm. Related to bug 1340329. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1421559/+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 1390440] Re: Checkbox needs visual update
** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid) Status: New = Fix Released -- 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/1390440 Title: Checkbox needs visual update Status in Ubuntu UI Toolkit: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Bug description: The checkbox is too large compared to the UITK PSD on Dropbox. https://www.dropbox.com/sh/7fnssmbsyuc6c8l/AADiZ5i-pZbDcPaFBUKPmjaUa?dl=0 It also needs to use the icon from the theme, not the included png. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1390440/+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 1391617] Re: Untranslated label In Progress when upgrading system
** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid) Status: New = Fix Released -- 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/1391617 Title: Untranslated label In Progress when upgrading system Status in Canonical System Image: Fix Released Status in Ubuntu UI Toolkit: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu RTM: Fix Released Bug description: When there's a system upgrade, there is a progress bar with the label In Progress. This doesn't seem to be translated. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1391617/+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 1452348] Re: please drop build-dependency on g++-4.9
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Michael Zanetti (mzanetti) -- 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/1452348 Title: please drop build-dependency on g++-4.9 Status in unity8 package in Ubuntu: Confirmed Bug description: The unity8 package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1452348/+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 1473485] Re: [MIR] python-contextlib2
** Changed in: contextlib2 (Ubuntu) Status: Incomplete = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to contextlib2 in Ubuntu. https://bugs.launchpad.net/bugs/1473485 Title: [MIR] python-contextlib2 Status in contextlib2 package in Ubuntu: Fix Committed Bug description: [Availability] Currently in universe [Rationale] Dependency for Openstack Ceilometer liberty-1. [Security] No security history [Quality Assurance] Package works out of the box with no prompting. There are no major bugs in Ubuntu and there are no major bugs in Debian. Unit tests are run during build. [Dependencies] All are in main [Standards Compliance] FHS and Debian Policy compliant. [Maintenance] Simple python package that the Ubuntu Server Team will take care of. [Background] python-contextlib2 provides backports of features in the latest version of the standard library’s contextlib module to earlier Python versions such as Python 2.7. The module provides utilities for common tasks involving the with statement. https://contextlib2.readthedocs.org/en/latest/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/contextlib2/+bug/1473485/+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 1367850] Re: Parallel build is broken
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Fix Released -- 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/1367850 Title: Parallel build is broken Status in Ubuntu UI Toolkit: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: New Bug description: make -j option (# of job slots) for parallel execution is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1367850/+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 1369506] Re: Header and popup menus don't handle rotation correctly
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Fix Released -- 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/1369506 Title: Header and popup menus don't handle rotation correctly Status in gallery-app: Fix Released Status in Ubuntu UI Toolkit: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: New Bug description: Using rtm-40 on krillin - click on a photo - open one of the menu of the headerbar - rotate the device the popdown menu gets misplaced, rotating back the device in the previous orientation doesn't bring it back where it was either To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1369506/+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 1273462] Re: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists
** Description changed: [ impact ] Previously, init.d scripts that were replaced by upstart jobs had upstart-job symlink as a redirect in-place, which directed users at using upstart commands. Despite the good intentions, that never actually taught people about the correct interfaces. Now with the advent of co- installability of multiple init systems, users may have systemd, upstart, and sysv-init all installed on users system and have init.d scripts / upstart jobs / systemd units all available. To avoid any daubt, we should support executing /etc/init.d/ scripts which may call into upstart, or into systemd, or actually execute the script in question depending on whether there is native configuration for that particular job and which init system we are running under. [ test case ] Invoking init.d script should invoke upstart commands, for example: $ /etc/init.d/ssh status ssh start/running, process 4620 $ /etc/init.d/ssh stop stop: Rejected send message, 1 matched rules; type=method_call, sender=:1.2469694 (uid=1000 pid=3908 comm=stop ssh ) interface=com.ubuntu.Upstart0_6.Job member=Stop error name=(unset) requested_reply=0 destination=com.ubuntu.Upstart (uid=0 pid=1 comm=/sbin/init) $ sudo /etc/init.d/ssh stop ssh stop/waiting $ sudo /etc/init.d/ssh start ssh start/running, process 5373 $ sudo /etc/init.d/ssh restart ssh stop/waiting ssh start/running, process 5405 - Description:Ubuntu 13.10 Release:13.10 mysql-server-5.5: Installed: 5.5.35-0ubuntu0.13.10.1 Candidate: 5.5.35-0ubuntu0.13.10.1 Version table: *** 5.5.35-0ubuntu0.13.10.1 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.5.32-0ubuntu7 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages In Ubuntu 13.10, the Upstart job and the init.d script do not work properly. In previous versions, the init.d script was a symlink to the wrapper script around upstart (/lib/init/upstart-job). This conflict means that if the server was started using the init.d script, upstart does not recognize that the server is running and will attempt to start a second instance of mysqld. Also problematic is that if the upstart job is started using the service or start commands, the init.d script's stop function runs a mysql shutdown, but upstart simply restarts mysqld (because it's marked respawn in the upstart config). + + + Description: Ubuntu 14.04 + Release: 14.04 + mysql: mysql-server-5.5.43-0ubuntu0.14.04.1 + The problem in some setup was that the upgrade von 12.04 to 14.04 requres the adjustment of the InnoDB log size. Therefore the start of MySQL via upstart failed directly while the one via init started successfully and then failed as below. + r...@webserver01.kurt..ref:~# status mysql + mysql start/running, process 5866 + r...@webserver01.kurt..ref:~# /etc/init.d/mysql stop + * Stopping MySQL database server mysqld [ OK ] + r...@webserver01.kurt..ref:~# status mysql + mysql start/running, process 6101 + r...@webserver01.kurt..ref:~# /etc/init.d/mysql status + * /usr/bin/mysqladmin Ver 8.42 Distrib 5.5.43, for debian-linux-gnu on x86_64 + Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved. + Oracle is a registered trademark of Oracle Corporation and/or its + affiliates. Other names may be trademarks of their respective + owners. + Server version5.5.43-0ubuntu0.14.04.1-log + Protocol version 10 + ConnectionLocalhost via UNIX socket + UNIX socket /var/run/mysqld/mysqld.sock + Uptime: 7 sec + Threads: 1 Questions: 108 Slow queries: 0 Opens: 48 Flush tables: 1 Open tables: 41 Queries per second avg: 15.428 + r...@webserver01.kurt..ref:~# stop mysql + mysql stop/waiting + r...@webserver01.kurt..ref:~# /etc/init.d/mysql status + * MySQL is stopped. + + This is horrible. The status commands report the wrong status and the start/stop commands do not work. If our operators are not super careful, our orchestration and monitoring system will go wild, report the wrong status and/or perform continuous restarts of the system as they think the service is not running. So we also fix it in trusty. the result will looks as below: + ubuntu@maas:~/work/deb$ sudo start mysql + mysql start/running, process 8523 + ubuntu@maas:~/work/deb$ sudo status mysql + mysql start/running, process 8523 + ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql stop + mysql stop/waiting + ubuntu@maas:~/work/deb$ sudo status mysql + mysql stop/waiting + ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql status + mysql stop/waiting + + + [Regression Potential] + + * None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is
[Touch-packages] [Bug 1475462] [NEW] Unity overrides refresh rate setting
Public bug reported: After installing the proprietary Nvidia drivers and then using the included Nvidia X Server Settings utility to manually set the resolution to 1920x1080 and the refresh rate to 144Hz (I have a 144Hz monitor), Unity still seems to move at the default f/s cap, which also limits the f/s in non-fullscreen games, including borderless window games. Setting the refresh rate in Compiz Configuration Settings Manager seems to have no affect. Also, on booting up the machine, the refresh rate setting gets overridden and reset to the default. For anyone with a high refresh rate monitor, this makes the Unity desktop environment a no-go. KDE and XFCE do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity (not installed) ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 16 18:41:37 2015 InstallationDate: Installed on 2015-06-23 (23 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1475462 Title: Unity overrides refresh rate setting Status in unity package in Ubuntu: New Bug description: After installing the proprietary Nvidia drivers and then using the included Nvidia X Server Settings utility to manually set the resolution to 1920x1080 and the refresh rate to 144Hz (I have a 144Hz monitor), Unity still seems to move at the default f/s cap, which also limits the f/s in non-fullscreen games, including borderless window games. Setting the refresh rate in Compiz Configuration Settings Manager seems to have no affect. Also, on booting up the machine, the refresh rate setting gets overridden and reset to the default. For anyone with a high refresh rate monitor, this makes the Unity desktop environment a no-go. KDE and XFCE do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity (not installed) ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 16 18:41:37 2015 InstallationDate: Installed on 2015-06-23 (23 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1475462/+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 1467743] Re: Lots of thumbnail requests with invalid size
We made a last-minute change to treat invalid QSize requests as 128x128, so the -1, -1 requests no longer show up in dubs.log. However, if you look in ~.cache/upstart/application-click- com.ubuntu.gallery_gallery_2.9.1.1209.log, you'll see tons and tons of invalid QSize requests. We are planning on returning an error for these soonish, so it would be good to pass the correct QSize for each thumbnail. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1467743 Title: Lots of thumbnail requests with invalid size Status in Canonical System Image: New Status in gallery-app package in Ubuntu: New Status in thumbnailer package in Ubuntu: New Bug description: When using the ballery app, the thumbnailer gets loads of requests with QSize(-1,-1), for example, when opening the gallery app. The problem with this is that the thumbnailer interprets this to mean give me the largest size you can (limited to a 1920x1920 bounding box). That's very expensive, especially in terms of disk space, because that 1920 thumbnail ends up going into the cache, needlessly hogging space. We are about to add a qWarning message to the QML side that reports invalid QSize requests. For now, we are going to retain the old behavior, but this will turn into an error soon. The most effective way to use the thumbnailer is to simply ask for an image in the desired size, with neither width nor height of -1. The thumbnailer will efficiently produce a thumbnail for that. (We do lots of internal caching to avoid extracting or downloading a thumbnail unnecessarily.) The thumbnailer may deliver a thumbnail that is smaller than what was asked for (because it never up-scales) so, if asked for a thumbnail of size 256, it's guaranteed not to be larger, but might be smaller (if the original image is smaller than what was asked for). Could you please adjust the gallery app behavior to ask for specific, valid sizes only? Running a tail -f on ~/.cache/upstart/dbus.log allows you to see the requests as they are made. Each request shows the size that was asked for. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1467743/+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 1453282] Re: [Neither headphones nor speakers are displayed under All Settings-Sound, VIA VT1718S, Green Headphone Out, Front] No sound at all
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete = Expired -- 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/1453282 Title: [Neither headphones nor speakers are displayed under All Settings-Sound, VIA VT1718S, Green Headphone Out, Front] No sound at all Status in pulseaudio package in Ubuntu: Expired Bug description: The motherboard speakers and microphone aren't listed under All Settings-Sound UNLESS I unplug them and then plug them back in. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username 11102 F pulseaudio /dev/snd/pcmC1D0c: username 11102 F...m pulseaudio /dev/snd/controlC1: username 11102 F pulseaudio /dev/snd/timer: username 11102 f pulseaudio CurrentDesktop: Unity Date: Fri May 8 16:09:24 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-07 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., VIA VT1718S, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H55M Pro dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd08/06/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1453282/+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 1437599] Re: Monitor is flickering at higher resolution 1366x768 but not in lower resolution like 1024x768
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1437599 Title: Monitor is flickering at higher resolution 1366x768 but not in lower resolution like 1024x768 Status in xorg package in Ubuntu: Expired Bug description: $dmesg | grep -i 'Graphic\|video\|VGA\|error\|fail' [0.102507] DMAR: Disabling IOMMU for graphics on this chipset [0.113036] vgaarb: setting as boot device: PCI::00:02.0 [0.113036] vgaarb: device added: PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none [0.113036] vgaarb: loaded [0.113036] vgaarb: bridge control possible :00:02.0 [0.134634] pci :00:02.0: Video device with shadowed ROM [0.535561] fb0: VESA VGA frame buffer device [0.561694] ACPI Error: Method parse/execution failed [\_SB_.PCI0.IDE1.GTM_] (Node 8800b8665230), AE_AML_PACKAGE_LIMIT (20131115/psparse-536) [0.561700] ACPI Error: Method parse/execution failed [\_SB_.PCI0.IDE1.CHN1._GTM] (Node 8800b86650f0), AE_AML_PACKAGE_LIMIT (20131115/psparse-536) [0.561705] ata4: ACPI get timing mode failed (AE 0x300b) [2.204028] psmouse serio1: Failed to enable mouse on isa0060/serio1 [ 20.745886] video: module verification failed: signature and/or required key missing - tainting kernel [ 21.424428] [drm] Memory usable by graphics device = 2048M [ 21.424434] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver [ 21.468204] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 21.654572] ACPI Exception: AE_NOT_FOUND, Evaluating _DOD (20131115/video-1279) [ 21.654575] ACPI: Video Device [GFX0] (multi-head: no rom: yes post: no) [ 21.654779] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input10 [ 34.595029] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro [ 44.670868] init: failsafe main process (690) killed by TERM signal ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Mar 28 15:06:36 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: i915-3.16-3.13, 1, 3.13.0-32-generic, x86_64: installed i915-3.16-3.13, 1, 3.13.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:d613] InstallationDate: Installed on 2015-02-22 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-generic root=UUID=33fb99a7-bac5-4585-95ce-c8f970c62c99 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: RQG4110H.86A.0017.2011.0322.1523 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41RQ dmi.board.vendor: Intel Corporation dmi.board.version: AAE54511-205 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRQG4110H.86A.0017.2011.0322.1523:bd03/22/2011:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-205:cvn:ct3:cvr: version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911-0intel1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Mar 28 14:51:41 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 53306 vendor DEL xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug
[Touch-packages] [Bug 1455833] Re: Missing essential package
[Expired for qtdeclarative-opensource-src (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: Incomplete = Expired -- 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/1455833 Title: Missing essential package Status in qtdeclarative-opensource-src package in Ubuntu: Expired Bug description: Virtual package qtdeclarative-abi-5-2-1 dissappeared from libqt5qml5 (5.2.1-3ubuntu15) and a huge quantity of libs are depending on it. Let's solve this, please answer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1455833/+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 1455977] Re: Letter missing in Latvian keymap
[Expired for xkeyboard-config (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xkeyboard-config (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1455977 Title: Letter missing in Latvian keymap Status in xkeyboard-config package in Ubuntu: Expired Bug description: After installation of 14.04LTS I noticed a letter in Latvian keymap missing. When typed AltGray (Right-Alt) + E it should give out ē, but types €. Capital Ē is typed correctly by typing AltGr+Shift+E. Please correct because it is very annoying not to be able to type a character, one of the frequently necessary ones. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1455977/+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 1430918] Re: Change setting requires manual refresh
Closing this because this was fixed by https://code.launchpad.net/~stolowski/unity-scopes-api/fix-settings- thread ** Changed in: unity-scopes-api (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1430918 Title: Change setting requires manual refresh Status in Canonical System Image: In Progress Status in The Savilerow project: Invalid Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Invalid Bug description: See comment 12 below for updated description. Summary is that changing a setting can require manual refresh. Original Description: Enabling and disabling child scopes from settings in an agg scope often causes an error that results in blank display that is sometimes difficult to recover from. For example, l launched the Music scope, then disabled 7 digital from settings, then enabled it. I got the following in log: phablet@ubuntu-phablet:~$ tail -F .cache/upstart/scope-registry.log Failed to get proxy for scope com.ubuntu.scopes.soundcloud_soundcloud Failed to get proxy for scope com.canonical.scopes.songkick_songkick aa_getcon failed, errno = 13 YouTube scope is unauthenticated YouTube scope is unauthenticated Failed to get proxy for scope com.ubuntu.scopes.soundcloud_soundcloud Failed to get proxy for scope com.canonical.scopes.songkick_songkick YouTube scope is unauthenticated YouTube scope is unauthenticated terminate called without an active exception I have seen this same thing with other agg scopes. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 127 device name: krillin channel: ubuntu-touch/vivid-proposed last update: 2015-03-10 22:34:24 version version: 127 version ubuntu: 20150228 version device: 20150210-95b6a9f version custom: 20150228 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1430918/+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 1470700] Re: QNetworkAccessManager hangs when in flight mode
I can't really test this as is. The problem is that, to test it, I need the new thumbnailer from silo 10, but the ppa includes the old thumbnailer. I can't easily get the new thumbnailer onto the device because Jenkins builds for Wily, not Vivid. Not sure what I can do for the moment. To test that networkAccessible() thing really is fixed, put the device into flight mode, and it should return zero. If the device isn't in flight mode, it should report that the network is accessible (even before sending the first request). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1470700 Title: QNetworkAccessManager hangs when in flight mode Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in thumbnailer package in Ubuntu: New Bug description: When my phone is in flight mode, HTTP requests made using QNetworkAccessManager seem to hang rather than erroring out immediately. From my tests, it looks like the HTTP request is blocked until the flight mode is disabled and a network connection is reestablished. This is contrary to the documentation, which states: If the network is not accessible the network access manager will not process any new network requests, all such requests will fail with an error. Requests with URLs with the file:// scheme will still be processed. http://doc.qt.io/qt-5/qnetworkaccessmanager.html#networkAccessible- prop By running strace on my test program, it doesn't even look like it attempts to open a TCP connection when blocked in flight mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1470700/+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 1474958] Re: bind mount produces incorrect entry in mtab
This is intentional. /etc/mtab has gone the way of the dodo and is now just a symlink to /proc/mounts. Bind mount origin information is no longer tracked on purpose, as there is no distinction between the bind mount and the original mount; both are equally valid, and neither is subordinate to the other. ** Changed in: util-linux (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1474958 Title: bind mount produces incorrect entry in mtab Status in util-linux package in Ubuntu: Invalid Bug description: Ubuntu 15.04 mount: Installed: 2.25.2-4ubuntu2 Candidate: 2.25.2-4ubuntu2 Version table: *** 2.25.2-4ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status System has LVM on SSD standard install ext4 filesystem. (/dev/mapper/ubuntu--vg-root) mdadm RAID5 3 disks, btrfs filesystem (/dev/md127p1) RAID5 is mounted at /mnt/raid at boot. --- Bind mounts only display the device mount, not the from directory. The mount works, but the mtab entry is incorrect. # From LVM device, to LVM device. mount -o bind /home/rfoos /srv/nfs4/homes # From Raid device, to LVM device mount -o bind /mnt/raid/var/lib/libvirt /var/lib/libvirt # With corrected fstab entries (below) mount -a does work mount -a --- /etc/mtab entries /dev/mapper/ubuntu--vg-root /srv/nfs4/homes ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 /dev/md127p1 /var/lib/libvirt btrfs rw,nosuid,nodev,relatime,space_cache 0 0 /dev/md127p1 /srv/nfs4/share btrfs rw,nosuid,nodev,relatime,space_cache 0 0 --- mount list of mounts /dev/md127p1 on /mnt/raid type btrfs (rw,nosuid,nodev,relatime,space_cache) /dev/md127p1 on /var/lib/libvirt type btrfs (rw,nosuid,nodev,relatime,space_cache) /dev/mapper/ubuntu--vg-root on /srv/nfs4/homes type ext4 (rw,relatime,errors=remount-ro,data=ordered) --- corrected fstab entries. # mount raid device /dev/md127p1 /mnt/raid btrfs rw,nosuid,nodev,relatime,space_cache 0 0 # corrected entries /mnt/raid/var/lib/libvirt /var/lib/libvirt none bind 0 0 /home/rfoos /srv/nfs4/homes none bind 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1474958/+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 1273462] Re: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists
@Edward, I tested above trusty.debdiff, but I found the constraint Replaces: upstart ( 1.12.1-0ubuntu8) Breaks: upstart ( 1.12.1-0ubuntu8) prevents installing lsb-base package. error logs pls refer the link [1], so I remove them. I will upload trusty_v2.debdiff. Then I built a local deb binary lsb package and test, it looks good to me, the test result pls refer the link [2]. [1], https://pastebin.canonical.com/135504/ [2], https://pastebin.canonical.com/135505/ ** Patch added: trusty_v2.debdiff https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+attachment/4430332/+files/trusty_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1273462 Title: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists Status in lsb package in Ubuntu: Fix Released Status in mysql-5.5 package in Ubuntu: Invalid Status in upstart package in Ubuntu: Fix Released Status in lsb source package in Trusty: Confirmed Status in mysql-5.5 source package in Trusty: Invalid Status in upstart source package in Trusty: Won't Fix Status in lsb source package in Utopic: Fix Released Status in mysql-5.5 source package in Utopic: Invalid Status in upstart source package in Utopic: Fix Released Status in upstart package in Debian: New Bug description: [ impact ] Previously, init.d scripts that were replaced by upstart jobs had upstart-job symlink as a redirect in-place, which directed users at using upstart commands. Despite the good intentions, that never actually taught people about the correct interfaces. Now with the advent of co-installability of multiple init systems, users may have systemd, upstart, and sysv-init all installed on users system and have init.d scripts / upstart jobs / systemd units all available. To avoid any daubt, we should support executing /etc/init.d/ scripts which may call into upstart, or into systemd, or actually execute the script in question depending on whether there is native configuration for that particular job and which init system we are running under. [ test case ] Invoking init.d script should invoke upstart commands, for example: $ /etc/init.d/ssh status ssh start/running, process 4620 $ /etc/init.d/ssh stop stop: Rejected send message, 1 matched rules; type=method_call, sender=:1.2469694 (uid=1000 pid=3908 comm=stop ssh ) interface=com.ubuntu.Upstart0_6.Job member=Stop error name=(unset) requested_reply=0 destination=com.ubuntu.Upstart (uid=0 pid=1 comm=/sbin/init) $ sudo /etc/init.d/ssh stop ssh stop/waiting $ sudo /etc/init.d/ssh start ssh start/running, process 5373 $ sudo /etc/init.d/ssh restart ssh stop/waiting ssh start/running, process 5405 Description:Ubuntu 13.10 Release:13.10 mysql-server-5.5: Installed: 5.5.35-0ubuntu0.13.10.1 Candidate: 5.5.35-0ubuntu0.13.10.1 Version table: *** 5.5.35-0ubuntu0.13.10.1 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.5.32-0ubuntu7 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages In Ubuntu 13.10, the Upstart job and the init.d script do not work properly. In previous versions, the init.d script was a symlink to the wrapper script around upstart (/lib/init/upstart-job). This conflict means that if the server was started using the init.d script, upstart does not recognize that the server is running and will attempt to start a second instance of mysqld. Also problematic is that if the upstart job is started using the service or start commands, the init.d script's stop function runs a mysql shutdown, but upstart simply restarts mysqld (because it's marked respawn in the upstart config). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1273462/+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 1462033] Re: [testsfail] NestedInput.nested_event_filter_receives_keyboard_from_host failure in CI
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1462033 Title: [testsfail] NestedInput.nested_event_filter_receives_keyboard_from_host failure in CI Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: https://jenkins.qa.ubuntu.com/job/mir-wily-amd64-ci/166/consoleFull 7: [ RUN ] NestedInput.nested_event_filter_receives_keyboard_from_host 7: [1433432727.674278] mirserver: Starting 7: [1433432727.675137] mirserver: Selected driver: dummy (version 0.14.0) 7: [1433432727.679338] mirserver: Using software cursor 7: [1433432727.681407] mirserver: Mir version 0.14.0 7: [1433432727.732641] mirserver: Starting 7: [1433432727.733449] mirserver: Selected driver: dummy (version 0.14.0) 7: [1433432727.894537] mirserver: Mir version 0.14.0 7: [1433432738.076193] mirserver: Stopping 7: /tmp/buildd/mir-0.14.0bzr2624pkg0wily166/tests/acceptance-tests/test_nested_input.cpp:149: Failure 7: Actual function call count doesn't match EXPECT_CALL(*nested_mir.mock_event_filter, handle(_))... 7: Expected: to be called at least once 7: Actual: never called - unsatisfied and active 7: [1433432738.154764] mirserver: Stopping 7: [ FAILED ] NestedInput.nested_event_filter_receives_keyboard_from_host (10518 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1462033/+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 1464174] Re: [regression] Touch input does not work at all any more
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1464174 Title: [regression] Touch input does not work at all any more Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: Compiling the latest Mir code (lp:mir series 0.14) none of the demos respond to touch. However compiling the stable maintenance branches lp:mir/0.12 or lp:mir/0.13 do work and demos get touch events. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1464174/+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 1465669] Re: Repeat input events keep being emitted even when user switches to different VT
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1465669 Title: Repeat input events keep being emitted even when user switches to different VT Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Repeat input events keep being emitted even when user switches to different VT. To reproduce: 1. Add a print statement in the VT filter handle function 2. Switch to another VT. 3. See repeat key events still being emitted and handled by the VT filter. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1465669/+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 1391976] Re: Loading libmirclient.so twice leads to a segfault in libmirprotobuf.so
** Branch linked: lp:ubuntu/wily-proposed/mir
--
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/1391976
Title:
Loading libmirclient.so twice leads to a segfault in libmirprotobuf.so
Status in Mir:
Fix Committed
Status in Mir 0.14 series:
Fix Committed
Status in mir package in Ubuntu:
Triaged
Bug description:
Can be reproduced with: load_twice libmircommon.so.1 (or .2)
For recent versions of mir use: load_twice libmirclient.so.X (currently .8)
load_twice.c:
#include stdio.h
#include dlfcn.h
int main(int argc, char** argv)
{
void *dl;
int i;
for (i = 0; i 2; i++)
{
dl = dlopen (argv[1], RTLD_LAZY);
printf (%d open dl: %p\n, i, dl);
if (dl)
dlclose (dl);
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1391976/+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 1461312] Re: client API version has wrong version
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1461312 Title: client API version has wrong version Status in Mir: Fix Committed Status in Mir 0.13 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: client API was broken in mir 0.13.0/mir 0.13.1 but the client API version was not updated in include/client/mir_toolkit/version.h To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1461312/+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 1451309] Re: [arale] Software cursor appears slightly corrupt on arale (black spots in place of white)
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1451309 Title: [arale] Software cursor appears slightly corrupt on arale (black spots in place of white) Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: [arale] Software cursor appears slightly corrupt on arale (black spots in place of white) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1451309/+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 1465585] Re: Stopping input in a nested server stops VT switching
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1465585 Title: Stopping input in a nested server stops VT switching Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Initially found by accident when encountering lp:1464690 (which deadlocks input in the nested server) The Ctrl+Alt+Fn combinations (which should be handled by the host) stop working. But ssh - chvt n still works. I saw the same by having the nested server stopped in gdb (and the problem disappeared when resumed). To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1465585/+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 1466594] Re: failure in CI in BufferStreamArrangement.arrangements_are_applied
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1466594 Title: failure in CI in BufferStreamArrangement.arrangements_are_applied Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Failure in CI on unrelated branch: https://jenkins.qa.ubuntu.com/job/mir-wily-amd64-autolanding/125/consoleFull I haven't been able to reproduce locally. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1466594/+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 1381330] Re: mesa platform is no longer accurate and needs renaming
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1381330 Title: mesa platform is no longer accurate and needs renaming Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Our mesa code and packages mostly represents support for DRM/DRI output. And the only use case for this till now also used Mesa for the libGL* implementation. This is no longer true however. With Nvidia and AMD soon to release DRM support in their proprietary drivers, we will be supporting them. These drivers will provide DRM display access, but as usual will probably provide their own custom libGL* implementations. So won't use Mesa. This should work for Mir. However when a vendor provides their own libGL*, we are technically no longer using Mesa at all. We will still be using the mesa code path in Mir though. So that all needs renaming to something more accurate like drm or dri etc. Not mesa. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1381330/+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 1465231] Re: CI failure in TestClientInput.clients_receive_many_button_events_inside_window
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1465231 Title: CI failure in TestClientInput.clients_receive_many_button_events_inside_window Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: CI failure in TestClientInput.clients_receive_many_button_events_inside_window as seen in: https://jenkins.qa.ubuntu.com/job/mir-wily- amd64-autolanding/99/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1465231/+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 1425043] Re: Thumbnails are returned one by one to QML thus already existing thumbnails can be blocked
** Changed in: thumbnailer Status: Fix Committed = Fix Released -- 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/1425043 Title: Thumbnails are returned one by one to QML thus already existing thumbnails can be blocked Status in Thumbnailer: Fix Released Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src package in Ubuntu RTM: Fix Released Bug description: Thumbnail requests made via the QML thumbnailer image provider are enqueued and processed one by one which has some nasty UX consequences: 1) if a thumbnail already exists it won't be returned immediately if other thumbnails are ahead in the queue 2) video thumbnails are much slower to be generated so if one is being generated, all other thumbnails are blocked until it finishes This issue would be alleviated if not for https://bugreports.qt.io/browse/QTBUG-37988 But even with the Qt bug fixed, 1) would still be an important issue in many cases To manage notifications about this bug go to: https://bugs.launchpad.net/thumbnailer/+bug/1425043/+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 1381713] Re: Support policy query interface for file
** Changed in: thumbnailer 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/1381713 Title: Support policy query interface for file Status in AppArmor: Triaged Status in Media Hub: New Status in mediascanner2: New Status in Thumbnailer: Fix Released Status in apparmor package in Ubuntu: Fix Committed Bug description: This bug tracks the work needed to support querying if a label can access a file. This is particularly useful with trusted helpers where an application requests access to a file and the trusted helper does something with it. For example, on Ubuntu when an app wants to play a music file, it (eventually) goes through the media-hub service. The media-hub service should be able to query if the app's policy has access to the file. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1381713/+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 1475458] [NEW] Xorg freeze
Public bug reported: Xorg completely frozen; must do REISUB in order to complete restart. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Jul 16 21:44:25 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-22-generic, x86_64: installed vboxhost, 4.3.30, 3.19.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00fa] MachineType: Apple Inc. MacBookPro9,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=facc7685-e5cd-460d-9856-3c8db9be0327 ro splash quiet vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D3.B0B.1506081214 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B0B.1506081214:bd06/08/2015:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.name: MacBookPro9,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Jul 10 10:16:49 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40135 vendor APP xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1475458 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Xorg completely frozen; must do REISUB in order to complete restart. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Jul 16 21:44:25 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-22-generic, x86_64: installed vboxhost, 4.3.30, 3.19.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00fa] MachineType: Apple Inc. MacBookPro9,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=facc7685-e5cd-460d-9856-3c8db9be0327 ro splash quiet vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D3.B0B.1506081214 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias:
[Touch-packages] [Bug 1297144] Re: [Lenovo ThinkPad X230] Invisible cursor after resume from suspend
I have the same problem on Asus X73B with Linux Mint 17.1, Did another fresh install and the problem is still there. When having lock screen with screen saver, cursor is visible, but when I resume without it - no cursor. Also it happens only when closing lid, not when suspending manually. The laptop is for elderly, not technical person so any lock screens with passwords or other workarounds are not solution for me. The only way to avoid it at this point is to set computer to do nothing when lid closes. The same effect is with unistalling power management. Tried gnome power manager but after install I saw no settings for it and I couldn't find it in start menu and the whole package seemed to be not there, although in program manager it showed as installed. Anyway, I didn't found a viable solution. It's a serious bug, a show stopper for laptop users and it affects all ubuntu family systems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1297144 Title: [Lenovo ThinkPad X230] Invisible cursor after resume from suspend Status in xorg package in Ubuntu: Expired Bug description: I am using the daily build of Xubuntu 14.04 x64 on a Lenovo Thinkpad x230. If I wake up the computer after it spending some time in the suspend state, the cursor will be invisible. The courser still works (I can click on stuff and hover the invisible cursor over stuff), but the little arrow is not visible. This bug showed up a few days ago after an update. Putting the computer back in suspend state and immediately waking it back up resolves the issue until the next time the computer is put in suspend state for an extended period of time. It is possible that this bug has something to do with Whisker Menu. Sometimes when the courser is invisible it will still show up over Whisker Menu. Most of the time it is invisible there too. Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 xfdesktop version 4.11.4, running on Xfce 4.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1297144/+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 1303962] Re: please integrate mediascanner2 and media-hub with apparmor
** Changed in: thumbnailer
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-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1303962
Title:
please integrate mediascanner2 and media-hub with apparmor
Status in Media Hub:
Fix Committed
Status in Thumbnailer:
Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu:
Fix Released
Status in mediascanner2 package in Ubuntu:
Fix Released
Bug description:
media-hub and mediascanner are separate processes from apps and are
used to play and scan music and video files respectively. Up until
now, apps would have to use the music_files_read or video_files_read
reserved policy groups to access media. The problem is, these policy
groups are reserved and not available to normal AppStore apps in order
to prevent information leaks (this user has this video installed) and
theft (can access the music and video directly). The path forward is
that media-hub and mediascanner are helpers that apps can use and they
should integrate with the trust store.
AppStore apps:
1. should be able to access their own content (installed or local)
2. should not be able to access, play or otherwise enumerate other apps'
media (ie, app 'foo' should not be able to play the facebook app's sound file
3. AppStore apps should be able to enumerate the global music (~/Music) and
video (~/Video) library via the mediascanner helper with permission from the
user
4. AppStore apps should be able to play the global music (~/Music) and video
(~/Video) library via the media-hub with permission from the user
5. AppStore apps should be able to have access to media files with
permission from the user. This is already handled by the content-hub paradigm
(though someone would need to add a media content provider for the content-hub
to have this work)
Both media-hub and mediascanner should do something like the below
pseudo code:
# see 'man aa_getcon()' from libapparmor-dev for more info
# conn_name is the unique D-Bus connection name of the application connecting
# to media-hub/mediascanner
apparmor_profile =
org.freedesktop.DBus.GetConnectionAppArmorSecurityContext(conn_name)
pkgname = apparmor_profile.split('_')[0]
if apparmor_profile == unconfined: # unconfined apps can access all the files
allow access
elif playback_file in ~/.local/share/$pkgname/... or playback_file in
~/.cache/$pkgname/..: # apps can access their own files
allow access
elif $pkgname can access playback_file in trust store: # apps can access the
files if user said so previously
allow access
elif playback_file in ~/Music:
answer = prompt user for access to global music files
if $answer == yes
update trust store for $pkgname can enumerate/play ~/Music
allow access
else:
deny access
elif playback_file in ~/Videos:
answer = prompt user for access to global video files
if $answer == yes
update trust store for $pkgname can enumerate/play ~/Videos
allow access
else:
deny access
else:
deny access
To have the best user experience and prevent multiple prompting,
mediascanner and media-hub should use the same trust store database.
I'm not sure that mediascanner2 offers a DBus API for enumerating
global media files yet or not (music-app seems to be accessing files
in ~/.cache/media-art/ and ~/.cache/mediascanner directly).
UPDATE: 2014-05-02
media-hub implemented '1' and '2' already (can access its own data, but not
other apps' data) and was marked Fix Released. Trust store integration ('3' and
'4') is now being tracked in bug #1315381.
mediascanner2 still needs to implement '1' and '2'. The 'audio' and
'video' policy groups will *not* add this access at this time.
Instead, apps can use 'read_path' as part of their policy to have
access to the mediascanner files. This is workable for the music app,
but will block other apps from inclusion in the app store.
To manage notifications about this bug go to:
https://bugs.launchpad.net/media-hub/+bug/1303962/+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 1474773] Re: Mir 0.14 bumps mirplatform ABI to 8 but symbols still versioned as MIRPLATFORM_7
Too late to fix in the 0.14 series. And this is not something that can be done in a point release like 0.14.1 either. ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir/0.14 Status: Triaged = Won't Fix ** Changed in: mir/0.14 Milestone: 0.14.0 = None -- 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/1474773 Title: Mir 0.14 bumps mirplatform ABI to 8 but symbols still versioned as MIRPLATFORM_7 Status in Mir: In Progress Status in Mir 0.14 series: Won't Fix Status in mir package in Ubuntu: New Bug description: Mir 0.14 bumps mirplatform ABI to 8 but symbols still versioned as MIRPLATFORM_7 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474773/+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 1469626] Re: Xorg freeze after [mi] EQ overflowing.
Sorry, Christopher, for misspelling your name! Found a bug with the same nouaveau signature - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444072 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1469626 Title: Xorg freeze after [mi] EQ overflowing. Status in xorg package in Ubuntu: Incomplete Bug description: Xorg freezes after logging in leaving some messages in Xorg.log about [mi] EQ overflowing. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jun 29 11:00:23 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.16.0-41-generic, x86_64: installed virtualbox, 4.3.26, 3.19.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation NV44 [GeForce 7100 GS] [10de:016a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:0273] InstallationDate: Installed on 2015-04-01 (88 days ago) InstallationMedia: SARDU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=a01d7e4a-9180-4f73-b6f6-b5fb1c9f94a6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: BX97510J.86A.1487.2007.0902.1724 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D975XBX dmi.board.vendor: Intel Corporation dmi.board.version: AAD27094-306 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBX97510J.86A.1487.2007.0902.1724:bd09/02/2007:svn:pn:pvr:rvnIntelCorporation:rnD975XBX:rvrAAD27094-306:cvn:ct2:cvr: version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Jun 29 10:14:37 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputSleep Button KEYBOARD, id 7 inputNOVATEK USB Keyboard KEYBOARD, id 8 inputNOVATEK USB Keyboard KEYBOARD, id 9 inputPS/2+USB Mouse MOUSE, id 10 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1469626/+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 1475434] Re: ipvlan module causes kernel crashes (backport fixes from upstream)
Got the wrong package initially. ** Package changed: iproute2 (Ubuntu) = linux-meta-lts-vivid (Ubuntu) ** Description changed: - Kernel version 3.19, currently being used an the vivid LTS kernel, + Kernel version 3.19, currently being used as the vivid LTS kernel, includes support for ipvlan. But at its current state it is unusable as simply removing an interface with an ip address attached will cause a kernel crash. The fix is already upstream: https://github.com/torvalds/linux/commit/27705f7085ce2e124fac4c280ce824962cc90bb6 Reproducing this is easy (requires a recent version of iproute2, with support for ipvlan, such as the one in debian/experimental): ip netns add ns0 ip link add link eth0 ipvl0 type ipvlan mode L3 ip link set dev ipvl0 netns ns0 ip netns exec ns0 bash ip link set dev ipvl0 up ip -4 addr add 192.168.0.10/24 dev ipvl0 ip link del dev ipvl0 The last line will cause a kernel crash, with a calltrace that looks like this: https://gist.github.com/fabiokung/b360cb2f3bdf2fb36c8b Can we get the fixes backported to the 3.19 LTS kernel from vivid? Ideally we would like to have the whole patchset backported: https://github.com/torvalds/linux/commit/d91e9015c78af1dc1f8ac4fdcf6118dbc2401668 and https://github.com/torvalds/linux/commit/8172ba51e257fdd353010cd7caaa37c8bc9eb44a -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1475434 Title: ipvlan module causes kernel crashes (backport fixes from upstream) Status in linux package in Ubuntu: Incomplete Bug description: Kernel version 3.19, currently being used as the vivid LTS kernel, includes support for ipvlan. But at its current state it is unusable as simply removing an interface with an ip address attached will cause a kernel crash. The fix is already upstream: https://github.com/torvalds/linux/commit/27705f7085ce2e124fac4c280ce824962cc90bb6 Reproducing this is easy (requires a recent version of iproute2, with support for ipvlan, such as the one in debian/experimental): ip netns add ns0 ip link add link eth0 ipvl0 type ipvlan mode L3 ip link set dev ipvl0 netns ns0 ip netns exec ns0 bash ip link set dev ipvl0 up ip -4 addr add 192.168.0.10/24 dev ipvl0 ip link del dev ipvl0 The last line will cause a kernel crash, with a calltrace that looks like this: https://gist.github.com/fabiokung/b360cb2f3bdf2fb36c8b Can we get the fixes backported to the 3.19 LTS kernel from vivid? Ideally we would like to have the whole patchset backported: https://github.com/torvalds/linux/commit/d91e9015c78af1dc1f8ac4fdcf6118dbc2401668 and https://github.com/torvalds/linux/commit/8172ba51e257fdd353010cd7caaa37c8bc9eb44a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475434/+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 1362548] Re: Migrate from EDS to Dbus to improve performance
** Description changed: Evolution Data Server should be replaced with dbus. Right now it is man in the middle which hits performance, Clock App-EDS-Indicator-datetime. - Wn 16.04, we are removing the middle man EDS from the equation + In 16.04, we are removing the middle man EDS from the equation so alarms created will appear instantly in the indicator and other improvements https://developer.ubuntu.com/en/blog/2015/04/15/retrospective-and- roadmap-ui-toolkit/ Just to note that this is also noticeable in the calendar app. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1362548 Title: Migrate from EDS to Dbus to improve performance Status in Ubuntu Clock App: Triaged Status in qtorganizer5-eds package in Ubuntu: Confirmed Bug description: Evolution Data Server should be replaced with dbus. Right now it is man in the middle which hits performance, Clock App-EDS-Indicator-datetime. In 16.04, we are removing the middle man EDS from the equation so alarms created will appear instantly in the indicator and other improvements https://developer.ubuntu.com/en/blog/2015/04/15/retrospective-and- roadmap-ui-toolkit/ Just to note that this is also noticeable in the calendar app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1362548/+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 1362548] Re: Alarms take several seconds to save (~5seconds) which is quite long compared to existing solutions
** Description changed: This is something I have noticed on several occasions that alarms take a long time (~5 seconds or higher to save). This issue isn't new and has been there for a while. Just to note that this is also noticeable in the calendar app. + + [COMMENT] + Most propably it caused by U1DB database storage. Migration to local storage should resolve this issue. ** Description changed: This is something I have noticed on several occasions that alarms take a long time (~5 seconds or higher to save). This issue isn't new and has been there for a while. Just to note that this is also noticeable in the calendar app. - - [COMMENT] - Most propably it caused by U1DB database storage. Migration to local storage should resolve this issue. ** Summary changed: - Alarms take several seconds to save (~5seconds) which is quite long compared to existing solutions + Migrate from EDS to dbus ** Description changed: - This is something I have noticed on several occasions that alarms take a - long time (~5 seconds or higher to save). This issue isn't new and has - been there for a while. + Evolution Data Server should be replaced with dbus. Right now it is man in the middle which hits performance, Clock App-EDS-Indicator-datetime. + Wn 16.04, we are removing the middle man EDS from the equation + so alarms created will appear instantly in the indicator and other improvements Just to note that this is also noticeable in the calendar app. ** Summary changed: - Migrate from EDS to dbus + Migrate from EDS to dbus to improve performance ** Changed in: ubuntu-clock-app Importance: High = Low ** Changed in: ubuntu-clock-app Status: Confirmed = Triaged ** Description changed: Evolution Data Server should be replaced with dbus. Right now it is man in the middle which hits performance, Clock App-EDS-Indicator-datetime. Wn 16.04, we are removing the middle man EDS from the equation so alarms created will appear instantly in the indicator and other improvements + https://developer.ubuntu.com/en/blog/2015/04/15/retrospective-and- + roadmap-ui-toolkit/ + Just to note that this is also noticeable in the calendar app. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1362548 Title: Migrate from EDS to Dbus to improve performance Status in Ubuntu Clock App: Triaged Status in qtorganizer5-eds package in Ubuntu: Confirmed Bug description: Evolution Data Server should be replaced with dbus. Right now it is man in the middle which hits performance, Clock App-EDS-Indicator-datetime. In 16.04, we are removing the middle man EDS from the equation so alarms created will appear instantly in the indicator and other improvements https://developer.ubuntu.com/en/blog/2015/04/15/retrospective-and- roadmap-ui-toolkit/ Just to note that this is also noticeable in the calendar app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1362548/+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 1362548] Re: Migrate from EDS to Dbus to improve performance
** Summary changed: - Migrate from EDS to dbus to improve performance + Migrate from EDS to Dbus to improve performance -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1362548 Title: Migrate from EDS to Dbus to improve performance Status in Ubuntu Clock App: Triaged Status in qtorganizer5-eds package in Ubuntu: Confirmed Bug description: Evolution Data Server should be replaced with dbus. Right now it is man in the middle which hits performance, Clock App-EDS-Indicator-datetime. In 16.04, we are removing the middle man EDS from the equation so alarms created will appear instantly in the indicator and other improvements https://developer.ubuntu.com/en/blog/2015/04/15/retrospective-and- roadmap-ui-toolkit/ Just to note that this is also noticeable in the calendar app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1362548/+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 1297144] Re: [Lenovo ThinkPad X230] Invisible cursor after resume from suspend
Forgot to mention, the problem apperas on mint 17.1 xfce. I wouldn't be surprised to find it in 17.2 as well, because I encountered many resilient bugs that are still there since 2011... and they all are present in all ubuntu systems. It's very annoying. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1297144 Title: [Lenovo ThinkPad X230] Invisible cursor after resume from suspend Status in xorg package in Ubuntu: Expired Bug description: I am using the daily build of Xubuntu 14.04 x64 on a Lenovo Thinkpad x230. If I wake up the computer after it spending some time in the suspend state, the cursor will be invisible. The courser still works (I can click on stuff and hover the invisible cursor over stuff), but the little arrow is not visible. This bug showed up a few days ago after an update. Putting the computer back in suspend state and immediately waking it back up resolves the issue until the next time the computer is put in suspend state for an extended period of time. It is possible that this bug has something to do with Whisker Menu. Sometimes when the courser is invisible it will still show up over Whisker Menu. Most of the time it is invisible there too. Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 xfdesktop version 4.11.4, running on Xfce 4.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1297144/+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 1419048] Re: Mir emits a mir_motion_action_hover_exit event before of a mir_motion_action_pointer_down
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1419048 Title: Mir emits a mir_motion_action_hover_exit event before of a mir_motion_action_pointer_down Status in Mir: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: This breaks toolkits such as gtk and clutter as this causes the input widget to be reset and thus not to get the pointer-down event. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1419048/+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 1463315] Re: [testsfail] InputEvents.reach_nested_client in CI
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1463315 Title: [testsfail] InputEvents.reach_nested_client in CI Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner- mako/5536/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1463315/+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 1418035] Re: [arale] software buffers have flickering line artefacts
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1418035 Title: [arale] software buffers have flickering line artefacts Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: On arale, software buffers have flickering line artefacts. This is immediately visible if you run fingerpaint but don't paint anything. It's also visible (comes and goes) in progressbar. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1418035/+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 1452320] Re: please drop build-dependency on g++-4.9
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1452320 Title: please drop build-dependency on g++-4.9 Status in Mir: Fix Committed Status in mir package in Ubuntu: Confirmed Status in mir source package in Vivid: Won't Fix Bug description: The mir package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1452320/+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 1461314] Re: [vegetahd] android buffer allocator does consider hwc alignment constraints
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1461314 Title: [vegetahd] android buffer allocator does consider hwc alignment constraints Status in Mir: Fix Committed Status in Mir 0.13 series: Fix Released Status in mir package in Ubuntu: New Bug description: Buffer allocations from vegetahd android gralloc do not consider the H/w alignment constraints required by HWC. This causes HWC to reject any buffer that's not aligned to a stride of 32 pixels to be composed as an overlay, falling back go EGL/GLES composition instead. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1461314/+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 1461697] Re: abi-dump-base make target is broken
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1461697 Title: abi-dump-base make target is broken Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: abi-dump-base make target is broken To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1461697/+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 1464690] Re: [regression] titlebar in canonical example WM + KeyRepeatDispatcher causes deadlock
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1464690 Title: [regression] titlebar in canonical example WM + KeyRepeatDispatcher causes deadlock Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Introducing the KeyRepeatDispatcher means that input events can now occur on two threads: the Input dispatch thread and the GLibMainLoop thread. This leads to lock contention in EventFilterChainDispatcher which isn't necessarily fatal - but I think we'd be better using a single thread for dispatching input (to impose an order on events). What is fatal is that this breaks the (dubious) assumption in CanonicalWindowManagerPolicyCopy that we can wait for swap_buffers() while handling an input event. This leads to a deadlock if an input event is on the GLibMainLoop thread (in the original description this is in EventFilterChainDispatcher, but that just prevents it occurring in BasicWindowManagerCopy). Original text: I caused this while testing a branch (lp:~alan- griffiths/mir/msh_SystemCompositorWindowManager), but I don't think the problem originates there: $ sudo bin/mir_demo_server --file /tmp/mir_socket --vt 2 --arw-file --window-manager system-compositor $ bin/mir_demo_server --host /tmp/mir_socket --window-manager canonical $ bin/mir_demo_client_multiwin bin/mir_demo_client_eglplasma After a few Alt+Tab focus switches things lock up in the nested server. Attaching with GDB gets the following stack traces: The event loop (via) KeyRepeatDispatcher is waiting for a lock in EventFilterChainDispatcher::handle(). #0 __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x76960cfd in __GI___pthread_mutex_lock (mutex=0x7ca060) at ../nptl/pthread_mutex_lock.c:80 #2 0x776e7815 in __gthread_mutex_lock (__mutex=0x7ca060) at /usr/include/x86_64-linux-gnu/c++/4.9/bits/gthr-default.h:748 #3 0x776e8738 in std::mutex::lock (this=0x7ca060) at /usr/include/c++/4.9/mutex:135 #4 0x776e8b2e in std::lock_guardstd::mutex::lock_guard (this=0x7fffdbb0, __m=...) at /usr/include/c++/4.9/mutex:377 #5 0x7775d1db in mir::input::EventFilterChainDispatcher::handle (this=0x7ca050, event=...) at /home/alan/display_server/mir3/src/server/input/event_filter_chain_dispatcher.cpp:34 #6 0x7775d510 in mir::input::EventFilterChainDispatcher::dispatch (this=0x7ca050, event=...) at /home/alan/display_server/mir3/src/server/input/event_filter_chain_dispatcher.cpp:67 #7 0x77796e2e in mir::input::KeyRepeatDispatcher::lambda()::operator()(void) (__closure=0x7fffe000a0a0) at /home/alan/display_server/mir3/src/server/input/key_repeat_dispatcher.cpp:117 #8 0x77797512 in std::_Function_handlervoid(), mir::input::KeyRepeatDispatcher::handle_key_input(MirInputDeviceId, const MirKeyboardEvent*)::lambda() ::_M_invoke(const std::_Any_data ) (__functor=...) at /usr/include/c++/4.9/functional:2039 #9 0x776ee54c in std::functionvoid ()::operator()() const (this=0x7fffee68) at /usr/include/c++/4.9/functional:2439 #10 0x7773b626 in mir::BasicCallback::operator() (this=0x7fffee60) at /home/alan/display_server/mir3/src/server/basic_callback.cpp:28 #11 0x7773b111 in mir::LockableCallbackWrapper::operator() (this=0x7fffe00036f0) at /home/alan/display_server/mir3/src/server/lockable_callback_wrapper.cpp:41 #12 0x7770face in mir::detail::TimerGSource::dispatch (source=0x949320) at /home/alan/display_server/mir3/src/server/glib_main_loop_sources.cpp:299 #13 0x75443c3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x75443f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x75443fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x77705f91 in mir::GLibMainLoop::run (this=0x6f6e70) ---Type return to continue, or q return to quit--- The lock is held by the window manager (which is trying to paint a titlebar). #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x764f7d1c in std::condition_variable::wait(std::unique_lockstd::mutex) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x004b270b in std::condition_variable::wait(anonymous namespace)::swap_buffers(const std::shared_ptrmir::scene::Surface, mir::graphics::Buffer*)::lambda() (std::unique_lockstd::mutex , (anonymous namespace)::lambda()) ( this=0x7fffee2f21b0, __lock=..., __p=...) at /usr/include/c++/4.9/condition_variable:98 #3 0x004aeaa4 in (anonymous namespace)::swap_buffers
[Touch-packages] [Bug 1454128] Re: [regression] Dragging windows by the titlebar is incredibly slow and laggy
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1454128 Title: [regression] Dragging windows by the titlebar is incredibly slow and laggy Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in mir source package in Vivid: New Bug description: [regression] Dragging windows by the titlebar is incredibly slow and laggy. Test case: 1. mir_demo_server 2. mir_demo_client_... 3. Drag the client by the titlebar Expected: Window moves in response to the mouse. Observed: Titlebar turns dark grey, window hardly moves, only very slowly. Strangely Alt+drag is still fast so the slowness is related to the titlebar changing colour. I've bisected the problem and it was introduced in: revno: 2563 [merge] author: Alan Griffiths a...@octopull.co.uk committer: Tarmac branch nick: development-branch timestamp: Mon 2015-05-11 17:14:31 + message: examples: repaint the titlebar to give an indicate the (in)active status of a surface. Approved by Kevin DuBois, PS Jenkins bot. Also worth noting I have my mouse configured for 1000Hz instead of the default 125Hz (usbhid.mousepoll kernel parameter). But of course it should still be responsive. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1454128/+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 1465692] Re: Pointer events are not mapped to correct output by nested Mir
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1465692 Title: Pointer events are not mapped to correct output by nested Mir Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: /0/ Have a two display setup /1/ Start a session compositor: bin/mir_demo_server with config: window-manager=system-compositor arw-file= file=/tmp/mir_socket vt=2 display-config=sidebyside /2/ Start a nested compositor: bin/mir_demo_server with config: window-manager=canonical file=/run/user/1000/mir_socket host=/tmp/mir_socket display-config=sidebyside /3/ Start a client: mir/mir_demo_client_multiwin Surfaces can be moved on the first screen [Alt+drag] by clicking on the corresponding part of the second screen. (It also works correctly on the first screen - the problem is that the co-ordinates are not transformed from surface local to presentation space.) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1465692/+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] Re: [vivid-overlay] Servers can't start - input-stub.so fails to load on i386
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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] Servers can't start - input-stub.so fails to load on i386 Status in Canonical System Image: Confirmed Status in Mir: Fix Committed Status in mir package in Ubuntu: Confirmed 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/canonical-devices-system-image/+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 1451844] Re: [enhancement] Mir servers should allow client connections only after server start-up has finished
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1451844 Title: [enhancement] Mir servers should allow client connections only after server start-up has finished Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in mir source package in Vivid: New Bug description: Mir servers should allow client connections only after start-up has finished, to avoid races with components that are in the process of initializing. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1451844/+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 1454518] Re: [regression] Opacity controls (Alt+mousewheel) don't work any more
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1454518 Title: [regression] Opacity controls (Alt+mousewheel) don't work any more Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: [regression] Opacity controls (Alt+mousewheel) don't work any more in mir_proving_server To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1454518/+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 1466492] Re: Spurious Failure in ClientLibrary.highly_threaded_client
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1466492 Title: Spurious Failure in ClientLibrary.highly_threaded_client Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: I noticed ClientLibrary.highly_threaded_client failing (approx 3/10 times) with this message with mir rev 2681. Note: Google Test filter = ClientLibrary.highly_threaded* [==] Running 1 test from 1 test case. [--] Global test environment set-up. [--] 1 test from ClientLibrary [ RUN ] ClientLibrary.highly_threaded_client /home/kdub/source/mir/mir/tests/acceptance-tests/test_client_library.cpp:555: Failure Value of: mir_surface_get_state(surface) Expected: is equal to 7 Actual: 2 (of type MirSurfaceState) [ FAILED ] ClientLibrary.highly_threaded_client (25 ms) [--] 1 test from ClientLibrary (25 ms total) [--] Global test environment tear-down [==] 1 test from 1 test case ran. (25 ms total) [ PASSED ] 0 tests. [ FAILED ] 1 test, listed below: [ FAILED ] ClientLibrary.highly_threaded_client 1 FAILED TEST To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1466492/+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 1457987] Re: [regression] Lost API for creating freestyle surfaces
** Branch linked: lp:ubuntu/wily-proposed/mir -- 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/1457987 Title: [regression] Lost API for creating freestyle surfaces Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: mir_surface_set_type() is deprecated, so there's no way to create freestyle surfaces any more. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1457987/+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 1475424] Re: package libdb5.3:i386 5.3.28-9 failed to install/upgrade: package libdb5.3:i386 is already installed and configured
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: db5.3 (Ubuntu) Importance: Undecided = Low ** Changed in: db5.3 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to db5.3 in Ubuntu. https://bugs.launchpad.net/bugs/1475424 Title: package libdb5.3:i386 5.3.28-9 failed to install/upgrade: package libdb5.3:i386 is already installed and configured Status in db5.3 package in Ubuntu: Invalid Bug description: It happened while setting up system languages. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libdb5.3:i386 5.3.28-9 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu3.1 Architecture: amd64 Date: Thu Jul 16 16:33:36 2015 Dependencies: gcc-5-base 5.1~rc1-0ubuntu1 libc6 2.21-0ubuntu4 libgcc1 1:5.1~rc1-0ubuntu1 multiarch-support 2.21-0ubuntu4 DuplicateSignature: package:libdb5.3:i386:5.3.28-9:package libdb5.3:i386 is already installed and configured ErrorMessage: package libdb5.3:i386 is already installed and configured InstallationDate: Installed on 2015-07-16 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: db5.3 Title: package libdb5.3:i386 5.3.28-9 failed to install/upgrade: package libdb5.3:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1475424/+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 1468029] Re: focus issues breaking autopilot tests entering text
** Also 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/1468029 Title: focus issues breaking autopilot tests entering text Status in Canonical System Image: New Status in Mir: Fix Committed Status in Mir 0.14 series: Fix Committed Status in mir package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: When running the autopilot tests for ubuntu-system-settings, at some point it fails to enter text using the OSK. It works fine for smaller subsets of the tests, but not a full run. It simply stops entering text with keyboard.type(). Once it gets in this state, it will continue to fail even for single tests until unity8 is restarted. During the test run, there is a unity8 crash file generated. I wasn't able to create a bug report for the problem directly from the OOPS on errors.ubuntu.com, you can find it at https://errors.ubuntu.com/oops/c4124284-1999-11e5-8fcb-fa163e75317b My device: current build number: 234 device name: mako channel: ubuntu-touch/devel-proposed/ubuntu last update: 2015-06-23 00:04:08 version version: 234 version ubuntu: 20150623 version device: 20150529.1 version custom: 20150623 @osomon has seen the same problem while running the webbrowser-app tests on krillin with vivid-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1468029/+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 1474720] Re: [regression] Mir servers crash on start-up. dummy graphics driver selected and then: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link
The log is not short. I just copied and pasted the relevant bits :) -- 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/1474720 Title: [regression] Mir servers crash on start-up. dummy graphics driver selected and then: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed: Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: All Mir demo servers are now crashing on start-up, with very little explanation: [1437011956.469215] mirserver: Selected driver: dummy (version 0.15.0) [1437011956.492673] mirserver: Using software cursor [1437011956.493899] mirserver: Mir version 0.15.0 ERROR: Dynamic exception type: St13runtime_error std::exception::what: Link failed: To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474720/+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
