[Touch-packages] [Bug 1412916] [NEW] evince: Bad PDF rendering: invalid font scale
You have been subscribed to a public bug: Evince in ubuntu 14.04 (3.10.3-0ubuntu10.1) suffers from this bug: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78042 The test case which is attached to the upstream bug demonstrates the problem with Evince in Ubuntu. Hopefully, the patch attached to the upstream bug report would fix the problem in ubuntu. ** Affects: poppler (Ubuntu) Importance: Low Status: Triaged -- evince: Bad PDF rendering: invalid font scale https://bugs.launchpad.net/bugs/1412916 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler 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 1412916] Re: evince: Bad PDF rendering: invalid font scale
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Vivid Vervet. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: gnome-keyring (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-keyring (Ubuntu) Status: New => Triaged ** Package changed: gnome-keyring (Ubuntu) => poppler (Ubuntu) ** Bug watch added: LibreOffice Bugzilla #78042 https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78042 ** Also affects: poppler via https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78042 Importance: Unknown Status: Unknown ** Changed in: poppler (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1412916 Title: evince: Bad PDF rendering: invalid font scale Status in Poppler: Unknown Status in poppler package in Ubuntu: Fix Released Bug description: Evince in ubuntu 14.04 (3.10.3-0ubuntu10.1) suffers from this bug: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78042 The test case which is attached to the upstream bug demonstrates the problem with Evince in Ubuntu. Hopefully, the patch attached to the upstream bug report would fix the problem in ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1412916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412916] Re: evince: Bad PDF rendering: invalid font scale
The commited fix was http://cgit.freedesktop.org/poppler/poppler/commit/?id=cbf2652c483d7010fc36191c8b209a57eeec93d8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1412916 Title: evince: Bad PDF rendering: invalid font scale Status in Poppler: Unknown Status in poppler package in Ubuntu: Fix Released Bug description: Evince in ubuntu 14.04 (3.10.3-0ubuntu10.1) suffers from this bug: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78042 The test case which is attached to the upstream bug demonstrates the problem with Evince in Ubuntu. Hopefully, the patch attached to the upstream bug report would fix the problem in ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1412916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373598] Re: apt-get update fails, hash sum mismatches (trusty)
Thanks Bernadette. Switching us.archive.ubuntu.com to de2.archive.ubuntu.com worked for me as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1373598 Title: apt-get update fails, hash sum mismatches (trusty) Status in apt package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: 1. Release: Description: Ubuntu 14.04.1 LTS Release: 14.04 2. not a package. The whole distro is broken. 3. I always expect apt-get update to work, at least with Ubuntu's own repositories. 4. "apt-get update" failed, and later "apt-get dist upgrade" It started with this when doing a normal "apt-get update" W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/source/Sources Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/binary-amd64/Packages Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/universe/binary-i386/Packages Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. When doing a dist-upgrade, I then got this: E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.13.0-36-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-extra-3.13.0-36-generic.postinst line 1025. No apport report written because the error message indicates its a followup error from a previous failure. dpkg: error processing package linux-image-extra-3.13.0-36-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-extra-3.13.0-36-generic; however: Package linux-image-extra-3.13.0-36-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured Setting up linux-headers-3.13.0-36 (3.13.0-36.63) ... Setting up linux-headers-3.13.0-36-generic (3.13.0-36.63) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-36-generic /boot/vmlinuz-3.13.0-36-generic Setting up linux-headers-generic (3.13.0.36.43) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 3.13.0.36.43); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured And later this at the end: Processing triggers for libc-bin (2.19-0ubuntu6.3) ... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.5 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Sep 24 21:57:55 2014 InstallationDate: Installed on 2013-05-09 (503 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to trusty on 2014-05-04 (142 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1373598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408235] Re: Some icons in Dash are too big
** Changed in: ubuntukylin Milestone: vivid-alpha2 => vivid-beta1 -- 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/1408235 Title: Some icons in Dash are too big Status in Ubuntu Kylin: New Status in unity package in Ubuntu: New Bug description: Some icons in Dash are too big, like Updete Manager, Amazon Dash中有些图标太大 Steps: 1. Open Dash 2. Check icons in it -->Failed. Some icons in Dash are too big Configuration: OS: Vivid x64 Daily Build 20150106 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1408235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412916] Re: evince: Bad PDF rendering: invalid font scale
Launchpad has imported 8 comments from the remote bug at
https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78042.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2014-04-28T18:22:15+00:00 Davide Capodaglio wrote:
Created attachment 98133
easyjet boarding pass not rendered correctly
Hello, the attached PDF (easyjet boarding pass) is not correctly rendered under
poppler (evince).
I am using Ubuntu 14.04 amd64, so evince 3.10.3 and poppler 0.24.5.
Evince prints a lot of messages like:
Syntax Warning: font matrix not invertible<0a>
while ghostscript renders the PDF correctly, but prints lots of:
Warning: Invalid 0.0 font scale given for Tf
Warning: /BBox has zero width or height, which is not allowed.
so I suspect the PDF is defective, but poppler should be made more "fault
tolerant" as ghostscript does.
Otherwise, no boarding pass print anymore :-(
I can fix the PDF with
gs -q -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite -sOutputFile=out.pdf in.pdf
Reply at:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1412916/comments/0
On 2014-04-28T18:32:26+00:00 Albert Astals Cid wrote:
Looks good in okular so it must be a cairo backend bug.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1412916/comments/1
On 2014-04-28T19:38:55+00:00 Davide Capodaglio wrote:
(In reply to comment #1)
> Looks good in okular so it must be a cairo backend bug.
Yeah also for me in okular is ok. And no log messages on stdout at all.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1412916/comments/2
On 2014-09-21T11:04:10+00:00 Martin McDowell wrote:
I am seeing the same problem using the Document Viewer 3.10.3 on Ubuntu
14.04 64-bit
Reply at:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1412916/comments/3
On 2014-10-07T11:03:20+00:00 Adrian Johnson wrote:
Created attachment 107478
cairo: don't render text when matrix is not invertable
Reply at:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1412916/comments/4
On 2014-10-07T16:04:29+00:00 Carlos Garcia Campos wrote:
Comment on attachment 107478
cairo: don't render text when matrix is not invertable
Review of attachment 107478:
-
LGTM, thanks!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1412916/comments/5
On 2014-10-07T20:17:20+00:00 Adrian Johnson wrote:
Pushed.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1412916/comments/6
On 2014-10-14T15:40:46+00:00 Neil-uy4g6 wrote:
*** Bug 83155 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1412916/comments/7
** Changed in: poppler
Status: Unknown => Fix Released
** Changed in: poppler
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1412916
Title:
evince: Bad PDF rendering: invalid font scale
Status in Poppler:
Fix Released
Status in poppler package in Ubuntu:
Fix Released
Bug description:
Evince in ubuntu 14.04 (3.10.3-0ubuntu10.1) suffers from this bug:
https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78042
The test case which is attached to the upstream bug demonstrates the
problem with Evince in Ubuntu.
Hopefully, the patch attached to the upstream bug report would fix the
problem in ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1412916/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403464] Re: Left-edge / home does not close Manage Dash
Selene, i agree that what you suggest may be a better behaviour but please report that as a new bug and not as part as this one since the left-edge has never behaved like that and thus is not a consequence of this bug. -- 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/1403464 Title: Left-edge / home does not close Manage Dash Status in the base for Ubuntu mobile products: Confirmed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: In Progress Bug description: The Manage Dash should be closed on Left-edge / home press To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1403464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358294] Re: App .config not removed when app uninstalled
** Changed in: click (Ubuntu) Status: Triaged => In Progress ** Changed in: click (Ubuntu) Assignee: (unassigned) => Michael Vogt (mvo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1358294 Title: App .config not removed when app uninstalled Status in Ubuntu UX bugs: Fix Committed Status in click package in Ubuntu: In Progress Bug description: If an app uses ~/.config/foo (say, uses Qt.labs.settings), and the user uninstalls the app, ~/.config/foo is not removed. It should be deleted when the app is uninstalled. Using latest utopic on the phone. - Desired resolution: - When a user deletes an app, 100% of files associated with the app should be deleted. - A warning notification should be displayed when a user goes to delete an app informing them that this action will also delete any data they have stored inside the app. This notification should give the options of cancelling or proceeding with the action. - Users should not be allowed to delete the key apps that ship with the phone. These key apps are defined as: Dialler, Address book, Messaging, Browser, Camera, Music player The above will give the user a simple easy to understand mental model while simultaneously protecting the user from deleting important content within the default apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1358294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413121] [NEW] MainView is missing an API to lock to landscape
Public bug reported: The MainView offers an api to lock the app to landscape. For games however, it's common to require landscape mode. This is not supported and causes most of the games to show a notice like "Please rotate the device" when in portrait mode which looks not very professional. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1413121 Title: MainView is missing an API to lock to landscape Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: The MainView offers an api to lock the app to landscape. For games however, it's common to require landscape mode. This is not supported and causes most of the games to show a notice like "Please rotate the device" when in portrait mode which looks not very professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1413121/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Branch linked: lp:~ci-train-bot/unity8/ubuntu-rtm-14.09-proposed -- 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 the base for Ubuntu mobile products: Confirmed Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: Triaged 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/canonical-devices-system-image/+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 1403464] Re: Left-edge / home does not close Manage Dash
** Branch linked: lp:~ci-train-bot/unity8/ubuntu-rtm-14.09-proposed -- 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/1403464 Title: Left-edge / home does not close Manage Dash Status in the base for Ubuntu mobile products: Confirmed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: In Progress Bug description: The Manage Dash should be closed on Left-edge / home press To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1403464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368677] Re: [Apps switcher] Move commit points toward right to make spread more accessible
** Branch linked: lp:~ci-train-bot/unity8/ubuntu-rtm-14.09-proposed -- 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/1368677 Title: [Apps switcher] Move commit points toward right to make spread more accessible Status in the base for Ubuntu mobile products: Confirmed 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: In our user testing users often failed to access the spread via long right edge swipe. We want to make spread a bit more accessible by moving second phase commit point few grid units to right. Not to affect the overall functionality and experience the right thing to do is to make first phase reveal phase shorter which then automatically moves both first phase and second phase commit point same amount towards right. See the spec for detailed descriptions of different gesture phases: https://docs.google.com/a/canonical.com/document/d/1FC_- 5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit# Desired solution: Shorten the first phase reveal by 4 gu Since the 4gu value is just an estimate and might need refining the result should be approved with design team before committing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368677/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368668] Re: [Apps switcher] Visual feedback of user's finger movement needed throughout the gesture
** Branch linked: lp:~ci-train-bot/unity8/ubuntu-rtm-14.09-proposed -- 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/1368668 Title: [Apps switcher] Visual feedback of user's finger movement needed throughout the gesture Status in the base for Ubuntu mobile products: Confirmed 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: Right edge compound gesture has two phases. During the second phase all the recent applications stack together in to the apps spread. There is a second phase commit threshold value after which this stacking happens. Currently when this commit threshold has been exceeded user loses control over the gesture. There is no way to go back and the UI doesn't react to further finger movement to left. We want user to be in control also after the second commit line. RIght edge gesture progress is explained and broken into pieces in this spec: https://docs.google.com/a/canonical.com/document/d/1FC_-5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit# There is already a bug about reversibility (movement back to right) after second commit line (#1355284). So this bug is to fix the non- responsiveness after second phase commit line when user moves finger towards left edge. Steps to repro: 1. Start right edge swipe 2. keep finger pressed and drag to left until you reach the point when apps spread is formed 3. keep still finger pressed and move finger towards left Current behaviour: No visual feedback Expected behaviour: Applications should start moving to left and stack the way they do when they're dragged to left in normal spread use case To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368668/+subscriptions -- Mailing list: https://launchpad.net/~touch-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:~ci-train-bot/unity8/ubuntu-rtm-14.09-proposed -- 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 the base for Ubuntu mobile products: In Progress 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: 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/canonical-devices-system-image/+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 1409555] Re: drop extras.ubuntu.com
** Tags added: kubuntu ** Changed in: kubuntu-meta (Ubuntu) Milestone: None => ubuntu-15.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1409555 Title: drop extras.ubuntu.com Status in Ubuntu Software Center: New Status in apt-setup package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Fix Released Status in lubuntu-meta package in Ubuntu: Fix Released Status in software-center package in Ubuntu: Fix Released Status in ubuntu-gnome-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntukylin-meta package in Ubuntu: Fix Released Status in ubuntustudio-meta package in Ubuntu: Fix Released Status in xubuntu-meta package in Ubuntu: Fix Released Bug description: drop extras.ubuntu.com No longer in use. https://lists.ubuntu.com/archives/technical- board/2015-January/002063.html To manage notifications about this bug go to: https://bugs.launchpad.net/software-center/+bug/1409555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1232130] Re: Uninstalling an app doesn't stop it
** Branch linked: lp:~mvo/click/lp1232130-kill-on-remove-2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1232130 Title: Uninstalling an app doesn't stop it Status in click package in Ubuntu: In Progress Status in ubuntu-touch-meta package in Ubuntu: Fix Released Bug description: Hi, Launch an installed app, uninstall it. Not only is it still listed in the list of installed apps (bug #1232129), it's also still in the running app lists, and if you press on the installed app icon or slide right, you get back to the running app. I think any running instance of this app should be killed along the removal. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1232130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393698] Re: Cross qmake to the chroots
** Branch linked: lp:click/devel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1393698 Title: Cross qmake to the chroots Status in click package in Ubuntu: New Bug description: The https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.3.2 +dfsg-4ubuntu3 release of the QtBase module provides the new qt5 -qmake-cross-armhf package and so the /usr/bin/qt5-qmake-cross-armhf binary. This qmake binary is made for x86 chroots with armhf development target. This change is to enable the build of qmake project type in the click chroot. In order to support qmake projects we need this package installed in the click chroot. The qt5-qmake-cross-armhf is not a multiarch package, it is made exclusively for i386 and amd64 targets. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1393698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403464] Re: Left-edge / home does not close Manage Dash
This bug was fixed in the package unity8 - 8.02+15.04.20150120~rtm- 0ubuntu1 --- unity8 (8.02+15.04.20150120~rtm-0ubuntu1) 14.09; urgency=medium [ Albert Astals ] * Fix going to scopes when the Manage Dash is open (LP: #1403464) [ Josh Arenson ] * Create a PhysicalKeyMapper to handle all physical/hardware keys (LP: #1390393) [ Michael Zanetti ] * make spread reversible (LP: #1368668, #1355284, #1368677) [ Nick Dedekind ] * Unhook Lights interface from indicator widgets -- Ubuntu daily releaseTue, 20 Jan 2015 11:18:21 + ** Changed in: unity8 (Ubuntu RTM) 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/1403464 Title: Left-edge / home does not close Manage Dash Status in the base for Ubuntu mobile products: Confirmed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: The Manage Dash should be closed on Left-edge / home press To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1403464/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
This bug was fixed in the package unity8 - 8.02+15.04.20150120~rtm- 0ubuntu1 --- unity8 (8.02+15.04.20150120~rtm-0ubuntu1) 14.09; urgency=medium [ Albert Astals ] * Fix going to scopes when the Manage Dash is open (LP: #1403464) [ Josh Arenson ] * Create a PhysicalKeyMapper to handle all physical/hardware keys (LP: #1390393) [ Michael Zanetti ] * make spread reversible (LP: #1368668, #1355284, #1368677) [ Nick Dedekind ] * Unhook Lights interface from indicator widgets -- Ubuntu daily releaseTue, 20 Jan 2015 11:18:21 + ** Changed in: unity8 (Ubuntu RTM) Status: Triaged => 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/1390393 Title: It's too easy to trigger a volume notification when taking a screenshot Status in the base for Ubuntu mobile products: Confirmed Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: Fix Released 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/canonical-devices-system-image/+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 1368668] Re: [Apps switcher] Visual feedback of user's finger movement needed throughout the gesture
This bug was fixed in the package unity8 - 8.02+15.04.20150120~rtm- 0ubuntu1 --- unity8 (8.02+15.04.20150120~rtm-0ubuntu1) 14.09; urgency=medium [ Albert Astals ] * Fix going to scopes when the Manage Dash is open (LP: #1403464) [ Josh Arenson ] * Create a PhysicalKeyMapper to handle all physical/hardware keys (LP: #1390393) [ Michael Zanetti ] * make spread reversible (LP: #1368668, #1355284, #1368677) [ Nick Dedekind ] * Unhook Lights interface from indicator widgets -- Ubuntu daily releaseTue, 20 Jan 2015 11:18:21 + ** Changed in: unity8 (Ubuntu RTM) 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/1368668 Title: [Apps switcher] Visual feedback of user's finger movement needed throughout the gesture Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: Right edge compound gesture has two phases. During the second phase all the recent applications stack together in to the apps spread. There is a second phase commit threshold value after which this stacking happens. Currently when this commit threshold has been exceeded user loses control over the gesture. There is no way to go back and the UI doesn't react to further finger movement to left. We want user to be in control also after the second commit line. RIght edge gesture progress is explained and broken into pieces in this spec: https://docs.google.com/a/canonical.com/document/d/1FC_-5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit# There is already a bug about reversibility (movement back to right) after second commit line (#1355284). So this bug is to fix the non- responsiveness after second phase commit line when user moves finger towards left edge. Steps to repro: 1. Start right edge swipe 2. keep finger pressed and drag to left until you reach the point when apps spread is formed 3. keep still finger pressed and move finger towards left Current behaviour: No visual feedback Expected behaviour: Applications should start moving to left and stack the way they do when they're dragged to left in normal spread use case To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368668/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368677] Re: [Apps switcher] Move commit points toward right to make spread more accessible
This bug was fixed in the package unity8 - 8.02+15.04.20150120~rtm- 0ubuntu1 --- unity8 (8.02+15.04.20150120~rtm-0ubuntu1) 14.09; urgency=medium [ Albert Astals ] * Fix going to scopes when the Manage Dash is open (LP: #1403464) [ Josh Arenson ] * Create a PhysicalKeyMapper to handle all physical/hardware keys (LP: #1390393) [ Michael Zanetti ] * make spread reversible (LP: #1368668, #1355284, #1368677) [ Nick Dedekind ] * Unhook Lights interface from indicator widgets -- Ubuntu daily releaseTue, 20 Jan 2015 11:18:21 + ** Changed in: unity8 (Ubuntu RTM) 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/1368677 Title: [Apps switcher] Move commit points toward right to make spread more accessible Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: In our user testing users often failed to access the spread via long right edge swipe. We want to make spread a bit more accessible by moving second phase commit point few grid units to right. Not to affect the overall functionality and experience the right thing to do is to make first phase reveal phase shorter which then automatically moves both first phase and second phase commit point same amount towards right. See the spec for detailed descriptions of different gesture phases: https://docs.google.com/a/canonical.com/document/d/1FC_- 5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit# Desired solution: Shorten the first phase reveal by 4 gu Since the 4gu value is just an estimate and might need refining the result should be approved with design team before committing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368677/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
This bug was fixed in the package unity8 - 8.02+15.04.20150120~rtm- 0ubuntu1 --- unity8 (8.02+15.04.20150120~rtm-0ubuntu1) 14.09; urgency=medium [ Albert Astals ] * Fix going to scopes when the Manage Dash is open (LP: #1403464) [ Josh Arenson ] * Create a PhysicalKeyMapper to handle all physical/hardware keys (LP: #1390393) [ Michael Zanetti ] * make spread reversible (LP: #1368668, #1355284, #1368677) [ Nick Dedekind ] * Unhook Lights interface from indicator widgets -- Ubuntu daily releaseTue, 20 Jan 2015 11:18:21 + ** Changed in: unity8 (Ubuntu RTM) 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/1355284 Title: Switching swipe directions should reverse app spread Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released 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/canonical-devices-system-image/+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 821000] Re: setuptools and distribute don't prepend PYTHONPATH to sys.path
** Also affects: python-setuptools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-setuptools (Ubuntu)
Assignee: (unassigned) => Barry Warsaw (barry)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-setuptools in
Ubuntu.
https://bugs.launchpad.net/bugs/821000
Title:
setuptools and distribute don't prepend PYTHONPATH to sys.path
Status in tools to distribute python packages:
New
Status in python-setuptools:
Unknown
Status in Tahoe, the Lovely Accessible File System:
New
Status in distribute package in Ubuntu:
Confirmed
Status in python-setuptools package in Ubuntu:
New
Bug description:
This is a long-standing issue in setuptools, which was copied into
distribute when distribute forked. There exist patches the attempt to
fix the issue offered against both setuptools and distribute. There
are tickets in the setuptools issue tracker, distribute issue tracker,
and the Tahoe-LAFS issue tracker (where we maintain a fork of
setuptools in order to fix this among other outstanding bugs).
The crux of the problem is that the Python documentation says:
"The PYTHONPATH variable can be set to a list of paths that will be
added to the beginning of sys.path."
http://docs.python.org/install/index.html#modifying-python-s-search-
path
This is true with standard distutils, false with setuptools, false
with distribute, and true if you apply the following patch to either
setuptools or distribute:
Index: setuptools/command/easy_install.py
===
--- setuptools/command/easy_install.py (revision 560)
+++ setuptools/command/easy_install.py (revision 562)
@@ -1365,5 +1365,5 @@
"import sys; new=sys.path[sys.__plen:];"
" del sys.path[sys.__plen:];"
-" p=getattr(sys,'__egginsert',0); sys.path[p:p]=new;"
+"
p=getattr(sys,'__egginsert',len(os.environ.get('PYTHONPATH','').split(os.pathsep)));
sys.path[p:p]=new;"
" sys.__egginsert = p+len(new)\n"
) % data
To manage notifications about this bug go to:
https://bugs.launchpad.net/distribute/+bug/821000/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1373221] Re: guvcview crashed with SIGSEGV in get_ctrl_by_id()
Hi,
please upgrade to version 2.0.1, you can use one of the following ppa:
stable: https://launchpad.net/~pj-assis/+archive/ubuntu/ppa
testing (latest git): https://launchpad.net/~pj-
assis/+archive/ubuntu/testing
Regards,
Paulo
2015-01-21 4:37 GMT+00:00 vedavata :
> The same problem. :-(
>
> uname -a
> Linux DELL-E6430 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC
> 2015 x86_64 x86_64 x86_64 GNU/Linux
>
> Ubuntu 14.10 (Utopic Unicorn)
>
>
> tosik@DELL-E6430:~$ guvcview
> guvcview 1.7.3
> file guvcview_video.mkv has extension type 1
> file guvcview_image.jpg has extension type 0
>
> ** (guvcview:24741): WARNING **: Couldn't connect to accessibility bus:
> Failed to connect to socket /tmp/dbus-Grv3g4WwxK: Connection refused
> file guvcview_image.jpg has extension type 0
> Video file suffix detected: 0
> Image file suffix detected: 0
> ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
> ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
> ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
> ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map
> bt_audio_service_open: connect() failed: Connection refused (111)
> Cannot connect to server socket err = No such file or directory
> Cannot connect to server request channel
> jack server is not running or cannot be started
> checking format: JPEG
> Format unavailable: JPEG
> Init v4L2 failed !!
> Init video returned -2
> trying minimum setup ...
> format: YUYV
> resolution: 640 x 480
> framerate: 1/30
> video device: /dev/video0
> vid:046d
> pid:0825
> driver:uvcvideo
> device doesn't seem to support uvc H264 (0)
> mapping control for Pan (relative)
> UVCIOC_CTRL_MAP - Error: No such file or directory
> mapping control for Tilt (relative)
> UVCIOC_CTRL_MAP - Error: No such file or directory
> mapping control for Pan Reset
> UVCIOC_CTRL_MAP - Error: No such file or directory
> mapping control for Tilt Reset
> UVCIOC_CTRL_MAP - Error: No such file or directory
> mapping control for Focus (absolute)
> UVCIOC_CTRL_MAP - Error: No such file or directory
> mapping control for LED1 Mode
> UVCIOC_CTRL_MAP - Error: No such file or directory
> mapping control for LED1 Frequency
> UVCIOC_CTRL_MAP - Error: No such file or directory
> mapping control for Disable video processing
> UVCIOC_CTRL_MAP - Error: No such file or directory
> mapping control for Raw bits per pixel
> UVCIOC_CTRL_MAP - Error: No such file or directory
> Init. UVC Camera (046d:0825) (location: usb-:00:1d.0-1.7.2)
> { pixelformat = 'YUYV', description = 'YUV 4:2:2 (YUYV)' }
> { pixelformat = 'MJPG', description = 'MJPEG' }
> { pixelformat = 'RGB3', description = 'RGB3' }
> { pixelformat = 'BGR3', description = 'BGR3' }
> { pixelformat = 'YU12', description = 'YU12' }
> { pixelformat = 'YV12', description = 'YV12' }
> checking muxed H264 format support
> device doesn't seem to support uvc H264 (0)
> checking format: YUYV
> fps is set to 1/30
> drawing controls
>
> Segmentation fault (core dumped)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1373221
>
> Title:
> guvcview crashed with SIGSEGV in get_ctrl_by_id()
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/guvcview/+bug/1373221/+subscriptions
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to v4l-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1373221
Title:
guvcview crashed with SIGSEGV in get_ctrl_by_id()
Status in GTK uvc viewer:
Confirmed
Status in One Hundred Papercuts:
Triaged
Status in libv4l v4l-utils:
Confirmed
Status in guvcview package in Ubuntu:
Triaged
Status in v4l-utils package in Ubuntu:
Triaged
Bug description:
HOW TO REPRODUCE:
- Launch guvcview
EXPECTED BEHAVIOUR:
- The application to start normally.
REAL BEHAVIOUR:
- The application crashes.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: guvcview 1.7.3-1.1build2
ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
Uname: Linux 3.16.0-17-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Sep 24 06:35:20 2014
ExecutablePath: /usr/bin/guvcview
InstallationDate: Installed on 2013-05-21 (490 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcCmdline: guvcview
SegvAnalysis:
Segfault happened at: 0x42d970: mov0x0,%eax
PC (0x0042d970) ok
source "0x0" (0x) not located in a known VMA region (needed readable
region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: guvcview
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
__libc_start_main (main=0x409920, argc=1, argv=0x7fff32c34208,
init=, fini=, rtld_fini=,
stack_end=0x7fff32c341f8) at libc-start.c:287
T
[Touch-packages] [Bug 1411201] Re: Scope framework seems to be caching location
** Branch linked: lp:ubuntu/vivid-proposed/unity-scopes-shell -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1411201 Title: Scope framework seems to be caching location Status in the base for Ubuntu mobile products: In Progress Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu RTM: New Bug description: I have seen two different symptoms , might be same or different bug. First, Scopes seem to be getting only geoip location even when using Nokia Here web app I get an accurate fix. Second, Scopes seem to be caching an older location. Example: I used yelp in Barcelona airport, and gave me accurate results on restaurants in the terminal. I then switch airplane mode on, and got on a plane. When I landed in London, and turn airplane mode off, I could not get scopes (any) to provide information for london, even though I was able to get accurate location from Nokia Maps. I tried over one hour, eventually I rebooted the phone and location started working again in scopes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411201] Re: Scope framework seems to be caching location
This bug was fixed in the package unity-scopes-shell - 0.5.4+15.04.20150120-0ubuntu1 --- unity-scopes-shell (0.5.4+15.04.20150120-0ubuntu1) vivid; urgency=low [ Pete Woods ] * Remove distance-based filtering and refresh GeoIP data every minute (LP: #1411201) -- Ubuntu daily releaseTue, 20 Jan 2015 09:16:15 + ** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1411201 Title: Scope framework seems to be caching location Status in the base for Ubuntu mobile products: In Progress Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu RTM: New Bug description: I have seen two different symptoms , might be same or different bug. First, Scopes seem to be getting only geoip location even when using Nokia Here web app I get an accurate fix. Second, Scopes seem to be caching an older location. Example: I used yelp in Barcelona airport, and gave me accurate results on restaurants in the terminal. I then switch airplane mode on, and got on a plane. When I landed in London, and turn airplane mode off, I could not get scopes (any) to provide information for london, even though I was able to get accurate location from Nokia Maps. I tried over one hour, eventually I rebooted the phone and location started working again in scopes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413121] Re: MainView is missing an API to lock to landscape
** Description changed: - The MainView offers an api to lock the app to landscape. For games + The MainView offers an api to lock the app to portrait. For games however, it's common to require landscape mode. This is not supported and causes most of the games to show a notice like "Please rotate the device" when in portrait mode which looks not very professional. -- 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/1413121 Title: MainView is missing an API to lock to landscape Status in Qt integration with the Mir display server: Confirmed Status in QT Ubuntu: New Status in qtmir package in Ubuntu: New Status in qtubuntu package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: The MainView offers an api to lock the app to portrait. For games however, it's common to require landscape mode. This is not supported and causes most of the games to show a notice like "Please rotate the device" when in portrait mode which looks not very professional. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1413121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413121] Re: MainView is missing an API to lock to landscape
Mir does provide an api for client to specify this to shell. But nothing is using it yet ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Also affects: qtubuntu (Ubuntu) Importance: Undecided Status: New ** Also affects: qtubuntu Importance: Undecided Status: New ** Also affects: qtmir Importance: Undecided Status: New ** Changed in: qtmir Status: New => Confirmed ** 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 ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1413121 Title: MainView is missing an API to lock to landscape Status in Qt integration with the Mir display server: Confirmed Status in QT Ubuntu: New Status in qtmir package in Ubuntu: New Status in qtubuntu package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: The MainView offers an api to lock the app to portrait. For games however, it's common to require landscape mode. This is not supported and causes most of the games to show a notice like "Please rotate the device" when in portrait mode which looks not very professional. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1413121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409995] Re: Queries to remote scopes time out
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1409995
Title:
Queries to remote scopes time out
Status in the base for Ubuntu mobile products:
New
Status in unity-scopes-api package in Ubuntu:
In Progress
Bug description:
I'm seeing this on Mako, image #63, devel-proposed.
Periodically, the music scope fails to return any results, leaving a
blank screen.
Looking through the log files, I'm seeing tons of messages such as
this:
[2015-01-13 01:33:27.056262] INFO: SSRegistry:
SmartScopesClient.get_remote_scopes(): GET
https://dash.ubuntu.com/smartscopes/v2/remote-scopes?locale=en_US
[2015-01-13 01:33:27.057239] ERROR: SSRegistry:
SmartScopesClient.get_remote_scopes(): failed to read /custom/partner-id:
unity::FileException: cannot open "/custom/partner-id": No such file or
directory (errno = 2)
[2015-01-13 01:33:46.996259] ERROR: SSRegistry:
SmartScopesClient.get_remote_scopes(): Failed to retrieve remote scopes from
uri: https://dash.ubuntu.com/smartscopes/v2/remote-scopes:
unity::ResourceException: Request timed out:
https://dash.ubuntu.com/smartscopes/v2/remote-scopes?locale=en_US
The request times out even though the remote end works fine. (Easy to
confirm by pasting the same URL into the browser.)
As an aside, the error about /custom/partner-id isn't an error: if the
file doesn't exist (errno = 2), we should say nothing. That'll get rid
of a lot of noise.
In addition, when I run a query, I see all queries to remote scopes
fail (see attached trace).
I'm not familiar with the code. Looking through, I noticed this:
HttpResponseHandle::SPtr response =
http_client_->get(remote_scopes_uri.str(), [&response_str](std::string const&
replyLine) {
response_str += replyLine; // accumulate all reply lines
}, headers);
response->get();
Following this through, it appears that response_str is being appended
to from a different thread without any lock. That looks like it's
wrong to me. But that doesn't explain the timeout exception that is
thrown from response->get().
I suspect a race condition somewhere because, occasionally, I get a
query that works.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1409995/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1312836] Re: [systemd] dh_installinit does not create /etc/rc*.d/S??foo if there is an /etc/init/foo.conf
Luis, that seems to be a different bug/cause now. To confirm, what does that show right after a clean boot: sudo systemctl status -l networking (Please confirm that you still don't have /run/network right after boot). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1312836 Title: [systemd] dh_installinit does not create /etc/rc*.d/S??foo if there is an /etc/init/foo.conf Status in debhelper package in Ubuntu: Fix Released Status in ifupdown package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Fix Released Bug description: I had no networking when I booted up with systemd just now. laney@raleigh> cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN laney@raleigh> ifconfig loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:572 errors:0 dropped:0 overruns:0 frame:0 TX packets:572 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:46364 (46.3 KB) TX bytes:46364 (46.3 KB) laney@raleigh> more /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual auto br0 iface br0 inet dhcp bridge_ports eth0 bridge_stp off bridge_fd 0 bridge_maxwait 0 laney@raleigh> sudo ifup eth0 br0 ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory Then copying from /etc/init/networking.conf's pre-start laney@raleigh> sudo mkdir -p /run/network laney@raleigh> sudo ifup -a Internet Systems Consortium DHCP Client 4.2.4 Copyright 2004-2012 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/br0/30:85:a9:9d:63:f6 Sending on LPF/br0/30:85:a9:9d:63:f6 Sending on Socket/fallback DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 3 (xid=0x1b02ce25) DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 7 (xid=0x1b02ce25) DHCPREQUEST of 192.168.1.136 on br0 to 255.255.255.255 port 67 (xid=0x1b02ce25) DHCPOFFER of 192.168.1.136 from 192.168.1.1 DHCPACK of 192.168.1.136 from 192.168.1.1 bound to 192.168.1.136 -- renewal in 39350 seconds. laney@raleigh> cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.1.1 I feel like there's probably an existing systemd-ish way of doing this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ifupdown 0.7.47.2ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 25 18:01:25 2014 InstallationDate: Installed on 2012-10-07 (564 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: ifupdown UpgradeStatus: Upgraded to trusty on 2013-05-07 (353 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1312836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401916] Re: Configuration of screens positions and geometry
Do we want Mir to have an ecosystem of configuration tools around it? Because this won't happen if every shell has to implement their own configuration save/restore/change system. -- 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/1401916 Title: Configuration of screens positions and geometry Status in Mir: Fix Released Status in Qt integration with the Mir display server: New Status in Ubuntu UX bugs: New Status in unity8 package in Ubuntu: Confirmed Bug description: Under unity7/xorg it's possible to configure the position of the screens and their geometry, that includes - resolution of each screen - rotation possible - relative position (external on top of laptop, or on the right) - definition of a "primary" monitor (the one containing the launcher if you decide to have that UI element only on one screen) - etc Under unity7 the configuration is applied on login by unity-settings- daemon using xrandr. In the new world unity8 should probably be the one setting up the configuration at start It would be useful to have input from design as well, on what should happen when connecting an unity8 powered device to an external screen. Should it mirror by default? Do we need settings control to configure what to do, ... To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1401916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413139] Re: [regression] mir_demo_client_fingerpaint doesn't paint anything any more (with the mouse)
** Changed in: mir Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mir Status: Triaged => In Progress ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Status: New => Triaged ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Branch linked: lp:~vanvugt/mir/fix-1413139 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1413139 Title: [regression] mir_demo_client_fingerpaint doesn't paint anything any more (with the mouse) Status in Mir: In Progress Status in mir package in Ubuntu: Triaged Bug description: [regression] mir_demo_client_fingerpaint doesn't paint anything any more To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1413139/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Changed in: unity8 (Ubuntu RTM) Status: Fix Released => 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/1390393 Title: It's too easy to trigger a volume notification when taking a screenshot Status in the base for Ubuntu mobile products: Confirmed Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: In Progress 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/canonical-devices-system-image/+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 1385331] Re: Notification LED stays on when no messages in notification center
** Changed in: unity8 (Ubuntu RTM) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qmenumodel in Ubuntu. https://bugs.launchpad.net/bugs/1385331 Title: Notification LED stays on when no messages in notification center Status in the base for Ubuntu mobile products: Confirmed Status in qmenumodel package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in qmenumodel package in Ubuntu RTM: In Progress Status in unity8 package in Ubuntu RTM: Fix Released Bug description: Observed the notification LED staying on even though there were no notifications in the indicators and the notification icon was greyed out. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1385331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408323] Re: Phone reboots when /home is full
As of image 72 i'm getting reboots ** Summary changed: - Doesn't work when /home is full + Phone reboots when /home is full -- 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/1408323 Title: Phone reboots when /home is full Status in unity8 package in Ubuntu: New Bug description: I happened to fill my /home to 100% in my Nexus4 under vivid. At that point the screen locker shows up but you can not unlock it (there seems to be no animation) Also the same happens with the indicators bar, and the indicators are empty. It is my undestandin that it shouldn't matter how much you fill /home that the basic functions of the phone should still work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408323] Re: Phone reboots when /home is full
lbert@albert-VirtualBox:~$ phablet-shell phablet@ubuntu-phablet:~$ df -h Filesystem Size Used Avail Use% Mounted on /dev/loop0 2.0G 1.4G 502M 74% / udev916M 4.0K 916M 1% /dev tmpfs 184M 672K 183M 1% /run /dev/mmcblk0p23 13G 13G 0 100% /home /dev/loop1 107M 105M 1.5M 99% /lib/modules none4.0K 0 4.0K 0% /android tmpfs 918M 4.0K 918M 1% /etc/fstab /dev/disk/by-partlabel/cache552M 11M 542M 2% /android/cache /dev/disk/by-partlabel/persist 16M 4.2M 12M 27% /android/persist /dev/disk/by-partlabel/modem 64M 54M 11M 84% /android/firmware none4.0K 0 4.0K 0% /sys/fs/cgroup tmpfs 918M 40K 918M 1% /tmp none5.0M 0 5.0M 0% /run/lock none918M 16K 918M 1% /run/shm none100M 0 100M 0% /run/user tmpfs 918M 0 918M 0% /media tmpfs 918M 0 918M 0% /var/lib/sudo tmpfs 184M 28K 184M 1% /run/user/32011 tmpfs 184M 0 184M 0% /run/user/0 Broadcast message from root@ubuntu-phablet (unknown) at 10:45 ... The system is going down for reboot NOW! Connection to localhost closed by remote host. Connection to localhost closed. -- 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/1408323 Title: Phone reboots when /home is full Status in unity8 package in Ubuntu: New Bug description: I happened to fill my /home to 100% in my Nexus4 under vivid. At that point the screen locker shows up but you can not unlock it (there seems to be no animation) Also the same happens with the indicators bar, and the indicators are empty. It is my undestandin that it shouldn't matter how much you fill /home that the basic functions of the phone should still work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307559] Re: Window decorations not drawn on external monitor
I have similair issues with a mac book 13" connected to dell u2410 monitor using VGA thunderbold connector -- 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/1307559 Title: Window decorations not drawn on external monitor Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Window decorations (close / minimize / maximize buttons) do not draw on the external monitor on a laptop with external display. Windows on the laptop display are not affected. UI scale on the built-in display is 1.25; it's 1.0 on the external display. I am not sure if this is relevant. To reproduce: 1) Plug in an external monitor to a laptop; ensure that it is running in extended display mode 2) Launch an application such as the terminal 3) The terminal launches on the laptop's built-in display. Observe the window decorations draw as expected 4) Drag the terminal window to the second display Expected results; The terminal window is drawn on the extended display Actual results: The terminal window is drawn on the extended display but the close, minimize, and maximize buttons are missing. The problem happens on windows from all applications I've tried (firefox, terminal, emacs, thunderbird) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 14 10:56:46 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.13.0-23-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-23-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (60 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 14 08:54:29 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1307559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1408323] Re: Weidness when /home is full
Still image 72, after i deleted some stuff and added some other stuff to get back to 100% the reboots are gone and i'm back to animations not working. ** Summary changed: - Phone reboots when /home is full + Weidness when /home is full ** Summary changed: - Weidness when /home is full + Weirdness when /home is full -- 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/1408323 Title: Weirdness when /home is full Status in unity8 package in Ubuntu: New Bug description: I happened to fill my /home to 100% in my Nexus4 under vivid. At that point the screen locker shows up but you can not unlock it (there seems to be no animation) Also the same happens with the indicators bar, and the indicators are empty. It is my undestandin that it shouldn't matter how much you fill /home that the basic functions of the phone should still work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413159] [NEW] kscreenlock incompatible with CJK input
Public bug reported: If KDE screen is locked with CJK input system active, password input is no longer possible, since there is no way to change the input method (default keyboard shortcut would be ctrl + space) from a locked screen. Hence a password named "password" would then become "ぱっすぉｒｄ". And since these two strings obviously do jot match, login is no longer possible. ubuntu 14.04 LTS ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1413159 Title: kscreenlock incompatible with CJK input Status in qt4-x11 package in Ubuntu: New Bug description: If KDE screen is locked with CJK input system active, password input is no longer possible, since there is no way to change the input method (default keyboard shortcut would be ctrl + space) from a locked screen. Hence a password named "password" would then become "ぱっすぉｒｄ". And since these two strings obviously do jot match, login is no longer possible. ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1413159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408644] Re: App namespace move to appname.devname
Bug 1412777 needs to be coordinated with this as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1408644 Title: App namespace move to appname.devname Status in tools to review click packages: Fix Released Status in Developer registration portal: Fix Released Status in Ubuntu App Developer site: Triaged Status in click package in Ubuntu: Invalid Status in qtcreator-plugin-ubuntu package in Ubuntu: Fix Released Bug description: Soon app namespaces will be appname.devname plus official apps which will be just appname . The old reverse domain namespaces (com.ubuntu.developer.<...>) will stay around for a while for old apps. This bug tracks the effort of moving our infrastructure, docs and tools over. To manage notifications about this bug go to: https://bugs.launchpad.net/click-reviewers-tools/+bug/1408644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408323] Re: Weirdness when /home is full
You can see the video of the weirdness when it doesn't reboot at http://www.youtube.com/watch?v=x3CEm6eh7gQ -- 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/1408323 Title: Weirdness when /home is full Status in unity8 package in Ubuntu: New Bug description: I happened to fill my /home to 100% in my Nexus4 under vivid. At that point the screen locker shows up but you can not unlock it (there seems to be no animation) Also the same happens with the indicators bar, and the indicators are empty. It is my undestandin that it shouldn't matter how much you fill /home that the basic functions of the phone should still work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413121] Re: MainView is missing an API to lock to landscape
Also, I always lock my phone's rotation so that it's always portrait only. A "lock to landscape" API for a game should override this, for that game only. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1413121 Title: MainView is missing an API to lock to landscape Status in Qt integration with the Mir display server: Confirmed Status in QT Ubuntu: New Status in qtmir package in Ubuntu: New Status in qtubuntu package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: The MainView offers an api to lock the app to portrait. For games however, it's common to require landscape mode. This is not supported and causes most of the games to show a notice like "Please rotate the device" when in portrait mode which looks not very professional. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1413121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368688] Re: Inconsistence between /etc/init and /etc/init.d files
# Workaround:
dpkg-divert --divert /etc/init.d/isc-dhcp-server.disabled --rename
/etc/init.d/isc-dhcp-server
ln -s /lib/init/upstart-job /etc/init.d/isc-dhcp-server
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1368688
Title:
Inconsistence between /etc/init and /etc/init.d files
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
After upgrade Ubuntu server from 12.04 LTS to 14.04 LTS (with
do-release-upgrade) I found a strange behavior in /var/log/messages from
isc-dhcp-server. It had doubled DHCPREQUESTS/OFFERS/ACKs... It was like:
~~
dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
~~
Futher investigation show that there was actually two dhcpd processes:
~~
dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcp-server/dhcpd.pid
/usr/sbin/dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcpd.pid
~~
The first one was executed from "/etc/init/isc-dhcp-server.conf" and second
from "/etc/init.d/isc-dhcp-server".
Looking inside "init/isc-dhcp-server.conf" I found:
~~
respawn
script
. /etc/default/isc-dhcp-server
..
exec dhcpd -user dhcpd -group dhcpd -f -q -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES
~~
As you can see path to PID file is hardcoded.
But in "init.d/isc-dhcp-server" startup script:
~~
# try to read pid file name from config file, with fallback to
/var/run/dhcpd.pid
if [ -z "$DHCPD_PID" ]; then
DHCPD_PID=$(sed -n -e 's/^[ \t]*pid-file-name[ \t]*"(.*)"[
\t]*;.*$/\1/p' < "$DHCPD_CONF" 2>/dev/null | head -n 1)
fi
DHCPD_PID="${DHCPD_PID:-/var/run/dhcpd.pid}"
..
case "$1" in
start)
test_config
log_daemon_msg "Starting $DESC" "$NAME"
start-stop-daemon --start --quiet --pidfile "$DHCPD_PID" \
--exec /usr/sbin/dhcpd -- \
-q $OPTIONS -cf "$DHCPD_CONF" -pf "$DHCPD_PID"
$INTERFACES
~~
So obivous is to either change init script to NOT use hardcoded path to PID
file and use $DHCP_PID (from /etc/default/isc-dhcp-server, which is sourced
inside this script), or at least change it to "default" one: /var/run/dhcpd.pid
OR
change init.d script to fallback to "/run/dhcp-server/dhcpd.pid"
instead of "/var/run/dhcpd.pid"
P.S. /var/run is a link to /run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1368688/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1355284] Re: Switching swipe directions should reverse app spread
Thanks all! -- 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 the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released 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/canonical-devices-system-image/+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 1408323] Re: Weirdness when /home is full
Here's a strace of when not full, i can only find a open with write for zeitgeist stuff (i didn't know we used zeitgeist) but i somehow doubt that is making it fail to animate or reboot ** Attachment added: "Strace when not full" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408323/+attachment/4302919/+files/strace_out_not_full -- 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/1408323 Title: Weirdness when /home is full Status in unity8 package in Ubuntu: New Bug description: I happened to fill my /home to 100% in my Nexus4 under vivid. At that point the screen locker shows up but you can not unlock it (there seems to be no animation) Also the same happens with the indicators bar, and the indicators are empty. It is my undestandin that it shouldn't matter how much you fill /home that the basic functions of the phone should still work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410365] Re: Phone UI fails to indicate when certain network services are unavailable
Hi, We have activated the carrier's service of call conference and try to merge calls. When we try it the one which is on hold is hung off. Is this not implemented yet? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1410365 Title: Phone UI fails to indicate when certain network services are unavailable Status in the base for Ubuntu mobile products: New Status in Dialer app for Ubuntu Touch: In Progress Status in Telepathy Ofono: New Status in Telephony Service: New Status in dialer-app package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Status in telephony-service package in Ubuntu: New Status in dialer-app package in Ubuntu RTM: New Status in telepathy-ofono package in Ubuntu RTM: New Status in telephony-service package in Ubuntu RTM: New Bug description: Product: Krillin bq Aquaris E4.5 Ubuntu Edition FW version: ubuntu-touch/stable/bq.aquaris.es #6 Material: Description: Steps to reproduce the issue: 1.- System Settings -> Phone -> Call waiting -> Activated 1.- Open dialer. 2.- Make a MO Call to DUT2. 3.- When call connected, on hold it. 3.- Use DUT3 to call DUT1. 4.- Call should appear on screen to answer or reject it. Currently result: Call from DUT3 to DUT1 while on hold can’t be answer or reject it because it doesn’t appear on screen. Expected result: Some networks permit this service, and some don't. In the case where the network does not permit call waiting or (related) call merging, some sort of UI should be presented, similarly to other handset OS. Reproducibility: 100% To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410365/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413170] [NEW] Not able to select contact while composing a SMS
Public bug reported: I'm using Nexus 5. I have installed Ubuntu using MultiROM I can reply to the SMS that i have received but following is not working. 1. Open SMS app 2. Select 'Compose' from bottom bar 3. Click the Add Contact icon 4. Choose the contact from the list 5. It shows as added 6. Type message 7. Click Send 8. Returns Failed error Message ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Tags: sms -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1413170 Title: Not able to select contact while composing a SMS Status in messaging-app package in Ubuntu: New Bug description: I'm using Nexus 5. I have installed Ubuntu using MultiROM I can reply to the SMS that i have received but following is not working. 1. Open SMS app 2. Select 'Compose' from bottom bar 3. Click the Add Contact icon 4. Choose the contact from the list 5. It shows as added 6. Type message 7. Click Send 8. Returns Failed error Message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1413170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363400] Re: [wizard] allows to "Continue" without connecting to network
** Changed in: unity8 (Ubuntu) Status: Triaged => In Progress ** Branch linked: lp:~cimi/unity8/fix-1363400 ** Changed in: ubuntu-system-settings (Ubuntu RTM) 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/1363400 Title: [wizard] allows to "Continue" without connecting to network Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu RTM: In Progress Bug description: The wifi page of the wizard lets you select the network, but doesn't wait for a connection to enable the Continue button. Until connected, the button should probably say "Skip", and if there's a connection in progress, that should be cancelled. Or we need a modal dialog introduced (like the one we have for notifications in the shell) in the wizard as well, so that you need to cancel the password entry before being able to skip. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-system-settings-wizard 0.3+14.10.20140828.2~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Sat Aug 30 11:17:34 2014 InstallationDate: Installed on 2014-08-30 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140830-030204) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) upstart.ubuntu-system-settings-wizard-cleanup.log: Ending wizard Resetting MIR_SOCKET to /run/mir_socket () ubuntu-system-settings-wizard stop/waiting To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1363400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 116453] Re: evince can not find ü in attached PDF
hdante: the problem is that, despite appearances, the PDF in the bug description does not contain the word 'Über'. It contains the word 'Uber', without a diaresis. You can see this if you copy and paste from the document using any PDF reader, including adobe reader, google chrome, foxit, etc. There is a diaresis, but it is not really attached to the 'U'. Even so, adobe reader and chrome can still find something if you search the document for 'über'. What they seem to be doing is ignoring any diacratic marks, so if you search for 'über' (or even 'ubér') it will find 'Uber'. I was proposing similar behavior for poppler. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/116453 Title: evince can not find ü in attached PDF Status in Poppler: Confirmed Status in poppler package in Ubuntu: Triaged Bug description: Binary package hint: evince 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy evince evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen with the attached document is when one searches for: über it is found: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/116453/+attachment/102979/+files/example.pdf 4) What happens instead is it does not return any matches. WORKAROUND: Use the built-in PDF viewer+search with chromium-browser or chrome (doesn't work in Firefox). apt-cache policy chromium-browser chromium-browser: Installed: 39.0.2171.65-0ubuntu0.14.04.1.1064 Candidate: 39.0.2171.65-0ubuntu0.14.04.1.1064 Version table: *** 39.0.2171.65-0ubuntu0.14.04.1.1064 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages 100 /var/lib/dpkg/status 34.0.1847.116-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages apt-cache policy google-chrome-stable:i386 google-chrome-stable:i386: Installed: 39.0.2171.95-1 Candidate: 39.0.2171.95-1 Version table: *** 39.0.2171.95-1 0 500 http://dl.google.com/linux/chrome/deb/ stable/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug Architecture: i386 Date: Wed May 23 18:22:27 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/evince Package: evince 0.8.1-0ubuntu1 PackageArchitecture: i386 ProcEnviron: LANGUAGE=en_US:en PATH=~/local/bin:~/local/lib:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince Uname: Linux copper 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/116453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408323] Re: Weirdness when /home is full
Some more info: * If after proving the animations are not working i phablet-shell into the phone * stop unity ( wait for a long time for it to stop ) * MIR_SERVER_NAME=session-0 MIR_SOCKET=/run/mir_socket QT_QPA_PLATFORM=mirserver /usr/bin/unity8 * The animations now work fine * Open another phablet-shell into the phone * /usr/bin/unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop * Now the unity8 animations don't work anymore -- 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/1408323 Title: Weirdness when /home is full Status in unity8 package in Ubuntu: New Bug description: I happened to fill my /home to 100% in my Nexus4 under vivid. At that point the screen locker shows up but you can not unlock it (there seems to be no animation) Also the same happens with the indicators bar, and the indicators are empty. It is my undestandin that it shouldn't matter how much you fill /home that the basic functions of the phone should still work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363400] Re: [wizard] allows to "Continue" without connecting to network
** Branch linked: lp:~cimi/ubuntu-system-settings/fix-1363400 -- 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/1363400 Title: [wizard] allows to "Continue" without connecting to network Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu RTM: In Progress Bug description: The wifi page of the wizard lets you select the network, but doesn't wait for a connection to enable the Continue button. Until connected, the button should probably say "Skip", and if there's a connection in progress, that should be cancelled. Or we need a modal dialog introduced (like the one we have for notifications in the shell) in the wizard as well, so that you need to cancel the password entry before being able to skip. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-system-settings-wizard 0.3+14.10.20140828.2~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Sat Aug 30 11:17:34 2014 InstallationDate: Installed on 2014-08-30 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140830-030204) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) upstart.ubuntu-system-settings-wizard-cleanup.log: Ending wizard Resetting MIR_SOCKET to /run/mir_socket () ubuntu-system-settings-wizard stop/waiting To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1363400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- 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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: In Progress Status in unity package in Ubuntu: New Bug description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408064] Re: [webapp-container] UA Override from webapp-properies.json file is not set
** Changed in: webbrowser-app (Ubuntu RTM)
Status: Confirmed => In Progress
--
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/1408064
Title:
[webapp-container] UA Override from webapp-properies.json file is not
set
Status in the base for Ubuntu mobile products:
In Progress
Status in Web Browser App:
Fix Released
Status in webbrowser-app package in Ubuntu:
Fix Released
Status in webbrowser-app package in Ubuntu RTM:
In Progress
Bug description:
[Impact]
Webapp has the option to either specify a command line option to have
a specific UA overriding the default or have a local webapp-
properties.json file that defines the UA override such as:
{
"name": "MyWebapp",
"includes":["http://user-agent.me/*";],
"domain":"user-agent.me",
"homepage":"http://user-agent.me/";,
"user-agent-override": "Mozilla/5.0 custom-user-agent-string (unlike
AnyOtheBrowser)"
}
This currently does work.
[Test Case]
- from qtcreator, create a webapp,
- update the Exec line from the desktop file to
Exec=webapp-container --enable-back-forward --store-session-cookies
--webappModelSearchPath=. %u
- create a webapp-properties.json file in the project folder with the
following content:
{
"name": "MyWebapp",
"includes":["http://user-agent.me/*";],
"domain":"user-agent.me",
"homepage":"http://user-agent.me/";,
"user-agent-override": "Mozilla/5.0 custom-user-agent-string (unlike
AnyOtheBrowser)"
}
- make sure that the webapp automatically browses to http://user-agent.me/
- make sure that the UA override is the same as the one listed above,
[Regression Potential]
Make sure that the window title is properly set to the webapp name.
Note:
this is not a dup of https://bugs.launchpad.net/webbrowser-app/+bug/1379497
but a regression
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1408064/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1316090] Re: Unable to drop/ place files and links on second screen in dual screen set up
With the update I received today (libcairo2*) the behaviour I described earlier disappeared. It is now possible to place icons on both screens/ desktops. On top of that this update also gave me a staggering speed increase! Hence, I think this bug report can be closed, the issue is solved. -- 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/1316090 Title: Unable to drop/ place files and links on second screen in dual screen set up Status in xorg package in Ubuntu: Confirmed Bug description: After updating from Xubuntu 13.10 (amd64) to Xubuntu 14.04 LTS (amd64) I have encountered a bug with my dual screen set up. Running the XOrg screen driver (xserver-xorg-video-nouveau), it is possible to place/ drag and drop files and links on my left screen desktop. This is also the desktop that contains the system icons (e.g. removable drives, rubbish bin). However, I I try to drag and drop a file or link on the right screen desktop, it will not "stick" and "fly back" to its original location on the left screen. Additionally, I noticed that, when dragging the file over the troubled desktop, the "placement squares" don't show up. They do on the functioning left screen. Although I have a NVIDIA Corporation GK107 [GeForce GTX 650] Geforce I do run the XOrg driver since it gives me the best results with the software I'm using frequently. However, when I tested this during my initial install of Trusty, I noticed that I did not encounter this bug with the proprietary NVidia 304.117 driver (331.38 did not work for me at all). Running the NVidia 304.117 driver, it was possible to drag and drop/ place files and links on both screen desktops. Also the "placement squares" appeared on both screens when a file was dragged over it. After returning to the XOrg driver, the problem reoccurred, and placement on the right screen was again not possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
** Changed in: unity (Ubuntu) Status: New => In Progress ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (andyrock) ** Changed in: unity Importance: Undecided => High -- 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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413193] [NEW] [vivid] Failed to reset devices.list
Public bug reported: Vivid i386 booted with systemd from syslog: dbus[668]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' systemd[1]: Starting Hostname Service... systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument systemd[1]: Failed to reset devices.list on /user.slice: Invalid argument dbus[668]: [system] Successfully activated service 'org.freedesktop.hostname1' systemd[1]: Started Hostname Service. sys/fs/cgroup/devices/system.slice owned by root and set 'read-only' sys/fs/cgroup/devices/user.slice " " " (all the files are 0 bytes) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-3ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4 Uname: Linux 3.19.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 BootDmesg: (Nothing has been logged yet.) CurrentDesktop: GNOME Date: Wed Jan 21 13:23:53 2015 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.19.0-2-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd SourcePackage: systemd 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 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid ** Description changed: + Vivid i386 booted with systemd + from syslog: - dbus[668]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' - systemd[1]: Starting Hostname Service... - systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument - systemd[1]: Failed to reset devices.list on /user.slice: Invalid argument - dbus[668]: [system] Successfully activated service 'org.freedesktop.hostname1' - systemd[1]: Started Hostname Service. - + dbus[668]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' + systemd[1]: Starting Hostname Service... + systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument + systemd[1]: Failed to reset devices.list on /user.slice: Invalid argument + dbus[668]: [system] Successfully activated service 'org.freedesktop.hostname1' + systemd[1]: Started Hostname Service. sys/fs/cgroup/devices/system.slice owned by root and set 'read-only' sys/fs/cgroup/devices/user.slice " " " (all the files are 0 bytes) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-3ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4 Uname: Linux 3.19.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 BootDmesg: (Nothing has been logged yet.) CurrentDesktop: GNOME Date: Wed Jan 21 13:23:53 2015 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 + 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.19.0-2-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd SourcePackage: systemd 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: ASUS
[Touch-packages] [Bug 1408029] Re: telephony-service-handler crashing
** Branch linked: lp:~boiko/telephony-service/rtm-fix_1408029 -- 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/1408029 Title: telephony-service-handler crashing Status in the base for Ubuntu mobile products: New Status in Telephony Service: New Status in telephony-service package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu RTM: In Progress Bug description: This was reported by om26er on rtm image and crash report is here: https://errors.ubuntu.com/oops/54247740-88c5-11e4-9904-fa163e373683 It appears the handler is crashing trying to acknowledge a chat message, top of stack trace is following: StacktraceTop AccountEntry::accountId() const () TextHandler::existingChat(QStringList const&, QString const&) () TextHandler::acknowledgeMessages(QStringList const&, QStringList const&, QString const&) () ?? () TelephonyServiceHandlerAdaptor::qt_metacall(QMetaObject::Call, int, void**) () Omer please list the steps to reproduce or the circumstances that caused this crash To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1408029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408029] Re: telephony-service-handler crashing
** Changed in: telephony-service (Ubuntu RTM) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) ** Changed in: telephony-service (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 telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1408029 Title: telephony-service-handler crashing Status in the base for Ubuntu mobile products: New Status in Telephony Service: New Status in telephony-service package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu RTM: In Progress Bug description: This was reported by om26er on rtm image and crash report is here: https://errors.ubuntu.com/oops/54247740-88c5-11e4-9904-fa163e373683 It appears the handler is crashing trying to acknowledge a chat message, top of stack trace is following: StacktraceTop AccountEntry::accountId() const () TextHandler::existingChat(QStringList const&, QString const&) () TextHandler::acknowledgeMessages(QStringList const&, QStringList const&, QString const&) () ?? () TelephonyServiceHandlerAdaptor::qt_metacall(QMetaObject::Call, int, void**) () Omer please list the steps to reproduce or the circumstances that caused this crash To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1408029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376240] Re: pressing power button should silence incoming call
** Changed in: telephony-service (Ubuntu RTM) Status: New => In Progress ** Changed in: telephony-service Status: Confirmed => In Progress ** Changed in: telephony-service (Ubuntu RTM) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1376240 Title: pressing power button should silence incoming call Status in the base for Ubuntu mobile products: Confirmed Status in Telephony Service: In Progress Status in Ubuntu UX bugs: Fix Committed Status in Unity System Compositor: In Progress Status in telephony-service package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu RTM: In Progress Bug description: In the incoming call dialog there is no way to dismiss a call, only reject it. I would like a way to keep the calling active but in silent mode. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1376240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413201] [NEW] date setted to 1970
Public bug reported: Everything worked normal until that day in November 2013. I started the netbook and suddenly the date was set on 01-01-1970. I tried to change it myself, but couldn't do it. Also surfing is a problem: it won't open https-websites anymore. Thanks in advance for your help. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-32.53-generic 3.5.7.11 Uname: Linux 3.5.0-32-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Thu Jan 1 01:24:21 1970 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DpkgLog: EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0349] Subsystem: Acer Incorporated [ALI] Device [1025:0349] InstallationDate: Installed on 2013-03-23 (-15787 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MachineType: Acer AOD255 MarkForUpload: True ProcEnviron: LANGUAGE=nl:en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-32-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2010 dmi.bios.vendor: Acer dmi.bios.version: V3.05(DDR2) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AOD255 dmi.board.vendor: Acer dmi.board.version: V3.05(DDR2) dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V3.05(DDR2) dmi.modalias: dmi:bvnAcer:bvrV3.05(DDR2):bd08/12/2010:svnAcer:pnAOD255:pvrV3.05(DDR2):rvnAcer:rnAOD255:rvrV3.05(DDR2):cvnAcer:ct10:cvrV3.05(DDR2): dmi.product.name: AOD255 dmi.product.version: V3.05(DDR2) dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 quantal running-unity 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/1413201 Title: date setted to 1970 Status in xorg package in Ubuntu: New Bug description: Everything worked normal until that day in November 2013. I started the netbook and suddenly the date was set on 01-01-1970. I tried to change it myself, but couldn't do it. Also surfing is a problem: it won't open https-websites anymore. Thanks in advance for your help. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-32.53-generic 3.5.7.11 Uname: Linux 3.5.0-32-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Thu Jan 1 01:24:21 1970 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DpkgLog: EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0349] Subsystem: Acer Incorporated [ALI] Device [1025:0349] InstallationDate: Installed on 2013-03-23 (-15787 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MachineType: Acer AOD255 MarkForUpload: True ProcEnviron: LANGUAGE=nl:en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-32-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2010 dmi.bios.vendor: Acer dmi.bios.version: V3.05(DDR2) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name
[Touch-packages] [Bug 1379375] Re: evince does not display ligatures
Could someone please also fix the bug for 14.10? For 14.10 there is only version 2.11.1-0ubuntu3 of fontconfig available. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1379375 Title: evince does not display ligatures Status in fontconfig package in Ubuntu: Fix Released Status in poppler package in Ubuntu: Fix Released Status in fontconfig source package in Trusty: Won't Fix Status in poppler source package in Trusty: In Progress Status in fontconfig source package in Utopic: Won't Fix Status in poppler source package in Utopic: In Progress Bug description: [ Description ] Some ligatures (e.g. "fi") are not displayed in certain fonts, because there are two different naming schemes in use in the wild. [ Fix ] Poppler upstream fixed this by adding a lookup table to fall back to the second scheme if necessary. [ QA ] 1. Install tex-gyre 2. Download https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1317599/+attachment/4213588/+files/rfa1415_15sep_lect1.pdf 3. Open the file in evince 4. Look at "Biometrics: file" on page 3 If the "fi" ligature in "file" is not displayed, you have this bug. "file" should be displayed normally after it's fixed. [ Regression potential ] Since this patch implements a fallback only when lookup false, there shouldn't be any problems. Still, check all existing PDFs are still displayed correctly. [ Original report ] While there's Bug #1325230 with the same title and the linked PDFs there are working fine here (displaying "fi" correctly) there seems to be still some bug regarding ligatures. https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1325230 I have some PDFs substituting Helvetica (and others) with TeX Gyre Heros and showing no "fi" ligature. I attached a patch I derived from the patch in Bug #1325230 which is working fine. Now it uses Nimbus Sans L and the ligatures are fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1379375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376240] Re: pressing power button should silence incoming call
** Branch linked: lp:~boiko/telephony-service/rtm-silence_incoming_cals -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1376240 Title: pressing power button should silence incoming call Status in the base for Ubuntu mobile products: Confirmed Status in Telephony Service: In Progress Status in Ubuntu UX bugs: Fix Committed Status in Unity System Compositor: In Progress Status in telephony-service package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu RTM: In Progress Bug description: In the incoming call dialog there is no way to dismiss a call, only reject it. I would like a way to keep the calling active but in silent mode. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1376240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413194] Re: Cut/Copy/Paste options displayed off the top of the screen from the addressbar
This is a rather recent regression, most likely in the UITK (as the issue is not present on RTM, although webbrowser-app was recently synced back from vivid to RTM, so both versions are virtually identical). ** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Changed in: webbrowser-app Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1413194 Title: [regression] Cut/Copy/Paste options displayed off the top of the screen from the addressbar Status in Web Browser App: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Steps to reproduce 1) Long press on the addressbar Expected result Cut/Copy/Paste option should appear in a pop-up below the addressbar Actual result The pop-up is displayed above the addressbar, meaning only the bottom of it is visible, the rest is cut off by the notification area/top of the screen. mako, vivid-proposed #72 To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1413194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413194] Re: Cut/Copy/Paste options displayed off the top of the screen from the addressbar
I can easily reproduce with the following standalone test app:
import QtQuick 2.0
import Ubuntu.Components 1.1
MainView {
TextField {
anchors {
top: parent.top
left: parent.left
right: parent.right
margins: units.gu(2)
}
focus: true
text: "long-press me to invoke contextual options"
Component.onCompleted: selectAll()
}
}
** Summary changed:
- Cut/Copy/Paste options displayed off the top of the screen from the
addressbar
+ [regression] Cut/Copy/Paste options displayed off the top of the screen from
the addressbar
--
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/1413194
Title:
[regression] Cut/Copy/Paste options displayed off the top of the
screen from the addressbar
Status in Web Browser App:
Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
Steps to reproduce
1) Long press on the addressbar
Expected result
Cut/Copy/Paste option should appear in a pop-up below the addressbar
Actual result
The pop-up is displayed above the addressbar, meaning only the bottom
of it is visible, the rest is cut off by the notification area/top of
the screen.
mako, vivid-proposed #72
To manage notifications about this bug go to:
https://bugs.launchpad.net/webbrowser-app/+bug/1413194/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359337] Re: dialer not remembering current view after lock/unlock
** Changed in: dialer-app (Ubuntu RTM) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1359337 Title: dialer not remembering current view after lock/unlock Status in the base for Ubuntu mobile products: Confirmed Status in Dialer app for Ubuntu Touch: Confirmed Status in dialer-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu RTM: In Progress Bug description: build 199 open dialer navigate to contacts page or recents page lock the phone unlock the phone Expected results: dialer should be on the page you left it on Actual results: keypad view is always shown To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1359337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411323] Re: [address book] share handler screen has a confusing "ok" icon
** Branch linked: lp:~renatofilho/address-book-app/fix-1411323-rtm -- 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/1411323 Title: [address book] share handler screen has a confusing "ok" icon Status in Address Book App: In Progress Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: Fix Released Status in address-book-app package in Ubuntu RTM: In Progress Bug description: as found on user testing, the share icon is confusing for users that get to this screen and do not know how to proceed. Steps to reproduce: Using telegram click in contacts then click in import select from address book once the content hub launches, select the address book select a few contact Expected result: there is a clear button to "ok" selection, that matches the "X" to cancel. Maybe a tick like in the camera app Actual result: A share icon is used to "ok" To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1411323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411323] Re: [address book] share handler screen has a confusing "ok" icon
** Changed in: address-book-app (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 address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1411323 Title: [address book] share handler screen has a confusing "ok" icon Status in Address Book App: In Progress Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: Fix Released Status in address-book-app package in Ubuntu RTM: In Progress Bug description: as found on user testing, the share icon is confusing for users that get to this screen and do not know how to proceed. Steps to reproduce: Using telegram click in contacts then click in import select from address book once the content hub launches, select the address book select a few contact Expected result: there is a clear button to "ok" selection, that matches the "X" to cancel. Maybe a tick like in the camera app Actual result: A share icon is used to "ok" To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1411323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412060] Re: Indicator sound fails to start with Asus Xonar
** Package changed: pulseaudio (Ubuntu) => indicator-sound (Ubuntu) -- 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/1412060 Title: Indicator sound fails to start with Asus Xonar Status in indicator-sound package in Ubuntu: New Bug description: Replaced Audigy with Xonar. Clean installed to new drive and partition. sound indicator fails to start upstart --user --startup-event indicator-services-start tries to start indicator - space in indicators shows where it is, clicking and menu doesn't appear ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20141105-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jan 17 21:37:27 2015 InstallationDate: Installed on 2015-01-09 (8 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150108) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1412060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379375] Re: evince does not display ligatures
The fix is in poppler. See comment #10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1379375 Title: evince does not display ligatures Status in fontconfig package in Ubuntu: Fix Released Status in poppler package in Ubuntu: Fix Released Status in fontconfig source package in Trusty: Won't Fix Status in poppler source package in Trusty: In Progress Status in fontconfig source package in Utopic: Won't Fix Status in poppler source package in Utopic: In Progress Bug description: [ Description ] Some ligatures (e.g. "fi") are not displayed in certain fonts, because there are two different naming schemes in use in the wild. [ Fix ] Poppler upstream fixed this by adding a lookup table to fall back to the second scheme if necessary. [ QA ] 1. Install tex-gyre 2. Download https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1317599/+attachment/4213588/+files/rfa1415_15sep_lect1.pdf 3. Open the file in evince 4. Look at "Biometrics: file" on page 3 If the "fi" ligature in "file" is not displayed, you have this bug. "file" should be displayed normally after it's fixed. [ Regression potential ] Since this patch implements a fallback only when lookup false, there shouldn't be any problems. Still, check all existing PDFs are still displayed correctly. [ Original report ] While there's Bug #1325230 with the same title and the linked PDFs there are working fine here (displaying "fi" correctly) there seems to be still some bug regarding ligatures. https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1325230 I have some PDFs substituting Helvetica (and others) with TeX Gyre Heros and showing no "fi" ligature. I attached a patch I derived from the patch in Bug #1325230 which is working fine. Now it uses Nimbus Sans L and the ligatures are fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1379375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413194] Re: [regression] Cut/Copy/Paste options displayed off the top of the screen from the addressbar
I can confirm i'm seeing this too on Vivid-proposed #72. -- 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/1413194 Title: [regression] Cut/Copy/Paste options displayed off the top of the screen from the addressbar Status in Web Browser App: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Steps to reproduce 1) Long press on the addressbar Expected result Cut/Copy/Paste option should appear in a pop-up below the addressbar Actual result The pop-up is displayed above the addressbar, meaning only the bottom of it is visible, the rest is cut off by the notification area/top of the screen. mako, vivid-proposed #72 To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1413194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413194] Re: [regression] Cut/Copy/Paste options displayed off the top of the screen from the addressbar
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Confirmed -- 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/1413194 Title: [regression] Cut/Copy/Paste options displayed off the top of the screen from the addressbar Status in Web Browser App: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Steps to reproduce 1) Long press on the addressbar Expected result Cut/Copy/Paste option should appear in a pop-up below the addressbar Actual result The pop-up is displayed above the addressbar, meaning only the bottom of it is visible, the rest is cut off by the notification area/top of the screen. mako, vivid-proposed #72 To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1413194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1405954] Re: Touchpad detected but not working
I did it at my configuration and the system updated itself. Is that it? Still only working through psmouse.proto=bare -- 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/1405954 Title: Touchpad detected but not working Status in xorg package in Ubuntu: New Bug description: Dec 27 10:49:30 skynote kernel: [0.838154] input: FocalTechPS/2 FocalTech FocalTech Touchpad as /devices/platform/i8042/serio1/input/input5 Dec 27 10:49:30 skynote kernel: [0.858259] psmouse serio1: Failed to enable mouse on isa0060/serio1 Notebook Asus x450lc. Description: Ubuntu 14.04.1 LTS Release: 14.04 I don't know how to figure the version at 'apt-cache policy pkgname' but it gave a lot of 500s without the pkgname I guess it's 500 then. I expected the touchpad to work, I updated the kernel to detect it and it detected but no working. It works if I add psmouse=proto.bare into /etc/default/grub and updating the grub. However it will work as a mouse (no multifingers) and it will crash at suspend. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Dec 27 11:23:05 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed bbswitch, 0.7, 3.13.0-41-generic, x86_64: installed bbswitch, 0.7, 3.13.0-43-generic, x86_64: installed bbswitch, 0.7, 3.13.0-44-generic, x86_64: installed bbswitch, 0.7, 3.16.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13fd] InstallationDate: Installed on 2014-11-05 (52 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUSTeK COMPUTER INC. X450LCP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=28130cba-7b95-42de-ab61-7fa6fdc62a4a ro quiet splash i8042.noloop=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X450LCP.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X450LCP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX450LCP.208:bd06/12/2014:svnASUSTeKCOMPUTERINC.:pnX450LCP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX450LCP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X450LCP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Dec 27 10:49:34 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12860 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1405954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410500] Re: Selecting matched numbers from Recent should use the full contact's number
** Changed in: history-service (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) ** Changed in: history-service (Ubuntu RTM) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) ** Changed in: history-service Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1410500 Title: Selecting matched numbers from Recent should use the full contact's number Status in the base for Ubuntu mobile products: New Status in Dialer app for Ubuntu Touch: New Status in Telephony History Service: New Status in Ubuntu UX bugs: Triaged Status in dialer-app package in Ubuntu: New Status in history-service package in Ubuntu: New Status in dialer-app package in Ubuntu RTM: New Status in history-service package in Ubuntu RTM: New Bug description: Steps: * store a number with the country code * call the contact without using the country code * interrupt the call * swipe from the bottom * tap on the call just made Expected: * you get the dialer keypad with the full number, including the country code Current: * you get the short number without the country code This was a problem for me when travelling, I couldn't use the Recent list to call home because it wouldn't include the country code. Somehow it's also remembered permanently, so now even if I call the full number with country code, tapping that Recent entry won't have the country code still. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20150108-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu2 Architecture: armhf Date: Tue Jan 13 19:32:43 2015 InstallationDate: Installed on 2015-01-13 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150113-020204) SourcePackage: dialer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372646] Re: Can't correct SMS number after entering it wrong once
** Changed in: history-service (Ubuntu) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) ** Changed in: history-service (Ubuntu RTM) Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1372646 Title: Can't correct SMS number after entering it wrong once Status in Telephony History Service: New Status in Messaging App: Confirmed Status in Telepathy Ofono: New Status in history-service package in Ubuntu: New Status in messaging-app package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Status in history-service package in Ubuntu RTM: New Status in messaging-app package in Ubuntu RTM: New Status in telepathy-ofono package in Ubuntu RTM: New Bug description: Steps to reproduce (example, I suspect more number combinations are possible to reproduce): * Using the bottom edge, write a new SMS to a foreign number which is not stored to your address book, but omit the country code. Eg, 01791234567 * Wait for the SMS delivery to fail. * Go back to the conversations list and use the bottom edge to start writing a new SMS. enter the same number again, this time including the country code. eg +491791234567 * The second SMS will be grouped with the first one and the first SMS's number will be used for the second SMS too causing all attempts to fail again. This does not recover after clearing the conversation. dbus-monitor always shows HistoryService bringing back the old wrong number. Also the conversation's header will revert to the old number after exiting and re-entering the conversation. To manage notifications about this bug go to: https://bugs.launchpad.net/history-service/+bug/1372646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413194] Re: [regression] Cut/Copy/Paste options displayed off the top of the screen from the addressbar
Screenshot of bug ** Attachment added: "popover.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1413194/+attachment/4302967/+files/popover.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1413194 Title: [regression] Cut/Copy/Paste options displayed off the top of the screen from the addressbar Status in Web Browser App: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Steps to reproduce 1) Long press on the addressbar Expected result Cut/Copy/Paste option should appear in a pop-up below the addressbar Actual result The pop-up is displayed above the addressbar, meaning only the bottom of it is visible, the rest is cut off by the notification area/top of the screen. mako, vivid-proposed #72 To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1413194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1158500] Re: auditd fails to add rules when used in precise with -lts-quantal kernel
any news ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1158500 Title: auditd fails to add rules when used in precise with -lts-quantal kernel Status in audit package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Bug description: auditctl fails to add rules when run with the -lts-quantal kernel Eample: # auditctl -l No rules # auditctl -a entry,always -F arch=b64 -S execve -k exec Error sending add rule data request (Invalid argument) # Looks like the syscall table needs updating, it works with the 3.2.0 kernel. Tagging this as a security vulnerability because it fails fairly quietly and may lead to high security systems not having required auditing (like PCI compliant systems), I only noticed by looking in /var/log/boot.log. Description: Ubuntu 12.04.2 LTS Release: 12.04 ii auditd 1.7.18-1ubuntu1 User space tools for security auditing ii linux-image-generic-lts-quantal3.5.0.26.33 Generic Linux kernel image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1158500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379375] Please test proposed package
Hello hede, or anyone else affected, Accepted poppler into utopic-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/poppler/0.26.5-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1379375 Title: evince does not display ligatures Status in fontconfig package in Ubuntu: Fix Released Status in poppler package in Ubuntu: Fix Released Status in fontconfig source package in Trusty: Won't Fix Status in poppler source package in Trusty: Fix Committed Status in fontconfig source package in Utopic: Won't Fix Status in poppler source package in Utopic: Fix Committed Bug description: [ Description ] Some ligatures (e.g. "fi") are not displayed in certain fonts, because there are two different naming schemes in use in the wild. [ Fix ] Poppler upstream fixed this by adding a lookup table to fall back to the second scheme if necessary. [ QA ] 1. Install tex-gyre 2. Download https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1317599/+attachment/4213588/+files/rfa1415_15sep_lect1.pdf 3. Open the file in evince 4. Look at "Biometrics: file" on page 3 If the "fi" ligature in "file" is not displayed, you have this bug. "file" should be displayed normally after it's fixed. [ Regression potential ] Since this patch implements a fallback only when lookup false, there shouldn't be any problems. Still, check all existing PDFs are still displayed correctly. [ Original report ] While there's Bug #1325230 with the same title and the linked PDFs there are working fine here (displaying "fi" correctly) there seems to be still some bug regarding ligatures. https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1325230 I have some PDFs substituting Helvetica (and others) with TeX Gyre Heros and showing no "fi" ligature. I attached a patch I derived from the patch in Bug #1325230 which is working fine. Now it uses Nimbus Sans L and the ligatures are fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1379375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379375] Re: evince does not display ligatures
Hello hede, or anyone else affected, Accepted poppler into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/poppler/0.24.5-2ubuntu4.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: poppler (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed ** Changed in: poppler (Ubuntu Utopic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1379375 Title: evince does not display ligatures Status in fontconfig package in Ubuntu: Fix Released Status in poppler package in Ubuntu: Fix Released Status in fontconfig source package in Trusty: Won't Fix Status in poppler source package in Trusty: Fix Committed Status in fontconfig source package in Utopic: Won't Fix Status in poppler source package in Utopic: Fix Committed Bug description: [ Description ] Some ligatures (e.g. "fi") are not displayed in certain fonts, because there are two different naming schemes in use in the wild. [ Fix ] Poppler upstream fixed this by adding a lookup table to fall back to the second scheme if necessary. [ QA ] 1. Install tex-gyre 2. Download https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1317599/+attachment/4213588/+files/rfa1415_15sep_lect1.pdf 3. Open the file in evince 4. Look at "Biometrics: file" on page 3 If the "fi" ligature in "file" is not displayed, you have this bug. "file" should be displayed normally after it's fixed. [ Regression potential ] Since this patch implements a fallback only when lookup false, there shouldn't be any problems. Still, check all existing PDFs are still displayed correctly. [ Original report ] While there's Bug #1325230 with the same title and the linked PDFs there are working fine here (displaying "fi" correctly) there seems to be still some bug regarding ligatures. https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1325230 I have some PDFs substituting Helvetica (and others) with TeX Gyre Heros and showing no "fi" ligature. I attached a patch I derived from the patch in Bug #1325230 which is working fine. Now it uses Nimbus Sans L and the ligatures are fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1379375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
Here is the output of the command on a vivid installation, that has not been updated since the middle of December 2014 and where the regression was not present yet: $ sudo apt-cache policy unity unity: Installed: 7.3.1+15.04.20141128-0ubuntu1 Candidate: 7.3.1+15.04.20150115-0ubuntu1 Version table: 7.3.1+15.04.20150115-0ubuntu1 0 500 http://ubuntu.mirror.root.lu/ubuntu/ vivid/main amd64 Packages *** 7.3.1+15.04.20141128-0ubuntu1 0 100 /var/lib/dpkg/status And here the output of the command on my uptodate vivid installation having the regression: $ sudo apt-cache policy unity unity: Installed: 7.3.1+15.04.20150115-0ubuntu1 Candidate: 7.3.1+15.04.20150115-0ubuntu1 Version table: *** 7.3.1+15.04.20150115-0ubuntu1 0 500 http://ubuntu.mirror.root.lu/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status As far as I understand, the regression happened somewhere between the two versions. -- 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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412465] Re: Enable support for Kilo Cloud Archive
Hello James, or anyone else affected, Accepted software-properties into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source /software-properties/0.92.37.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: software-properties (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1412465 Title: Enable support for Kilo Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Trusty: Fix Committed Status in software-properties source package in Vivid: Fix Released Bug description: Impact: End users have to manually enable the kilo cloud archive pockets. Test case: sudo add-apt-repository cloud-archive:kilo sudo add-apt-repository cloud-archive:kilo-proposed Regression potential: Limited - just a data item addition Original bug report: That time of the cycle: add-apt-repository cloud-archive:kilo should work on 14.04 only. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: python-software-properties (not installed) ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1 Uname: Linux 3.18.0-8-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 19 14:31:23 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-25 (55 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141124) SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1412465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1405954] Re: Touchpad detected but not working
Strange thing is that it gives me. ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCam id=10 [slave keyboard (3)] ↳ Asus WMI hotkeys id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)] When I remove mouse and run the xinput. This another xinput is with my mouse atached. ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎜ ↳ USB OPTICAL MOUSEid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCam id=10 [slave keyboard (3)] ↳ Asus WMI hotkeys id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)] Oh, since it didn't work I tried a lot of distributions, I'm sticking to Kubuntu 14.10 with the new Plasma5. This desktop is just too beautiful to not use. -- 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/1405954 Title: Touchpad detected but not working Status in xorg package in Ubuntu: New Bug description: Dec 27 10:49:30 skynote kernel: [0.838154] input: FocalTechPS/2 FocalTech FocalTech Touchpad as /devices/platform/i8042/serio1/input/input5 Dec 27 10:49:30 skynote kernel: [0.858259] psmouse serio1: Failed to enable mouse on isa0060/serio1 Notebook Asus x450lc. Description: Ubuntu 14.04.1 LTS Release: 14.04 I don't know how to figure the version at 'apt-cache policy pkgname' but it gave a lot of 500s without the pkgname I guess it's 500 then. I expected the touchpad to work, I updated the kernel to detect it and it detected but no working. It works if I add psmouse=proto.bare into /etc/default/grub and updating the grub. However it will work as a mouse (no multifingers) and it will crash at suspend. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Dec 27 11:23:05 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed bbswitch, 0.7, 3.13.0-41-generic, x86_64: installed bbswitch, 0.7, 3.13.0-43-generic, x86_64: installed bbswitch, 0.7, 3.13.0-44-generic, x86_64: installed bbswitch, 0.7, 3.16.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13fd] InstallationDate: Installed on 2014-11-05 (52 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUSTeK COMPUTER INC. X450LCP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=28130cba-7b95-42de-ab61-7fa6fdc62a4a ro quiet splash i8042.noloop=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X450LCP.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X450LCP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dm
[Touch-packages] [Bug 1379375] Re: evince does not display ligatures
What is the exact name of the package that I have to install from utopic-proposed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1379375 Title: evince does not display ligatures Status in fontconfig package in Ubuntu: Fix Released Status in poppler package in Ubuntu: Fix Released Status in fontconfig source package in Trusty: Won't Fix Status in poppler source package in Trusty: Fix Committed Status in fontconfig source package in Utopic: Won't Fix Status in poppler source package in Utopic: Fix Committed Bug description: [ Description ] Some ligatures (e.g. "fi") are not displayed in certain fonts, because there are two different naming schemes in use in the wild. [ Fix ] Poppler upstream fixed this by adding a lookup table to fall back to the second scheme if necessary. [ QA ] 1. Install tex-gyre 2. Download https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1317599/+attachment/4213588/+files/rfa1415_15sep_lect1.pdf 3. Open the file in evince 4. Look at "Biometrics: file" on page 3 If the "fi" ligature in "file" is not displayed, you have this bug. "file" should be displayed normally after it's fixed. [ Regression potential ] Since this patch implements a fallback only when lookup false, there shouldn't be any problems. Still, check all existing PDFs are still displayed correctly. [ Original report ] While there's Bug #1325230 with the same title and the linked PDFs there are working fine here (displaying "fi" correctly) there seems to be still some bug regarding ligatures. https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1325230 I have some PDFs substituting Helvetica (and others) with TeX Gyre Heros and showing no "fi" ligature. I attached a patch I derived from the patch in Bug #1325230 which is working fine. Now it uses Nimbus Sans L and the ligatures are fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1379375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412465] Re: Enable support for Kilo Cloud Archive
** Branch linked: lp:ubuntu/trusty-proposed/software-properties -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1412465 Title: Enable support for Kilo Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Trusty: Fix Committed Status in software-properties source package in Vivid: Fix Released Bug description: Impact: End users have to manually enable the kilo cloud archive pockets. Test case: sudo add-apt-repository cloud-archive:kilo sudo add-apt-repository cloud-archive:kilo-proposed Regression potential: Limited - just a data item addition Original bug report: That time of the cycle: add-apt-repository cloud-archive:kilo should work on 14.04 only. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: python-software-properties (not installed) ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1 Uname: Linux 3.18.0-8-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 19 14:31:23 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-25 (55 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141124) SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1412465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400730] Re: libxext fills up .xsession-errors log files
Hello Jonathan, or anyone else affected, Accepted libxext into utopic-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libxext/2:1.3.2-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libxext (Ubuntu Utopic) Status: Confirmed => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxext in Ubuntu. https://bugs.launchpad.net/bugs/1400730 Title: libxext fills up .xsession-errors log files Status in libxext package in Ubuntu: Fix Released Status in libxext source package in Utopic: Fix Committed Status in libxext source package in Vivid: Fix Released Bug description: libxext can write debug output, and it can write so much of it that it fills up .xsession-errors t be several GB and fill up the hard disk (or the equivalent file with lightdm). error is "_xgeWireToEvent: Unknown extension 148, this should never happen" [TEST CASE] Install Plasma 5 on utopic Use it for a while Notice that ~/.xsession-errors is filling up saying "_xgeWireToEvent: Unknown extension 148, this should never happen" with the new packages this will not happen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxext/+bug/1400730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398372] Re: webbrowser + u-s-s-online-accounts + ubuntu-html5-theme fail to build against Qt 5.4
Re-opening u-s-s-online-accounts task, the tests still fail: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-005/+build/6737467 ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-html5-theme in Ubuntu. https://bugs.launchpad.net/bugs/1398372 Title: webbrowser + u-s-s-online-accounts + ubuntu-html5-theme fail to build against Qt 5.4 Status in ubuntu-html5-theme package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Triaged Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Similar to bug #1398044 (oxide) and bug #1397979 (ui-toolkit), webbrowser-app and ubuntu-system-settings-online-accounts fail to build against Qt 5.4. UITK's fix is at https://code.launchpad.net /~ubuntu-sdk-team/ubuntu-ui-toolkit/newOpenGlPrivates/+merge/243373 This bug will become invalid if bug #1387537 is fixed instead. Build logs: https://launchpad.net/~canonical-qt5-edgers/+archive/ubuntu/qt5-beta2/+sourcepub/4598562/+listing-archive-extra https://launchpad.net/~canonical-qt5-edgers/+archive/ubuntu/qt5-beta2/+sourcepub/4598561/+listing-archive-extra More information about Qt testing at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-html5-theme/+bug/1398372/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393447] Re: Launcher over greeter should remain on screen if the left edge gesture did not swipe the greeter away
** Description changed: + Preconditions: + * Have the screen lock method configured to use a PIN code + Steps: - * swipe from the left edge so that the welcome screen is moved, but springs back into place + * swipe from the left edge so that the welcome screen (Greeter) is moved, but springs back into place Expected: * launcher remains on screen Current: * launcher hides ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.01+15.04.20141107.2-0ubuntu2 Uname: Linux 3.18.0-031800rc4-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 17 16:01:43 2014 SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** 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/1393447 Title: Launcher over greeter should remain on screen if the left edge gesture did not swipe the greeter away Status in unity8 package in Ubuntu: In Progress Bug description: Preconditions: * Have the screen lock method configured to use a PIN code Steps: * swipe from the left edge so that the welcome screen (Greeter) is moved, but springs back into place Expected: * launcher remains on screen Current: * launcher hides ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.01+15.04.20141107.2-0ubuntu2 Uname: Linux 3.18.0-031800rc4-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 17 16:01:43 2014 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/1393447/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Branch unlinked: lp:~ci-train-bot/unity8/ubuntu-rtm-14.09-proposed -- 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 the base for Ubuntu mobile products: Confirmed Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: In Progress 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/canonical-devices-system-image/+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 1379375] Re: evince does not display ligatures
According to https://launchpad.net/ubuntu/+source/poppler the package you want is libpoppler46 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1379375 Title: evince does not display ligatures Status in fontconfig package in Ubuntu: Fix Released Status in poppler package in Ubuntu: Fix Released Status in fontconfig source package in Trusty: Won't Fix Status in poppler source package in Trusty: Fix Committed Status in fontconfig source package in Utopic: Won't Fix Status in poppler source package in Utopic: Fix Committed Bug description: [ Description ] Some ligatures (e.g. "fi") are not displayed in certain fonts, because there are two different naming schemes in use in the wild. [ Fix ] Poppler upstream fixed this by adding a lookup table to fall back to the second scheme if necessary. [ QA ] 1. Install tex-gyre 2. Download https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1317599/+attachment/4213588/+files/rfa1415_15sep_lect1.pdf 3. Open the file in evince 4. Look at "Biometrics: file" on page 3 If the "fi" ligature in "file" is not displayed, you have this bug. "file" should be displayed normally after it's fixed. [ Regression potential ] Since this patch implements a fallback only when lookup false, there shouldn't be any problems. Still, check all existing PDFs are still displayed correctly. [ Original report ] While there's Bug #1325230 with the same title and the linked PDFs there are working fine here (displaying "fi" correctly) there seems to be still some bug regarding ligatures. https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1325230 I have some PDFs substituting Helvetica (and others) with TeX Gyre Heros and showing no "fi" ligature. I attached a patch I derived from the patch in Bug #1325230 which is working fine. Now it uses Nimbus Sans L and the ligatures are fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1379375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412333] Re: unable to properly mount/unmount multiple img files
You haven't given any command list or output at all. You named one single command you used, and gave a very rough description of what you were doing with it ( which I can't follow ). I need the full commands and output. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1412333 Title: unable to properly mount/unmount multiple img files Status in util-linux package in Ubuntu: Incomplete Bug description: I mounted 3 img files and attempted to mkisofs -o with the path to 3 img (all img files were in the same directory), then the output was data.img merged with platform.img successfully but now the platform.img is mounted twice and won't unmount, data.img was mounted twice but I could unmount it, and the ums.img is mounted but completely inaccessable, unmountable, and doesn't have the eject button next to it's name in the files window. I probably wasn't supposed to try it with 3 but now they're stuck mounted even after it asked for my password. Terminal output this... 51.32% done, estimate finish Mon Jan 19 01:36:57 2015 Total translation table size: 0 Total rockridge attributes bytes: 0 Total directory bytes: 342016 Path table size(bytes): 2316 Max brk space used ca000 9768 extents written (19 MB) (process:4299): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mount 2.20.1-5.1ubuntu20.3 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Mon Jan 19 01:39:52 2015 InstallationDate: Installed on 2014-12-26 (23 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1412333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392380] Re: OA gives out all tokens to any app
** Branch linked: lp:~dbarth/ubuntu-seeds/ubuntu-touch.utopic-signon- apparmor-extension -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1392380 Title: OA gives out all tokens to any app Status in the base for Ubuntu mobile products: Confirmed Status in signon package in Ubuntu: Fix Released Status in signon source package in Utopic: Confirmed Status in signon source package in Vivid: Fix Released Status in signon package in Ubuntu RTM: In Progress Bug description: The attached app will steal all your tokens. All it takes is the "accounts" permission in the apparmor file. Here's the code: https://pastebin.canonical.com/120398/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1392380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
** Branch linked: lp:~andyrock/unity/fix-1413165 -- 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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409995] Re: Queries to remote scopes time out
approving while we look also for a fix to QNetworkAccessManager and the
backend to network manager
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Status: New => In Progress
** Changed in: canonical-devices-system-image
Milestone: None => ww05-2015
--
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/1409995
Title:
Queries to remote scopes time out
Status in the base for Ubuntu mobile products:
In Progress
Status in unity-scopes-api package in Ubuntu:
In Progress
Bug description:
I'm seeing this on Mako, image #63, devel-proposed.
Periodically, the music scope fails to return any results, leaving a
blank screen.
Looking through the log files, I'm seeing tons of messages such as
this:
[2015-01-13 01:33:27.056262] INFO: SSRegistry:
SmartScopesClient.get_remote_scopes(): GET
https://dash.ubuntu.com/smartscopes/v2/remote-scopes?locale=en_US
[2015-01-13 01:33:27.057239] ERROR: SSRegistry:
SmartScopesClient.get_remote_scopes(): failed to read /custom/partner-id:
unity::FileException: cannot open "/custom/partner-id": No such file or
directory (errno = 2)
[2015-01-13 01:33:46.996259] ERROR: SSRegistry:
SmartScopesClient.get_remote_scopes(): Failed to retrieve remote scopes from
uri: https://dash.ubuntu.com/smartscopes/v2/remote-scopes:
unity::ResourceException: Request timed out:
https://dash.ubuntu.com/smartscopes/v2/remote-scopes?locale=en_US
The request times out even though the remote end works fine. (Easy to
confirm by pasting the same URL into the browser.)
As an aside, the error about /custom/partner-id isn't an error: if the
file doesn't exist (errno = 2), we should say nothing. That'll get rid
of a lot of noise.
In addition, when I run a query, I see all queries to remote scopes
fail (see attached trace).
I'm not familiar with the code. Looking through, I noticed this:
HttpResponseHandle::SPtr response =
http_client_->get(remote_scopes_uri.str(), [&response_str](std::string const&
replyLine) {
response_str += replyLine; // accumulate all reply lines
}, headers);
response->get();
Following this through, it appears that response_str is being appended
to from a different thread without any lock. That looks like it's
wrong to me. But that doesn't explain the timeout exception that is
thrown from response->get().
I suspect a race condition somewhere because, occasionally, I get a
query that works.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1409995/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400730] Re: libxext fills up .xsession-errors log files
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/libxext/utopic- proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxext in Ubuntu. https://bugs.launchpad.net/bugs/1400730 Title: libxext fills up .xsession-errors log files Status in libxext package in Ubuntu: Fix Released Status in libxext source package in Utopic: Fix Committed Status in libxext source package in Vivid: Fix Released Bug description: libxext can write debug output, and it can write so much of it that it fills up .xsession-errors t be several GB and fill up the hard disk (or the equivalent file with lightdm). error is "_xgeWireToEvent: Unknown extension 148, this should never happen" [TEST CASE] Install Plasma 5 on utopic Use it for a while Notice that ~/.xsession-errors is filling up saying "_xgeWireToEvent: Unknown extension 148, this should never happen" with the new packages this will not happen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxext/+bug/1400730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404309] Re: contact expansion incorrect when keyboard visible
This bug was fixed in the package address-book-app - 0.2+15.04.20150113 ~rtm-0ubuntu1 --- address-book-app (0.2+15.04.20150113~rtm-0ubuntu1) 14.09; urgency=low [ Renato Araujo Oliveira Filho ] * Fix check for keyboard visibility. (LP: #1404309) -- Ubuntu daily releaseTue, 13 Jan 2015 12:39:37 + ** Changed in: address-book-app (Ubuntu RTM) Status: In Progress => Fix Released ** Changed in: ubuntu-keyboard (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 address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1404309 Title: contact expansion incorrect when keyboard visible Status in Address Book App: Fix Committed Status in Ubuntu Keyboard: In Progress Status in address-book-app package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu: Fix Released Status in address-book-app package in Ubuntu RTM: Fix Released Status in ubuntu-keyboard package in Ubuntu RTM: Fix Released Bug description: rtm build 184 on krillin Steps to reproduce: - open address book app - click on search button - click on one of the contacts at the top of the results to expand it Expected results: - the contact will expand and the keyboard will be dismissed Actual results: - the contact expands then immediately close and the keyboard is dismissed To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1404309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384278] Re: Impossible to change enter button without unfocusing the textfield
This bug was fixed in the package ubuntu-keyboard -
0.99.trunk.phablet2+15.04.20150119~rtm-0ubuntu1
---
ubuntu-keyboard (0.99.trunk.phablet2+15.04.20150119~rtm-0ubuntu1) 14.09;
urgency=low
[ Michael Sheldon ]
* Deactivate autocaps if we receive find out we're in a field that
doesn't support it after having already entered the field (LP:
#1412460)
* Add dependencies for any keyboard layouts used in autopilot tests
-- Ubuntu daily releaseMon, 19 Jan 2015
16:21:41 +
** Changed in: ubuntu-keyboard (Ubuntu RTM)
Status: In Progress => Fix Released
--
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/1384278
Title:
Impossible to change enter button without unfocusing the textfield
Status in Ubuntu Keyboard:
In Progress
Status in ubuntu-keyboard package in Ubuntu:
Fix Released
Status in ubuntu-keyboard package in Ubuntu RTM:
Fix Released
Bug description:
In webbrowser app we want to change enter icon on keyboard following
what's the address in the addressbar. So if the url in addressbar is
the same of page url we want the reload icon, if not we want the enter
icon.
Unfortunately to change icon we need to reload the keyboard, and to do
this we need to unfocus and focus again the textfield, that isn't a
viable way.
This is the code I tried, and it isn't calculate in realtime
InputMethod.extensions: {
"enterKeyIconSource": actionStatus == "reload" ? "reload" :
"keyboard-enter"
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1384278/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408323] Re: Weirdness when /home is full
It also breaks if instead of /usr/bin/unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop i start qmlscene --desktop_file_hint=/usr/share/applications/unity8-dash.desktop So it seems to be more related to unity8 code on handling new apps than on unity8+unity-dash together -- 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/1408323 Title: Weirdness when /home is full Status in unity8 package in Ubuntu: New Bug description: I happened to fill my /home to 100% in my Nexus4 under vivid. At that point the screen locker shows up but you can not unlock it (there seems to be no animation) Also the same happens with the indicators bar, and the indicators are empty. It is my undestandin that it shouldn't matter how much you fill /home that the basic functions of the phone should still work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404309] Re: contact expansion incorrect when keyboard visible
This bug was fixed in the package ubuntu-keyboard - 0.99.trunk.phablet2+15.04.20150119~rtm-0ubuntu1 --- ubuntu-keyboard (0.99.trunk.phablet2+15.04.20150119~rtm-0ubuntu1) 14.09; urgency=low [ Michael Sheldon ] * Deactivate autocaps if we receive find out we're in a field that doesn't support it after having already entered the field (LP: #1412460) * Add dependencies for any keyboard layouts used in autopilot tests -- Ubuntu daily releaseMon, 19 Jan 2015 16:21:41 + -- 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/1404309 Title: contact expansion incorrect when keyboard visible Status in Address Book App: Fix Committed Status in Ubuntu Keyboard: In Progress Status in address-book-app package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu: Fix Released Status in address-book-app package in Ubuntu RTM: Fix Released Status in ubuntu-keyboard package in Ubuntu RTM: Fix Released Bug description: rtm build 184 on krillin Steps to reproduce: - open address book app - click on search button - click on one of the contacts at the top of the results to expand it Expected results: - the contact will expand and the keyboard will be dismissed Actual results: - the contact expands then immediately close and the keyboard is dismissed To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1404309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412460] Re: Keyboard enabled upper case in some webbrowser password fields
This bug was fixed in the package ubuntu-keyboard - 0.99.trunk.phablet2+15.04.20150119~rtm-0ubuntu1 --- ubuntu-keyboard (0.99.trunk.phablet2+15.04.20150119~rtm-0ubuntu1) 14.09; urgency=low [ Michael Sheldon ] * Deactivate autocaps if we receive find out we're in a field that doesn't support it after having already entered the field (LP: #1412460) * Add dependencies for any keyboard layouts used in autopilot tests -- Ubuntu daily releaseMon, 19 Jan 2015 16:21:41 + ** Changed in: ubuntu-keyboard (Ubuntu RTM) Status: Confirmed => Fix Released -- 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/1412460 Title: Keyboard enabled upper case in some webbrowser password fields Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu Keyboard: In Progress Status in ubuntu-keyboard package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu RTM: Fix Released Bug description: Steps to reproduce: 1) Visit http://m.twitter.com (Log out, if already logged in) 2) Enter the "Password" field Expected result Keyboard should be lower case Actual result Keyboard is upper case To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1412460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1248729] Re: maliit-server doesn't respect the QT_LOAD_TESTABILITY environment variable
This bug was fixed in the package maliit-framework - 0.99.0+git20130923+17fdf86-0ubuntu5~rtm --- maliit-framework (0.99.0+git20130923+17fdf86-0ubuntu5~rtm) 14.09; urgency=medium [ Michael Sheldon ] * 0013-check-testability-environment-variable.patch: check for the QT_LOAD_TESTABILITY envrionment variable (LP: #1248729) -- Ricardo Salveti de AraujoThu, 20 Nov 2014 17:28:39 -0200 ** Changed in: maliit-framework (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 maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1248729 Title: maliit-server doesn't respect the QT_LOAD_TESTABILITY environment variable Status in Ubuntu Keyboard: Invalid Status in maliit-framework package in Ubuntu: Fix Released Status in maliit-framework package in Ubuntu RTM: Fix Released Bug description: For testing we need to restart maliit-server with testability enabled, for the likes of unity8 we can do something like: $ stop unity8 && start unity8 QT_LOAD_TESTABILITY=1 Currently this does't work for the maliit-server and I've had to resort to writing an override file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1248729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347488] Re: Backspace should accelerate for single letters as well as words
This bug was fixed in the package ubuntu-keyboard - 0.99.trunk.phablet2+15.04.20150119~rtm-0ubuntu1 --- ubuntu-keyboard (0.99.trunk.phablet2+15.04.20150119~rtm-0ubuntu1) 14.09; urgency=low [ Michael Sheldon ] * Deactivate autocaps if we receive find out we're in a field that doesn't support it after having already entered the field (LP: #1412460) * Add dependencies for any keyboard layouts used in autopilot tests -- Ubuntu daily releaseMon, 19 Jan 2015 16:21:41 + ** Changed in: ubuntu-keyboard (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 ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1347488 Title: Backspace should accelerate for single letters as well as words Status in the base for Ubuntu mobile products: New Status in Ubuntu Keyboard: In Progress Status in ubuntu-keyboard package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu RTM: Fix Released Bug description: Currently the backspace only accelerates when it starts deleting words, so deleting a very long string of characters which are unbroken by spaces takes a long time. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1347488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
