[Touch-packages] [Bug 1391069] [NEW] package libdbus-1-3 1.4.18-1ubuntu1.4 [modified: usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: libdbus-1-3:amd64 1.4.18-1ubuntu1.4 cann
Public bug reported: fail to install update ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libdbus-1-3 1.4.18-1ubuntu1.4 [modified: usr/share/doc/libdbus-1-3/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.8.0-42.63~precise1-generic 3.8.13.23 Uname: Linux 3.8.0-42-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: libdbus-1-3: Install libdbus-1-3: Configure libdbus-1-3: Configure Architecture: amd64 Date: Mon Nov 10 14:09:37 2014 DpkgHistoryLog: Start-Date: 2014-11-10 14:08:13 Commandline: aptdaemon role='role-fix-broken-depends' sender=':1.77' Upgrade: libdbus-1-3:amd64 (1.4.18-1ubuntu1.4, 1.4.18-1ubuntu1.6), libdbus-1-3:i386 (1.4.18-1ubuntu1.4, 1.4.18-1ubuntu1.6) DuplicateSignature: package:libdbus-1-3:1.4.18-1ubuntu1.4 [modified: usr/share/doc/libdbus-1-3/changelog.Debian.gz]:libdbus-1-3:amd64 1.4.18-1ubuntu1.4 cannot be configured because libdbus-1-3 ErrorMessage: libdbus-1-3:amd64 1.4.18-1ubuntu1.4 cannot be configured because libdbus-1-3 MarkForUpload: True SourcePackage: dbus Title: package libdbus-1-3 1.4.18-1ubuntu1.4 [modified: usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: libdbus-1-3:amd64 1.4.18-1ubuntu1.4 cannot be configured because libdbus-1-3 UpgradeStatus: Upgraded to precise on 2014-10-19 (22 days ago) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1391069 Title: package libdbus-1-3 1.4.18-1ubuntu1.4 [modified: usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: libdbus-1-3:amd64 1.4.18-1ubuntu1.4 cannot be configured because libdbus-1-3 Status in “dbus” package in Ubuntu: New Bug description: fail to install update ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libdbus-1-3 1.4.18-1ubuntu1.4 [modified: usr/share/doc/libdbus-1-3/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.8.0-42.63~precise1-generic 3.8.13.23 Uname: Linux 3.8.0-42-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: libdbus-1-3: Install libdbus-1-3: Configure libdbus-1-3: Configure Architecture: amd64 Date: Mon Nov 10 14:09:37 2014 DpkgHistoryLog: Start-Date: 2014-11-10 14:08:13 Commandline: aptdaemon role='role-fix-broken-depends' sender=':1.77' Upgrade: libdbus-1-3:amd64 (1.4.18-1ubuntu1.4, 1.4.18-1ubuntu1.6), libdbus-1-3:i386 (1.4.18-1ubuntu1.4, 1.4.18-1ubuntu1.6) DuplicateSignature: package:libdbus-1-3:1.4.18-1ubuntu1.4 [modified: usr/share/doc/libdbus-1-3/changelog.Debian.gz]:libdbus-1-3:amd64 1.4.18-1ubuntu1.4 cannot be configured because libdbus-1-3 ErrorMessage: libdbus-1-3:amd64 1.4.18-1ubuntu1.4 cannot be configured because libdbus-1-3 MarkForUpload: True SourcePackage: dbus Title: package libdbus-1-3 1.4.18-1ubuntu1.4 [modified: usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: libdbus-1-3:amd64 1.4.18-1ubuntu1.4 cannot be configured because libdbus-1-3 UpgradeStatus: Upgraded to precise on 2014-10-19 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1391069/+subscriptions -- Mailing list: https://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 1162781] Re: bluez package out of date, 5.3 is available
how is this tagged with Wishlist importance? while i was reporting my issue w/ wireless keyboard i've noticed a few other issues which seem to be resolved in newer bluez releases (5.25 this month). there is a bunch of people affected w/ various mouse/keyboard/headphones not working which can be resolved w/ bluez update. -- 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/1162781 Title: bluez package out of date, 5.3 is available Status in “bluez” package in Ubuntu: Triaged Bug description: Looks like there have been a lot of improvements to bluez since the 4.x series. Would be nice to get the latest release pulled in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1162781/+subscriptions -- Mailing list: https://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 1354092] Re: Location service needs internationalization
** Changed in: trust-store (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: trust-store (Ubuntu RTM) Assignee: (unassigned) = Thomas Voß (thomas-voss) ** Changed in: trust-store (Ubuntu RTM) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1354092 Title: Location service needs internationalization Status in Ubuntu Translations: Fix Released Status in “location-service” package in Ubuntu: Fix Released Status in “trust-store” package in Ubuntu: Fix Released Status in “trust-store” package in Ubuntu RTM: Fix Released Bug description: The location dialog is displayed untranslated. Test case. - Switch the phone to Spanish. - Open webbrowser-app. - Go to maps.google.com - Accept to use location in the app. - Dialog appears. Expected result. - The dialog should be displayed in Spanish. Actual result. - The dialog appears untranslated: unconfined: An unconfined application wants to access your current location. Deny, Allow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1354092/+subscriptions -- Mailing list: https://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 1391069] Re: package libdbus-1-3 1.4.18-1ubuntu1.4 [modified: usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: libdbus-1-3:amd64 1.4.18-1ubuntu1.4 cannot
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1391069 Title: package libdbus-1-3 1.4.18-1ubuntu1.4 [modified: usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: libdbus-1-3:amd64 1.4.18-1ubuntu1.4 cannot be configured because libdbus-1-3 Status in “dbus” package in Ubuntu: New Bug description: fail to install update ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libdbus-1-3 1.4.18-1ubuntu1.4 [modified: usr/share/doc/libdbus-1-3/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.8.0-42.63~precise1-generic 3.8.13.23 Uname: Linux 3.8.0-42-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: libdbus-1-3: Install libdbus-1-3: Configure libdbus-1-3: Configure Architecture: amd64 Date: Mon Nov 10 14:09:37 2014 DpkgHistoryLog: Start-Date: 2014-11-10 14:08:13 Commandline: aptdaemon role='role-fix-broken-depends' sender=':1.77' Upgrade: libdbus-1-3:amd64 (1.4.18-1ubuntu1.4, 1.4.18-1ubuntu1.6), libdbus-1-3:i386 (1.4.18-1ubuntu1.4, 1.4.18-1ubuntu1.6) DuplicateSignature: package:libdbus-1-3:1.4.18-1ubuntu1.4 [modified: usr/share/doc/libdbus-1-3/changelog.Debian.gz]:libdbus-1-3:amd64 1.4.18-1ubuntu1.4 cannot be configured because libdbus-1-3 ErrorMessage: libdbus-1-3:amd64 1.4.18-1ubuntu1.4 cannot be configured because libdbus-1-3 MarkForUpload: True SourcePackage: dbus Title: package libdbus-1-3 1.4.18-1ubuntu1.4 [modified: usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: libdbus-1-3:amd64 1.4.18-1ubuntu1.4 cannot be configured because libdbus-1-3 UpgradeStatus: Upgraded to precise on 2014-10-19 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1391069/+subscriptions -- Mailing list: https://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 1326513] Re: Applications are orphaned when unity8 crashes
The problem is that non-foreground apps are SIGSTOPed, meaning that they won't find out about unity8 dying until such time that they get resumed again. Which will not happen if it crashed... So yeah, they still do get orphaned. I'm thinking that the whole session should be brought down and restarted, which would cause upstart to SIGKILL all the suspended apps. Otherwise we'd need to try and tell upstart to kill them one by one... but we're in the process of crashing, so it's not like this would ever be reliable, would it? ** Changed in: unity8 (Ubuntu) Status: Expired = Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided = Medium ** Changed in: qtmir Status: Expired = Triaged ** Changed in: qtmir Importance: Undecided = Medium -- 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/1326513 Title: Applications are orphaned when unity8 crashes Status in Mir: Expired Status in Qt integration with the Mir display server: Triaged Status in “unity8” package in Ubuntu: Triaged Bug description: For some reason Unity8 crashed on me. The applications I had open are now orphaned. They're still running but you can't get to it as it no longer shows up under the recent applications. In addition if I attempt to start the app, it fails to run or come back from orphaned state, so I have to restart. My unity process where Unity8 died an hour or two back. lightdm 1871 0.0 0.0 1392 464 ?Ss 10:06 0:00 /bin/sh /usr/lib/lightdm/lightdm-greeter-session /usr/bin/unity8-greeter-wrapper /usr/bin/unity8-greeter lightdm 1875 0.0 0.0 1392 472 ?S10:06 0:00 /bin/sh /usr/bin/unity8-greeter-wrapper /usr/bin/unity8-greeter lightdm 2362 0.2 5.0 343724 95000 ?Sl 10:06 1:47 /usr/bin/unity8-greeter phablet 22852 0.4 5.6 452692 105852 ? Ssl 19:03 0:34 unity8 The application:- phablet 8503 10.3 8.6 297792 161652 ? Ssl 11:33 59:33 /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene ubuntu-calculator- app.qml Now when I start calculator it just white-screens. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.87+14.10.20140603.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Wed Jun 4 21:04:34 2014 InstallationDate: Installed on 2014-06-04 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140604) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1326513/+subscriptions -- Mailing list: https://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 1390618] Re: Uniy8 crashed when creating a wireless connection with an access point
Thanks for the report. The issue arises when trying to communicate to the dbus daemon in a dtor, and I can easily make that call exception safe. However, that specific call failing is concerning, and we should further investigate why removing a match rule apparently fails (probably times out). ** Changed in: dbus-cpp (Ubuntu) Importance: Undecided = Critical ** Changed in: dbus-cpp (Ubuntu) Status: New = In Progress ** Changed in: dbus-cpp (Ubuntu) Assignee: (unassigned) = Thomas Voß (thomas-voss) ** Branch linked: lp:~thomas-voss/dbus-cpp/ensure-Signal-for-void-dtor- is-exception-safe -- 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/1390618 Title: Uniy8 crashed when creating a wireless connection with an access point Status in “dbus-cpp” package in Ubuntu: In Progress Status in “media-hub” package in Ubuntu: New Status in “unity8” package in Ubuntu: Invalid Bug description: current build number: 11 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2014-11-07 19:25:24 version version: 11 version ubuntu: 20141106.1 version device: 20141106 version custom: 20141106.1 Had system-settings opened in order to verify for updates, but noticed that I didn't have any valid wireless connection, so when I tried to connect with my access point, unity8 crashed completely. This happened after adding the password and hitting 'Connect'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1390618/+subscriptions -- Mailing list: https://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 1390596] Re: Sync jbigkit 2.1-3.1 (main) from Debian unstable (main)
This bug was fixed in the package jbigkit - 2.1-3.1 Sponsored for Logan Rosen (logan) --- jbigkit (2.1-3.1) unstable; urgency=medium * Non maintainer upload. * Allow the package to cross build, remove libtool usage. Closes: #761760. -- Matthias Klose d...@debian.org Mon, 13 Oct 2014 21:07:40 +0200 ** Changed in: jbigkit (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jbigkit in Ubuntu. https://bugs.launchpad.net/bugs/1390596 Title: Sync jbigkit 2.1-3.1 (main) from Debian unstable (main) Status in “jbigkit” package in Ubuntu: Fix Released Bug description: Please sync jbigkit 2.1-3.1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Merge with Debian; remaining changes: - Allow the package to cross build, remove libtool usage. Closes: #761760. Merged into Debian. Changelog entries since current vivid version 2.1-3ubuntu1: jbigkit (2.1-3.1) unstable; urgency=medium * Non maintainer upload. * Allow the package to cross build, remove libtool usage. Closes: #761760. -- Matthias Klose d...@debian.org Mon, 13 Oct 2014 21:07:40 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jbigkit/+bug/1390596/+subscriptions -- Mailing list: https://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 1390618] Re: Uniy8 crashed when creating a wireless connection with an access point
** Changed in: unity8 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1390618 Title: Uniy8 crashed when creating a wireless connection with an access point Status in “dbus-cpp” package in Ubuntu: In Progress Status in “media-hub” package in Ubuntu: New Status in “unity8” package in Ubuntu: Invalid Bug description: current build number: 11 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2014-11-07 19:25:24 version version: 11 version ubuntu: 20141106.1 version device: 20141106 version custom: 20141106.1 Had system-settings opened in order to verify for updates, but noticed that I didn't have any valid wireless connection, so when I tried to connect with my access point, unity8 crashed completely. This happened after adding the password and hitting 'Connect'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1390618/+subscriptions -- Mailing list: https://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 1376445] Re: Addition of signon-apparmor-extension causes token lookup problems
Since the go-onlineaccounts bug task was added, I guess we are also tracking the problems with scopes here too. In my investigations last week, I came to the conclusion that the problems were not limited to the Go scopes, but instead affected all scopes running under confinement. After digging in a bit, it isn't clear how it can be fixed without changes to the online accounts API. The way the online accounts integration for scopes works is: 1. the scope starts a signin session for the account service with the no interaction flag set. If no token can be retrieved (either because no account is available, or because the token isn't available), it will push a result with a special login button. 2. When the special result is clicked by the user, the dash will initiate the account creation process with the OnlineAccountsClient::Setup class. 3. If the account is successfully created, the dash refreshes the scope's results. The scope starts another signin session and finds the new token and displays personalised results. From my understanding, this breaks down because it is the dash's AppArmor label (which I guess would be unconfined) that gets added to the ACL for the account service. What would be needed here would be some kind of API the dash could use to ask for a second AppArmor label to be added to the ACL. ** Changed in: go-onlineaccounts Status: Triaged = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1376445 Title: Addition of signon-apparmor-extension causes token lookup problems Status in go-onlineaccounts: Incomplete Status in The Savilerow project: Invalid Status in ACL for signond, AppArmor backend: Fix Released Status in Online Accounts setup for Ubuntu Touch: In Progress Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: In Progress Status in “ubuntuone-credentials” package in Ubuntu: Confirmed Status in “signon-apparmor-extension” package in Ubuntu RTM: Triaged Status in “ubuntuone-credentials” package in Ubuntu RTM: Confirmed Bug description: As of image ~264 of ubuntu-touch, the signon-apparmor-extension package is included. As a result, apps like pay-ui cannot find the token any longer, and are not being notified that they are not allowed to access the token. The following error appears in the payui log file: 2014-10-01 19:15:51,550 - DEBUG - ../../../../lib/SignOn/authsessionimpl.cpp 184 errorSlot QDBusError(com.google.code.AccountsSSO.SingleSignOn.Error.PermissionDenied, Client has insuficient permissions to access the service.Method:getAuthSessionObjectPath) To manage notifications about this bug go to: https://bugs.launchpad.net/go-onlineaccounts/+bug/1376445/+subscriptions -- Mailing list: https://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 1390618] Re: Uniy8 crashed when creating a wireless connection with an access point
** Branch linked: lp:~thomas-voss/media-hub/bump-build-dep ** Changed in: media-hub (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1390618 Title: Uniy8 crashed when creating a wireless connection with an access point Status in “dbus-cpp” package in Ubuntu: In Progress Status in “media-hub” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Invalid Bug description: current build number: 11 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2014-11-07 19:25:24 version version: 11 version ubuntu: 20141106.1 version device: 20141106 version custom: 20141106.1 Had system-settings opened in order to verify for updates, but noticed that I didn't have any valid wireless connection, so when I tried to connect with my access point, unity8 crashed completely. This happened after adding the password and hitting 'Connect'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1390618/+subscriptions -- Mailing list: https://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 1391077] [NEW] Inappropriate notification of system update
Public bug reported: 1. Wait for a system update to become available. What happens: A notification bubble appears, There's an updated syste…. What should happen: No notification bubble. https://wiki.ubuntu.com/SoftwareUpdates#prompt-mobile ** Affects: system-image (Ubuntu) Importance: Undecided Status: New ** Attachment added: screenshot of the problem https://bugs.launchpad.net/bugs/1391077/+attachment/4257085/+files/update.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1391077 Title: Inappropriate notification of system update Status in “system-image” package in Ubuntu: New Bug description: 1. Wait for a system update to become available. What happens: A notification bubble appears, There's an updated syste…. What should happen: No notification bubble. https://wiki.ubuntu.com/SoftwareUpdates#prompt-mobile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1391077/+subscriptions -- Mailing list: https://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 1391078] [NEW] Screenshot 3-finger keypress hard to do
Public bug reported: Seems we can now take screenshots using Power+VolUp+VolDown together. Can we change this to just two buttons? It's hard enough pressing two physical buttons located on the same side of the device as it is, making the user try and hit all three at once is even harder. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01.1+14.10.20141105.2~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 10 08:44:33 2014 InstallationDate: Installed on 2014-11-10 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141110-030204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: Invalid ** Tags: apport-bug armhf utopic -- 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/1391078 Title: Screenshot 3-finger keypress hard to do Status in “unity8” package in Ubuntu: Invalid Bug description: Seems we can now take screenshots using Power+VolUp+VolDown together. Can we change this to just two buttons? It's hard enough pressing two physical buttons located on the same side of the device as it is, making the user try and hit all three at once is even harder. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01.1+14.10.20141105.2~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 10 08:44:33 2014 InstallationDate: Installed on 2014-11-10 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141110-030204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1391078/+subscriptions -- Mailing list: https://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 1391078] Re: Screenshot 3-finger keypress hard to do
Hah! Turns out it's only volup+voldown, no need for power. Sorry for the noise. ** Changed in: unity8 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1391078 Title: Screenshot 3-finger keypress hard to do Status in “unity8” package in Ubuntu: Invalid Bug description: Seems we can now take screenshots using Power+VolUp+VolDown together. Can we change this to just two buttons? It's hard enough pressing two physical buttons located on the same side of the device as it is, making the user try and hit all three at once is even harder. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01.1+14.10.20141105.2~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 10 08:44:33 2014 InstallationDate: Installed on 2014-11-10 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141110-030204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1391078/+subscriptions -- Mailing list: https://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 1390393] Re: It's too easy to trigger a volume notification when taking a screenshot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New = Confirmed -- 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/1390393 Title: It's too easy to trigger a volume notification when taking a screenshot Status in “unity8” package in Ubuntu: Confirmed Bug description: On Mako, I'm unable to take a screenshot (Vol up + Vol down) without changing the volume, which would be fine if there wasn't a notification appearing on the screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1390393/+subscriptions -- Mailing list: https://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 1306507] Re: 网络连接默认名称Wired connection 1-应汉化 - Network indicator is not localizing connection names
Some po file, including zh_CN.po, en_CA.po, need update. ** Changed in: ubuntukylin Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1306507 Title: 网络连接默认名称Wired connection 1-应汉化 - Network indicator is not localizing connection names Status in Ubuntu Translations: New Status in Ubuntu Kylin: Triaged Status in “network-manager” package in Ubuntu: New Bug description: 系统测试版本:UK14.04-Daily-0410-i386 网络连接默认名称Wired connection 1-应汉化,应和新建网络的默认名称一样:“有线连接 *”。 -- Network indicator is not localizing connection names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1306507/+subscriptions -- Mailing list: https://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 1384730] Re: [notifications] remove combo button from incoming call snap
** Branch linked: lp:~unity-team/unity8/rtm-14.09-staging -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-notifications in Ubuntu. https://bugs.launchpad.net/bugs/1384730 Title: [notifications] remove combo button from incoming call snap Status in Ubuntu UX bugs: Fix Committed Status in Server and client library for desktop notifications in Unity: New Status in “telephony-service” package in Ubuntu: New Status in “unity-notifications” package in Ubuntu: New Status in “unity8” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu RTM: In Progress Bug description: Build r123 The current incoming snap decision has a combo button for additional options, allowing users to reply with a quick message if they are busy/can not take the call. This combo button has two hit areas which caused a lot of confusion with users. One part DECLINES the call the other expands for additional options. Please remove combo button and replace with a toggle button with only one hit area. Hitting that button will reveal an expansion with additional options to users for a quick reply. Remove the CUSTOM option in the quick reply menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1384730/+subscriptions -- Mailing list: https://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 1351559] Re: Apps in spread are not anti-aliased
** Branch linked: lp:~unity-team/unity8/rtm-14.09-staging -- 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/1351559 Title: Apps in spread are not anti-aliased Status in Qt integration with the Mir display server: In Progress Status in “qtmir” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Fix Released Status in “qtmir” package in Ubuntu RTM: New Status in “unity8” package in Ubuntu RTM: In Progress Bug description: With qtcomp enabled, smoothing in the spread was disabled. This is unfortunately very visible on lower density devices, causing sharp edges on all diagonal lines. We need to investigate how to enable anti-aliasing with as little performance hit as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1351559/+subscriptions -- Mailing list: https://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 1352821] Re: 0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working
The issue is still not fixed, using Ubuntu 14.10 with 3.16.0-24-generic kernel. I've tried changing the DeviceID in /etc/bluetooth/main.conf with no success, the system seems to think everything is running correctly. Here is some data I collected : http://pastebin.com/E0Q05x0D -- 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/1352821 Title: 0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working Status in “bluez” package in Ubuntu: Confirmed Bug description: Hi, Nature of peoblem : Bluetooth not wotrking under Ubuntu 14.04 but wifi working fine. pls help to provide the solution Vendor ID : 0489:e078 Make of Wifi BT combo : Qualcom Atheros QCA9565 /AR9565 Regds, Bala S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1352821/+subscriptions -- Mailing list: https://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 1306507] Re: 网络连接默认名称Wired connection 1-应汉化 - Network indicator is not localizing connection names
该软件包在ubuntu翻译列表靠后的位置,上次集中翻译没有覆盖,目前还有250条没有翻译 https://translations.launchpad.net/ubuntu/utopic/+source/network-manager/+pots/networkmanager/zh_CN/+translate?start=0batch=10show=untranslatedfield.alternative_language=field.alternative_language-empty-marker=1old_show=all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1306507 Title: 网络连接默认名称Wired connection 1-应汉化 - Network indicator is not localizing connection names Status in Ubuntu Translations: New Status in Ubuntu Kylin: Triaged Status in “network-manager” package in Ubuntu: New Bug description: 系统测试版本:UK14.04-Daily-0410-i386 网络连接默认名称Wired connection 1-应汉化,应和新建网络的默认名称一样:“有线连接 *”。 -- Network indicator is not localizing connection names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1306507/+subscriptions -- Mailing list: https://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 654759] Re: before/after are different with librsvg
The issue has been fixed upstream in https://git.gnome.org/browse/librsvg/commit/?id=5ba4343bccc7e1765f38f87490b3d6a3a500fde1 The fix should be in Ubuntu with the new version update ** Changed in: librsvg (Ubuntu) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/654759 Title: before/after are different with librsvg Status in Inkscape: A Vector Drawing Tool: Fix Committed Status in libRSVG - SVG Rendering Library: Fix Released Status in Scour - Cleaning SVG Files: Fix Released Status in “librsvg” package in Ubuntu: Fix Committed Status in “scour” package in Ubuntu: Fix Released Bug description: I don't know if this is a problem with scour or librsvg, but I don't know where to file a bug against libsvg, so you win! I did this: $ wget http://tavmjong.free.fr/INKSCAPE/MANUAL/images/SVG_TESTS/svg_test.svg $ inkscape svg_test.svg selecte the pattern, (its the small pattern labelled Pattern) Edit/Copy File/New/A4 Edit/Paste Make it big so you can see the detail: using the x/Y and H/W entry fields in the controls bar of the select tool set the x,y to 0,0 and hight/width to 400,400 mm (box should about fill the page) File/SaveAs pattern1.svg ./scour.py ../pattern1.svg ../pattern1a.svg $ convert pattern1.svg pattern1.png $ convert pattern1a.svg pattern1a.png To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/654759/+subscriptions -- Mailing list: https://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 1388582] Re: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks
https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1388582 Title: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have a fresh install of KUbuntu 14.10 with this problem and i come of a KUbuntu 13.10 without problems. I don't have any sound from speakers or headphone, i think the driver isn't loaded, but the microphone works, it records. The sound playback works too, but the sound doesn't go through speakers or headphones. I was testing with a lot of LiveCD KUbuntu when the problem comes. With LiveCDs KUbuntu 12.04.5 LTS, 12.10, 13.04 the sound works, they configs the sound system as HDA Intel AD198x. Since LiveCDs 13.10, 14.04.1 LTS and, of course, 14.10 Live CD and my install, i have this problem, because the sound system is now AD1986A. I will attach the alsa-info output for all this systems in my computer. But with HDA_Analyzer http://www.alsa- project.org/main/index.php/HDA_Analyzer i found the details of the problem: i can create a python script to brought back the sound working in a basic mode, like as previously. The details are activating EAPD in Card 0, Codec 0, Node 0x1b PIN (In my computer, it could be different in another) what brought back the sound to the speakers, and unmuting Output Amplifier in Card 0, Codec 0, Node 0x1a VAL[0] and VAL[1] to brought back sound to the headphones when they are plugged. I will attach too the output of this diff and the python script created by HDA_Analyzer for my system. At least, the basic working state should be back, because with a untoching fresh install there isn't any sound. There are related bugs here and other post in internet, but i collected all information i found and can give more if it's necessary. For additional information: Searching the solution, i tested too all the models availables for HDA Intel AD1986A (editing /etc/modprobe.d /alsa-base.conf with AD1986A models /usr/share/doc/alsa-base/driver /HD-Audio-Models.txt.gz) and i found the default one doesn't fit my system and anothers are better, but have problems of no sound too and i don't found how to fix these problem. When this bug is corrected, i want to help to found a better model for my computer, i don't know how now, but first it brought back the sound. Also, i test with snd-hda- tools https://launchpad.net/~diwic/+archive/ubuntu/hda and with hda- jack-sense-test the Green Line Out sense doesn't work (always NO present) but the Pink Mic sense works without problems. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thywalls 2380 F pulseaudio CurrentDesktop: KDE Date: Sun Nov 2 16:24:36 2014 InstallationDate: Installed on 2014-10-30 (3 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T12JNC.206 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EasyNote_MX65 dmi.board.vendor: Packard Bell BV dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell BV dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT12JNC.206:bd09/28/2006:svnPackardBellBV:pnEasyNote_MX65:pvrPB63E03104:rvnPackardBellBV:rnEasyNote_MX65:rvr1.0:cvnPackardBellBV:ct10:cvr: dmi.product.name: EasyNote_MX65 dmi.product.version: PB63E03104 dmi.sys.vendor: Packard Bell BV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1388582/+subscriptions -- Mailing list: https://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 1384286] Re: add directory allowing scopes and apps to share data
Just to follow up on mardy's suggestion about sharing the cache directory. On the Reminders app we're integrating the scope and app, and the notes and their thumbnails are stored under the cache dir, which would be ideal to share. In this particular case, it might not apply, as we're shipping the scope and the app in the same click, though, so I understand they should both be able to access the cache data. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1384286 Title: add directory allowing scopes and apps to share data Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Confirmed Bug description: Summary says it all, just need to decide on the directory. I propose using this rule: # Allow scopes to share data with the app shipped in the same click owner @{HOME}/.local/share/@{APP_PKGNAME}/rw, owner @{HOME}/.local/share/@{APP_PKGNAME}/** mrwkl, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1384286/+subscriptions -- Mailing list: https://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 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
** Also affects: ofono (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) ** Changed in: ofono (Ubuntu) Assignee: (unassigned) = Alfonso Sanchez-Beato (alfonsosanchezbeato) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: In Progress Status in The Savilerow project: New Status in “network-manager” package in Ubuntu: New Status in “ofono” package in Ubuntu: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://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 1384286] Re: add directory allowing scopes and apps to share data
As I said, I don't really mind what particular directory is used as the cache directory. I just think it shouldn't be the same as the click scope installation directory. Right now, when you call cache_directory(), you get a path that (as far as I know) should be shared with the app if the scope and the app are in the same click package. Is that actually the case? If not, either the app path or the scope path need to be changed, so they agree. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1384286 Title: add directory allowing scopes and apps to share data Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Confirmed Bug description: Summary says it all, just need to decide on the directory. I propose using this rule: # Allow scopes to share data with the app shipped in the same click owner @{HOME}/.local/share/@{APP_PKGNAME}/rw, owner @{HOME}/.local/share/@{APP_PKGNAME}/** mrwkl, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1384286/+subscriptions -- Mailing list: https://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 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
Adding more eyes for network manager (cyphermox) and ofono (abeato). Could you try to reproduce the problem and try to see what's going in oFono / Network Manager when the disconnect/reconnect cycle happens, and whether there's something that could be fixed? To recap, if you use 3G only, images don't load in eg Video scope. If you add the rtm-022 PPA to your device and upgrade from there, images start to load but the 3G connection goes down and up all the time. The PPA includes an improved network-manager bearer backend for Qt to fix several issues like the problem related to scopes. To add the PPA, you can use among else the 'citrain' tool from phablet- tools-citrain package. First flash the device, set pin code to , enable developer mode, and run: citrain device-upgrade 22 ubuntu-rtm ** Changed in: network-manager (Ubuntu) Importance: Undecided = Critical ** Changed in: ofono (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: In Progress Status in The Savilerow project: New Status in “network-manager” package in Ubuntu: New Status in “ofono” package in Ubuntu: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://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 1387088] Re: Launcher popup should hide on screen lock
** Changed in: unity8 (Ubuntu) Status: New = In Progress -- 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/1387088 Title: Launcher popup should hide on screen lock Status in “unity8” package in Ubuntu: In Progress Bug description: How to reproduce: * Show launcher * Long press item so that popup shows * Press hardware lock button * Tap on the greeter so that launcher animation happens * See how the popup is part of the launcher animation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387088/+subscriptions -- Mailing list: https://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 1387088] Re: Launcher popup should hide on screen lock
** Branch linked: lp:~mzanetti/unity8/hide-quicklist-on-launcher-hide -- 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/1387088 Title: Launcher popup should hide on screen lock Status in “unity8” package in Ubuntu: In Progress Bug description: How to reproduce: * Show launcher * Long press item so that popup shows * Press hardware lock button * Tap on the greeter so that launcher animation happens * See how the popup is part of the launcher animation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387088/+subscriptions -- Mailing list: https://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 1351559] Re: Apps in spread are not anti-aliased
** Changed in: qtmir (Ubuntu RTM) Assignee: (unassigned) = Michał Sawicz (saviq) -- 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/1351559 Title: Apps in spread are not anti-aliased Status in Qt integration with the Mir display server: In Progress Status in “qtmir” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Fix Released Status in “qtmir” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: With qtcomp enabled, smoothing in the spread was disabled. This is unfortunately very visible on lower density devices, causing sharp edges on all diagonal lines. We need to investigate how to enable anti-aliasing with as little performance hit as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1351559/+subscriptions -- Mailing list: https://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 1336715] Re: [TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings
** Changed in: ubuntu-system-settings (Ubuntu RTM) Assignee: Nick Dedekind (nick-dedekind) = Michał Sawicz (saviq) -- 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/1336715 Title: [TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings Status in Display Indicator: Invalid Status in Indicator Location: Invalid Status in Network Menu: Invalid Status in Sound Menu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: I noticed when testing flightmode with indicator-network that the switch items sometimes get out of sync from what GActions states on dbus are and stop updating their states when action states on dbus change. This seems to happen randomly and I have no procedure to reproduce reliably. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-display/+bug/1336715/+subscriptions -- Mailing list: https://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 1351559] Re: Apps in spread are not anti-aliased
** Changed in: qtmir (Ubuntu RTM) Status: New = In Progress -- 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/1351559 Title: Apps in spread are not anti-aliased Status in Qt integration with the Mir display server: In Progress Status in “qtmir” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Fix Released Status in “qtmir” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: With qtcomp enabled, smoothing in the spread was disabled. This is unfortunately very visible on lower density devices, causing sharp edges on all diagonal lines. We need to investigate how to enable anti-aliasing with as little performance hit as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1351559/+subscriptions -- Mailing list: https://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 1385473] Re: Unlock dialogs (SIM PIN as well as Unlock screen) both do not use custom selected wallpaper
** Changed in: unity8 (Ubuntu RTM) Assignee: Michael Zanetti (mzanetti) = Michał Sawicz (saviq) -- 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/1385473 Title: Unlock dialogs (SIM PIN as well as Unlock screen) both do not use custom selected wallpaper Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: Confirmed Bug description: All unlock dialogs currently do not use a custom wallpaper but show the violet default wallpaper even if the user selected a custom one ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1385473/+subscriptions -- Mailing list: https://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 1384730] Re: [notifications] remove combo button from incoming call snap
** Changed in: unity8 (Ubuntu RTM) Assignee: Mirco Müller (macslow) = Michał Sawicz (saviq) ** No longer affects: unity-notifications (Ubuntu) ** No longer affects: telephony-service (Ubuntu) ** No longer affects: unity-notifications -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-notifications in Ubuntu. https://bugs.launchpad.net/bugs/1384730 Title: [notifications] remove combo button from incoming call snap Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu RTM: In Progress Bug description: Build r123 The current incoming snap decision has a combo button for additional options, allowing users to reply with a quick message if they are busy/can not take the call. This combo button has two hit areas which caused a lot of confusion with users. One part DECLINES the call the other expands for additional options. Please remove combo button and replace with a toggle button with only one hit area. Hitting that button will reveal an expansion with additional options to users for a quick reply. Remove the CUSTOM option in the quick reply menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1384730/+subscriptions -- Mailing list: https://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 1363214] Re: [System Settings] [design] allow Passcodes of variable length instead of just 4 digits
** Changed in: unity8 (Ubuntu) Status: Confirmed = Incomplete ** Changed in: ubuntu-system-settings (Ubuntu) Status: Confirmed = Incomplete -- 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/1363214 Title: [System Settings] [design] allow Passcodes of variable length instead of just 4 digits Status in Ubuntu UX bugs: In Progress Status in “ubuntu-system-settings” package in Ubuntu: Incomplete Status in “unity8” package in Ubuntu: Incomplete Bug description: Currently when setting a Passcode on the device, it must be 4 digits. This is artificially limiting. Other platforms (eg Android) allow longer Passcodes. It has always been my understanding that we should support Swipe, Passphrase and Passcode where Passphrase and Passcode can be arbitrarily long. However, once longer Passcodes are supported, we will have to add an Enter key. Right now, the lockscreen checks the Passcode once 4 digits are added so that you don't have to press Enter. I guess this was done for usability, but would be a security issue because an attacker can easily determine the Passcode length, which makes it easier to for an attacker to guess the Passcode. Eg, if I have a 5 digit Passcode set, then an attacker need only type '1' and know that the Passcode is only five characters. Now, a Passcode isn't strong to begin with and an automated attack could rather quickly brute force Passcodes, but we shouldn't make it easier for someone manually trying to guess the Passcode. The passphrase lockscreen prompt correctly allows variable length passphrases and requires you to press Enter. I suggest moving the 'X' up t the left of '0' and an Enter symbol to the rigth of '0'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1363214/+subscriptions -- Mailing list: https://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 1390557] Re: [oobe] passcode screen continues after 3 visible dots to confirmation scree
** Changed in: unity8 (Ubuntu) Status: New = Invalid ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-system-settings (Ubuntu) Assignee: (unassigned) = Andrea Cimitan (cimi) ** Changed in: unity8 (Ubuntu) Assignee: Andrea Cimitan (cimi) = (unassigned) -- 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/1390557 Title: [oobe] passcode screen continues after 3 visible dots to confirmation scree Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity8” package in Ubuntu: Invalid Bug description: krillin build 143 Steps to reproduce in the initial set up wizard 1. after selecting your language and setting up wifi continue to the passcode set up screen 2. type in your 4 digit passcode and pay attention to the dots representing the digits Expected result: all 4 dots are visible before screen moves on to confirm your passcode Actual result: only 3 dots are visible and it looks like you only picked a 3 digit passcode It would be great to have a slight delay and show user the last dot before screen moves on to the next step as we currently have when unlocking your device after swiping away the greeter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1390557/+subscriptions -- Mailing list: https://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 1342031] Re: Rename QML modules to follow qml-module-foo naming
This bug was fixed in the package accounts-qml-module - 0.5+15.04.20141110-0ubuntu1 --- accounts-qml-module (0.5+15.04.20141110-0ubuntu1) vivid; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Alberto Mardegan ] * Rename QML module (LP: #1342031) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 10 Nov 2014 09:49:57 + ** Changed in: accounts-qml-module (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 content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1342031 Title: Rename QML modules to follow qml-module-foo naming Status in “accounts-qml-module” package in Ubuntu: Fix Released Status in “address-book-app” package in Ubuntu: New Status in “bacon2d” package in Ubuntu: Triaged Status in “clickmanager-plugin” package in Ubuntu: New Status in “content-hub” package in Ubuntu: New Status in “cordova-ubuntu” package in Ubuntu: New Status in “dee-qt” package in Ubuntu: New Status in “gsettings-qt” package in Ubuntu: New Status in “history-service” package in Ubuntu: New Status in “libhud-qt” package in Ubuntu: Won't Fix Status in “libqofono” package in Ubuntu: New Status in “libusermetrics” package in Ubuntu: New Status in “mediascanner2” package in Ubuntu: New Status in “poppler-qml-plugin” package in Ubuntu: New Status in “qml-box2d” package in Ubuntu: New Status in “qml-friends” package in Ubuntu: New Status in “qt3d-opensource-src” package in Ubuntu: New Status in “qtconnectivity-opensource-src” package in Ubuntu: Fix Released Status in “qtdeclarative-opensource-src” package in Ubuntu: Fix Released Status in “qtgrilo” package in Ubuntu: New Status in “qtlocation-opensource-src” package in Ubuntu: New Status in “qtmultimedia-opensource-src” package in Ubuntu: Fix Released Status in “qtpim-opensource-src” package in Ubuntu: Fix Released Status in “qtquickcontrols-opensource-src” package in Ubuntu: Fix Released Status in “qtsensors-opensource-src” package in Ubuntu: Fix Released Status in “qtsystems-opensource-src” package in Ubuntu: Fix Released Status in “reminders-app” package in Ubuntu: New Status in “solid” package in Ubuntu: New Status in “sync-monitor” package in Ubuntu: New Status in “telephony-service” package in Ubuntu: Triaged Status in “thumbnailer” package in Ubuntu: New Status in “u1db-qt” package in Ubuntu: New Status in “ubuntu-download-manager” package in Ubuntu: New Status in “ubuntu-keyboard” package in Ubuntu: New Status in “ubuntu-settings-components” package in Ubuntu: New Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Fix Released Status in “ubuntu-ui-extras” package in Ubuntu: New Status in “ubuntu-ui-toolkit” package in Ubuntu: New Status in “ubuntuone-credentials” package in Ubuntu: New Status in “unity-action-api” package in Ubuntu: Triaged Status in “unity-notifications” package in Ubuntu: New Status in “webbrowser-app” package in Ubuntu: Confirmed Bug description: The package names of QML modules should be of the format qml- module-{$modulename}[version], a transition that was started during Qt 5.3 preparation in Ubuntu. For example this could be qml-module- qtquick-localstorage or qml-module-qtsysteminfo for non versioned modules, and qml-module-ubuntu-webthing0.3 for versioned/co- installable modules. Further details in Debian e-mail: http://lists.alioth.debian.org/pipermail/pkg-kde- talk/2014-March/001889.html For Ubuntu, transitional packages should be put in place for smooth distribution upgrades, since we're shipping with the old names in previous Ubuntus. An example of that is at http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtsystems-opensource-src/revision/31 - in other words: - Make the old package a transitional oldlibs package that depends on the new package - Add Breaks/Replaces to the new package for the old non-transitional packages (be careful about the version number specification) - Keep Multi-Arch: same and Architecture: any for the transitional package - Write QML module instead of QML plugin - Rename also the *.install files --- One more example on naming: For example, the test (qtdeclarative5-test-plugin) in the old qtdeclarative5-style package naming became qttest (qml-module- qttest) in the new naming since the path is actually under /usr/lib/*/qt5/qml/QtTest/ qml-module-qtquick-xmllistmodel has path /usr/lib/*/qt5/qml/QtQuick/XmlListModel, as an example if you have more than one subdir. /usr/lib/*/qt5/qml/Ubuntu/Connectivity/ would be qml-module-ubuntu-connectivity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accounts-qml-module/+bug/1342031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1346734] Re: Unprivileged LXC containers don't work under systemd
For my own notes: No hints from upstream; my current theory is that the best place to hook this in would be in src/core/service.c service_spawn(): After a successful exec_spawn(), if the unit is a *.scope, also put it into all other cgroup controlles (cg_create() and cg_attach()). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1346734 Title: Unprivileged LXC containers don't work under systemd Status in “systemd” package in Ubuntu: Triaged Bug description: With systemd 208, unprivileged containers stop working when running under systemd (working fine under upstart with cgmanager). Quoting Stephane Graber: In this setup, things don't work nearly as well. On login I'm only placed into the name=systemd cgroup and not in any of the others, which means that unprivileged LXC isn't usable. Martin suggested setting JoinControllers in /etc/systemd/system.conf but upon closer inspection, this isn't at all what we want. This setting is used to tell systemd what controllers to co-mount, by default this is set to cpu,cpuset (which caused the earlier cgmanager breakage). Even though this option isn't helpful for what we want (i.e. setting the list of cgroup controllers the first PID of a user session should be added to), we should nonetheless set it to an empty string which should instruct systemd not to co-mount any controller, therefore giving us a more reliable behavior (identical to what we have in the upstart world and unlikely to confuse lxc and other stuff doing direct cgroup access). Additionally, we need to find an equivalent to our good old Controllers logind.conf option, or re-introduce it or just patch logind so that it will always join all the controllers (similar to what the shim does). == Actions == * Update systemd.conf to set JoinControllers to an empty value. * Make it so new user sessions are joined to all the available controllers by doing one of the following: - Find the magic undocumented config variable - Re-introduce the Controllers option in logind.conf - Patch logind to have it always join all available controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1346734/+subscriptions -- Mailing list: https://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 1391120] [NEW] Webapp-container problem with meteofrance website
Public bug reported: Hi I report this bug because there is something since the RTM with a webapp I made (webapp meteofrance). The corresponding website is http://www .meteo-france.mobi In my tests, it works well if opened manually in the web browser app but not in the webapp. In the webapp, the website begin to load but stay on an empty page with just the blue background. I never changed anything in the app and it stopped working a day (I discovered it reading comments in the software center). I tried removing the webapp patterns and remake the webapp from scratch, nothing works, it seems the problem is in the webapp-container itself (see the logs from the ubuntu sdk joined to the bug report). ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: webapp-container 0.23+14.10.20141028~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 10 12:18:55 2014 InstallationDate: Installed on 2014-10-31 (9 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-175022) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf touch utopic ** Attachment added: App project + logs https://bugs.launchpad.net/bugs/1391120/+attachment/4257171/+files/M%C3%A9t%C3%A9o%20France.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1391120 Title: Webapp-container problem with meteofrance website Status in “webbrowser-app” package in Ubuntu: New Bug description: Hi I report this bug because there is something since the RTM with a webapp I made (webapp meteofrance). The corresponding website is http://www.meteo-france.mobi In my tests, it works well if opened manually in the web browser app but not in the webapp. In the webapp, the website begin to load but stay on an empty page with just the blue background. I never changed anything in the app and it stopped working a day (I discovered it reading comments in the software center). I tried removing the webapp patterns and remake the webapp from scratch, nothing works, it seems the problem is in the webapp- container itself (see the logs from the ubuntu sdk joined to the bug report). ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: webapp-container 0.23+14.10.20141028~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 10 12:18:55 2014 InstallationDate: Installed on 2014-10-31 (9 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-175022) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1391120/+subscriptions -- Mailing list: https://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 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
(as a data point, I tried a build without the last three patches and the behavior is the same. It's now just easier to see as scopes/Unity8 don't crash anymore) I test simply by putting 'ping 8.8.8.8' in one adb shell terminal. The cycle seems constant 20 seconds up, 9 seconds down. When it's down, ifconfig tells me rmnet_usb0 is not there anymore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: In Progress Status in The Savilerow project: New Status in “network-manager” package in Ubuntu: New Status in “ofono” package in Ubuntu: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://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 1391128] [NEW] automatic punctuation doesn't works for parenthesis etc
Public bug reported: Hi I think there is a bug with the automatic punctuation feature : What should happen : In system settings, it' indicated ubuntu keyboard automatically add a point or a missing parenthesis /quotation mark when you double click on space. What happens : Ubuntu keyboard never add missing parenthesis / quotation mark but always add a point How to reproduce : try typing some text (SMS, mail...), open a parenthesis, type a word, double click on space. It adds a point and not the missing closing parenthesis. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-keyboard 0.99.trunk.phablet2+14.10.20141010-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 10 12:33:10 2014 InstallationDate: Installed on 2014-10-31 (9 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-175022) SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1391128 Title: automatic punctuation doesn't works for parenthesis etc Status in “ubuntu-keyboard” package in Ubuntu: New Bug description: Hi I think there is a bug with the automatic punctuation feature : What should happen : In system settings, it' indicated ubuntu keyboard automatically add a point or a missing parenthesis /quotation mark when you double click on space. What happens : Ubuntu keyboard never add missing parenthesis / quotation mark but always add a point How to reproduce : try typing some text (SMS, mail...), open a parenthesis, type a word, double click on space. It adds a point and not the missing closing parenthesis. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-keyboard 0.99.trunk.phablet2+14.10.20141010-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 10 12:33:10 2014 InstallationDate: Installed on 2014-10-31 (9 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-175022) SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1391128/+subscriptions -- Mailing list: https://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 1083225] Re: [greeter] Operator label is not shown in the top bar of the greeter
** Changed in: unity8 (Ubuntu) Status: New = Won't Fix -- 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/1083225 Title: [greeter] Operator label is not shown in the top bar of the greeter Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Won't Fix Bug description: The top bar currently shows Magnifying Glass + Search. The magnifying glass should be removed and operator name string displayed instead, in all caps. E.g. VODAFONE UK, EE or ATT. The orange bar should be removed as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1083225/+subscriptions -- Mailing list: https://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 1083221] Re: [Dash] Touchdown effect kicks in too soon
** Changed in: unity8 (Ubuntu) Assignee: Andrea Cimitan (cimi) = (unassigned) ** Changed in: unity8 (Ubuntu) Status: Incomplete = Triaged ** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Also affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1083221 Title: [Dash] Touchdown effect kicks in too soon Status in Ubuntu UX bugs: Fix Released Status in “qtdeclarative-opensource-src” package in Ubuntu: New Status in “ubuntu-ui-toolkit” package in Ubuntu: New Status in “unity8” package in Ubuntu: Triaged Bug description: When scrolling the People Scope, the list cells under the finger flash grey as soon as the finger touches the screen. This is distracting, when the user's intention is to scroll instead of tapping. Expected result: Some sort of threshold should be introduced, so that generally tap on cell results in the cell darkening and scrolling does not. That means possibly adding a delay into the effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1083221/+subscriptions -- Mailing list: https://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 884121] Re: Printer stops on German double quotes
Please provide a complete cups error_log: https://wiki.ubuntu.com/DebuggingPrintingProblems#CUPS_error_log ** Changed in: cups (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/884121 Title: Printer stops on German double quotes Status in “cups” package in Ubuntu: Incomplete Bug description: Hardware: Konica-Minolta PagePro 1300W Software: min12xxw 0.0.9-3ubuntu2 on Kubuntu 10.04 Input: Text file text.txt containing „German double quotes“, created with AltGr+v and AltGr+b Command line: lpr -P PagePro text.txt Result: Print job in status „Angehalten“ (stopped), no printing “Print again“ also falls into “stopped“ status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/884121/+subscriptions -- Mailing list: https://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 1391135] [NEW] Autosuggestion doesn't add a space
Public bug reported: There is a problem (maybe design bug I don't know) with the auto word suggestion : What happens : When you start typing a word, the keyboard suggest you possibilities. If you pick one it complete the word, just the word. What I expect : I expect the auto completion to add a space after the word : You just picked a word, so you will of course start typing a new one. There are two exception : - EIther you wan't to add a letter at the end of the word you selected == not very often but it can happen ; - Or you use a punctuation that doesn't need a space (point, comma...) -- In this case, once you picked your punctuation caracter, the OSK should know that there is no space between the word and this punctuation, and automatically remove it. Then, add another one after the comma/point... (if needed, it depends languages and punctuation) How to reproduce : start typing a word, select a proposed one. No space added (with just auto suggestion activated, not autocompletion) ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-keyboard 0.99.trunk.phablet2+14.10.20141010-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 10 12:41:36 2014 InstallationDate: Installed on 2014-10-31 (9 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-175022) SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1391135 Title: Autosuggestion doesn't add a space Status in “ubuntu-keyboard” package in Ubuntu: New Bug description: There is a problem (maybe design bug I don't know) with the auto word suggestion : What happens : When you start typing a word, the keyboard suggest you possibilities. If you pick one it complete the word, just the word. What I expect : I expect the auto completion to add a space after the word : You just picked a word, so you will of course start typing a new one. There are two exception : - EIther you wan't to add a letter at the end of the word you selected == not very often but it can happen ; - Or you use a punctuation that doesn't need a space (point, comma...) -- In this case, once you picked your punctuation caracter, the OSK should know that there is no space between the word and this punctuation, and automatically remove it. Then, add another one after the comma/point... (if needed, it depends languages and punctuation) How to reproduce : start typing a word, select a proposed one. No space added (with just auto suggestion activated, not autocompletion) ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-keyboard 0.99.trunk.phablet2+14.10.20141010-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 10 12:41:36 2014 InstallationDate: Installed on 2014-10-31 (9 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-175022) SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1391135/+subscriptions -- Mailing list: https://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 49579] Re: screen doesn't lock when some menu is open
The only way to fix it is to switch away from X.org, Mir is in the works so you could say that they are working on fixing it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Confirmed Status in “gnome-screensaver” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Confirmed Status in “gnome-screensaver” source package in Precise: Confirmed Status in “unity” source package in Precise: Confirmed Status in “xorg-server” package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- Mailing list: https://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 1336715] Re: [TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings
Just had this issue with the silent mode switch: http://people.canonical.com/~rsalveti/silent.png -- 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/1336715 Title: [TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings Status in Display Indicator: Invalid Status in Indicator Location: Invalid Status in Network Menu: Invalid Status in Sound Menu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: I noticed when testing flightmode with indicator-network that the switch items sometimes get out of sync from what GActions states on dbus are and stop updating their states when action states on dbus change. This seems to happen randomly and I have no procedure to reproduce reliably. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-display/+bug/1336715/+subscriptions -- Mailing list: https://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 1326513] Re: Applications are orphaned when unity8 crashes
Hmm maybe we could add stop on stopping unity8 or so to the UAL job? ** Also affects: ubuntu-app-launch (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/1326513 Title: Applications are orphaned when unity8 crashes Status in Mir: Expired Status in Qt integration with the Mir display server: Triaged Status in “ubuntu-app-launch” package in Ubuntu: New Status in “unity8” package in Ubuntu: Triaged Bug description: For some reason Unity8 crashed on me. The applications I had open are now orphaned. They're still running but you can't get to it as it no longer shows up under the recent applications. In addition if I attempt to start the app, it fails to run or come back from orphaned state, so I have to restart. My unity process where Unity8 died an hour or two back. lightdm 1871 0.0 0.0 1392 464 ?Ss 10:06 0:00 /bin/sh /usr/lib/lightdm/lightdm-greeter-session /usr/bin/unity8-greeter-wrapper /usr/bin/unity8-greeter lightdm 1875 0.0 0.0 1392 472 ?S10:06 0:00 /bin/sh /usr/bin/unity8-greeter-wrapper /usr/bin/unity8-greeter lightdm 2362 0.2 5.0 343724 95000 ?Sl 10:06 1:47 /usr/bin/unity8-greeter phablet 22852 0.4 5.6 452692 105852 ? Ssl 19:03 0:34 unity8 The application:- phablet 8503 10.3 8.6 297792 161652 ? Ssl 11:33 59:33 /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene ubuntu-calculator- app.qml Now when I start calculator it just white-screens. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.87+14.10.20140603.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Wed Jun 4 21:04:34 2014 InstallationDate: Installed on 2014-06-04 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140604) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1326513/+subscriptions -- Mailing list: https://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 1391138] [NEW] .com not proposed as a website Top Level Domain on the french OSK
Public bug reported: There is a little problem with the french OSK : What happens : When you enter an URL (in the wbebrowser app generally), the OSK propose you some TLD for the end of the URL : .fr is the main one, end with a long press you have .cd, .ci, .ca, .ch, .be and .ht, which are almost never used in France. What should happen : .fr as the main one is probably a good choice (this one or .com) . .com must be proposed in the long press pop-up. .cd,.ci etc are TLD of french speaking country (Congo, Côte d'Ivoire...). I don't know there, but in France, the main used TLD are .com and .fr (probably as much the first than the second one). You find a few .org too, but never use .cd, .ci etc. So probably, the best thing to do would be to have separated keyboards for these countries, and for France having .fr as the main choice, and .com, .org and probably some others (.net ?) proposed via the long press How to reproduce : start typing an URL with french keyboard layout. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-keyboard-french 0.99.trunk.phablet2+14.10.20141010-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 10 13:00:22 2014 InstallationDate: Installed on 2014-10-31 (9 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-175022) SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1391138 Title: .com not proposed as a website Top Level Domain on the french OSK Status in “ubuntu-keyboard” package in Ubuntu: New Bug description: There is a little problem with the french OSK : What happens : When you enter an URL (in the wbebrowser app generally), the OSK propose you some TLD for the end of the URL : .fr is the main one, end with a long press you have .cd, .ci, .ca, .ch, .be and .ht, which are almost never used in France. What should happen : .fr as the main one is probably a good choice (this one or .com) . .com must be proposed in the long press pop- up. .cd,.ci etc are TLD of french speaking country (Congo, Côte d'Ivoire...). I don't know there, but in France, the main used TLD are .com and .fr (probably as much the first than the second one). You find a few .org too, but never use .cd, .ci etc. So probably, the best thing to do would be to have separated keyboards for these countries, and for France having .fr as the main choice, and .com, .org and probably some others (.net ?) proposed via the long press How to reproduce : start typing an URL with french keyboard layout. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-keyboard-french 0.99.trunk.phablet2+14.10.20141010-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 10 13:00:22 2014 InstallationDate: Installed on 2014-10-31 (9 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-175022) SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1391138/+subscriptions -- Mailing list: https://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 1308037] Re: No results from application scope
This bug was introduced with Ubuntu 13.10 and now it is still not fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1308037 Title: No results from application scope Status in LibUnity: Confirmed Status in Unity: Confirmed Status in Unity Applications Lens: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Unity is in a state where I don't get any results from the applications lens. This sometimes happens for one search but either re-entering the search or toggling the lens has always fixed it in the past for me. This time neither of these steps work. I'm attaching a bustle log of the problem in case that's helpful. I searched for spotify, which I've got installed, and got 0 results. The only way to fix the issue is to log out and back in. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 13:29:40 2014 InstallationDate: Installed on 2012-10-07 (554 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1308037/+subscriptions -- Mailing list: https://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 1391137] [NEW] After a flash enabling developer mode does not work
Public bug reported: Using a krillin * Have developer mode enabled * Flash with ubuntu-device-flash --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed --wipe --device krillin * Go to system settings and enable developer mode * Go back and then go to Developer mode screen * See it is marked as disabled * Enabled it again * Now it is enabled ** Affects: android-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1391137 Title: After a flash enabling developer mode does not work Status in “android-tools” package in Ubuntu: New Bug description: Using a krillin * Have developer mode enabled * Flash with ubuntu-device-flash --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed --wipe --device krillin * Go to system settings and enable developer mode * Go back and then go to Developer mode screen * See it is marked as disabled * Enabled it again * Now it is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1391137/+subscriptions -- Mailing list: https://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 1391128] Re: automatic punctuation doesn't works for parenthesis etc
*** This bug is a duplicate of bug 1385312 *** https://bugs.launchpad.net/bugs/1385312 Thank's for reporting this, there's actually already a bug for this (#1385312), so I'll mark this as a duplicate; but information purposes there's also a bug logged against system settings: #1385288, since the string shouldn't be advertising features we don't yet have implement. ** This bug has been marked a duplicate of bug 1385312 Auto-punctuation should support closing brackets and quotes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1391128 Title: automatic punctuation doesn't works for parenthesis etc Status in “ubuntu-keyboard” package in Ubuntu: New Bug description: Hi I think there is a bug with the automatic punctuation feature : What should happen : In system settings, it' indicated ubuntu keyboard automatically add a point or a missing parenthesis /quotation mark when you double click on space. What happens : Ubuntu keyboard never add missing parenthesis / quotation mark but always add a point How to reproduce : try typing some text (SMS, mail...), open a parenthesis, type a word, double click on space. It adds a point and not the missing closing parenthesis. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-keyboard 0.99.trunk.phablet2+14.10.20141010-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 10 12:33:10 2014 InstallationDate: Installed on 2014-10-31 (9 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-175022) SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1391128/+subscriptions -- Mailing list: https://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 1381971] Re: Selecting artists from My Music scope doesn't show albums_of_artist view anymore
** Branch linked: lp:~stolowski/unity-scope-mediascanner/fix-albums-of- artist-vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1381971 Title: Selecting artists from My Music scope doesn't show albums_of_artist view anymore Status in Unity Media Scanner Scope: New Status in “unity-scope-mediascanner” package in Ubuntu: Confirmed Status in “unity-scopes-shell” package in Ubuntu: Invalid Bug description: I was able to reproduce this problem with ubuntu-rtm image #91 for Nexus 4: version_detail: ubuntu=20141016,device=20140929.1,custom=mako-1.1,version=91 Steps to reproduce: 1. Load some music onto device 2. Navigate to My Music scope in dash (e.g. by clicking the My Music category header in music scope). 3. Select an artist from the surfacing results Observed behaviour: Standard search results for the artist's name are displayed with small icons for artists, albums and tracks. Expected behaviour: The special albums_of_artist view should be displayed with a full width result showing art for the artist. Surprisingly, if I select the same artist result as it appears in the music aggregator scope, I get the albums_of_artist view. This makes me suspect that this is a problem in the dash or unity-scopes-shell, where the department ID from the canned query is being lost. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scope-mediascanner/+bug/1381971/+subscriptions -- Mailing list: https://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 1386840] Re: failure to start a container
This the workaround: apt-get install apparmor-utils aa-complain /usr/bin/lxc-start here, I think, there should be the solution: https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-October/010662.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1386840 Title: failure to start a container Status in “lxc” package in Ubuntu: Triaged Status in “lxc” source package in Trusty: Confirmed Status in “lxc” source package in Utopic: Confirmed Bug description: On utopic using lxc version 1.1.0~alpha2-0ubuntu3, I was unable to start a container. $ sudo lxc-start -F -n lxc-errors lxc-start: lsm/apparmor.c: mount_feature_enabled: 61 Permission denied - Error mounting securityfs lxc-start: lsm/apparmor.c: apparmor_process_label_set: 186 If you really want to start this container, set lxc-start: lsm/apparmor.c: apparmor_process_label_set: 187 lxc.aa_allow_incomplete = 1 lxc-start: lsm/apparmor.c: apparmor_process_label_set: 188 in your container configuration file lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 4 lxc-start: start.c: __lxc_start: 1087 failed to spawn 'lxc-errors' lxc-start: cgmanager.c: cgm_remove_cgroup: 503 call to cgmanager_remove_sync failed: invalid request lxc-start: cgmanager.c: cgm_remove_cgroup: 505 Error removing name=systemd:lxc/lxc-errors-2 Switching to the version of lxc in http://ppa.launchpad.net/ubuntu- lxc/daily/ resolved the failure to start for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1386840/+subscriptions -- Mailing list: https://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 884121] Re: Printer stops on German double quotes
The problem can not be reproduced. Example text prints fine on Konica Minolta PagePro 1300W. Kubuntu 12.04.5 LTS cups 1.5.3-0ubuntu8.5 printer-driver-min12xxw 0.0.9-6ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/884121 Title: Printer stops on German double quotes Status in “cups” package in Ubuntu: Incomplete Bug description: Hardware: Konica-Minolta PagePro 1300W Software: min12xxw 0.0.9-3ubuntu2 on Kubuntu 10.04 Input: Text file text.txt containing „German double quotes“, created with AltGr+v and AltGr+b Command line: lpr -P PagePro text.txt Result: Print job in status „Angehalten“ (stopped), no printing “Print again“ also falls into “stopped“ status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/884121/+subscriptions -- Mailing list: https://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 1391149] [NEW] greeter not reacting to swipes
Public bug reported: i had this a few times over the weekend with images 150-153, suddenly the greeter does not react to right/left swipes on the wallpaper to reveal the PIN unlock dialog ... swiping in the launcher from the left makes the greeter go away and reveals the PIN unlock dialog then. ** 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/1391149 Title: greeter not reacting to swipes Status in “unity8” package in Ubuntu: New Bug description: i had this a few times over the weekend with images 150-153, suddenly the greeter does not react to right/left swipes on the wallpaper to reveal the PIN unlock dialog ... swiping in the launcher from the left makes the greeter go away and reveals the PIN unlock dialog then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1391149/+subscriptions -- Mailing list: https://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 1384749] Re: [TOPBLOCKER] Detected X, Y coordinates for touch event on text field is off
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui- toolkit/cursorWithFrameSpacing ** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui- toolkit/cursorPosWithFrameSpacing -- 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/1384749 Title: [TOPBLOCKER] Detected X,Y coordinates for touch event on text field is off Status in Ubuntu UI Toolkit: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Bug description: Tapping on a word in a text input seems to select the word below, rather than the one I intended to select The Y seems to be lower by approx. 1 GU Reproduce by - Go to messages and tap on message filed - Enter 4 rows of content - Tap on a word in the second row - The word below is often selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1384749/+subscriptions -- Mailing list: https://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 1391149] Re: greeter not reacting to swipes
Some more notes after an IRC conversation with ogra: * The launcher can still be flicked up/down, so not a touch vs mouse issue. * hiding the greeter using the launcher gets a fully working phone * tapping the greeter does NOT tease the launcher -- 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/1391149 Title: greeter not reacting to swipes Status in “unity8” package in Ubuntu: New Bug description: i had this a few times over the weekend with images 150-153, suddenly the greeter does not react to right/left swipes on the wallpaper to reveal the PIN unlock dialog ... swiping in the launcher from the left makes the greeter go away and reveals the PIN unlock dialog then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1391149/+subscriptions -- Mailing list: https://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 1391149] Re: greeter not reacting to swipes
i am wondering if that is the same as bug #1391076 , just in a less intrusive manifestation -- 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/1391149 Title: greeter not reacting to swipes Status in “unity8” package in Ubuntu: New Bug description: i had this a few times over the weekend with images 150-153, suddenly the greeter does not react to right/left swipes on the wallpaper to reveal the PIN unlock dialog ... swiping in the launcher from the left makes the greeter go away and reveals the PIN unlock dialog then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1391149/+subscriptions -- Mailing list: https://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 1384749] Re: [TOPBLOCKER] Detected X, Y coordinates for touch event on text field is off
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui- toolkit/cursorPosWithFrameSpacingRTM -- 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/1384749 Title: [TOPBLOCKER] Detected X,Y coordinates for touch event on text field is off Status in Ubuntu UI Toolkit: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Bug description: Tapping on a word in a text input seems to select the word below, rather than the one I intended to select The Y seems to be lower by approx. 1 GU Reproduce by - Go to messages and tap on message filed - Enter 4 rows of content - Tap on a word in the second row - The word below is often selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1384749/+subscriptions -- Mailing list: https://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 1390624] Re: Black line on top of the scope headers with image vivid/mako 12
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Tim Peeters (tpeeters) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = Medium ** Changed in: ubuntu-ui-toolkit (Ubuntu) Milestone: None = ubuntu-14.12 -- 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/1390624 Title: Black line on top of the scope headers with image vivid/mako 12 Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: current build number: 12 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2014-11-07 21:01:06 version version: 12 version ubuntu: 20141107 version device: 20141106 version custom: 20141107 See: http://people.canonical.com/~rsalveti/home.png Opening against the toolkit as this bug was introduced on image 12, which got only the following changes: http://people.canonical.com/~ogra/touch-image-stats/12.changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1390624/+subscriptions -- Mailing list: https://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 1066062] Re: [quantal] Sound volume changes without user interaction
Ubuntu 14.04 here (originally Xubuntu). The same issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1066062 Title: [quantal] Sound volume changes without user interaction Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: I can listen to the sound but automatically the sound is getting increased and decreased spontaneously. Some times popping up some error, as I am new to this it's very difficult to troubleshoot. Some please advice on this. What action should I need to take? Mail ID is optimous.prim...@gmail.com. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1066062/+subscriptions -- Mailing list: https://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 1389969] Re: [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] No sound at all
banshee completely died -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1389969 Title: [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: Playing Banshee when everything stopped, screen greyed out. Happens occasionally but restart fixes problem ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jim2677 F pulseaudio /dev/snd/controlC0: jim2677 F pulseaudio /dev/snd/controlC1: jim2677 F pulseaudio CurrentDesktop: Unity Date: Thu Nov 6 10:34:19 2014 InstallationDate: Installed on 2013-01-20 (654 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro successful Symptom_Card: GF108 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jim2677 F pulseaudio /dev/snd/controlC0: jim2677 F pulseaudio /dev/snd/controlC1: jim2677 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] No sound at all UpgradeStatus: Upgraded to utopic on 2014-10-31 (5 days ago) dmi.bios.date: 09/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0HVRTT dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/30/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0HVRTT:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1389969/+subscriptions -- Mailing list: https://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 1390390] Re: [xorg-edgers] No drm_driver.set_busid() implementation provided by nv_drm_driver
** Package changed: xorg (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1390390 Title: [xorg-edgers] No drm_driver.set_busid() implementation provided by nv_drm_driver Status in “linux” package in Ubuntu: Incomplete Bug description: Using the nvidia-340.58 (from xorg-edgers ppa) with the latest 3.18 kernel, get that warning logged: kernel: [ 35.160563] No drm_driver.set_busid() implementation provided by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly. This is related to a recent patch: http://lists.freedesktop.org/archives/dri-devel/2014-May/060235.html so it seems an upgrade is needed; there is no trouble seen by the way. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-2.2-generic 3.18.0-rc3 Uname: Linux 3.18.0-2-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 340.58 Fri Oct 31 16:44:41 PDT 2014 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-1ubuntu1) ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 BootLog: initctl: Event failed * Setting up X socket directories... [80G [74G[ OK ] * Starting automatic crash report generation: apport [80G [74G[ OK ] CurrentDesktop: GNOME CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file or directory Date: Fri Nov 7 10:49:32 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:362e] Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-2-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC version.compiz: compiz 1:0.9.12.0+15.04.20141105-0ubuntu1 version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 07:45:48 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB RECEIVER MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390390/+subscriptions -- Mailing list: https://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 1390557] Re: [oobe] passcode screen continues after 3 visible dots to confirmation scree
** Changed in: ubuntu-system-settings (Ubuntu) Importance: Undecided = Low ** Summary changed: - [oobe] passcode screen continues after 3 visible dots to confirmation scree + [oobe] passcode screen continues after 3 visible dots to confirmation screen -- 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/1390557 Title: [oobe] passcode screen continues after 3 visible dots to confirmation screen Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Invalid Bug description: krillin build 143 Steps to reproduce in the initial set up wizard 1. after selecting your language and setting up wifi continue to the passcode set up screen 2. type in your 4 digit passcode and pay attention to the dots representing the digits Expected result: all 4 dots are visible before screen moves on to confirm your passcode Actual result: only 3 dots are visible and it looks like you only picked a 3 digit passcode It would be great to have a slight delay and show user the last dot before screen moves on to the next step as we currently have when unlocking your device after swiping away the greeter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1390557/+subscriptions -- Mailing list: https://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 1390557] Re: [oobe] passcode screen continues after 3 visible dots to confirmation screen
** Changed in: ubuntu-system-settings (Ubuntu) Status: New = Confirmed -- 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/1390557 Title: [oobe] passcode screen continues after 3 visible dots to confirmation screen Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Invalid Bug description: krillin build 143 Steps to reproduce in the initial set up wizard 1. after selecting your language and setting up wifi continue to the passcode set up screen 2. type in your 4 digit passcode and pay attention to the dots representing the digits Expected result: all 4 dots are visible before screen moves on to confirm your passcode Actual result: only 3 dots are visible and it looks like you only picked a 3 digit passcode It would be great to have a slight delay and show user the last dot before screen moves on to the next step as we currently have when unlocking your device after swiping away the greeter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1390557/+subscriptions -- Mailing list: https://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 1383785] Re: Edges Demo: If you know the sequence you can complete the guide while the lock screen is up
Tried several times, when I do your steps I never see step 4. If I set a sim pin lock, it happens before edge demo ** Changed in: unity8 (Ubuntu) Status: New = Incomplete ** Changed in: unity8 (Ubuntu RTM) Status: New = Incomplete -- 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/1383785 Title: Edges Demo: If you know the sequence you can complete the guide while the lock screen is up Status in “unity8” package in Ubuntu: Incomplete Status in “unity8” package in Ubuntu RTM: Incomplete Bug description: STEPS: 1. Install a fresh image 2. Run through the welcome wizard setting a pin 3. Do the initial Swipe on the Edges Demo 4. This reveals the Pin lock screen 5. Without typing in the pin, Swipe Down, Swipe Up, Swipe Right 6. Now type in the pin 7. You are now at the congratulations you have completed the edge demo EXPECTED: I expecte the edge demo to complete only after I unlock the screen ACTUAL: I am on the last page meaning that the edge demo is running under the lock screen and is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383785/+subscriptions -- Mailing list: https://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 1389215] Re: Brightness controls are not working in Unity / Xorg.
Some more clarification. I tried under KDE Plasma 5.1 (Neon) and still I could not change the brightness of the backlight. However, the CLI commands that fail in a terminal running under an Xorg session work flawlessly under a console (CTRLALTF1). cd /sys/class/backlight/acpi_video0 echo 5 brightness # Works under the console! echo 10 brightness # Works under the console! This all suggest that somehow, Xorg is inhibiting the brightness control. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1389215 Title: Brightness controls are not working in Unity / Xorg. Status in “xorg” package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
[Touch-packages] [Bug 1386466] Re: alt-grave switcher does not iterate through all windows
As per bug #1349281 also the order of the windows in spread won't follow anymore what you say. Instead windows will spread based on their actual position, more than on the focus state. What happens with Alt-` instead, is that it follows the same behavior of alt+tab: the first and quick tap should select the *previously* focused window, not the window to be focused next (as it happened with spread). So windows switcher spread are arranged based on their last focused time, so that you can quickly access the windows you used more recently. ** Summary changed: - alt-backtick switcher does not iterate through all windows + alt-grave switcher does not iterate through all windows ** Changed in: unity Status: Incomplete = Won't Fix ** Changed in: unity (Ubuntu) Status: Incomplete = Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1386466 Title: alt-grave switcher does not iterate through all windows Status in Unity: Won't Fix Status in “unity” package in Ubuntu: Won't Fix Bug description: There is a serious problem with how the alt-backtick (or alt-grave) switching works. Say I have 10 windows open in Firefox. It is almost impossible to iterate through all 10 of them. This is, I think, for 2 reasons. First, every time the spread comes up, the windows are in a different, and seemingly random, order. If I hit alt-grave over and over again, I just observed it cycling back and forth between 2 windows. It goes between the start window and another, and I have no idea how that window was chosen. How do I look at the 2nd window, then the 3rd, the the 4th, and so on? As of now, I have to look at the spread and, for each one, remember which one I have looked at and which I have not. If there are 3 windows, this is fine. But if there are 10 or 12? No. The fact that the windows come up in random order (mentioned above) makes this harder. I cannot even remember the positions of the windows I have examined. I have to actually find the window content. It would be nice if the job of remember which windows I have seen as I iterated through the available windows was not a job that I had to do, but a job that software could do for me. Is there software that can do this for me? If so, please let me know which it is. thanx - ray ps: I have read through these for help: http://www.reddit.com/r/Ubuntu/comments/jv5vy/ubuntu_1110_so_far_screenshot_tour_by_jono_bacon/c2fk1bs http://askubuntu.com/questions/28086/what-are-unitys-keyboard-and- mouse-shortcuts http://design.canonical.com/2012/03/task-switching-in-ubuntu-and-a -introduction-to-the-spread/ Let me know if there is other doc that shows how to configure window switching or what key-combo to use. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Oct 27 17:11:22 2014 InstallationDate: Installed on 2014-01-31 (269 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-08-14 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386466/+subscriptions -- Mailing list: https://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 1390624] Re: Black line on top of the scope headers with image vivid/mako 12
** Also affects: ubuntu-ui-toolkit Importance: Undecided Status: New ** Changed in: ubuntu-ui-toolkit Assignee: (unassigned) = Tim Peeters (tpeeters) ** Changed in: ubuntu-ui-toolkit Status: New = Confirmed ** Changed in: ubuntu-ui-toolkit Importance: Undecided = High -- 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/1390624 Title: Black line on top of the scope headers with image vivid/mako 12 Status in Ubuntu UI Toolkit: Confirmed Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: current build number: 12 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2014-11-07 21:01:06 version version: 12 version ubuntu: 20141107 version device: 20141106 version custom: 20141107 See: http://people.canonical.com/~rsalveti/home.png Opening against the toolkit as this bug was introduced on image 12, which got only the following changes: http://people.canonical.com/~ogra/touch-image-stats/12.changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1390624/+subscriptions -- Mailing list: https://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 1355284] Re: Switching swipe directions should reverse app spread
** Branch linked: lp:~mzanetti/unity8/reversible-spread -- 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/1355284 Title: Switching swipe directions should reverse app spread Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Bug description: The new app spread is gorgeous, thank you! In general we try to ensure reversibility of transitions - if a user starts a gesture and changes their mind they should be able to reverse the gesture and exit the transition as long as they have not lifted their finger. In this case, a user swiping from the right who intends to toggle windows but overshoots (thereby entering the spread) should be able to change direction, move their finger back towards the right edge, returning to the toggle and then to the original app if they move their finger all the way off the right edge. --- Desired solution User should be in control through the whole the gesture. We want to have reversibility also after second commit point the same way we have for the first commit point in current implementation. This has now been captured also in the right edge documentation: https://docs.google.com/a/canonical.com/document/d/1FC_- 5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1355284/+subscriptions -- Mailing list: https://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 1355284] Re: Switching swipe directions should reverse app spread
** Changed in: unity8 (Ubuntu) Status: Triaged = In Progress -- 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/1355284 Title: Switching swipe directions should reverse app spread Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Bug description: The new app spread is gorgeous, thank you! In general we try to ensure reversibility of transitions - if a user starts a gesture and changes their mind they should be able to reverse the gesture and exit the transition as long as they have not lifted their finger. In this case, a user swiping from the right who intends to toggle windows but overshoots (thereby entering the spread) should be able to change direction, move their finger back towards the right edge, returning to the toggle and then to the original app if they move their finger all the way off the right edge. --- Desired solution User should be in control through the whole the gesture. We want to have reversibility also after second commit point the same way we have for the first commit point in current implementation. This has now been captured also in the right edge documentation: https://docs.google.com/a/canonical.com/document/d/1FC_- 5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1355284/+subscriptions -- Mailing list: https://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 1383785] Re: Edges Demo: If you know the sequence you can complete the guide while the lock screen is up
Ah sorry. I think this can now be closed. There has been a change in the behaviour and lock screen is no longer displayed after the first swipe. I think that this bug can be marked invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383785 Title: Edges Demo: If you know the sequence you can complete the guide while the lock screen is up Status in “unity8” package in Ubuntu: Incomplete Status in “unity8” package in Ubuntu RTM: Incomplete Bug description: STEPS: 1. Install a fresh image 2. Run through the welcome wizard setting a pin 3. Do the initial Swipe on the Edges Demo 4. This reveals the Pin lock screen 5. Without typing in the pin, Swipe Down, Swipe Up, Swipe Right 6. Now type in the pin 7. You are now at the congratulations you have completed the edge demo EXPECTED: I expecte the edge demo to complete only after I unlock the screen ACTUAL: I am on the last page meaning that the edge demo is running under the lock screen and is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383785/+subscriptions -- Mailing list: https://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 1388582] Re: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks
have you look at last page of ad1986a datasheet and git log of patch_analog.c related to ad1986a? some laptop seem to use 3stack instead of laptop model in the past since the mic select is quite complicated -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1388582 Title: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have a fresh install of KUbuntu 14.10 with this problem and i come of a KUbuntu 13.10 without problems. I don't have any sound from speakers or headphone, i think the driver isn't loaded, but the microphone works, it records. The sound playback works too, but the sound doesn't go through speakers or headphones. I was testing with a lot of LiveCD KUbuntu when the problem comes. With LiveCDs KUbuntu 12.04.5 LTS, 12.10, 13.04 the sound works, they configs the sound system as HDA Intel AD198x. Since LiveCDs 13.10, 14.04.1 LTS and, of course, 14.10 Live CD and my install, i have this problem, because the sound system is now AD1986A. I will attach the alsa-info output for all this systems in my computer. But with HDA_Analyzer http://www.alsa- project.org/main/index.php/HDA_Analyzer i found the details of the problem: i can create a python script to brought back the sound working in a basic mode, like as previously. The details are activating EAPD in Card 0, Codec 0, Node 0x1b PIN (In my computer, it could be different in another) what brought back the sound to the speakers, and unmuting Output Amplifier in Card 0, Codec 0, Node 0x1a VAL[0] and VAL[1] to brought back sound to the headphones when they are plugged. I will attach too the output of this diff and the python script created by HDA_Analyzer for my system. At least, the basic working state should be back, because with a untoching fresh install there isn't any sound. There are related bugs here and other post in internet, but i collected all information i found and can give more if it's necessary. For additional information: Searching the solution, i tested too all the models availables for HDA Intel AD1986A (editing /etc/modprobe.d /alsa-base.conf with AD1986A models /usr/share/doc/alsa-base/driver /HD-Audio-Models.txt.gz) and i found the default one doesn't fit my system and anothers are better, but have problems of no sound too and i don't found how to fix these problem. When this bug is corrected, i want to help to found a better model for my computer, i don't know how now, but first it brought back the sound. Also, i test with snd-hda- tools https://launchpad.net/~diwic/+archive/ubuntu/hda and with hda- jack-sense-test the Green Line Out sense doesn't work (always NO present) but the Pink Mic sense works without problems. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thywalls 2380 F pulseaudio CurrentDesktop: KDE Date: Sun Nov 2 16:24:36 2014 InstallationDate: Installed on 2014-10-30 (3 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T12JNC.206 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EasyNote_MX65 dmi.board.vendor: Packard Bell BV dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell BV dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT12JNC.206:bd09/28/2006:svnPackardBellBV:pnEasyNote_MX65:pvrPB63E03104:rvnPackardBellBV:rnEasyNote_MX65:rvr1.0:cvnPackardBellBV:ct10:cvr: dmi.product.name: EasyNote_MX65 dmi.product.version: PB63E03104 dmi.sys.vendor: Packard Bell BV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1388582/+subscriptions -- Mailing list: https://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 1386709] Re: Queries to remote scopes don't include location data (even if the scope needs it)
** Changed in: unity-scopes-api (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1386709 Title: Queries to remote scopes don't include location data (even if the scope needs it) Status in “unity-scopes-api” package in Ubuntu: Confirmed Bug description: The query to weatherchannel is not including lat/long, even if the remote-scopes listing have the needs_location_data in true: https://pastebin.canonical.com/119512/ The server try to guess user location using geo-ip, but it's not always as accurate as we need for a user service (it depends heavily on your IP being representative of where you really are, which may not be the case for hotel proxys, weird ISPs, etc). Plase, send user's latitude and longitude for the remote scopes that need this information. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1386709/+subscriptions -- Mailing list: https://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 1384707] Re: sync monitor reports error on boot when no network
** Changed in: sync-monitor Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1384707 Title: sync monitor reports error on boot when no network Status in Sync monitor for Ubuntu Touch: Fix Released Status in “address-book-app” package in Ubuntu: Fix Released Status in “sync-monitor” package in Ubuntu RTM: Fix Released Bug description: if you have google contacts setup for sync, it will start before the network connection sometimes and upon reboot displays a a sync failed message. The service should check network connectivity and only attempt to sync when on wifi (and add a switch for 3g later). To manage notifications about this bug go to: https://bugs.launchpad.net/sync-monitor/+bug/1384707/+subscriptions -- Mailing list: https://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 1384749] Re: [TOPBLOCKER] Detected X, Y coordinates for touch event on text field is off
reducing to High as per comment #6 and discussion on 11/7 ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Critical = High ** Changed in: ubuntu-ui-toolkit Importance: Critical = High -- 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/1384749 Title: [TOPBLOCKER] Detected X,Y coordinates for touch event on text field is off Status in Ubuntu UI Toolkit: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Bug description: Tapping on a word in a text input seems to select the word below, rather than the one I intended to select The Y seems to be lower by approx. 1 GU Reproduce by - Go to messages and tap on message filed - Enter 4 rows of content - Tap on a word in the second row - The word below is often selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1384749/+subscriptions -- Mailing list: https://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 1381930] Re: [TOPBLOCKER] 7digital previews do not play in the scope
marking the remaining Ubuntu task as high to get off rtm list ** Changed in: unity-scopes-api (Ubuntu) Importance: Critical = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1381930 Title: [TOPBLOCKER] 7digital previews do not play in the scope Status in “qtbase-opensource-src” package in Ubuntu: Invalid Status in “qtubuntu-media” package in Ubuntu: Fix Released Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: Fix Committed Status in “unity8” package in Ubuntu: Invalid Status in “qtubuntu-media” package in Ubuntu RTM: Fix Released Status in “unity-scopes-api” package in Ubuntu RTM: Fix Released Status in “unity8” package in Ubuntu RTM: Invalid Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1381930/+subscriptions -- Mailing list: https://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 1383785] Re: Edges Demo: If you know the sequence you can complete the guide while the lock screen is up
** Changed in: unity8 (Ubuntu) Status: Incomplete = Invalid ** Changed in: unity8 (Ubuntu RTM) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383785 Title: Edges Demo: If you know the sequence you can complete the guide while the lock screen is up Status in “unity8” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu RTM: Invalid Bug description: STEPS: 1. Install a fresh image 2. Run through the welcome wizard setting a pin 3. Do the initial Swipe on the Edges Demo 4. This reveals the Pin lock screen 5. Without typing in the pin, Swipe Down, Swipe Up, Swipe Right 6. Now type in the pin 7. You are now at the congratulations you have completed the edge demo EXPECTED: I expecte the edge demo to complete only after I unlock the screen ACTUAL: I am on the last page meaning that the edge demo is running under the lock screen and is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383785/+subscriptions -- Mailing list: https://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 1351559] Re: Apps in spread are not anti-aliased
This bug was fixed in the package qtmir - 0.4.4+15.04.20141110-0ubuntu1 --- qtmir (0.4.4+15.04.20141110-0ubuntu1) vivid; urgency=low [ Michael Zanetti ] * Use QSGDefaultImageNode instead of QSGSimpleTexture to gain surface manipulation features such as antialiasing (LP: #1351559) [ josharenson ] * Add support for enabling/disabling orientation sensor based on screen power state. (LP: #1375297) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 10 Nov 2014 09:41:58 + ** Changed in: qtmir (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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1351559 Title: Apps in spread are not anti-aliased Status in Qt integration with the Mir display server: In Progress Status in “qtmir” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “qtmir” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: With qtcomp enabled, smoothing in the spread was disabled. This is unfortunately very visible on lower density devices, causing sharp edges on all diagonal lines. We need to investigate how to enable anti-aliasing with as little performance hit as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1351559/+subscriptions -- Mailing list: https://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 1307413] Re: apport-unpack requires too much main memory to run
** Tags added: cts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1307413 Title: apport-unpack requires too much main memory to run Status in “apport” package in Ubuntu: In Progress Bug description: when running apport-unpack on large apport reports (linux-image kernel dumps is a good example), it requires an enormous amount of main memory to run. An example is a 1.3Gb apport report that runs for more than 24 hours with more than 4Gb of RSS. The command should requires less memory to extract those big reports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1307413/+subscriptions -- Mailing list: https://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 1391149] Re: greeter not reacting to swipes
Looks like it could be related to the TouchGate in Greeter.qml. Enabling TouchRegistry and TouchGate logging, as well as adding some debug prints to the DraggingArea in Greeter.qml, should be enough to clarify what's happening. Provided there's a way to reproduce the bug, that is. -- 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/1391149 Title: greeter not reacting to swipes Status in “unity8” package in Ubuntu: New Bug description: i had this a few times over the weekend with images 150-153, suddenly the greeter does not react to right/left swipes on the wallpaper to reveal the PIN unlock dialog ... swiping in the launcher from the left makes the greeter go away and reveals the PIN unlock dialog then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1391149/+subscriptions -- Mailing list: https://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 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Tags added: rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1389008 Title: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control) Status in Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Status in “indicator-sound” package in Ubuntu RTM: New Status in “unity8” package in Ubuntu RTM: New Bug description: Often after boot indicator-sound fails to connect to Pulseaudio and to unity-notifications using libnotify. Therefore, volume notifications aren't shown and changes to the volume role go unnoticed, which then results in improper volume control. As already mentioned in the original bug description, running restart indicator-sound resolves the issue. Original description: Happens often after phone boot where changing volume by touch or by phone buttons. Volume correctly changes, but the org.freedesktop.Notifications popup isn't displayed. The problem seems fixes itself if you run restart indicator-sound, so maybe there's an issue with i-sound and unity-notifications starting at the same time, with the former querying the latter's capabilities before it's ready for business? To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1389008/+subscriptions -- Mailing list: https://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 1386682] Re: Facebook share is broken
** Also affects: webbrowser-app (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1386682 Title: Facebook share is broken Status in The Webapps-core project: In Progress Status in Web Browser App: In Progress Status in “webbrowser-app” package in Ubuntu: New Status in “webbrowser-app” package in Ubuntu RTM: New Bug description: Facebook share is broken To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-core/+bug/1386682/+subscriptions -- Mailing list: https://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 1242113] Re: Cannot input chinese in Unity Dash or HUD using fcitx input method.
Hi, Unity Dash should support input method now since bug 983254 is fixed. ** Changed in: unity Status: New = Invalid ** Changed in: unity Status: Invalid = Fix Released ** Changed in: unity (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1242113 Title: Cannot input chinese in Unity Dash or HUD using fcitx input method. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Cannot change input method engine into any Chinese one under the Unity Dash or HUD interface. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1242113/+subscriptions -- Mailing list: https://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 1384749] Re: [TOPBLOCKER] Detected X, Y coordinates for touch event on text field is off
Olli, I already got a branch reviewed for this and it's targeting RTM. Should it be held off? -- 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/1384749 Title: [TOPBLOCKER] Detected X,Y coordinates for touch event on text field is off Status in Ubuntu UI Toolkit: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Bug description: Tapping on a word in a text input seems to select the word below, rather than the one I intended to select The Y seems to be lower by approx. 1 GU Reproduce by - Go to messages and tap on message filed - Enter 4 rows of content - Tap on a word in the second row - The word below is often selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1384749/+subscriptions -- Mailing list: https://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 1383042] Re: Newly added locations display strange text rather than city name
Fix committed into lp:ubuntu-weather-app at revision 387, scheduled for release in ubuntu-weather-app, milestone alpha-1 ** Changed in: ubuntu-weather-app Status: In Progress = Fix Committed -- 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/1383042 Title: Newly added locations display strange text rather than city name Status in Weather application for Ubuntu devices: Fix Committed Status in “ubuntu-ui-toolkit” package in Ubuntu: New Bug description: Started the weather app, it had two previously defined locations. I added two new locations, the first displayed a file:// url in the header, the second display context something After restarting the app the strings were correct. Deleting a city and re-adding worked correctly. I deleted one city then added it back, and the two new cities are reversed, the show each others weather data rather than their own. Not sure if this is related or needs a separate bug. Restarting the app again fixed this issue as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-weather-app/+bug/1383042/+subscriptions -- Mailing list: https://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 1386682] Re: Facebook share is broken
** Tags added: rtm14 ** Changed in: webbrowser-app (Ubuntu) Importance: Undecided = High ** Changed in: webbrowser-app (Ubuntu RTM) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1386682 Title: Facebook share is broken Status in The Webapps-core project: In Progress Status in Web Browser App: In Progress Status in “webbrowser-app” package in Ubuntu: New Status in “webbrowser-app” package in Ubuntu RTM: New Bug description: Facebook share is broken To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-core/+bug/1386682/+subscriptions -- Mailing list: https://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 1364292] Re: [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45 chipset
No, nothing changed. The bug still exists. Was there any reason to believe that it wouldn't? Closing bugs on which there has been no comment for 60 days is absurd. It's the equivalent of brushing dirt under the rug. But I don't want to check the latest image every 60 days on the off chance something has changed, when nobody is trying to fix this - that's a complete waste of my time. So there's a problem with the bug tracking system here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1364292 Title: [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45 chipset Status in “xorg” package in Ubuntu: Incomplete Bug description: I have just installed Ubuntu 14.04 64-bit on my Toshiba Portege R600-10Q laptop (a model from 2009). I am now trying to display the desktop on a BenQ Senseye3 22 monitor, via the vga output, but it's not working - the monitor says No Signal Detected!. What I've done: I have gone into Screen Display, where I can see the monitor is detected by the laptop. The monitor has a 1920 x 1080 native resolution, which I have tried to use, but I have also set it to lower resolutions, e.g. 1024 x 576. I have tried to use the monitor in dual screen, mirrored and single screen mode - none work. I have tried pressing Fn + F5 to get single screen output - the laptop screen goes blank, but still no output on the monitor. I have tried several monitors (of the same type, and also of a different make), so I don't think it's that. If I plug the vga cable in after boot up, then the monitor receives no signal. WORKAROUND: If, and only if, the monitor was plugged in to the PC's VGA output during boot up, then the display outputs to the monitor correctly. The laptop has the Intel® GS45 Express chipset for graphics acceleration. I installed mesa-utils and ran glxinfo in a terminal. Amongst the output was: OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset Also, in the About This Computer window I see: Graphics: Mobile Intel® GM45 Express Chipset I wonder if the problem is that my chipset is GS45 not GM45. The output of sudo lshw -C video is: *-display:0 description: VGA compatible controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 07 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:44 memory:ff40-ff7f memory:e000-efff ioport:cff8(size=8) *-display:1 UNCLAIMED description: Display controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2.1 bus info: pci@:00:02.1 version: 07 width: 64 bits clock: 33MHz capabilities: pm bus_master cap_list configuration: latency=0 resources: memory:ffc0-ffcf ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Sep 2 10:00:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:000c] Subsystem: Toshiba America Info Systems Device [1179:000c] InstallationDate: Installed on 2014-08-28 (4 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: TOSHIBA PORTEGE R600 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=fe977943-4013-472e-b627-f7184c9e190f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd11/27/2008:svnTOSHIBA:pnPORTEGER600:pvrPPR61E-00Q00CEN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE R600
[Touch-packages] [Bug 1351559] Re: Apps in spread are not anti-aliased
** Changed in: qtmir Status: In Progress = Fix Released -- 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/1351559 Title: Apps in spread are not anti-aliased Status in Qt integration with the Mir display server: Fix Released Status in “qtmir” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “qtmir” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: With qtcomp enabled, smoothing in the spread was disabled. This is unfortunately very visible on lower density devices, causing sharp edges on all diagonal lines. We need to investigate how to enable anti-aliasing with as little performance hit as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1351559/+subscriptions -- Mailing list: https://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 1386682] Re: Facebook share is broken
** Tags added: touch-2014-11-13 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1386682 Title: Facebook share is broken Status in The Webapps-core project: In Progress Status in Web Browser App: In Progress Status in “webbrowser-app” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu RTM: New Bug description: Facebook share is broken To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-core/+bug/1386682/+subscriptions -- Mailing list: https://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 1388089] Re: [webapp-container] apps are not handled by lifecycle management properly
tagged for review and tracking ** Tags added: rtm14 ** Changed in: webbrowser-app (Ubuntu RTM) Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1388089 Title: [webapp-container] apps are not handled by lifecycle management properly Status in Oxide Webview: New Status in Web Browser App: New Status in “qtmir” package in Ubuntu: New Status in “webbrowser-app” package in Ubuntu: New Status in “qtmir” package in Ubuntu RTM: New Status in “webbrowser-app” package in Ubuntu RTM: New Bug description: in image 137, if you open a gazillion of apps and have webapps among them, the webapp screenshots never turn blurry when the OOM score is reached on high memory pressure ... once you switch to such a webapp, the whole content window turns white (sometimes the app header stays around, sometimes the whole app window is white). seemingly the renderer is lifecycle managed and gets properly OOM killed on high memory pressure , but the frontend of the webapp does not. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1388089/+subscriptions -- Mailing list: https://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 1391214] [NEW] dimensions and positions of objects not reading correctly
Public bug reported: Hi, I am using inkscape to create a SVG files containing multiple objects and rsvg to then render these via cairo. I am using rsvg_handle_get_dimensions_sub and position_sub() to read the (x,y) and (w,h) for the objects which are then used to translate and scale cairo before using rsvg_handle_render_cairo_sub() to render the object. I am running into anomalies when reading this attributes. I have attached a stripped down source for a simple utility which 'walks' the XML of the file and calls the two functions to dump out all the objects in the file. I have also attached a sample SVG file created with inkscape with a single rectangle of 45x20px on a canvas of 100x100px Running svgsize on this produces: $ ./svgsize /tmp/inkscape.svg svg : svg2 100x 100 ( 0, 0) defs : defs4 0x 0 ( 0, 0) namedview : base 0x 0 ( 0, 0) grid : grid4469 0x 0 ( 0, 0) metadata : metadata7 0x 0 ( 0, 0) g : layer1 50x1047 ( 0,-1022) rect : rect4471 50x1047 ( 0,-1022) with scrambled sizes and positions for the rect. If I load the file into karbon (the KDE editor) and save it (with no other modifications), svgsize produces the correct numbers: $ ./svgsize /tmp/karbon1.svg g : layer1 45x 20 ( 5, 5) rect : rect4471 45x 20 ( 5, 5) Loading this back into Inkscape and saving it out again, and the original values are shown. I have tried this on inkscape stable 0.48 and the development 0.91 I am using rsvg 2.36.1-0ubuntu1 from precise. I get the same problem with trusty. Thanks, ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New ** Attachment added: inkscape-dimensions.zip https://bugs.launchpad.net/bugs/1391214/+attachment/4257291/+files/inkscape-dimensions.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1391214 Title: dimensions and positions of objects not reading correctly Status in “librsvg” package in Ubuntu: New Bug description: Hi, I am using inkscape to create a SVG files containing multiple objects and rsvg to then render these via cairo. I am using rsvg_handle_get_dimensions_sub and position_sub() to read the (x,y) and (w,h) for the objects which are then used to translate and scale cairo before using rsvg_handle_render_cairo_sub() to render the object. I am running into anomalies when reading this attributes. I have attached a stripped down source for a simple utility which 'walks' the XML of the file and calls the two functions to dump out all the objects in the file. I have also attached a sample SVG file created with inkscape with a single rectangle of 45x20px on a canvas of 100x100px Running svgsize on this produces: $ ./svgsize /tmp/inkscape.svg svg : svg2 100x 100 ( 0, 0) defs : defs4 0x 0 ( 0, 0) namedview : base 0x 0 ( 0, 0) grid : grid4469 0x 0 ( 0, 0) metadata : metadata7 0x 0 ( 0, 0) g : layer1 50x1047 ( 0,-1022) rect : rect4471 50x1047 ( 0,-1022) with scrambled sizes and positions for the rect. If I load the file into karbon (the KDE editor) and save it (with no other modifications), svgsize produces the correct numbers: $ ./svgsize /tmp/karbon1.svg g : layer1 45x 20 ( 5, 5) rect : rect4471 45x 20 ( 5, 5) Loading this back into Inkscape and saving it out again, and the original values are shown. I have tried this on inkscape stable 0.48 and the development 0.91 I am using rsvg 2.36.1-0ubuntu1 from precise. I get the same problem with trusty. Thanks, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1391214/+subscriptions -- Mailing list: https://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 1390726] Re: Error message init: startpar-bridge (*) main process (*) terminated with status 127 appears multiple times on booting
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sysvinit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1390726 Title: Error message init: startpar-bridge (*) main process (*) terminated with status 127 appears multiple times on booting Status in “sysvinit” package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 15.04 dev with sysvinit-utils 2.88dsf-53.2ubuntu1 and for a few days I'm seeing always on booting error messages like from this booting instance: sworddragon@ubuntu:~$ dmesg | grep startpar-bridge [ 11.251848] init: startpar-bridge (hwclock.sh--started) main process (273) terminated with status 127 [ 11.252052] init: startpar-bridge (plymouth-ready-startup-started) main process (275) terminated with status 127 [ 11.261156] init: startpar-bridge (hwclock--started) main process (276) terminated with status 127 [ 11.264019] init: startpar-bridge (hostname--stopped) main process (279) terminated with status 127 [ 11.264298] init: startpar-bridge (hwclock--stopped) main process (280) terminated with status 127 [ 11.264497] init: startpar-bridge (hostname.sh--started) main process (281) terminated with status 127 [ 11.300143] init: startpar-bridge (plymouth-upstart-bridge--started) main process (282) terminated with status 127 [ 11.441524] init: startpar-bridge (plymouth--started) main process (285) terminated with status 127 [ 11.458996] init: startpar-bridge (plymouth-upstart-bridge--stopped) main process (286) terminated with status 127 [ 11.459185] init: startpar-bridge (plymouth--stopped) main process (287) terminated with status 127 [ 11.533663] init: startpar-bridge (plymouth-ready-startup-stopped) main process (290) terminated with status 127 [ 11.979125] init: startpar-bridge (mountall--started) main process (293) terminated with status 127 [ 11.982885] init: startpar-bridge (mounted-proc--started) main process (301) terminated with status 127 [ 11.983119] init: startpar-bridge (init.d/cpufreq--started) main process (302) terminated with status 127 [ 11.983318] init: startpar-bridge (mounted-dev--started) main process (303) terminated with status 127 [ 11.983509] init: startpar-bridge (mounted-run--started) main process (304) terminated with status 127 [ 12.061686] init: startpar-bridge (mounted-proc--stopped) main process (314) terminated with status 127 [ 12.062344] init: startpar-bridge (mounted-dev--stopped) main process (315) terminated with status 127 [ 12.210948] init: startpar-bridge (mounted-run--stopped) main process (320) terminated with status 127 [ 12.369938] init: startpar-bridge (mounted-debugfs--started) main process (332) terminated with status 127 [ 12.370143] init: startpar-bridge (mounted-debugfs--stopped) main process (334) terminated with status 127 [ 12.981052] init: startpar-bridge (container-detect--stopped) main process (344) terminated with status 127 [ 13.681176] init: startpar-bridge (checkroot.sh--started) main process (354) terminated with status 127 [ 13.681397] init: startpar-bridge (checkfs.sh--started) main process (355) terminated with status 127 [ 13.681599] init: startpar-bridge (checkroot-bootclean.sh--started) main process (356) terminated with status 127 [ 14.054084] init: startpar-bridge (init.d/automount--started) main process (357) terminated with status 127 [ 14.054297] init: startpar-bridge (init.d/log--started) main process (358) terminated with status 127 [ 16.168987] init: startpar-bridge (init.d/log--stopped) main process (391) terminated with status 127 [ 16.372769] init: startpar-bridge (resolvconf--started) main process (398) terminated with status 127 [ 17.038956] init: startpar-bridge (mountnfs-bootclean.sh--started) main process (409) terminated with status 127 [ 17.039189] init: startpar-bridge (mountkernfs.sh--started) main process (410) terminated with status 127 [ 17.039380] init: startpar-bridge (bootmisc.sh--started) main process (411) terminated with status 127 [ 17.039566] init: startpar-bridge (mountdevsubfs.sh--started) main process (412) terminated with status 127 [ 17.039757] init: startpar-bridge (mtab.sh--started) main process (413) terminated with status 127 [ 17.247406] init: startpar-bridge (mountall-bootclean.sh--started) main process (414) terminated with status 127 [ 17.530744] init: startpar-bridge (procps-instance-virtual-filesystems-started) main process (421) terminated with status 127 [ 17.530852] init: startpar-bridge (procps--started) main process (422) terminated with status 127 [ 17.748589] init: startpar-bridge (console-setup--started) main process (424) terminated with status 127 [ 17.748674]
[Touch-packages] [Bug 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
How come do we not see this when the updated QtBearer plugin isn't installed? What this tells me is something is asking NM to activate a connection when it already is; so rather than looking at NetworkManager, I'd look at whatever is activating connections. indicator-network/connectivity- api maybe? or the APN editor? Nov 7 16:39:07 ubuntu-phablet NetworkManager[1333]: info (/ril_0): disconnecting for new activation request. Nov 7 16:39:07 ubuntu-phablet NetworkManager[1333]: info (/ril_0): device state change: activated - disconnected (reason 'none') [100 30 0] Nov 7 16:39:07 ubuntu-phablet NetworkManager[1333]: info (/ril_0): deactivating device (reason 'none') [0] ^ This isn't done by NetworkManager. It seems to be consistently happening after 20-25 seconds of being connected. Please try to increasing the logging in NetworkManager (add --log- level=debug to the exec line /etc/init/network-manager.conf), and attach syslog again, maybe there is something to be found out from there. ** Changed in: network-manager (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: In Progress Status in The Savilerow project: New Status in “network-manager” package in Ubuntu: Incomplete Status in “ofono” package in Ubuntu: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://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 1386682] Re: Facebook share is broken
This bug was fixed in the package webbrowser-app - 0.23+15.04.20141110-0ubuntu1 --- webbrowser-app (0.23+15.04.20141110-0ubuntu1) vivid; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Alexandre Abreu ] * Fix facebook content hub share, the proper share API was not enabled to access from the webapp-container. (LP: #1386682) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 10 Nov 2014 12:54:51 + ** Changed in: webbrowser-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 webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1386682 Title: Facebook share is broken Status in The Webapps-core project: In Progress Status in Web Browser App: In Progress Status in “webbrowser-app” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu RTM: New Bug description: Facebook share is broken To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-core/+bug/1386682/+subscriptions -- Mailing list: https://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 1391214] Re: dimensions and positions of objects not reading correctly
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: librsvg (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1391214 Title: dimensions and positions of objects not reading correctly Status in “librsvg” package in Ubuntu: New Bug description: Hi, I am using inkscape to create a SVG files containing multiple objects and rsvg to then render these via cairo. I am using rsvg_handle_get_dimensions_sub and position_sub() to read the (x,y) and (w,h) for the objects which are then used to translate and scale cairo before using rsvg_handle_render_cairo_sub() to render the object. I am running into anomalies when reading this attributes. I have attached a stripped down source for a simple utility which 'walks' the XML of the file and calls the two functions to dump out all the objects in the file. I have also attached a sample SVG file created with inkscape with a single rectangle of 45x20px on a canvas of 100x100px Running svgsize on this produces: $ ./svgsize /tmp/inkscape.svg svg : svg2 100x 100 ( 0, 0) defs : defs4 0x 0 ( 0, 0) namedview : base 0x 0 ( 0, 0) grid : grid4469 0x 0 ( 0, 0) metadata : metadata7 0x 0 ( 0, 0) g : layer1 50x1047 ( 0,-1022) rect : rect4471 50x1047 ( 0,-1022) with scrambled sizes and positions for the rect. If I load the file into karbon (the KDE editor) and save it (with no other modifications), svgsize produces the correct numbers: $ ./svgsize /tmp/karbon1.svg g : layer1 45x 20 ( 5, 5) rect : rect4471 45x 20 ( 5, 5) Loading this back into Inkscape and saving it out again, and the original values are shown. I have tried this on inkscape stable 0.48 and the development 0.91 I am using rsvg 2.36.1-0ubuntu1 from precise. I get the same problem with trusty. Thanks, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1391214/+subscriptions -- Mailing list: https://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 1390994] [NEW] Lost ability to print duplex
You have been subscribed to a public bug: A recent update (about a week or two ago) has resulted in my HP 8600 printer no longer printing double-sided. All the configuration information appears to be unchanged, but pages are not printed double- sided, when requested. The duplexer works properly in local mode. My configuration is: Ubuntu 14.04 (up-to-date), HP Pavilion dv6 with AMD quad-core processor. I have been running Ubuntu on this machine for about 27 months. I successfully upgraded from 12.04 to 14.04 last summer. The 8600 printer has been in use for about two years. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Lost ability to print duplex https://bugs.launchpad.net/bugs/1390994 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. -- Mailing list: https://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 1218289] Re: [dialer app] Incoming call (snap decision) not to spec
** Changed in: telephony-service (Ubuntu) Status: New = In Progress ** Changed in: telephony-service (Ubuntu RTM) Status: New = In Progress ** Changed in: telephony-service (Ubuntu) Importance: Undecided = High ** Changed in: telephony-service (Ubuntu RTM) Importance: Undecided = High ** Changed in: telephony-service (Ubuntu) Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) ** Changed in: telephony-service (Ubuntu RTM) Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) ** No longer affects: dialer-app ** No longer affects: dialer-app (Ubuntu) -- 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/1218289 Title: [dialer app] Incoming call (snap decision) not to spec Status in Ubuntu UX bugs: Fix Released Status in The Unity 8 shell: Fix Released Status in “telephony-service” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Fix Released Status in “unity8” source package in Saucy: Confirmed Status in “telephony-service” package in Ubuntu RTM: In Progress Bug description: Current situation: Incoming call appears in snap decision format, but missing: - Decision buttons not the right visual colours and assets (missing colour and combo button) - background is currently transparent, so can see content below. Desired solution: - As per spec, when receiving an incoming call the snap decision should be solid background. And the notification buttons and style should be as per design. - See Notification and Snap Decision spec for full details of the final signed off design, https://docs.google.com/a/canonical.com/document/d/1puQ9Z0yKqzsQ1VQ1OOBkxgp78iWGnAhAkFXWJFTWIrE/edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1218289/+subscriptions -- Mailing list: https://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 1390726] Re: Error message init: startpar-bridge (*) main process (*) terminated with status 127 appears multiple times on booting
I installed 'startpar' and the problem went away; but sysvinit-utils conflicts with startpar, so somehow the sysvinit-utils package isn't providing the right startpar-* scripts. Debian has a newer version so I'm guessing it may need to be synced. ** Changed in: sysvinit (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1390726 Title: Error message init: startpar-bridge (*) main process (*) terminated with status 127 appears multiple times on booting Status in “sysvinit” package in Ubuntu: In Progress Bug description: I'm using Ubuntu 15.04 dev with sysvinit-utils 2.88dsf-53.2ubuntu1 and for a few days I'm seeing always on booting error messages like from this booting instance: sworddragon@ubuntu:~$ dmesg | grep startpar-bridge [ 11.251848] init: startpar-bridge (hwclock.sh--started) main process (273) terminated with status 127 [ 11.252052] init: startpar-bridge (plymouth-ready-startup-started) main process (275) terminated with status 127 [ 11.261156] init: startpar-bridge (hwclock--started) main process (276) terminated with status 127 [ 11.264019] init: startpar-bridge (hostname--stopped) main process (279) terminated with status 127 [ 11.264298] init: startpar-bridge (hwclock--stopped) main process (280) terminated with status 127 [ 11.264497] init: startpar-bridge (hostname.sh--started) main process (281) terminated with status 127 [ 11.300143] init: startpar-bridge (plymouth-upstart-bridge--started) main process (282) terminated with status 127 [ 11.441524] init: startpar-bridge (plymouth--started) main process (285) terminated with status 127 [ 11.458996] init: startpar-bridge (plymouth-upstart-bridge--stopped) main process (286) terminated with status 127 [ 11.459185] init: startpar-bridge (plymouth--stopped) main process (287) terminated with status 127 [ 11.533663] init: startpar-bridge (plymouth-ready-startup-stopped) main process (290) terminated with status 127 [ 11.979125] init: startpar-bridge (mountall--started) main process (293) terminated with status 127 [ 11.982885] init: startpar-bridge (mounted-proc--started) main process (301) terminated with status 127 [ 11.983119] init: startpar-bridge (init.d/cpufreq--started) main process (302) terminated with status 127 [ 11.983318] init: startpar-bridge (mounted-dev--started) main process (303) terminated with status 127 [ 11.983509] init: startpar-bridge (mounted-run--started) main process (304) terminated with status 127 [ 12.061686] init: startpar-bridge (mounted-proc--stopped) main process (314) terminated with status 127 [ 12.062344] init: startpar-bridge (mounted-dev--stopped) main process (315) terminated with status 127 [ 12.210948] init: startpar-bridge (mounted-run--stopped) main process (320) terminated with status 127 [ 12.369938] init: startpar-bridge (mounted-debugfs--started) main process (332) terminated with status 127 [ 12.370143] init: startpar-bridge (mounted-debugfs--stopped) main process (334) terminated with status 127 [ 12.981052] init: startpar-bridge (container-detect--stopped) main process (344) terminated with status 127 [ 13.681176] init: startpar-bridge (checkroot.sh--started) main process (354) terminated with status 127 [ 13.681397] init: startpar-bridge (checkfs.sh--started) main process (355) terminated with status 127 [ 13.681599] init: startpar-bridge (checkroot-bootclean.sh--started) main process (356) terminated with status 127 [ 14.054084] init: startpar-bridge (init.d/automount--started) main process (357) terminated with status 127 [ 14.054297] init: startpar-bridge (init.d/log--started) main process (358) terminated with status 127 [ 16.168987] init: startpar-bridge (init.d/log--stopped) main process (391) terminated with status 127 [ 16.372769] init: startpar-bridge (resolvconf--started) main process (398) terminated with status 127 [ 17.038956] init: startpar-bridge (mountnfs-bootclean.sh--started) main process (409) terminated with status 127 [ 17.039189] init: startpar-bridge (mountkernfs.sh--started) main process (410) terminated with status 127 [ 17.039380] init: startpar-bridge (bootmisc.sh--started) main process (411) terminated with status 127 [ 17.039566] init: startpar-bridge (mountdevsubfs.sh--started) main process (412) terminated with status 127 [ 17.039757] init: startpar-bridge (mtab.sh--started) main process (413) terminated with status 127 [ 17.247406] init: startpar-bridge (mountall-bootclean.sh--started) main process (414) terminated with status 127 [ 17.530744] init: startpar-bridge (procps-instance-virtual-filesystems-started) main process (421) terminated with status 127 [ 17.530852] init: startpar-bridge
[Touch-packages] [Bug 1385630] Re: systemd 215 hangs during boot
Martin, My setup is fairly new, from September 2014. I installed Ubuntu-Gnome Trusty then and upraded it first to Utopic and now to Vivid dev. I haven't mofified /etc/initramfs-tools/initramfs.conf in any way. I attach this file here. The folder /etc/initramfs-tools/conf.d/ is empty. ** Attachment added: initramfs.conf https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+attachment/4257299/+files/initramfs.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1385630 Title: systemd 215 hangs during boot Status in “systemd” package in Ubuntu: Incomplete Bug description: I just installed (for testing) the newest systemd from Vivid proposed repositories. Yes, that is only a proposed package. The version is 215-5ubuntu1. Also the new plymouth was needed to do this (version 0.9.0-0ubuntu8). After the installation I found that every now and then booting or rebooting fails. It fails in a system-fsck line. So, nowhere to go from that, no tty's, no nothing. After each failure the next booting is successful, however. My setup is extremely fast, I am able to get to the desktop in about 5 seconds from grub menu. The setup contains Intel Core i7 4790 processor and Samsung 850 Pro SSD. This may also be some sort of race situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+subscriptions -- Mailing list: https://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 1387216] Re: [Dash] Remove Header's Suru Background
** Branch linked: lp:~alecu/unity-scope-mediascanner/remove-header- background -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1387216 Title: [Dash] Remove Header's Suru Background Status in Ubuntu UX bugs: Fix Committed Status in “unity-scope-click” package in Ubuntu: Fix Released Status in “unity-scope-mediascanner” package in Ubuntu: New Status in “unity8” package in Ubuntu: Invalid Status in “unity-scope-click” package in Ubuntu RTM: Triaged Bug description: The origami pattern on the header is not working as expected from a design standpoint and should be removed and reverted to the plain header. -- Desired resolution: - revert the single asset swap that introduced the new header background that does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1387216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp