[Touch-packages] [Bug 1674459] [NEW] Restart daemon after upgrade
Public bug reported: It is important that the daemon is restarted after package upgrades so that clients are always running the latest version. Note that currently this might cause clients that are already running to fail (in case the dbus interfaces are changed). ** Affects: history-service (Ubuntu) Importance: Medium Assignee: Gustavo Pichorim Boiko (boiko) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1674459 Title: Restart daemon after upgrade Status in history-service package in Ubuntu: New Bug description: It is important that the daemon is restarted after package upgrades so that clients are always running the latest version. Note that currently this might cause clients that are already running to fail (in case the dbus interfaces are changed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1674459/+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 1447601] Re: "Phone" app settings are oddly in System Settings
** Branch linked: lp:~phablet-team/dialer-app/phone_settings ** Branch linked: lp:~phablet-team/ubuntu-system- settings/remove_dialer_settings ** Changed in: ubuntu-system-settings (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) ** Changed in: dialer-app (Ubuntu) Importance: Undecided => Low ** Changed in: dialer-app (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) ** Changed in: ubuntu-system-settings (Ubuntu) Status: Triaged => In Progress ** Changed in: dialer-app (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1447601 Title: "Phone" app settings are oddly in System Settings Status in ubuntu-system-settings: New Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: In System Settings, most of the "Phone" settings are about things that happen inside, or (in the case of ringtone) when you are about to use, the Phone app. Therefore it is weird for those settings to be accessed from System Settings. They should be moved to the Phone app. [Realized during discussion of bug 1306078.] <https://goo.gl/LteZNn>: "The Settings button should open the “Settings” screen..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings/+bug/1447601/+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 1646611] Re: mission-control should use different paths when in a snap environment
Well, mission-control is not using Qt at all, so certainly not using QStandardPaths -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1646611 Title: mission-control should use different paths when in a snap environment Status in Canonical System Image: Confirmed Status in telepathy-mission-control-5 package in Ubuntu: New Bug description: When running confined into a snap environment, mission-control needs to use different paths for its files: Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Unable to create directory '/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file system Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Failed to create file '/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.CC7LOY': No such file or directory Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Unable to create directory '/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file system Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Failed to create file '/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.7I1LOY': No such file or Instead of using $SNAP, it probably should use $SNAP_DATA To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646611/+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 1646611] Re: mission-control should use different paths when in a snap environment
** Also affects: telepathy-mission-control-5 (Ubuntu) Importance: Undecided Status: New ** No longer affects: history-service (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1646611 Title: mission-control should use different paths when in a snap environment Status in Canonical System Image: Confirmed Status in telepathy-mission-control-5 package in Ubuntu: New Bug description: When running confined into a snap environment, mission-control needs to use different paths for its files: Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Unable to create directory '/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file system Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Failed to create file '/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.CC7LOY': No such file or directory Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Unable to create directory '/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file system Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Failed to create file '/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.7I1LOY': No such file or Instead of using $SNAP, it probably should use $SNAP_DATA To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646611/+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 1646611] [NEW] mission-control should use different paths when in a snap environment
Public bug reported: When running confined into a snap environment, mission-control needs to use different paths for its files: Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Unable to create directory '/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file system Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Failed to create file '/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.CC7LOY': No such file or directory Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Unable to create directory '/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file system Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Failed to create file '/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.7I1LOY': No such file or Instead of using $SNAP, it probably should use $SNAP_DATA ** Affects: canonical-devices-system-image Importance: Medium Assignee: Bill Filler (bfiller) Status: Confirmed ** Affects: history-service (Ubuntu) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1646611 Title: mission-control should use different paths when in a snap environment Status in Canonical System Image: Confirmed Status in history-service package in Ubuntu: New Bug description: When running confined into a snap environment, mission-control needs to use different paths for its files: Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Unable to create directory '/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file system Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Failed to create file '/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.CC7LOY': No such file or directory Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Unable to create directory '/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file system Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Failed to create file '/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.7I1LOY': No such file or Instead of using $SNAP, it probably should use $SNAP_DATA To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646611/+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 1625805] Re: dragonboard: history daemon dereferences a rogue pointer
** Changed in: history-service (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- 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/1625805 Title: dragonboard: history daemon dereferences a rogue pointer Status in Canonical System Image: Confirmed Status in Snappy: New Status in history-service package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625805/+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 1614943] Re: No ringtone on incoming calls
** Also affects: telephony-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1614943 Title: No ringtone on incoming calls Status in Canonical System Image: Confirmed Status in telephony-service package in Ubuntu: New Bug description: current build number: 405 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en Regularly on incoming calls, there is no ringtone or just a click. Apart from that, the notification is displayed, I can answer the call normally. Phone is not muted, sound is close to the max, and if I reboot it works again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614943/+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 1619332] [NEW] Tests failing with Qt5.6
Public bug reported: On xenial+overlay and yakkety (where we have Qt5.6) some unit tests started to fail: - ChatManagerTest::testSendMessage - ChatManagerTest::testSendMessageWithAttachments - HandlerTest::testSendMessage ** Affects: telephony-service (Ubuntu) Importance: High Assignee: Gustavo Pichorim Boiko (boiko) Status: New ** Changed in: telephony-service (Ubuntu) Importance: Undecided => High ** Changed in: telephony-service (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1619332 Title: Tests failing with Qt5.6 Status in telephony-service package in Ubuntu: New Bug description: On xenial+overlay and yakkety (where we have Qt5.6) some unit tests started to fail: - ChatManagerTest::testSendMessage - ChatManagerTest::testSendMessageWithAttachments - HandlerTest::testSendMessage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1619332/+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 1613490] [NEW] [MIR] telephony-service
Public bug reported: [Availability] * Available in universe [Rationale] * This package is required by unity8 [Security] * No known security issues at this time. It has been reviewed by security in the past for use on the phone. [Quality assurance] * This package has unit tests that are executed at build time [Dependencies] Most dependencies are already in main with the exception of the following: * history-service (bug #1613486) * telepathy-qt5 (bug #1613474) * libphonenumber * platform-api * libusermetrics * dbus-test-runner * telepathy-mission-control-5 * xvfb [Standards compliance] * This package uses cmake and is properly translated. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images ** Affects: telephony-service (Ubuntu) Importance: Undecided Assignee: Gustavo Pichorim Boiko (boiko) Status: New ** Changed in: telephony-service (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1613490 Title: [MIR] telephony-service Status in telephony-service package in Ubuntu: New Bug description: [Availability] * Available in universe [Rationale] * This package is required by unity8 [Security] * No known security issues at this time. It has been reviewed by security in the past for use on the phone. [Quality assurance] * This package has unit tests that are executed at build time [Dependencies] Most dependencies are already in main with the exception of the following: * history-service (bug #1613486) * telepathy-qt5 (bug #1613474) * libphonenumber * platform-api * libusermetrics * dbus-test-runner * telepathy-mission-control-5 * xvfb [Standards compliance] * This package uses cmake and is properly translated. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1613490/+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 1613486] [NEW] [MIR] history-service
Public bug reported: [Availability] * Available in universe [Rationale] * This package is required by unity8 [Security] * No known security issues at this time. It has been reviewed by security in the past for use on the phone. [Quality assurance] * This package has unit tests that are executed at build time [Dependencies] Most dependencies are already in main with the exception of the following: * telepathy-qt5 (bug #1613474) * dbus-test-runner * telepathy-mission-control-5 * xvfb [Standards compliance] * This package uses cmake and is properly translated. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images ** Affects: history-service (Ubuntu) Importance: Undecided Assignee: Gustavo Pichorim Boiko (boiko) Status: New ** Changed in: history-service (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1613486 Title: [MIR] history-service Status in history-service package in Ubuntu: New Bug description: [Availability] * Available in universe [Rationale] * This package is required by unity8 [Security] * No known security issues at this time. It has been reviewed by security in the past for use on the phone. [Quality assurance] * This package has unit tests that are executed at build time [Dependencies] Most dependencies are already in main with the exception of the following: * telepathy-qt5 (bug #1613474) * dbus-test-runner * telepathy-mission-control-5 * xvfb [Standards compliance] * This package uses cmake and is properly translated. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1613486/+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 1599184] Re: When switching to 2-column landscape mode, current conversations are closed
** Changed in: messaging-app (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: messaging-app (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1599184
Title:
When switching to 2-column landscape mode, current conversations are
closed
Status in Canonical System Image:
Fix Committed
Status in messaging-app package in Ubuntu:
Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
Invalid
Bug description:
messaging-app.qml has the following code:
onColumnsChanged: {
// we only have things to do here in case no thread is selected
if (layout.columns == 2 &&
!application.findMessagingChild("emptyStatePage") &&
!application.findMessagingChild("fakeItem")) {
layout.removePage(mainPage)
emptyStack()
}
}
This causes the current conversation to be closed when the user
rotates the phone (on a large-enough screen to go to two-column mode),
and that can be very annoying. The APL can already take care of moving
pages to the correct column and correct place in the stack when
needed, so this code should be removed. Also note that emptyStack()
will again call layout.removePage(mainPage).
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1599184/+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 1598181] Re: No network showing from the dialer app even though phone calls are possible
** Changed in: dialer-app (Ubuntu) Status: New => Triaged ** Changed in: dialer-app (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1598181 Title: No network showing from the dialer app even though phone calls are possible Status in Canonical System Image: Confirmed Status in dialer-app package in Ubuntu: Triaged Status in indicator-network package in Ubuntu: New Status in ofono package in Ubuntu: Confirmed Bug description: I noticed that I am seeing "No network" being displayed in the upper right hand corner of the dialer app even though I am able to make phone calls. This is on turbo and using the smaller SIM slot (#2) with T-Mobile in the US. Build version info: current build number: 116 device name: turbo channel: ubuntu-touch/rc-proposed/ubuntu last update: 2016-07-01 09:38:31 version version: 116 version ubuntu: 20160701 version device: 20160617-82a5c0d version custom: 20160701 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598181/+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 1598181] Re: No network showing from the dialer app even though phone calls are possible
** Changed in: dialer-app (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1598181 Title: No network showing from the dialer app even though phone calls are possible Status in Canonical System Image: Confirmed Status in dialer-app package in Ubuntu: New Status in indicator-network package in Ubuntu: New Status in ofono package in Ubuntu: Confirmed Bug description: I noticed that I am seeing "No network" being displayed in the upper right hand corner of the dialer app even though I am able to make phone calls. This is on turbo and using the smaller SIM slot (#2) with T-Mobile in the US. Build version info: current build number: 116 device name: turbo channel: ubuntu-touch/rc-proposed/ubuntu last update: 2016-07-01 09:38:31 version version: 116 version ubuntu: 20160701 version device: 20160617-82a5c0d version custom: 20160701 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598181/+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 1599184] Re: When switching to 2-column landscape mode, current conversations are closed
After some discussion we decided not to use the bottom edge animation
when in two columns mode, so this problem is not going to happen
anymore.
At some point the SDK might need to have animated transitions in APL and
PageStack, but that's out of scope for this bug, so I'll mark as Invalid
for SDK.
** Branch linked: lp:~phablet-team/messaging-app/fix_bottom_edge
** Changed in: messaging-app (Ubuntu)
Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko)
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New => Invalid
--
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/1599184
Title:
When switching to 2-column landscape mode, current conversations are
closed
Status in messaging-app package in Ubuntu:
Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
Invalid
Bug description:
messaging-app.qml has the following code:
onColumnsChanged: {
// we only have things to do here in case no thread is selected
if (layout.columns == 2 &&
!application.findMessagingChild("emptyStatePage") &&
!application.findMessagingChild("fakeItem")) {
layout.removePage(mainPage)
emptyStack()
}
}
This causes the current conversation to be closed when the user
rotates the phone (on a large-enough screen to go to two-column mode),
and that can be very annoying. The APL can already take care of moving
pages to the correct column and correct place in the stack when
needed, so this code should be removed. Also note that emptyStack()
will again call layout.removePage(mainPage).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1599184/+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 1597929] Re: ListItem's actions not cropped
The bug actually doesn't exist yet on the app, as this problem is in a branch that was not merged yet. Just wondering if it wouldn't it be a good idea to have the actions anchored to the listview itself? ** Changed in: messaging-app (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1597929 Title: ListItem's actions not cropped Status in Canonical System Image: Confirmed Status in messaging-app package in Ubuntu: Invalid Bug description: Steps to reproduce: - Get an app that has two layouts and uses a listitem with leading actions in the second panel (the one to the right - Swipe from left to right to reveal the action Expected behavior: - Action icon is visible but not overflowing to the panel on the left What actually happens: - The contents of the left panel get covered by the action item's background (see attached screenshot) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597929/+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 1534674] Re: [AdaptivePageLayout] Add function to return the top Page of a PageColumn
This would also help to identify when a column is empty. In messaging-app, for instance, we need to add an empty state page to the second column when switching from one to two columns layout in case there is no content there. -- 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/1534674 Title: [AdaptivePageLayout] Add function to return the top Page of a PageColumn Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: Add a function that will return a reference to the top Page object in a specific PageColumn. Suggestion: getPageInColumn(int columnIndex) Use Case: In uReadIt I have at most a 3-column layout. I would like a user action on an item in the first column to add a Page to the 3rd column. This requires knowing the current page in the 2nd column in order to call pageStack.addPageToNextColumn(secondPage, "SourcePage.qml"). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1534674/+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 1599183] Re: Use the built-in synchronous loading of pages in AdaptivePageLayout
** Changed in: messaging-app (Ubuntu) Importance: Undecided => Medium ** Changed in: messaging-app (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1599183 Title: Use the built-in synchronous loading of pages in AdaptivePageLayout Status in messaging-app package in Ubuntu: New Bug description: MessagingPageLayout implements synchronous loading of pages in the AdaptivePageLayout (APL). This is a workaround that is no longer needed, because the APL can now do this by setting its asynchronous property to false. This means that most of the code from MessagingPageLayout can be removed :) Note that this bug: https://bugs.launchpad.net/ubuntu/+source/ubuntu- ui-toolkit/+bug/1544745 is fixed, so the MessagingPageLayout is no longer needed to work around that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1599183/+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 1597929] [NEW] ListItem's actions not cropped
Public bug reported: Steps to reproduce: - Get an app that has two layouts and uses a listitem with leading actions in the second panel (the one to the right - Swipe from left to right to reveal the action Expected behavior: - Action icon is visible but not overflowing to the panel on the left What actually happens: - The contents of the left panel get covered by the action item's background (see attached screenshot) ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot of the problem" https://bugs.launchpad.net/bugs/1597929/+attachment/4693184/+files/listitem_no_crop.png -- 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/1597929 Title: ListItem's actions not cropped Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Steps to reproduce: - Get an app that has two layouts and uses a listitem with leading actions in the second panel (the one to the right - Swipe from left to right to reveal the action Expected behavior: - Action icon is visible but not overflowing to the panel on the left What actually happens: - The contents of the left panel get covered by the action item's background (see attached screenshot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1597929/+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 1581206] Re: Cannot read the time and SIM information on a message
** Changed in: messaging-app (Ubuntu) Assignee: Tiago Salem Herrmann (tiagosh) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1581206 Title: Cannot read the time and SIM information on a message Status in Canonical System Image: Confirmed Status in Ubuntu UX: Fix Committed Status in messaging-app package in Ubuntu: Confirmed Bug description: Light gray on a white background with miniscule font size is illegible for many people See bug #1579704 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581206/+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 1581206] Re: Cannot read the time and SIM information on a message
** Branch linked: lp:~boiko/messaging-app/update_colors -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1581206 Title: Cannot read the time and SIM information on a message Status in Canonical System Image: Confirmed Status in Ubuntu UX: Fix Committed Status in messaging-app package in Ubuntu: Confirmed Bug description: Light gray on a white background with miniscule font size is illegible for many people See bug #1579704 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581206/+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 1579626] Re: Cannot send SMS with single SIM card
Fixed on messaging-app=0.1+15.04.20160506-0ubuntu1 ** Changed in: messaging-app (Ubuntu) Status: Confirmed => Fix Released ** Changed in: canonical-devices-system-image Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1579626 Title: Cannot send SMS with single SIM card Status in Canonical System Image: Fix Committed Status in messaging-app package in Ubuntu: Fix Released Bug description: current build number: 326 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-05-09 10:49:33 version version: 326 version ubuntu: 20160506.1 version device: 20160329-a9bacdb version custom: 20160324--36-54-vivid Steps: 1.Get a Krillin or Turbo 2.Insert only one SIM (no matter slot1 or slot2) 3.Try to make a phone call 4.try to send a SMS Actual result: You can make a phone call, but cannot send a SMS because of dialog "No Sim card selected: You need to select a SIM card" Expected result: Be able to send SMS with single SIM card. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579626/+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 1579626] Re: Cannot send SMS with single SIM card
Can you try again on krillin image version 327? We landed a fix that solves this problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1579626 Title: Cannot send SMS with single SIM card Status in Canonical System Image: Fix Committed Status in messaging-app package in Ubuntu: Fix Released Bug description: current build number: 326 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-05-09 10:49:33 version version: 326 version ubuntu: 20160506.1 version device: 20160329-a9bacdb version custom: 20160324--36-54-vivid Steps: 1.Get a Krillin or Turbo 2.Insert only one SIM (no matter slot1 or slot2) 3.Try to make a phone call 4.try to send a SMS Actual result: You can make a phone call, but cannot send a SMS because of dialog "No Sim card selected: You need to select a SIM card" Expected result: Be able to send SMS with single SIM card. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579626/+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 1572880] Re: Cannot call emergency number from sim lock screen if phone screen is unlocked before
** Changed in: dialer-app (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1572880 Title: Cannot call emergency number from sim lock screen if phone screen is unlocked before Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in dialer-app package in Ubuntu: Triaged Bug description: current build number: 4 device name: turbo channel: ubuntu-touch/rc/meizu.en last update: 2016-04-19 10:38:50 version version: 4 version ubuntu: 20160418 version device: 20160412-d272a77, Steps: 1.Turn on sim pin 2.Reboot the device 3.Don't unlock the SIM but unlock phone screen 4.Swipe down the indicator and select network section 5.Tap on "Unlock sim" to bring up sim lock screen 6.Tap on "Emergency Call" button 7.Enter an emergency number and call Actual result: At step6, it shows regular dial pad with SIM locked header At step7, "SIM card is locked" dialog appears Expected result: At step6, it shows emergency dial pad with emergency header At step7, be able to make an emergency call Error also can be reproduced with krillin and arale. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1572880/+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 1572880] Re: Cannot call emergency number from sim lock screen if phone screen is unlocked before
I checked the code and the only case where the dialog is shown is when the number being called is not really an emergency number. What number are you trying to call there? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1572880 Title: Cannot call emergency number from sim lock screen if phone screen is unlocked before Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in dialer-app package in Ubuntu: New Bug description: current build number: 4 device name: turbo channel: ubuntu-touch/rc/meizu.en last update: 2016-04-19 10:38:50 version version: 4 version ubuntu: 20160418 version device: 20160412-d272a77, Steps: 1.Turn on sim pin 2.Reboot the device 3.Don't unlock the SIM but unlock phone screen 4.Swipe down the indicator and select network section 5.Tap on "Unlock sim" to bring up sim lock screen 6.Tap on "Emergency Call" button 7.Enter an emergency number and call Actual result: At step6, it shows regular dial pad with SIM locked header At step7, "SIM card is locked" dialog appears Expected result: At step6, it shows emergency dial pad with emergency header At step7, be able to make an emergency call Error also can be reproduced with krillin and arale. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1572880/+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 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default
** Changed in: telephony-service (Ubuntu) Status: Triaged => Fix Released -- 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/1418040 Title: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: What happened Placed call from car over bluetooth Call was placed on my first SIM card, even though I selected my second SIM as default for calls What should have happened The call should have been placed on my second SIM ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20150124-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu4 Architecture: armhf Date: Wed Feb 4 14:25:44 2015 InstallationDate: Installed on 2015-02-02 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150202-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+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 1548374] Re: /usr/lib/telepathy/telepathy-ofono:11:QPulseAudioEngineWorker::sourceInfoCallback:context_get_source_info_callback:run_action:pa_pdispatch_run:pstream_packet_callbac
** Changed in: telepathy-ofono (Ubuntu) Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1548374 Title: /usr/lib/telepathy/telepathy- ofono:11:QPulseAudioEngineWorker::sourceInfoCallback:context_get_source_info_callback:run_action:pa_pdispatch_run:pstream_packet_callback Status in telepathy-ofono package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding telepathy-ofono. This problem was most recently seen with version 0.2+15.04.20151120-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/0b54d2ff53db7ded66f0a8c16e63e6623babe669 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1548374/+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 1571094] Re: /usr/bin/phone-gsettings-migration.py:ValueError:/usr/bin/phone-gsettings-migration.py@27:__call__:call_blocking
** Changed in: telephony-service (Ubuntu) Importance: Undecided => Medium ** Changed in: telephony-service (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1571094 Title: /usr/bin/phone-gsettings-migration.py:ValueError:/usr/bin/phone- gsettings-migration.py@27:__call__:call_blocking Status in telephony-service package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding telephony-service. This problem was most recently seen with version 0.1+15.04.20160411-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e33f885bbc5d071b30c62ddbad840cf30b893ef4 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1571094/+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 1571094] Re: /usr/bin/phone-gsettings-migration.py:ValueError:/usr/bin/phone-gsettings-migration.py@27:__call__:call_blocking
** Changed in: telephony-service (Ubuntu) Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1571094 Title: /usr/bin/phone-gsettings-migration.py:ValueError:/usr/bin/phone- gsettings-migration.py@27:__call__:call_blocking Status in telephony-service package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding telephony-service. This problem was most recently seen with version 0.1+15.04.20160411-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e33f885bbc5d071b30c62ddbad840cf30b893ef4 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1571094/+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 1570040] Re: [Feature request] In dual-SIM configurations show SIM-card used in call list
** Also affects: dialer-app Importance: Undecided Status: New ** Project changed: dialer-app => ubuntu-ux ** Changed in: dialer-app (Ubuntu) Status: New => Triaged ** Changed in: dialer-app (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1570040 Title: [Feature request] In dual-SIM configurations show SIM-card used in call list Status in Ubuntu UX: New Status in dialer-app package in Ubuntu: Triaged Bug description: In dual-SIM configurations, when phone receives a call, SIM-card in use is being indicated. The list of calls does not show this information, however. It is only available in the call details. Providing this information in a list of calls will help user to phone back using appropriate SIM-card/phone number. Moreover, it would be logical to select the SIM card used to receive the call for placing an outgoing call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1570040/+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 1388594] Re: [TOPBLOCKER] dialer app can thrash cpu after caller hangs up on you
** Changed in: dialer-app (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1388594 Title: [TOPBLOCKER] dialer app can thrash cpu after caller hangs up on you Status in dialer-app package in Ubuntu: Invalid Bug description: summary dialer app can thrash cpu after caller hangs up on you steps: 1. answer call from someone using snap decision bubble 2. talk for a while 3. let the caller hang up on you expected results: dialer app isn't using 100% cpu after call actual results dialer app continues to thrash cpu snap shot from top 5 minutes after call PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 7412 phablet 20 0 253352 50876 25296 S 100.0 5.2 11:41.13 dialer-app 751 message+ 20 09480 6680756 S 1.3 0.7 4:03.64 dbus-daemon version info: [service] base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/ubuntu-rtm/14.09-proposed device: krillin build_number: 140 version_detail: ubuntu=20141031.1,device=20141028-3ca60be,custom=1414598646,version=140 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1388594/+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 1565103] Re: bottom edge first time wizard is being incorrectly displayed on dialer-app and messaging-app
** Description changed: A new bottom edge wizard is being displayed in the recent images, but there are cases where it is being displayed when it shouldn't. Steps to reproduce: 1) Flash the phone with --wipe. 2) Before opening dialer-app, lock the phone and receive a call. 3) Once you accept the call, dialer-app is launched and instead of the live call view, the wizard is displayed on top of it, but there is no bottom edge on that screen, and I believe in this case we should not display any wizards, specially because the phone is locked, but even if the phone was unlocked, we should not display the wizard if the view does not have bottom edge enabled. - Another case is when launching messaging-app or dialer-app. we have a - first time dialog that appears behind the wizard. Not sure if that's - expected, but seems to cause a bad user experience to me. + Another case is when launching messaging-app or dialer-app in a dual sim + environment. We have a first time dialog that appears behind the wizard. + Not sure if that's expected, but seems to cause a bad user experience to + me. -- 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/1565103 Title: bottom edge first time wizard is being incorrectly displayed on dialer-app and messaging-app Status in unity8 package in Ubuntu: New Bug description: A new bottom edge wizard is being displayed in the recent images, but there are cases where it is being displayed when it shouldn't. Steps to reproduce: 1) Flash the phone with --wipe. 2) Before opening dialer-app, lock the phone and receive a call. 3) Once you accept the call, dialer-app is launched and instead of the live call view, the wizard is displayed on top of it, but there is no bottom edge on that screen, and I believe in this case we should not display any wizards, specially because the phone is locked, but even if the phone was unlocked, we should not display the wizard if the view does not have bottom edge enabled. Another case is when launching messaging-app or dialer-app in a dual sim environment. We have a first time dialog that appears behind the wizard. Not sure if that's expected, but seems to cause a bad user experience to me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1565103/+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 1563050] Re: History's QML plugin needs to initialize Telepathy-Qt types
** Changed in: history-service (Ubuntu) Importance: Undecided => High ** Changed in: history-service (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) ** Changed in: history-service (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1563050 Title: History's QML plugin needs to initialize Telepathy-Qt types Status in Canonical System Image: Confirmed Status in history-service package in Ubuntu: In Progress Bug description: Since the latest contact matching changes, history's QML plugin uses some things from telepathy to gather account information, but Telepathy-Qt types are not being initialized anywhere there. This causes a crash in system-settings when you go to Settings->Phone->Sim Services To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563050/+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 1563050] [NEW] History's QML plugin needs to initialize Telepathy-Qt types
Public bug reported: Since the latest contact matching changes, history's QML plugin uses some things from telepathy to gather account information, but Telepathy- Qt types are not being initialized anywhere there. This causes a crash in system-settings when you go to Settings->Phone->Sim Services ** Affects: history-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1563050 Title: History's QML plugin needs to initialize Telepathy-Qt types Status in history-service package in Ubuntu: New Bug description: Since the latest contact matching changes, history's QML plugin uses some things from telepathy to gather account information, but Telepathy-Qt types are not being initialized anywhere there. This causes a crash in system-settings when you go to Settings->Phone->Sim Services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1563050/+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 1557707] Re: [Sections] selectedIndex binding is broken if the model changes
The use case for messaging-app is more or less the following:
model: simNames
selectedIndex: getDefaultSim()
You go to system settings, rename the sim. This will make the model
change, but the selectedIndex binding will be broken and reset to the
first one.
But maybe you are right, as hard as it is to do that in the app, it
might be still better than to rely on a default behavior of this.
--
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/1557707
Title:
[Sections] selectedIndex binding is broken if the model changes
Status in Canonical System Image:
Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
Incomplete
Bug description:
If I assign a default value for the selectedIndex, it is expected that
the binding for this value will be kept until the user selects a
different section. Changing the model should not affect that, but it
does, as this example shows:
import QtQuick 2.0
import Ubuntu.Components 1.3
MainView {
width: 720
height: 1280
Page {
id: myPage
anchors.fill: parent
title: "Click the page"
header: PageHeader {
id: pageHeader
title: myPage.title
extension: Sections {
id: pageSections
model: [ "one", "two", "three" ]
selectedIndex: 1
}
}
MouseArea {
anchors.fill: parent
onClicked: pageSections.model = [ "first", "second", "third" ]
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557707/+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 1557707] [NEW] [Sections] selectedIndex binding is broken if the model changes
Public bug reported:
If I assign a default value for the selectedIndex, it is expected that
the binding for this value will be kept until the user selects a
different section. Changing the model should not affect that, but it
does, as this example shows:
import QtQuick 2.0
import Ubuntu.Components 1.3
MainView {
width: 720
height: 1280
Page {
id: myPage
anchors.fill: parent
title: "Click the page"
header: PageHeader {
id: pageHeader
title: myPage.title
extension: Sections {
id: pageSections
model: [ "one", "two", "three" ]
selectedIndex: 1
}
}
MouseArea {
anchors.fill: parent
onClicked: pageSections.model = [ "first", "second", "third" ]
}
}
}
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided
Status: New
--
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/1557707
Title:
[Sections] selectedIndex binding is broken if the model changes
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
If I assign a default value for the selectedIndex, it is expected that
the binding for this value will be kept until the user selects a
different section. Changing the model should not affect that, but it
does, as this example shows:
import QtQuick 2.0
import Ubuntu.Components 1.3
MainView {
width: 720
height: 1280
Page {
id: myPage
anchors.fill: parent
title: "Click the page"
header: PageHeader {
id: pageHeader
title: myPage.title
extension: Sections {
id: pageSections
model: [ "one", "two", "three" ]
selectedIndex: 1
}
}
MouseArea {
anchors.fill: parent
onClicked: pageSections.model = [ "first", "second", "third" ]
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1557707/+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 1555080] [NEW] In dual panel mode, in some cases it is not possible to create new conversations
Public bug reported: Consider the following case: - Open messaging-app in dual panel mode (desktop, pocket desktop or arale in landscape mode) - Click one existing conversation - Open the contact profile, or click the add to contact button - Press "+" on the header to create a new conversation Currently in this case nothing happens, but it is expected that somehow the new conversation page appears. ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: messaging-app (Ubuntu) Importance: Medium Status: New ** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1555080 Title: In dual panel mode, in some cases it is not possible to create new conversations Status in Ubuntu UX: New Status in messaging-app package in Ubuntu: New Bug description: Consider the following case: - Open messaging-app in dual panel mode (desktop, pocket desktop or arale in landscape mode) - Click one existing conversation - Open the contact profile, or click the add to contact button - Press "+" on the header to create a new conversation Currently in this case nothing happens, but it is expected that somehow the new conversation page appears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1555080/+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 1555073] [NEW] [AdaptivePageLayout] Make it possible to access the current page of each column
Public bug reported: Sometimes it is useful for the applications to know what is the current page on each column. Currently there is no way to do that. Maybe something like: property list currentItems ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Wishlist Status: New -- 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/1555073 Title: [AdaptivePageLayout] Make it possible to access the current page of each column Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Sometimes it is useful for the applications to know what is the current page on each column. Currently there is no way to do that. Maybe something like: property list currentItems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1555073/+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 1553334] [NEW] contacts service queried twice per received message
Public bug reported: The current implementation of telephony-service-indicator does two queries to the address-book-service: - one to show the OSD notification - one to add the item to the messaging menu This could be optimized to query the service just once for contact information. ** Affects: telephony-service (Ubuntu) Importance: Low Assignee: Gustavo Pichorim Boiko (boiko) Status: New ** Changed in: telephony-service (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) ** Changed in: telephony-service (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1553334 Title: contacts service queried twice per received message Status in telephony-service package in Ubuntu: New Bug description: The current implementation of telephony-service-indicator does two queries to the address-book-service: - one to show the OSD notification - one to add the item to the messaging menu This could be optimized to query the service just once for contact information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1553334/+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 1553337] [NEW] Telephony-service should use events from history-service to popupate the messaging-menu
Public bug reported: Telephony-service currently watches for telepathy events (text messages, calls, etc) to populate the messaging-menu. While this is not a problem itself, there would be some advantages of using history-service data for that: - telepathy events are not persisted across reboots, so unread text messages won't show up again in messaging-menu if you restart the device - history-service already queries for contact information to display the data in its clients (like messaging-app and the scopes), so we would eliminate one extra query to the contacts service. ** Affects: telephony-service (Ubuntu) Importance: Low Assignee: Gustavo Pichorim Boiko (boiko) Status: New ** Changed in: telephony-service (Ubuntu) Importance: Undecided => Low ** Changed in: telephony-service (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1553337 Title: Telephony-service should use events from history-service to popupate the messaging-menu Status in telephony-service package in Ubuntu: New Bug description: Telephony-service currently watches for telepathy events (text messages, calls, etc) to populate the messaging-menu. While this is not a problem itself, there would be some advantages of using history- service data for that: - telepathy events are not persisted across reboots, so unread text messages won't show up again in messaging-menu if you restart the device - history-service already queries for contact information to display the data in its clients (like messaging-app and the scopes), so we would eliminate one extra query to the contacts service. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1553337/+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 1553217] [NEW] [Bottom edge] After starting a new conversation, the bottom edge view should turn into a regular conversation view
Public bug reported: Composing new messages in messaging-app is always done in a view that slides from the bottom to the top, but after sending the first message, this view turns into the conversation view with the message recipient. To match the other views, after sending the message the bottom edge view should turn into a regular conversation view (with the < icon on the header and without the sliding down animation). ** Affects: messaging-app (Ubuntu) Importance: Medium Assignee: Gustavo Pichorim Boiko (boiko) Status: New ** Changed in: messaging-app (Ubuntu) Importance: Undecided => Medium ** Changed in: messaging-app (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1553217 Title: [Bottom edge] After starting a new conversation, the bottom edge view should turn into a regular conversation view Status in messaging-app package in Ubuntu: New Bug description: Composing new messages in messaging-app is always done in a view that slides from the bottom to the top, but after sending the first message, this view turns into the conversation view with the message recipient. To match the other views, after sending the message the bottom edge view should turn into a regular conversation view (with the < icon on the header and without the sliding down animation). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1553217/+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 1553220] [NEW] Microphone icon is displayed on top of Send icon
Public bug reported: After sending a message, the microphone icon is appearing on top of the send icon for some time before it disappears. There should be a transition between them to avoid this. ** Affects: messaging-app (Ubuntu) Importance: Low Assignee: Gustavo Pichorim Boiko (boiko) Status: New ** Changed in: messaging-app (Ubuntu) Importance: Undecided => Low ** Changed in: messaging-app (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1553220 Title: Microphone icon is displayed on top of Send icon Status in messaging-app package in Ubuntu: New Bug description: After sending a message, the microphone icon is appearing on top of the send icon for some time before it disappears. There should be a transition between them to avoid this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1553220/+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 1552811] [NEW] Replace the current static page managing by object incubator
Public bug reported: Depending on the contents of the page, its asynchronous creation might take a really long time because of the internal behavior (or bug?) of QtQuick. Loading pages synchronously fixes the problem, but the way it is implemented in messaging-app, there is a risk of leaking memory due to pages not being deleted properly when switching views. There is another way to workaround this QtQuick limitation which is to force the page creation to finish before returning to the event loop, in the AdaptivePageLayout context, it would look like this: var incubator = layout.addPageToNextColumn(originalPage, newPage, properties) incubator.forceCompletion() In order for this to be fixed, there is one but in AdaptivePageLayout which needs to be fixed (#1544745). ** Affects: messaging-app (Ubuntu) Importance: Medium Assignee: Gustavo Pichorim Boiko (boiko) Status: New ** Changed in: messaging-app (Ubuntu) Importance: Undecided => Medium ** Changed in: messaging-app (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) ** Branch linked: lp:~boiko/messaging-app/fix_thread_removing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1552811 Title: Replace the current static page managing by object incubator Status in messaging-app package in Ubuntu: New Bug description: Depending on the contents of the page, its asynchronous creation might take a really long time because of the internal behavior (or bug?) of QtQuick. Loading pages synchronously fixes the problem, but the way it is implemented in messaging-app, there is a risk of leaking memory due to pages not being deleted properly when switching views. There is another way to workaround this QtQuick limitation which is to force the page creation to finish before returning to the event loop, in the AdaptivePageLayout context, it would look like this: var incubator = layout.addPageToNextColumn(originalPage, newPage, properties) incubator.forceCompletion() In order for this to be fixed, there is one but in AdaptivePageLayout which needs to be fixed (#1544745). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1552811/+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 1552814] [NEW] After removing one conversation, the view should load the next one
Public bug reported: In desktop mode (showing two views simultaneously), do the following: - Click one of the conversations in the left panel (the conversation will open in the right panel) - Swipe from left to right the conversation item on the left panel and remove it Expected behavior: - The next conversation should be loaded into the view What happens: - The current conversation stays displayed, but as it was deleted, no more messages are on the screen. ** Affects: messaging-app (Ubuntu) Importance: Medium Assignee: Gustavo Pichorim Boiko (boiko) Status: New ** Changed in: messaging-app (Ubuntu) Importance: Undecided => Medium ** Changed in: messaging-app (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) ** Branch linked: lp:~boiko/messaging-app/fix_thread_removing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1552814 Title: After removing one conversation, the view should load the next one Status in messaging-app package in Ubuntu: New Bug description: In desktop mode (showing two views simultaneously), do the following: - Click one of the conversations in the left panel (the conversation will open in the right panel) - Swipe from left to right the conversation item on the left panel and remove it Expected behavior: - The next conversation should be loaded into the view What happens: - The current conversation stays displayed, but as it was deleted, no more messages are on the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1552814/+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 1546369] Re: Messages display in wrong chat channel if sent a message to yourself first
** Changed in: messaging-app (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1546369 Title: Messages display in wrong chat channel if sent a message to yourself first Status in Canonical System Image: Triaged Status in messaging-app package in Ubuntu: In Progress Bug description: $ system-image-cli -i current build number: 258 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 02:38:23 version version: 258 version ubuntu: 20160213 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid Steps to reproduce: 1. First, send a message to yourself 2. Then, send a message to another contact or phone number 3. Check if the messages are displayed in the right chat channel Actual results: 1. The messages both sent and received are displayed on the right in first chat channel 2. The messages are displayed in chat channel of yourself phone number, they are should be displayed in the chat channel of second contact. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546369/+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 1546521] Re: Keyboard overlaps writing area in landscape for multi-line messages
** Changed in: messaging-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1546521 Title: Keyboard overlaps writing area in landscape for multi-line messages Status in messaging-app package in Ubuntu: Confirmed Bug description: Steps to reproduce 1) Switch the phone to landscape orientation 2) Compose a new message 3) In the message input area press return 4 times Expected result Text area shouldn't go beneath the keyboard Actual result The bottom of the message area is now hidden by the keyboard, making it impossible to see what is being typed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1546521/+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 1373059] Re: Messages sent as reply from the notification panel are counted as unseen
** Changed in: messaging-app (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 messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1373059 Title: Messages sent as reply from the notification panel are counted as unseen Status in Canonical System Image: Fix Committed Status in messaging-app package in Ubuntu: Fix Released Bug description: Step to reproduce: - Receive a message - Reply to the messagge from the shortcut in the notification panel - Open the messagges app - There is a number '2' (or 1, don't remember atm, I'll update asap) near the conversation, as you have unseen messages. I expect there are no unread messages, because if I reply to a message, I read it. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373059/+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 1514849] Re: [messaging-app] Gray frame around green message bubble looks jagged
** Branch linked: lp:~boiko/messaging-app/fix_bubble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1514849 Title: [messaging-app] Gray frame around green message bubble looks jagged Status in Ubuntu UX: Triaged Status in messaging-app package in Ubuntu: New Bug description: For some time now the message bubbles have grey frame around them. It looks bad specially on the green bubbles. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1514849/+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 1514849] Re: [messaging-app] Gray frame around green message bubble looks jagged
** Changed in: messaging-app (Ubuntu) Importance: Undecided => Low ** Changed in: messaging-app (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) ** Changed in: messaging-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1514849 Title: [messaging-app] Gray frame around green message bubble looks jagged Status in Ubuntu UX: Triaged Status in messaging-app package in Ubuntu: Confirmed Bug description: For some time now the message bubbles have grey frame around them. It looks bad specially on the green bubbles. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1514849/+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 1493851] Re: Port to upstreamed versions of Audio Role patch
** Also affects: telephony-service (Ubuntu) Importance: Undecided Status: New ** Changed in: telephony-service (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-camera in Ubuntu. https://bugs.launchpad.net/bugs/1493851 Title: Port to upstreamed versions of Audio Role patch Status in Ubuntu Clock App: Fix Released Status in dropping-letters package in Ubuntu: Fix Committed Status in media-hub package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in qtubuntu-camera package in Ubuntu: Fix Committed Status in qtubuntu-media package in Ubuntu: In Progress Status in telephony-service package in Ubuntu: New Status in ubuntu-clock-app package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: The Qt 5.5 packages at https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-012 now include the upstream versions of QML Playlist and Audio Role patches that went in to Qt 5.6. There are some differences in the Audio Role patch compared to the version on vivid-overlay PPA that requires changes. Qt 5.5 targets landing soon after xenial opens. For reference, Old API: http://anonscm.debian.org/cgit/pkg-kde/qt/qtmultimedia.git/diff/debian/patches/adding_media_role_property.patch?h=ubuntu=d5149eefcd093d96be3191d5f8a7f622f788e1f4 New, upstreamed API: http://anonscm.debian.org/cgit/pkg-kde/qt/qtmultimedia.git/tree/debian/patches/Add-audio-role-API-to-QMediaPlayer.patch?h=ubuntu More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting The plan (2015-11-02): Patch some components to work with both old API & Qt 5.4 + new API & Qt 5.5 - qtubuntu-camera, qtubuntu-media to detect at compile time and Unity 8 at runtime. Pulseaudio and media-hub would land only to xenial, switching to the new API as part of the Qt 5.5 silo. Clock and dropping-letters drop the audio role usage as it's not supposed to be used in those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1493851/+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 1483888] Re: Ringtone cannot be heard when jack/headphones plugged
** Changed in: telephony-service (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 telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1483888 Title: Ringtone cannot be heard when jack/headphones plugged Status in Canonical System Image: Fix Released Status in Ubuntu UX: Triaged Status in telephony-service package in Ubuntu: Fix Released Bug description: Aquaris E5: Ringtone cannot be heard when jack/headphones are plugged. This I consider a bug, since user cannot depend on the such a device with hearing calls in the morning. Typical scenario: listening to music/watching movies during the night and falling asleep. It already happened several times to me that I did not get awakened by the phone in the morning, since headphones were plugged into the device and all the sounds could be heard only in headphones. (The equivalent for the alarm clock is bug 1364647.) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1483888/+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 1517612] Re: Page.head.sections selects the first item even though selectedIndex is -1
That's a different problem, not sure it was a problem introduced by the MR
fixing bug 1511839 or if the problem was already there.
Just try the sample program above using the latest UI toolkit (which already
includes the fix for the other mentioned bug) and see the problem.
--
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/1517612
Title:
Page.head.sections selects the first item even though selectedIndex is
-1
Status in Canonical System Image:
Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
In some cases it is desired that no header section is selected when
the program starts. We used to achieve that by setting
head.sections.selectedIndex to -1, but on Ubuntu.Components 1.3 this
doesn't work: the first item gets selected by default. See the sample
program below:
import QtQuick 2.4
import Ubuntu.Components 1.3
MainView {
id: mainview
objectName: "mainView"
width: units.gu(100)
height: units.gu(75)
Page {
id: mainPage
title: "Should not select"
head.sections.model: [ "first", "second", "third" ]
head.sections.selectedIndex: -1
}
}
This is actually a regression, the sample program below works fine on
Ubuntu.Components 1.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517612/+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 1517612] [NEW] Page.head.sections selects the first item even though selectedIndex is -1
Public bug reported:
In some cases it is desired that no header section is selected when the
program starts. We used to achieve that by setting
head.sections.selectedIndex to -1, but on Ubuntu.Components 1.3 this
doesn't work: the first item gets selected by default. See the sample
program below:
import QtQuick 2.4
import Ubuntu.Components 1.3
MainView {
id: mainview
objectName: "mainView"
width: units.gu(100)
height: units.gu(75)
Page {
id: mainPage
title: "Should not select"
head.sections.model: [ "first", "second", "third" ]
head.sections.selectedIndex: -1
}
}
This is actually a regression, the sample program below works fine on
Ubuntu.Components 1.2
** Affects: canonical-devices-system-image
Importance: Medium
Assignee: Zoltan Balogh (bzoltan)
Status: New
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: Medium
Assignee: Zoltan Balogh (bzoltan)
Status: New
--
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/1517612
Title:
Page.head.sections selects the first item even though selectedIndex is
-1
Status in Canonical System Image:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
In some cases it is desired that no header section is selected when
the program starts. We used to achieve that by setting
head.sections.selectedIndex to -1, but on Ubuntu.Components 1.3 this
doesn't work: the first item gets selected by default. See the sample
program below:
import QtQuick 2.4
import Ubuntu.Components 1.3
MainView {
id: mainview
objectName: "mainView"
width: units.gu(100)
height: units.gu(75)
Page {
id: mainPage
title: "Should not select"
head.sections.model: [ "first", "second", "third" ]
head.sections.selectedIndex: -1
}
}
This is actually a regression, the sample program below works fine on
Ubuntu.Components 1.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517612/+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 1517614] [NEW] Page.head.sections.selectedIndex binding of values is broken
Public bug reported:
When trying to assign a binding value to head.sections.selectedIndex, this
value is not updated when the bound value changes.
See the example program below:
import QtQuick 2.4
import Ubuntu.Components 1.3
MainView {
id: mainview
objectName: "mainView"
width: units.gu(100)
height: units.gu(75)
Page {
id: mainPage
title: "selectedIndex: " + head.sections.selectedIndex + " should be: "
+ mainPage.selectedIndex
property int selectedIndex: -1
head.sections.model: [ "first", "second", "third" ]
head.sections.selectedIndex: mainPage.selectedIndex
Rectangle {
anchors.fill: parent
color: "white"
Label {
anchors.centerIn: parent
text: "Click me"
}
}
MouseArea {
anchors.fill: parent
onClicked: mainPage.selectedIndex = (mainPage.selectedIndex + 1) % 3
}
}
}
** Affects: canonical-devices-system-image
Importance: High
Assignee: Zoltan Balogh (bzoltan)
Status: New
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: High
Assignee: Zoltan Balogh (bzoltan)
Status: New
--
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/1517614
Title:
Page.head.sections.selectedIndex binding of values is broken
Status in Canonical System Image:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
When trying to assign a binding value to head.sections.selectedIndex, this
value is not updated when the bound value changes.
See the example program below:
import QtQuick 2.4
import Ubuntu.Components 1.3
MainView {
id: mainview
objectName: "mainView"
width: units.gu(100)
height: units.gu(75)
Page {
id: mainPage
title: "selectedIndex: " + head.sections.selectedIndex + " should be:
" + mainPage.selectedIndex
property int selectedIndex: -1
head.sections.model: [ "first", "second", "third" ]
head.sections.selectedIndex: mainPage.selectedIndex
Rectangle {
anchors.fill: parent
color: "white"
Label {
anchors.centerIn: parent
text: "Click me"
}
}
MouseArea {
anchors.fill: parent
onClicked: mainPage.selectedIndex = (mainPage.selectedIndex + 1)
% 3
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517614/+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 1515734] Re: header not resizing properly after showing Recents view
** Changed in: dialer-app (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) ** Changed in: dialer-app (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1515734 Title: header not resizing properly after showing Recents view Status in dialer-app package in Ubuntu: New Bug description: rc-proposed on krillin build 175 The header is too big after you first view the Recents page, it does not properly resize to it's initial height. Steps to reproduce: 1) Launch dialer 2) Verify header does not contain extra white space lines 3) pull up recents page from bottom edge 4) make a phone call or go back to main view Expected results: header should resize to initial size without extra white space Actual results: header stays same size as it was in Recents page with extra white space (see attachments) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1515734/+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 1515675] Re: Keypad view not properly formatted when on live call
** Changed in: dialer-app (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1515675 Title: Keypad view not properly formatted when on live call Status in Canonical System Image: Confirmed Status in dialer-app package in Ubuntu: In Progress Bug description: latest rc-proposed 1) Make a phone call 2) after call connected, press the keypad icon Expected results: - contact name should stay in header - all action buttons should still be visible Actual results: - contact name disapears from header - keypad buttons overlap the action buttons see attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1515675/+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 1515012] Re: SIM not selected in header on incoming call
** Changed in: dialer-app (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1515012 Title: SIM not selected in header on incoming call Status in Canonical System Image: Confirmed Status in dialer-app package in Ubuntu: In Progress Bug description: latest rc-proposed When you receive a call, the dialer shows the correct SIM label in the header but it is not selected. It should be selected (i.e. should have orange highlighting). See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1515012/+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 1484300] Re: /usr/bin/dialer-app:11:QScopedLoopLevelCounter:QCoreApplication::notifyInternal:sendEvent:QCoreApplicationPrivate::sendPostedEvents:QCoreApplication::sendPostedEvent
** Changed in: dialer-app (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 dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1484300 Title: /usr/bin/dialer- app:11:QScopedLoopLevelCounter:QCoreApplication::notifyInternal:sendEvent:QCoreApplicationPrivate::sendPostedEvents:QCoreApplication::sendPostedEvents Status in Canonical System Image: Fix Committed Status in dialer-app package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding dialer-app. This problem was most recently seen with version 0.1+15.10.20150615-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/86fd27665d578509408b73f1950422e5b3f31faa contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1484300/+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 1513044] Re: autopilot tests failing, unable to find 'Label'
A fix for that is already landed in messaging-app.
** Changed in: messaging-app (Ubuntu)
Status: New => Fix Released
** Changed in: messaging-app (Ubuntu)
Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1513044
Title:
autopilot tests failing, unable to find 'Label'
Status in Canonical System Image:
Confirmed
Status in messaging-app package in Ubuntu:
Fix Released
Bug description:
Running the messaging-app autopilot tests, we get 20 out of 27 tests
failing. The majority of them due to not being able to find 'Label'
objects. This appears to be because Label has changed to UCLabel in a
recent version of messaging-app. Below is a typical traceback from one
of the failures:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/messaging_app/tests/test_messaging.py", line
290, in test_delete_message_swipe_right
self.main_view.send_message([phone_num], message)
File "/usr/lib/python3/dist-packages/autopilot/logging.py", line 46, in
inner
return f(instance, *args, **kwargs)
File "/usr/lib/python3/dist-packages/messaging_app/emulators.py", line 392,
in send_message
thread_bubble = self.get_message(message)
File "/usr/lib/python3/dist-packages/messaging_app/emulators.py", line 68,
in get_message
'{}'.format(text))
messaging_app.emulators.EmulatorException: Could not find message with the
text delete me okay
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 164
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-11-04 10:36:00
version version: 164
version ubuntu: 20151104
version device: 20150821-736d127
version custom: 20150925-901-35-40-vivid
Attached is a subunit file with all the results from the run - it can
be best viewed with the 'trv' application:
https://launchpad.net/~thomir/+archive/ubuntu/trv
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513044/+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 1415458] Re: Add support for MMS group chat
** Changed in: telepathy-ofono (Ubuntu) Status: In Progress => Fix Released ** No longer affects: gsettings-ubuntu-touch-schemas (Ubuntu Vivid) ** No longer affects: messaging-app (Ubuntu Vivid) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-ubuntu-touch- schemas in Ubuntu. https://bugs.launchpad.net/bugs/1415458 Title: Add support for MMS group chat Status in Canonical System Image: Fix Released Status in GSettings Ubuntu touch schemas: Fix Released Status in messaging-app: Fix Released Status in telepathy-ofono: Fix Released Status in telephony-service: Fix Released Status in gsettings-ubuntu-touch-schemas package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in telepathy-ofono package in Ubuntu: Fix Released Status in telepathy-qt5 package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu: Fix Released Bug description: Currently when you send a message to multiple recipients, one SMS is sent per recipient, and they don't know about each other. Messaging-app needs to also support MMS group chat, which allows for true group conversations. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415458/+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 1511839] [NEW] On dynamically created pages, head.sections.selectedIndex can't be set to -1
Public bug reported:
Ubuntu.Components version: 1.3
Some times it is desirable that none of the entries in the head.sections.model
is selected by default.
While that works fine on statically created pages, if I define a page inside a
component, or load it directly from a QML file, this is not respected.
The following sample QML application reproduces the problem:
import QtQuick 2.3
import Ubuntu.Components 1.3
MainView {
width: units.gu(30)
height: units.gu(60)
Component {
id: pageComponent
Page {
id: page
title: i18n.tr("The Page")
head.sections.model: ["one","two","three"]
head.sections.selectedIndex: -1
}
}
PageStack {
id: stack
}
Component.onCompleted: {
stack.push(pageComponent)
}
}
Expected result: a page with no section selected.
What happens: the first section of the header is selected by default
** Affects: canonical-devices-system-image
Importance: High
Assignee: Zoltan Balogh (bzoltan)
Status: New
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: High
Assignee: Zoltan Balogh (bzoltan)
Status: New
--
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/1511839
Title:
On dynamically created pages, head.sections.selectedIndex can't be set
to -1
Status in Canonical System Image:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
Ubuntu.Components version: 1.3
Some times it is desirable that none of the entries in the
head.sections.model is selected by default.
While that works fine on statically created pages, if I define a page inside
a component, or load it directly from a QML file, this is not respected.
The following sample QML application reproduces the problem:
import QtQuick 2.3
import Ubuntu.Components 1.3
MainView {
width: units.gu(30)
height: units.gu(60)
Component {
id: pageComponent
Page {
id: page
title: i18n.tr("The Page")
head.sections.model: ["one","two","three"]
head.sections.selectedIndex: -1
}
}
PageStack {
id: stack
}
Component.onCompleted: {
stack.push(pageComponent)
}
}
Expected result: a page with no section selected.
What happens: the first section of the header is selected by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1511839/+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 1511839] Re: On dynamically created pages, head.sections.selectedIndex can't be set to -1
Just as a note, this bug is actually a regression, since this used to
work fine in previous versions of UITK.
Messaging-app is affected by this problem: although visually it looks
like the first SIM card is selected, when the user presses the "Send"
button he gets a message saying that no SIM card was selected
--
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/1511839
Title:
On dynamically created pages, head.sections.selectedIndex can't be set
to -1
Status in Canonical System Image:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
Ubuntu.Components version: 1.3
Some times it is desirable that none of the entries in the
head.sections.model is selected by default.
While that works fine on statically created pages, if I define a page inside
a component, or load it directly from a QML file, this is not respected.
The following sample QML application reproduces the problem:
import QtQuick 2.3
import Ubuntu.Components 1.3
MainView {
width: units.gu(30)
height: units.gu(60)
Component {
id: pageComponent
Page {
id: page
title: i18n.tr("The Page")
head.sections.model: ["one","two","three"]
head.sections.selectedIndex: -1
}
}
PageStack {
id: stack
}
Component.onCompleted: {
stack.push(pageComponent)
}
}
Expected result: a page with no section selected.
What happens: the first section of the header is selected by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1511839/+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 1488852] Re: [pocket desktop] + [dialer app] window feels funny on windowed mode
** Changed in: dialer-app (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1488852 Title: [pocket desktop] + [dialer app] window feels funny on windowed mode Status in Canonical System Image: Confirmed Status in canonical-pocket-desktop: New Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: In Progress Bug description: while trying out simulated phone calls on nexus4 vivid+o+silo0 the dialer app has the big green dial/hangup button floating over the numbers if not sized to the expected phone formfactor (specifically sized smaller) so maybe this is a design question - should the dialer app have a fixed minimum? should the dialer app window even be allowed to resize ? and what to do if that minimum doesn't fit on screen well ? - UX comment - The dialer app should have a set minimum window size on the desktop so that all functionalities are always visible and accessible. Ideally the window should not be resized for the time being. If it is unavoidable to increase the window size then the additional GU can simply be filled with white space/the same background the dialer is using. For a greater user experience a longer term solution is to make the dialer convergent, meaning it would use the multi column layout similar to the AB and messaging apps. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488852/+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 1480815] Re: Receiving MMS will auto change into group chat for some operators
** Changed in: messaging-app (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 messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1480815 Title: Receiving MMS will auto change into group chat for some operators Status in Canonical System Image: Fix Committed Status in messaging-app package in Ubuntu: Fix Released Bug description: system-image-cli -i current build number: 80 device name: arale channel: ubuntu-touch/devel-proposed/meizu.en last update: 2015-08-03 15:23:15 version version: 80 version ubuntu: 20150802 version device: 20150709-8965e37 version custom: 20150716-819-8-42 reproduce steps: 1.there is a CMCC SIM card inserted in the DUT device. 2.there is no contact in the device and the MMS group chat option was disabled 3.other device send one MMS just to the DUT 4.the DUT received the MMS 5.launch the message app check the received MMS expect result: (5) the MMS display in the dialog panel and show the the number of the sender and the word content actual result: the dialog panel of the message change to group chat auto. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480815/+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 1511072] [NEW] Language selector scrolling performance is poor in welcome wizard
Public bug reported: Device: krillin Image version: 159 Channel: ubuntu-touch/rc-proposed/bq-aquaris.en Scrolling in the language selector is slow. In the image reported above, the list doesn't even scroll automatically if you swipe. It just moves two or three items down and stops. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1511072 Title: Language selector scrolling performance is poor in welcome wizard Status in unity8 package in Ubuntu: New Bug description: Device: krillin Image version: 159 Channel: ubuntu-touch/rc-proposed/bq-aquaris.en Scrolling in the language selector is slow. In the image reported above, the list doesn't even scroll automatically if you swipe. It just moves two or three items down and stops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1511072/+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 1484300] Re: /usr/bin/dialer-app:11:QScopedLoopLevelCounter:QCoreApplication::notifyInternal:sendEvent:QCoreApplicationPrivate::sendPostedEvents:QCoreApplication::sendPostedEvent
** Changed in: dialer-app (Ubuntu) Status: New => In Progress ** Changed in: canonical-devices-system-image Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1484300 Title: /usr/bin/dialer- app:11:QScopedLoopLevelCounter:QCoreApplication::notifyInternal:sendEvent:QCoreApplicationPrivate::sendPostedEvents:QCoreApplication::sendPostedEvents Status in Canonical System Image: In Progress Status in dialer-app package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding dialer-app. This problem was most recently seen with version 0.1+15.10.20150615-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/86fd27665d578509408b73f1950422e5b3f31faa contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1484300/+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 1508074] [NEW] Timezone changes are only reflected in history-service data after rebooting
Public bug reported: Right now if you change the timezone of the phone, history-service will continue to use the previous timezone until the phone is rebooted. Ideally the service would use UTC for everything and only the apps using it would need to be restarted to reflect the changes. ** Affects: history-service (Ubuntu) Importance: Medium Assignee: Gustavo Pichorim Boiko (boiko) Status: New ** Changed in: history-service (Ubuntu) Importance: Undecided => Medium ** Changed in: history-service (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1508074 Title: Timezone changes are only reflected in history-service data after rebooting Status in history-service package in Ubuntu: New Bug description: Right now if you change the timezone of the phone, history-service will continue to use the previous timezone until the phone is rebooted. Ideally the service would use UTC for everything and only the apps using it would need to be restarted to reflect the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1508074/+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 1508074] Re: Timezone changes are only reflected in history-service data after rebooting
Just realized Qt internally gets the new timezone. ** Changed in: history-service (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1508074 Title: Timezone changes are only reflected in history-service data after rebooting Status in history-service package in Ubuntu: Invalid Bug description: Right now if you change the timezone of the phone, history-service will continue to use the previous timezone until the phone is rebooted. Ideally the service would use UTC for everything and only the apps using it would need to be restarted to reflect the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1508074/+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 1507662] [NEW] if history has multiple calls to same phone number, not all entries are displayed
Public bug reported: Steps to reproduce: - using dialer-app make sure you have lots of calls to the same phone number happening in sequence (around 20 or 30). - reopen the app expected result: - all calls are shown in the call log what happens: - the call log stops at the entry which has the multiple calls ** Affects: canonical-devices-system-image Importance: Medium Assignee: Bill Filler (bfiller) Status: Confirmed ** Affects: history-service (Ubuntu) Importance: Medium Assignee: Gustavo Pichorim Boiko (boiko) Status: Confirmed ** Changed in: history-service (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1507662 Title: if history has multiple calls to same phone number, not all entries are displayed Status in Canonical System Image: Confirmed Status in history-service package in Ubuntu: Confirmed Bug description: Steps to reproduce: - using dialer-app make sure you have lots of calls to the same phone number happening in sequence (around 20 or 30). - reopen the app expected result: - all calls are shown in the call log what happens: - the call log stops at the entry which has the multiple calls To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507662/+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 1485803] Re: [system settings] No notification for which Sim card call is received from
** Project changed: dialer-app => ubuntu ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1485803 Title: [system settings] No notification for which Sim card call is received from Status in Ubuntu UX: Triaged Status in dialer-app package in Ubuntu: New Bug description: When using the dual sim feature of the BQ Aquaris 4.5, there is no indication of which sim card a call is being received from. I.e., I run two businesses, and when my phone rings I have no idea which number someone is calling. Ideally there would be a different ringtone per sim card, as well as text notification on the answer call panel. There should also be the option of setting a different message tone for incoming messages per sim card. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1485803/+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 1485803] Re: [system settings] No notification for which Sim card call is received from
** Also affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1485803 Title: [system settings] No notification for which Sim card call is received from Status in Ubuntu UX: Triaged Status in dialer-app package in Ubuntu: New Bug description: When using the dual sim feature of the BQ Aquaris 4.5, there is no indication of which sim card a call is being received from. I.e., I run two businesses, and when my phone rings I have no idea which number someone is calling. Ideally there would be a different ringtone per sim card, as well as text notification on the answer call panel. There should also be the option of setting a different message tone for incoming messages per sim card. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1485803/+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 1494630] Re: app crashes when selecting a contact from favourites
Can you confirm that this problem still happens? ** Changed in: dialer-app (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) ** Changed in: dialer-app (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1494630 Title: app crashes when selecting a contact from favourites Status in dialer-app package in Ubuntu: New Bug description: On a bq aquaris 4.5, stable channel, since September: When selecting a contact from 'Favourites', the app crashes every time. When selecting the same person from 'All', everyhing is fine. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1494630/+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 1360241] Re: [Regression] "LLVM ERROR: Do not know how to split the result of this operator!" in executing Ubuntu UI Toolkit tests on x86
Got the same in messaging-app on ppc64el too: https://launchpadlibrarian.net/219673246/buildlog_ubuntu-wily-ppc64el .messaging-app_0.1%2B15.10.20151002-0ubuntu1_BUILDING.txt.gz (http://paste.ubuntu.com/12638691/) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1360241 Title: [Regression] "LLVM ERROR: Do not know how to split the result of this operator!" in executing Ubuntu UI Toolkit tests on x86 Status in llvm-toolchain-3.5 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Fix Released Bug description: With upgrade to LLVM 3.5, UITK tests start failing with LLVM error. This was reported earlier and the change to 3.5 reverted, but now 3.5 landed again. So we're seeing errors like this: https://launchpadlibrarian.net/182951835/buildlog_ubuntu-utopic-i386.ubuntu-ui-toolkit_1.1.1206%2B14.10.20140822-0ubuntu1_FAILEDTOBUILD.txt.gz To reproduce, simply bzr branch lp:ubuntu-ui-toolkit and run bzr bd which also executes the unit tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.5/+bug/1360241/+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 1502255] Re: make it possible to use custom history.sqlite files in FillCustomSmsHistory
** Changed in: messaging-app (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1502255 Title: make it possible to use custom history.sqlite files in FillCustomSmsHistory Status in messaging-app package in Ubuntu: New Bug description: Hi! Right now the database is hard coded, we need a way to provide custom database as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1502255/+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 1488498] Re: Message indicator shows not existing messages
** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1488498 Title: Message indicator shows not existing messages Status in Canonical System Image: Fix Committed Status in messaging-app package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu: Fix Released Bug description: As I travelled abroad, I got some network messages which I deleted without reading through the inbox of the messaging application. The problem is, that indicator above the screen steel sees the message though it doesn't exist any more. The LED of my bq blinks green and I see a green envelope in the indicator area above. When I click the green envelope that is supposed to inform me that there is/are some unread messages in my Inbox, I see a preview of the whole message, I can answer it but when I click the white message cloud, my Inbox of the messenger application will be opened and shows me all messages but not the one from indicator that I already had deleted. As I wrote at the start, I had my Inbox opened when the two messages came and I deleted them both without openning. Seems like we've got some Matrix situation where two phone application get an information about the new message but the apps doesn't communicate with each other to inform the indicator, that the indicated message had already been deleted. Not a big problem but looks pretty primitive in comparison to other devices on the market. There is one more indicator: the LED of the phone that blinks as long as the notification envelope is green. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488498/+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 1488984] Re: new send button touch area too small
** Changed in: messaging-app (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1488984 Title: new send button touch area too small Status in Canonical System Image: Confirmed Status in messaging-app package in Ubuntu: In Progress Bug description: with the updated send button in messaging-app, it seems the touch target area has been quite reduced and now it's difficult to try and press it but miss. Happens often to me. We should leave the new icon the same, but add some additional padding to each side and make sure the touch area is bigger than the icon and extends the touch area so it's easier to trigger. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488984/+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 1488498] Re: Message indicator shows not existing messages
** Changed in: messaging-app (Ubuntu) Status: Confirmed => In Progress ** Changed in: messaging-app (Ubuntu) Assignee: Tiago Salem Herrmann (tiagosh) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1488498 Title: Message indicator shows not existing messages Status in Canonical System Image: Confirmed Status in messaging-app package in Ubuntu: In Progress Bug description: As I travelled abroad, I got some network messages which I deleted without reading through the inbox of the messaging application. The problem is, that indicator above the screen steel sees the message though it doesn't exist any more. The LED of my bq blinks green and I see a green envelope in the indicator area above. When I click the green envelope that is supposed to inform me that there is/are some unread messages in my Inbox, I see a preview of the whole message, I can answer it but when I click the white message cloud, my Inbox of the messenger application will be opened and shows me all messages but not the one from indicator that I already had deleted. As I wrote at the start, I had my Inbox opened when the two messages came and I deleted them both without openning. Seems like we've got some Matrix situation where two phone application get an information about the new message but the apps doesn't communicate with each other to inform the indicator, that the indicated message had already been deleted. Not a big problem but looks pretty primitive in comparison to other devices on the market. There is one more indicator: the LED of the phone that blinks as long as the notification envelope is green. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488498/+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 1488498] Re: Message indicator shows not existing messages
** Also affects: telephony-service (Ubuntu) Importance: Undecided Status: New ** Changed in: telephony-service (Ubuntu) Status: New => In Progress ** Changed in: telephony-service (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1488498 Title: Message indicator shows not existing messages Status in Canonical System Image: Confirmed Status in messaging-app package in Ubuntu: In Progress Status in telephony-service package in Ubuntu: In Progress Bug description: As I travelled abroad, I got some network messages which I deleted without reading through the inbox of the messaging application. The problem is, that indicator above the screen steel sees the message though it doesn't exist any more. The LED of my bq blinks green and I see a green envelope in the indicator area above. When I click the green envelope that is supposed to inform me that there is/are some unread messages in my Inbox, I see a preview of the whole message, I can answer it but when I click the white message cloud, my Inbox of the messenger application will be opened and shows me all messages but not the one from indicator that I already had deleted. As I wrote at the start, I had my Inbox opened when the two messages came and I deleted them both without openning. Seems like we've got some Matrix situation where two phone application get an information about the new message but the apps doesn't communicate with each other to inform the indicator, that the indicated message had already been deleted. Not a big problem but looks pretty primitive in comparison to other devices on the market. There is one more indicator: the LED of the phone that blinks as long as the notification envelope is green. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488498/+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 1490645] Re: "Message" not translated in notification
This string actually comes from ubuntu-settings-components, and is properly wrapped around with i18n.tr() tags. The problem is that the package itself doesn't seem to be generating the potfile anywhere. ** Also affects: ubuntu-settings-components (Ubuntu) Importance: Undecided Status: New ** Changed in: telephony-service (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-settings-components (Ubuntu) Importance: Undecided => High ** Changed in: telephony-service (Ubuntu) Assignee: Tiago Salem Herrmann (tiagosh) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1490645 Title: "Message" not translated in notification Status in Canonical System Image: New Status in telephony-service package in Ubuntu: Invalid Status in ubuntu-settings-components package in Ubuntu: New Bug description: Test case. - Flash the phone - Switch to Spanish. - Make a missing call. - Open the messaging indicator. - Tap on the missed call notification to display snap decisions. Expected result. - All buttons must be translated to Spanish. Actual result. - "Message" button is shown in English. current build number: 112 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1490645/+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 1488988] Re: slow to load a thread
** Branch linked: lp:~boiko/history- service/store_normalized_phone_numbers ** Branch linked: lp:~tiagosh/messaging-app/updateFilters-binding -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1488988 Title: slow to load a thread Status in Canonical System Image: Confirmed Status in messaging-app package in Ubuntu: Confirmed Bug description: On latest rc-proposed and ota-6 the time to load a message thread has increased. It sometimes takes a very long time to open the thread view, longer in some cases then others. We should profile what is happening, possibly the contact lookup is taking a long time. In theory, we should load the view immediately and async fill in any information that we need. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488988/+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 1488988] Re: slow to load a thread
** Also affects: history-service (Ubuntu) Importance: Undecided Status: New ** Changed in: history-service (Ubuntu) Importance: Undecided = High ** Changed in: history-service (Ubuntu) Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1488988 Title: slow to load a thread Status in Canonical System Image: Confirmed Status in history-service package in Ubuntu: New Status in messaging-app package in Ubuntu: Confirmed Bug description: On latest rc-proposed and ota-6 the time to load a message thread has increased. It sometimes takes a very long time to open the thread view, longer in some cases then others. We should profile what is happening, possibly the contact lookup is taking a long time. In theory, we should load the view immediately and async fill in any information that we need. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488988/+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 1488922] [NEW] AdaptivePageLayout fails to show custom header contents
Public bug reported: In some cases AdaptivePageLayout fails to show the header contents. The attached QML example should be showing an orange rectangle in the header contents, but it is not. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Attachment added: AdaptivePageLayout bug https://bugs.launchpad.net/bugs/1488922/+attachment/4452704/+files/adaptivelayoutexample.qml -- 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/1488922 Title: AdaptivePageLayout fails to show custom header contents Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: In some cases AdaptivePageLayout fails to show the header contents. The attached QML example should be showing an orange rectangle in the header contents, but it is not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1488922/+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 1486187] Re: Sending an SMS to your own number triggers an empty row in messaging-app
** Changed in: history-service (Ubuntu) Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) ** Changed in: history-service (Ubuntu) Importance: Undecided = Low ** Changed in: history-service (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1486187 Title: Sending an SMS to your own number triggers an empty row in messaging- app Status in history-service package in Ubuntu: Confirmed Bug description: Steps to reproduce: - open messaging-app - send an SMS to your own number Expected behavior: - a conversation with your own number is displayed What happens: - an empty row is shown in the conversation list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1486187/+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 1449598] Re: messages not getting cleared from messaging indicator
*** This bug is a duplicate of bug 1482401 *** https://bugs.launchpad.net/bugs/1482401 ** No longer affects: messaging-app (Ubuntu Vivid) ** This bug has been marked a duplicate of bug 1482401 Race condition when removing read sms's from the indicator menu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1449598 Title: messages not getting cleared from messaging indicator Status in Canonical System Image: Fix Released Status in history-service package in Ubuntu: In Progress Status in messaging-app package in Ubuntu: Fix Released Bug description: on arale r185 Not sure exact steps to reproduce, but sometimes when reading a message in the messaging app it still remains in the messaging menu. It does not get cleared as it should. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449598/+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 1486187] [NEW] Sending an SMS to your own number triggers an empty row in messaging-app
Public bug reported: Steps to reproduce: - open messaging-app - send an SMS to your own number Expected behavior: - a conversation with your own number is displayed What happens: - an empty row is shown in the conversation list ** Affects: history-service (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:~tiagosh/history- service/manually_add_self_contact_to_participants -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1486187 Title: Sending an SMS to your own number triggers an empty row in messaging- app Status in history-service package in Ubuntu: New Bug description: Steps to reproduce: - open messaging-app - send an SMS to your own number Expected behavior: - a conversation with your own number is displayed What happens: - an empty row is shown in the conversation list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1486187/+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 1485724] Re: Fail to match phone number when receiving a message
** Also affects: libphonenumber (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1485724 Title: Fail to match phone number when receiving a message Status in libphonenumber package in Ubuntu: New Status in messaging-app package in Ubuntu: New Bug description: Receiving a message from +28909 shows the wrong contact on the notification. Steps to reproduce: 1 - Create a contact with the phone number: +13611361530 and name Contact bug 2 - Install ofono-phonesim-autostart package (sim card emulator) 3 - reboot the device 4 - Run: mc-tool update ofono/ofono/account0 string:modem-objpath=/phonesim mc-tool reconnect ofono/ofono/account0 5 - Try to run the attached python script : python3 script-name Expected result: 6 - The message menu should show a messaging from number +28909 Current result: 7 - The message menu is showing a new message from contact Contact bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libphonenumber/+bug/1485724/+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 1473011] Re: [PATCH] Skip network checks on always dispatchable accounts
Sorry for the delay, the fix is currently being tested and should be available soon on Wily and on vivid stable phone overlay. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1473011 Title: [PATCH] Skip network checks on always dispatchable accounts Status in telepathy-mission-control-5 package in Ubuntu: New Bug description: MissionControl does not seem to connect accounts that have always_dispatch=true attribute set; that attribute is meant to serve as skip network connection checks when connecting-kind of thing. After some investigation, I've found a possible bug and created a patch. I've posted this patch to upstream [1] but the general activity in the project has declined and so it might take quite some time before it's reviewed and put into a release. Therefore I was advised to file a bug report here for a chance for this patch to be included as a distro patch. This would also help fix this issue in ubuntu-phone, where it is currently being workarounded[2]. The patch itself is located at [1] so I'm not going to reupload it here. Cheers, Martin [1] - https://bugs.freedesktop.org/show_bug.cgi?id=91272 [2] - http://bazaar.launchpad.net/~phablet-team/telephony-service/trunk/view/head:/tools/ofono-setup#L39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1473011/+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 1470938] Re: Unknown number not translated
** Changed in: dialer-app (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 dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1470938 Title: Unknown number not translated Status in Canonical System Image: Confirmed Status in dialer-app package in Ubuntu: Fix Released Bug description: Test case. - Flash the phone. - Switch to Spanish. - Reboot. - Receive and accept a call from a hidden number. Expected result. - Unknown number is displayed in Spanish. Actual result. - Unknown number is displayed in English. The string is available in dialer-app.mo. This happened when receiving the call from Telegram for the signup code. current build number: 55 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470938/+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 1476826] [NEW] Calling from car does not display live call view on dialer-app
Public bug reported: Steps to reproduce: 1. connect your device to the car kit's bluetooth 2. start a call from the car kit (startin the call from the device won't show the problem) 3. wait for dialer-app to be launched Expected results: - the live call view is displayed on dialer-app Actual result: - the dialpad view is displayed Note that after the remote end accepts the call, the live call is then displayed on dialer-app. ** Affects: canonical-devices-system-image Importance: Medium Assignee: Bill Filler (bfiller) Status: Confirmed ** Affects: telephony-service (Ubuntu) Importance: Medium Assignee: Gustavo Pichorim Boiko (boiko) Status: Confirmed ** Changed in: telephony-service (Ubuntu) Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1476826 Title: Calling from car does not display live call view on dialer-app Status in Canonical System Image: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. connect your device to the car kit's bluetooth 2. start a call from the car kit (startin the call from the device won't show the problem) 3. wait for dialer-app to be launched Expected results: - the live call view is displayed on dialer-app Actual result: - the dialpad view is displayed Note that after the remote end accepts the call, the live call is then displayed on dialer-app. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1476826/+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 1471306] Re: stuck on LiveCall screen after call is remotely hung up
** Changed in: dialer-app (Ubuntu) Status: New = Confirmed ** Changed in: dialer-app (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1471306 Title: stuck on LiveCall screen after call is remotely hung up Status in Canonical System Image: Confirmed Status in dialer-app package in Ubuntu: In Progress Bug description: latest vivid image 55 krillin or 44 arale Steps to reproduce: 1) open dialer and place phone call 2) when call is active, click on the + button to add another contact 3) click on a contact from the contact list 4) now hang up the call from the remote phone Expected results: - LIve Call page should be shown with Call Ended message which should disappear after some time Actual results: - contact page stays shown - clicking the back button will bring you back to Live Call page that is stuck on Call Ended message and an active hang up button which performs no action when clicked - you are stuck on this page until you kill the app To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471306/+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 1364372] Re: [dialer] No way out if dialed from passcode locked device.
This has been fixed already. After the call ends, the lock screen is brought up, and if for any reason it doesn't, there is a back button in dialpad that will get you out of dialer and into the lock screen. ** Changed in: dialer-app (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1364372 Title: [dialer] No way out if dialed from passcode locked device. Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: Fix Released Bug description: USED VERSION: current build number: 11 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-09-02 10:10:53 version version: 11 version ubuntu: 20140902 version device: 20140829-678239d TEST STEPS: 1) Start phone with SIM without locked SIM PIN. Phone must be such that you haven't change the security to swipe ever before. Phone must have passcode protection on. 2) Wait for phone to connect to cellular network. 3) Choose emergency call and dial. 4) End the call. Try to swipe the UI back. EXPECTED RESULT: UI goes back to the Enter passphase view or basic idle screen shown when UI is locked ACTUAL RESULT: There is no way to go swipe back before UI has dimmed. Only way is to double-click the power key. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1364372/+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 1461861] Re: Cannot dismiss 'No network' dialog
** Changed in: messaging-app (Ubuntu) Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1461861 Title: Cannot dismiss 'No network' dialog Status in Canonical System Image: Confirmed Status in messaging-app package in Ubuntu: Confirmed Bug description: current build number: 24 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-06-03 23:14:51 version version: 24 version ubuntu: 20150603 version device: 20150529-8e13c5f version custom: 20150528-722-29-15-vivid Test Case: Requires a SIM with no service 1. Boot a freshly flashed device 2. Don't unlock the SIM or use a SIM without credit 3. Open the messaging app, select the SIM without service as default 4. Enter a message and send it EXPECTED BEHAVIOUR The 'No network' dialog is displayed and can be dismissed ACTUAL RESULT The 'No network' dialog is displayed and cannot be dismissed Note that the 'swipe message' demo is displayed behind the 'no network' dialog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1461861/+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 1470938] Re: Unknown number not translated
** Changed in: dialer-app (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1470938 Title: Unknown number not translated Status in Canonical System Image: Confirmed Status in dialer-app package in Ubuntu: In Progress Bug description: Test case. - Flash the phone. - Switch to Spanish. - Reboot. - Receive and accept a call from a hidden number. Expected result. - Unknown number is displayed in Spanish. Actual result. - Unknown number is displayed in English. The string is available in dialer-app.mo. This happened when receiving the call from Telegram for the signup code. current build number: 55 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470938/+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 1444883] Re: Emergency numbers other than 112 and 911 (and 999 for the UK) are not available in emergency mode
This is the same bug as #1334860 We need to switch telephony-service, dialer-app, etc to use libphonenumber's emergency number database instead of relying on ofono to get the list -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1444883 Title: Emergency numbers other than 112 and 911 (and 999 for the UK) are not available in emergency mode Status in Canonical System Image: Confirmed Status in dialer-app package in Ubuntu: New Status in ofono package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: New Bug description: arale device, r177, ubuntu-touch/vivid-proposed Steps 1. Emergency mode (e.g. Lock phone with a passcode, slide left, tap on Emergency Call) 2. try input 911, 112 == OK 2. try input 110, 119 == Dial button is inactive after number is input Expect Allow these numbers in emergency mode To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1444883/+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 1470938] Re: Unknown number not translated
** Changed in: dialer-app (Ubuntu) Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1470938 Title: Unknown number not translated Status in dialer-app package in Ubuntu: Triaged Bug description: Test case. - Flash the phone. - Switch to Spanish. - Reboot. - Receive and accept a call from a hidden number. Expected result. - Unknown number is displayed in Spanish. Actual result. - Unknown number is displayed in English. The string is available in dialer-app.mo. This happened when receiving the call from Telegram for the signup code. current build number: 55 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1470938/+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 1473537] Re: App icon inconsistency
** Changed in: messaging-app (Ubuntu) Status: New = In Progress ** Changed in: messaging-app (Ubuntu) Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) ** Changed in: messaging-app (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1473537 Title: App icon inconsistency Status in messaging-app package in Ubuntu: In Progress Bug description: STEPS: 1. Receive a message from someone not in your addressbook 2. Open the messaging app 3. Note the icon on the message in the main view 4. Open the message 5. Note the icon on the top right to add a contact EXPECTED: I expect to see the same icons throughout ACTUAL: The new icon looks like a fat number 8 which is correct in the main view but wrong in the message view for add a user, I expect to see the icon you see in the recent calls slider for add to addressbook VERSION: current build number: 64 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en-proposed last update: 2015-07-10 14:12:17 version version: 64 version ubuntu: 20150710 version device: 20150709-8965e37 version custom: 20150709-814-6-40 MODIFICATIONS: Nil SCREENSHOT STORY: 1. Main view of messaging app 2. Messaging view with erroneous icon 3. Dialer app recent slider view for expected icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1473537/+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 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default
I guess the problem here is that telephony-service is not involved in the process of placing the call: that's all done at the ofono level. When telepathy-ofono (and thus telephony-service) get notified about the call, it is already placed in the wrong modem. I don't know how this is handle inside ofono, but maybe there is a way for us to set a property saying which of the modems should be used when placing calls via HFP? ** Changed in: telephony-service (Ubuntu) Assignee: Tiago Salem Herrmann (tiagosh) = Gustavo Pichorim Boiko (boiko) ** Changed in: telephony-service (Ubuntu RTM) Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default Status in the base for Ubuntu mobile products: New Status in ofono package in Ubuntu: New Status in telephony-service package in Ubuntu: New Status in telephony-service package in Ubuntu RTM: New Bug description: What happened Placed call from car over bluetooth Call was placed on my first SIM card, even though I selected my second SIM as default for calls What should have happened The call should have been placed on my second SIM ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20150124-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu4 Architecture: armhf Date: Wed Feb 4 14:25:44 2015 InstallationDate: Installed on 2015-02-02 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150202-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+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 1356497] Re: Can't make the project in a build dir
Just tried with a fresh checkout of dialer-app, it is fixed: boiko@thinkpad:/tmp/dialer-app$ mkdir build boiko@thinkpad:/tmp/dialer-app$ cd build/ boiko@thinkpad:/tmp/dialer-app/build$ cmake ../ -- The C compiler identification is GNU 4.9.2 -- The CXX compiler identification is GNU 4.9.2 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Found Lcov: /usr/bin/lcov -- Found gcovr: /usr/bin/gcovr -- Found PkgConfig: /usr/bin/pkg-config (found version 0.28) -- Found Gettext: /usr/bin/msgmerge (found version 0.19.2) -- Configuring done -- Generating done -- Build files have been written to: /tmp/dialer-app/build ** Changed in: dialer-app (Ubuntu) Status: Confirmed = Fix Released ** Changed in: dialer-app (Ubuntu) Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1356497 Title: Can't make the project in a build dir Status in dialer-app package in Ubuntu: Fix Released Bug description: cmake is instended to separate the source from the built files, but it's currently not possible to make the project in a builddir. To reproduce: mkdir builddir cd builddir cmake .. make - fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1356497/+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 1469266] Re: Voicemail message shown after a reboot when there are no messages
According to the logs, ofono thinks a voicemail message exists, and telephony-service is correctly exposing that to the user. Alfonso, how can Pat debug that? ** Also affects: ofono (Ubuntu) Importance: Undecided Status: New ** Changed in: ofono (Ubuntu) Assignee: (unassigned) = Alfonso Sanchez-Beato (alfonsosanchezbeato) ** Changed in: ofono (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1469266 Title: Voicemail message shown after a reboot when there are no messages Status in the base for Ubuntu mobile products: Confirmed Status in ofono package in Ubuntu: New Status in telephony-service package in Ubuntu: Confirmed Bug description: As of today every time I reboot the arale on ota4 the notification center reports a voice message. Dialing the voicemail ATT says there are no messages. If an actual message is left, it functions properly but clearing it does not fix the errant reporting on the next boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1469266/+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 1469266] Re: Voicemail message shown after a reboot when there are no messages
Could you please post the result of: /usr/share/ofono/scripts/list-modems | grep Voicemail This way we can make sure that ofono is providing the correct info and that the bug is on telephony-service itself. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1469266 Title: Voicemail message shown after a reboot when there are no messages Status in the base for Ubuntu mobile products: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: As of today every time I reboot the arale on ota4 the notification center reports a voice message. Dialing the voicemail ATT says there are no messages. If an actual message is left, it functions properly but clearing it does not fix the errant reporting on the next boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1469266/+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 1458990] Re: history-service crash calling back number from indicator
From the logs it looks like telepathy-ofono stopped responding and thus caused history-service to get an empty list of participants. I will change the code not to crash, but still it would be nice to investigate why telepathy-ofono got stuck. My bet would be pulseaudio, but that needs investigation. ** Also affects: telepathy-ofono (Ubuntu) Importance: Undecided Status: New ** Changed in: history-service (Ubuntu) Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) ** Changed in: telepathy-ofono (Ubuntu) Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1458990 Title: history-service crash calling back number from indicator Status in history-service package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Bug description: latest arale, image 16 Steps to reproduce: - recv a call from a known contact but don't answer it - pull down indicator, tap the call back button - dialer is invoked with the number - press call button Expected Results: - number is called and header shows the contact name Actual results: - the header is blank, and don't think the call was placed (or it might have been placed and failed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1458990/+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
