[Touch-packages] [Bug 1483279] [NEW] Unit tests fail where mouseClick() is used to simulate a click event on a MouseArea which is a descendant of a TextField
Public bug reported: This appears to be a regression in version 1.3 of the UITK. The browser has an AddressBar component which contains a TextField, and the secondaryItem for this TextField is a MouseArea (for toggling the bookmarked status of the current address). This component is unit tested, and there is a test that simulates a click on the secondaryItem to verify that the bookmarked status is correctly toggled. This test worked with version 1.2 of the UITK, but fails when I update the import of Ubuntu.Components to 1.3. It appears that the TextField itself intercepts the simulated mouse click event, thus getting active focus. Note that the component works as expected when used in an app by a normal user manipulating a mouse (i.e. the secondaryItem can be clicked and that toggles the bookmark status as expected). It’s only the unit tests that are failing. I’m suspecting that the way QtTest simulates a mouse click event doesn’t play well with Ubuntu.Mouse.forwardTo, although I’m not really sure how and why. ** 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/1483279 Title: Unit tests fail where mouseClick() is used to simulate a click event on a MouseArea which is a descendant of a TextField Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: This appears to be a regression in version 1.3 of the UITK. The browser has an AddressBar component which contains a TextField, and the secondaryItem for this TextField is a MouseArea (for toggling the bookmarked status of the current address). This component is unit tested, and there is a test that simulates a click on the secondaryItem to verify that the bookmarked status is correctly toggled. This test worked with version 1.2 of the UITK, but fails when I update the import of Ubuntu.Components to 1.3. It appears that the TextField itself intercepts the simulated mouse click event, thus getting active focus. Note that the component works as expected when used in an app by a normal user manipulating a mouse (i.e. the secondaryItem can be clicked and that toggles the bookmark status as expected). It’s only the unit tests that are failing. I’m suspecting that the way QtTest simulates a mouse click event doesn’t play well with Ubuntu.Mouse.forwardTo, although I’m not really sure how and why. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1483279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481834] Re: App background should be white by default, without texture
** Changed in: ubuntu-ux Status: Fix Committed = In Progress -- 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/1481834 Title: App background should be white by default, without texture Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: The background of apps should be white by default. When discussed with timp on IRC, it is currently defined at EDEDED - please change to FF. Tim also mentioned there is still some texture by default on app background - please remove this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1481834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481834] Re: App background should be white by default, without texture
The MR is done. See attached screenshots ** Attachment added: before https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1481834/+attachment/4442294/+files/grey-background.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/1481834 Title: App background should be white by default, without texture Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: The background of apps should be white by default. When discussed with timp on IRC, it is currently defined at EDEDED - please change to FF. Tim also mentioned there is still some texture by default on app background - please remove this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1481834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481834] Re: App background should be white by default, without texture
** Attachment added: After (phone layout) https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1481834/+attachment/4442296/+files/50gu-left.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/1481834 Title: App background should be white by default, without texture Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: The background of apps should be white by default. When discussed with timp on IRC, it is currently defined at EDEDED - please change to FF. Tim also mentioned there is still some texture by default on app background - please remove this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1481834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481834] Re: App background should be white by default, without texture
** Attachment added: After (2 columns) https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1481834/+attachment/4442297/+files/100gu-right.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/1481834 Title: App background should be white by default, without texture Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: The background of apps should be white by default. When discussed with timp on IRC, it is currently defined at EDEDED - please change to FF. Tim also mentioned there is still some texture by default on app background - please remove this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1481834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483331] [NEW] Minimum window dimensions
Public bug reported: We need to have a story for minimum window dimensions. Apps shouldn't shrink smaller than their contents can reasonably adapt. The UI toolkit gallery itself is an example of it, at a certain width the window clips components at the right side. ** 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/1483331 Title: Minimum window dimensions Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: We need to have a story for minimum window dimensions. Apps shouldn't shrink smaller than their contents can reasonably adapt. The UI toolkit gallery itself is an example of it, at a certain width the window clips components at the right side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1483331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451243] Re: MainView helper still uses useDeprecatedToolbar when under 1.2 components
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1451243 Title: MainView helper still uses useDeprecatedToolbar when under 1.2 components Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: When using 1.2 components and the autopilot helper for MainView, the helper attempts to access useDeprecatedToolbar (which has been removed). Causing errors such as AttributeError: Class 'MainView' has no attribute 'useDeprecatedToolbar'. 0 - http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/trunk/view/head:/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_mainview.py#L130 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1451243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1282867] Re: Frequent hang and render glitches in Xorg, caused by SNA
looks like the original bug reporter doesn't have this bug anymore, as the upstream bug is closed, and the kernel is also a newer one in wily if you still see hangs in wily, file a new bug. ** Changed in: mesa (Ubuntu) Status: Confirmed = Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1282867 Title: Frequent hang and render glitches in Xorg, caused by SNA Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: After the latest kernel upgrade, my system has many graphical glitches, and is locking up frequently. The dmesg output has errors like these: [ 1951.568672] Watchdog[2753]: segfault at 0 ip 7fe00773a32e sp 7fdff869f680 error 6 in chrome[7fe003cbe000+5dd9000] [ 1959.241676] [drm] stuck on render ring [ 1959.241685] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 1959.241686] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 1959.241687] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI - DRM/Intel [ 1959.241688] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 1959.241689] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 1959.244266] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x3dc32000 ctx 17) at 0x3dc32c48 [ 3964.330034] perf samples too long (2503 2500), lowering kernel.perf_event_max_sample_rate to 5 [ 4849.028446] [drm] stuck on render ring [ 4849.028492] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x565c2000 ctx 17) at 0x565c2c48 [ 4861.093551] Watchdog[5226]: segfault at 0 ip 7fc00d36f32e sp 7fbffe2d4680 error 6 in chrome[7fc0098f3000+5dd9000] [ 4863.020198] [drm] stuck on render ring [ 4863.020255] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x3dc32000 ctx 17) at 0x3dc32c48 [ 4893.028245] [drm] stuck on render ring [ 4893.028295] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x4cbed000 ctx 10) at 0x4cbedc98 [ 4899.041855] [drm] stuck on render ring [ 4899.041900] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0xea3d000 ctx 10) at 0xea3dc98 [ 4899.041903] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned! [ 5833.173837] warning: `VBoxHeadless' uses 32-bit capabilities (legacy support in use) [ 5833.326542] device vboxnet0 entered promiscuous mode [ 6429.476175] [drm] stuck on render ring [ 6488.455986] [drm] stuck on render ring [ 6547.507818] [drm] stuck on render ring [ 6615.490047] [drm] stuck on render ring I am not sure if the xserver-xorg-video-intel ricver was also updated at the same time. This is the version in use: rdhruva@ubuntu:~$ apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: 2:2.99.910-0ubuntu1 Candidate: 2:2.99.910-0ubuntu1 Version table: *** 2:2.99.910-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rdhruva2154 F pulseaudio /dev/snd/pcmC0D0p: rdhruva2154 F...m pulseaudio CurrentDesktop: KDE Date: Thu Feb 20 19:29:20 2014 HibernationDevice: RESUME=UUID=33c83ff3-ead7-4122-a1f0-9602e848cb80 InstallationDate: Installed on 2014-01-24 (27 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140121.1) MachineType: LENOVO 2356EF2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-11-generic root=UUID=9a425350-3b9f-45f7-9587-97f5e539c7e6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-11-generic N/A linux-backports-modules-3.13.0-11-generic N/A linux-firmware 1.125 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/16/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET98WW (2.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356EF2 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: 2045260 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Touch-packages] [Bug 1480877] Re: Access points' PropertiesChanged dbus signals freeze UI on mobile devices
@ingo Thanks for the comment and DBus logs. In the original bug report, NetworkManager's WiFi device was stuck connecting to an access point which no longer existed. Also as noted, the access point in question was a softAP configured on a machine running Windows8.1. Rebooting, solved his issue. In order to make further progress on this bug, what we really need is a concrete set of steps to reproduce the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' PropertiesChanged dbus signals freeze UI on mobile devices Status in indicator-network package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: Krillin, rc-proposed, r83 DESCRIPTION: I've been trying to track down the cause of the occasional UI freezes on my Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I get a burst of PropertiesChanged signals in dbus-monitor Here's a log of what's shown in dbus-monitor: http://pastebin.ubuntu.com/11992322/ I'd guess the problem is in the code that actually catches the signals and acts accordingly. HOW TO REPRODUCE: 1) Move to a place where many wifi hotspots are available 2) Connect the device via USB and run phablet-shell and then dbus-monitor 3) Use the device while keeping an eye on dbus-monitor output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1480877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483331] Re: Minimum window dimensions
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-toolkit/minimumGallery -- 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/1483331 Title: Minimum window dimensions Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: We need to have a story for minimum window dimensions. Apps shouldn't shrink smaller than their contents can reasonably adapt. The UI toolkit gallery itself is an example of it, at a certain width the window clips components at the right side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1483331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483327] [NEW] /usr/sbin/unity-system-compositor:11:__exchange_and_add:__exchange_and_add_dispatch:_M_release:~__shared_count:~__shared_ptr
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with version 0.1.1+15.04.20150804-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1770fbadf225a96999bab768dd7c0b886fa3046d contains more details. ** Affects: unity-system-compositor (Ubuntu) Importance: Undecided Status: New ** Tags: rtm-14.09 utopic vivid wily -- 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/1483327 Title: /usr/sbin/unity-system- compositor:11:__exchange_and_add:__exchange_and_add_dispatch:_M_release:~__shared_count:~__shared_ptr Status in unity-system-compositor package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with version 0.1.1+15.04.20150804-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1770fbadf225a96999bab768dd7c0b886fa3046d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1483327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482317] Re: Unify code that turns screen on when a notification happens
Humph... Unity8 is not running when the device is suspended, is it?
That might put a damper on this plan.
--
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/1482317
Title:
Unify code that turns screen on when a notification happens
Status in unity8 package in Ubuntu:
New
Bug description:
Right now, there are several places we ask USC to turn the screen on
when a notification happens:
- powerd for SMS, USSD, and incoming calls
- telephony-service for MMS and telephony messages
And we don't seem to be turning them on for ubuntu-push notifications,
but we should, right? Following the pattern above, we'd have ubuntu-
push itself turn the screen on, for a third location.
We don't turn the screen on at all for notifications that don't come
via those sources. For example, the following command line doesn't
turn the screen on, but I think it should:
gdbus call --session --dest org.freedesktop.Notifications --object-
path /org/freedesktop/Notifications --method
org.freedesktop.Notifications.Notify '' 0 '' 'Hello' 'World' '[]' '{}'
0
It feels weird to have telephony-service turning the screen on.
Logically, it is just emitting a notification. The presentation of
that notification is up to a higher layer (maybe we're on a raspberry
pi2 and we present notifications as LED morse code or whatever). It
just makes sense that unity8, which is drawing the notification, is
the one that knows that the screen needs to be on. It also knows what
form factor we are in (I assume we only want to turn screen on for
phones/tablets, not desktops).
So I'm proposing that we unify all those places into one code path in
unity8 that can turn the screen on when a notification is received.
(This is a breakout bug from bug 1426115.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1482317/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483279] Re: Unit tests fail where mouseClick() is used to simulate a click event on a MouseArea which is a descendant of a TextField
Note that that the enabled-ness (or visibility) of the MouseArea plays a key role in the issue: if 'enabled' (or 'visible') is set to !textField.activeFocus, the issue occurs. If always visible/enabled, the issue doesn’t occur. -- 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/1483279 Title: Unit tests fail where mouseClick() is used to simulate a click event on a MouseArea which is a descendant of a TextField Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: This appears to be a regression in version 1.3 of the UITK. The browser has an AddressBar component which contains a TextField, and the secondaryItem for this TextField is a MouseArea (for toggling the bookmarked status of the current address). This component is unit tested, and there is a test that simulates a click on the secondaryItem to verify that the bookmarked status is correctly toggled. This test worked with version 1.2 of the UITK, but fails when I update the import of Ubuntu.Components to 1.3. It appears that the TextField itself intercepts the simulated mouse click event, thus getting active focus. Note that the component works as expected when used in an app by a normal user manipulating a mouse (i.e. the secondaryItem can be clicked and that toggles the bookmark status as expected). It’s only the unit tests that are failing. I’m suspecting that the way QtTest simulates a mouse click event doesn’t play well with Ubuntu.Mouse.forwardTo, although I’m not really sure how and why. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1483279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481834] Re: App background should be white by default, without texture
** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/white -- 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/1481834 Title: App background should be white by default, without texture Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: The background of apps should be white by default. When discussed with timp on IRC, it is currently defined at EDEDED - please change to FF. Tim also mentioned there is still some texture by default on app background - please remove this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1481834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481834] Re: App background should be white by default, without texture
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = In Progress ** Changed in: ubuntu-ui-toolkit (Ubuntu) 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/1481834 Title: App background should be white by default, without texture Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: The background of apps should be white by default. When discussed with timp on IRC, it is currently defined at EDEDED - please change to FF. Tim also mentioned there is still some texture by default on app background - please remove this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1481834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481834] Re: App background should be white by default, without texture
** Attachment added: After (2 columns, with sections) https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1481834/+attachment/4442295/+files/100gu-sections.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/1481834 Title: App background should be white by default, without texture Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: The background of apps should be white by default. When discussed with timp on IRC, it is currently defined at EDEDED - please change to FF. Tim also mentioned there is still some texture by default on app background - please remove this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1481834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483279] Re: Unit tests fail where mouseClick() is used to simulate a click event on a MouseArea which is a descendant of a TextField
I’m attaching a simple standalone reproducer. Observe the issue by running it like that: qmltestrunner -input tst_test.qml ** Attachment added: tst_test.qml https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1483279/+attachment/4442293/+files/tst_test.qml -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1483279 Title: Unit tests fail where mouseClick() is used to simulate a click event on a MouseArea which is a descendant of a TextField Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: This appears to be a regression in version 1.3 of the UITK. The browser has an AddressBar component which contains a TextField, and the secondaryItem for this TextField is a MouseArea (for toggling the bookmarked status of the current address). This component is unit tested, and there is a test that simulates a click on the secondaryItem to verify that the bookmarked status is correctly toggled. This test worked with version 1.2 of the UITK, but fails when I update the import of Ubuntu.Components to 1.3. It appears that the TextField itself intercepts the simulated mouse click event, thus getting active focus. Note that the component works as expected when used in an app by a normal user manipulating a mouse (i.e. the secondaryItem can be clicked and that toggles the bookmark status as expected). It’s only the unit tests that are failing. I’m suspecting that the way QtTest simulates a mouse click event doesn’t play well with Ubuntu.Mouse.forwardTo, although I’m not really sure how and why. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1483279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483279] Re: Unit tests fail where mouseClick() is used to simulate a click event on a MouseArea which is a descendant of a TextField
** Branch linked: lp:~osomon/webbrowser-app/uitk-1.3 -- 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/1483279 Title: Unit tests fail where mouseClick() is used to simulate a click event on a MouseArea which is a descendant of a TextField Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: This appears to be a regression in version 1.3 of the UITK. The browser has an AddressBar component which contains a TextField, and the secondaryItem for this TextField is a MouseArea (for toggling the bookmarked status of the current address). This component is unit tested, and there is a test that simulates a click on the secondaryItem to verify that the bookmarked status is correctly toggled. This test worked with version 1.2 of the UITK, but fails when I update the import of Ubuntu.Components to 1.3. It appears that the TextField itself intercepts the simulated mouse click event, thus getting active focus. Note that the component works as expected when used in an app by a normal user manipulating a mouse (i.e. the secondaryItem can be clicked and that toggles the bookmark status as expected). It’s only the unit tests that are failing. I’m suspecting that the way QtTest simulates a mouse click event doesn’t play well with Ubuntu.Mouse.forwardTo, although I’m not really sure how and why. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1483279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471338] Re: sometimes phone never wakes up or rings on incoming call
** Changed in: ofono (Ubuntu) Status: Confirmed = Incomplete -- 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/1471338 Title: sometimes phone never wakes up or rings on incoming call Status in Canonical System Image: Confirmed Status in ofono package in Ubuntu: Incomplete Status in telephony-service package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Bug description: testing on krilin build 56 vivid+overlay latest dual sims installed The problem is sometimes during an incoming call the phone never wakes up or rings at all (and no snap decision). From the remote end the call just continues to ring and eventually goes to voicemail. When this occurs the signal strength appears to have at least 3 bars. It seems ofono is not notifying the upper layers that a call is incoming. This can be verifed by running the following command: dbus-monitor --system | grep CallAdded This never gets fired during error condition when the incoming call is ringing from remote end. Attached is the ofono log when I got it to happen once (not sure where in the log corresponds to the failure) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483338] [NEW] /usr/lib/arm-linux-gnueabihf/address-book-service/address-book-service:11:QString::operator:galera::AddressBook::updateContactsDone:galera::AddressBook::qt_static_
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding address-book-service. This problem was most recently seen with version 0.1.1+15.04.20150214~rtm-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3a15cdb6b4b4026ef5ee11c40169b22411be55a0 contains more details. ** Affects: address-book-service (Ubuntu) Importance: Undecided Status: New ** Tags: rtm-14.09 vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-service in Ubuntu. https://bugs.launchpad.net/bugs/1483338 Title: /usr/lib/arm-linux-gnueabihf/address-book-service/address-book- service:11:QString::operator:galera::AddressBook::updateContactsDone:galera::AddressBook::qt_static_metacall:QMetaMethod::invoke:invoke Status in address-book-service package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding address-book-service. This problem was most recently seen with version 0.1.1+15.04.20150214~rtm-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3a15cdb6b4b4026ef5ee11c40169b22411be55a0 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-service/+bug/1483338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483331] Re: Minimum window dimensions
** Description changed: We need to have a story for minimum window dimensions. Apps shouldn't shrink smaller than their contents can reasonably adapt. The UI toolkit gallery itself is an example of it, at a certain width the window clips components at the right side. + + I'd like to suggest we have a default approach in AdaptivePageLayout so + apps don't need to deal with the window. -- 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/1483331 Title: Minimum window dimensions Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: We need to have a story for minimum window dimensions. Apps shouldn't shrink smaller than their contents can reasonably adapt. The UI toolkit gallery itself is an example of it, at a certain width the window clips components at the right side. I'd like to suggest we have a default approach in AdaptivePageLayout so apps don't need to deal with the window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1483331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483368] [NEW] Saned deamon not running
Public bug reported: With Kubuntu 15.10 I never could get saned deamon installed. Consecuently it is not possible to install a scanner on the lan though this usb scanner works fine with xsane on th computer where the usb is plugged. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1483368 Title: Saned deamon not running Status in xorg package in Ubuntu: New Bug description: With Kubuntu 15.10 I never could get saned deamon installed. Consecuently it is not possible to install a scanner on the lan though this usb scanner works fine with xsane on th computer where the usb is plugged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1483368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482593] [NEW] Mobile Browser shows white screen instead of the webpage
You have been subscribed to a public bug: On ubuntu phone, after the last update the Mobile Browser behaves in a strange way. Sometimes, while scrolling down the page just goes completely white (no content is shown). The only thing that helps is to close the tab and then open the same webpage once again. If I rotate the screen the browser turns ok (as normal), but the page is still white and no content is shown. If I would swipe the bottom part of the screen (like for opening a new tab) I can still see the name of the tab (webpage), but no content is shown, if I try to reopen the tab by tapping on it then the content blinks for a fraction of the second and then the screen is white again and I can not see the content (just like before). It appears very often on 9gag.com and I also get it each time when I open a page on lyricsmode.com I also got it several times on other random websites. It's an ubuntu 15.04 OS build number 24 ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment browser mobile phone -- Mobile Browser shows white screen instead of the webpage https://bugs.launchpad.net/bugs/1482593 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app 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 1482593] Re: Mobile Browser shows white screen instead of the webpage
*** This bug is a duplicate of bug 1478853 *** https://bugs.launchpad.net/bugs/1478853 ** Package changed: ubuntu = webbrowser-app (Ubuntu) -- 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/1482593 Title: Mobile Browser shows white screen instead of the webpage Status in webbrowser-app package in Ubuntu: New Bug description: On ubuntu phone, after the last update the Mobile Browser behaves in a strange way. Sometimes, while scrolling down the page just goes completely white (no content is shown). The only thing that helps is to close the tab and then open the same webpage once again. If I rotate the screen the browser turns ok (as normal), but the page is still white and no content is shown. If I would swipe the bottom part of the screen (like for opening a new tab) I can still see the name of the tab (webpage), but no content is shown, if I try to reopen the tab by tapping on it then the content blinks for a fraction of the second and then the screen is white again and I can not see the content (just like before). It appears very often on 9gag.com and I also get it each time when I open a page on lyricsmode.com I also got it several times on other random websites. It's an ubuntu 15.04 OS build number 24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1482593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482593] Re: Mobile Browser shows white screen instead of the webpage
*** This bug is a duplicate of bug 1478853 *** https://bugs.launchpad.net/bugs/1478853 ** This bug has been marked a duplicate of bug 1478853 OOM scoring kills the browser's render process while the browser is running -- 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/1482593 Title: Mobile Browser shows white screen instead of the webpage Status in webbrowser-app package in Ubuntu: New Bug description: On ubuntu phone, after the last update the Mobile Browser behaves in a strange way. Sometimes, while scrolling down the page just goes completely white (no content is shown). The only thing that helps is to close the tab and then open the same webpage once again. If I rotate the screen the browser turns ok (as normal), but the page is still white and no content is shown. If I would swipe the bottom part of the screen (like for opening a new tab) I can still see the name of the tab (webpage), but no content is shown, if I try to reopen the tab by tapping on it then the content blinks for a fraction of the second and then the screen is white again and I can not see the content (just like before). It appears very often on 9gag.com and I also get it each time when I open a page on lyricsmode.com I also got it several times on other random websites. It's an ubuntu 15.04 OS build number 24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1482593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334860] [NEW] EmergencyNumbers not correctly filled for brazilian operators
You have been subscribed to a public bug: Using a SIM card from VIVO, I get the following list of emergency numbers: [ org.ofono.VoiceCallManager ] EmergencyNumbers = 08 000 999 110 112 911 118 119 And on a SIM card from OI, the same list is returned: [ org.ofono.VoiceCallManager ] EmergencyNumbers = 08 000 999 110 112 911 118 119 But those are not the emergency numbers for Brazil, they should be similar to the numbers listed in ServiceNumbers: [ org.ofono.SimManager ] ServiceNumbers = [Ambulancia] = '192' [Defesa Civil] = '199' [Policia] = '190' [Bombeiros] = '193' ** Affects: telephony-service (Ubuntu) Importance: High Assignee: Tiago Salem Herrmann (tiagosh) Status: In Progress ** Tags: emergency -- EmergencyNumbers not correctly filled for brazilian operators https://bugs.launchpad.net/bugs/1334860 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service 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 1483010] Re: Add a C wrapper
Well that's unfortunate :( And I agree with the last sentence, I forgot about the virtual functions, which make it so complicated. -- 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/1483010 Title: Add a C wrapper Status in unity-scopes-api package in Ubuntu: New Bug description: libunity-scopes has the potential to have bindings for a lot of programming languages (there are already a few). It would be much easier if the library provided a C API, and it's relatively easy to add To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1483010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449778] Re: [dialer-app] + [messaging-app] remove pop up asking to select a SIM
** Branch linked: lp:~tiagosh/messaging-app/update-sim-dialogs -- 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/1449778 Title: [dialer-app] + [messaging-app] remove pop up asking to select a SIM Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: New Status in messaging-app package in Ubuntu: New Bug description: krillin vivid and RTM Current behaviour: If the device has both SIM slots occupied, users are asked on action to select a SIM card for either placing a phone call or sending a text message. This can be very annoying for users because on first time launch there is a different pop up asking a similar question and explaining to users where to amend their default SIM for outgoing communication. --UX comment-- The desired solution is to change the text of the popup on first time launch and remove the popup on action. A 3rd popup appears on the dialer app after user made a phone call and didn't select a default SIM. This should be removed as well. The SIM card in the first SIM slot should be selected by default and the first popup will inform users where to alter the selection and change the default SIM for outgoing communication. Please follow guidance in this spec: https://docs.google.com/document/d/1BRy9-DEXr3A1D7PHkJaXmjbe7xbRmxKkzANXuu-F6lc/edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1449778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1248642] Re: dynamic library inconsistencies with OpenGL/C++
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glibc (Ubuntu Trusty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1248642
Title:
dynamic library inconsistencies with OpenGL/C++
Status in binutils package in Ubuntu:
Fix Released
Status in glibc package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-319 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-331 package in Ubuntu:
Confirmed
Status in binutils source package in Trusty:
Fix Released
Status in glibc source package in Trusty:
Confirmed
Status in nvidia-graphics-drivers-319 source package in Trusty:
Confirmed
Status in nvidia-graphics-drivers-331 source package in Trusty:
Confirmed
Status in binutils package in Debian:
Fix Released
Bug description:
While using the nvidia-319 driver, the following C++ program won't
run:
$ cat test.cpp EOF
#include string
#include GL/gl.h
int main(int argc, char *argv[]) {
std::string s;
glEnable(GL_LIGHT0);
}
EOF
Instead, it fails with the following error message:
$ g++ test.cpp -lGL
$ ./a.out
Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions:
Assertion `needed != ((void *)0)' failed!
Using the xserver-xorg-video-nouveau driver, the problem does not
occur. Also, when std::string is not used, the program runs without
problems. Using OpenGL from pure C programs is also not a problem. The
problem can be reproduced with both g++-4.6 and g++-4.8.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: nvidia-319 319.32-0ubuntu7
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: openafs nvidia
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Wed Nov 6 18:25:48 2013
InstallationDate: Installed on 2013-11-01 (5 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64
(20131017)
MarkForUpload: True
SourcePackage: nvidia-graphics-drivers-319
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.modprobe.d.nvidia.319.hybrid.conf: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1248642/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482990] Re: ld -lpython3.4 failed
** Changed in: python3.4 (Ubuntu) Status: New = Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/python3.4/+question/270210 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1482990 Title: ld -lpython3.4 failed Status in python3.4 package in Ubuntu: Invalid Bug description: #ld -lpython3.4 --verbose attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.so failed attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.a failed attempt to open //usr/local/lib32/libpython3.4.so failed attempt to open //usr/local/lib32/libpython3.4.a failed attempt to open //lib32/libpython3.4.so failed attempt to open //lib32/libpython3.4.a failed attempt to open //usr/lib32/libpython3.4.so failed attempt to open //usr/lib32/libpython3.4.a failed attempt to open //usr/local/lib/i386-linux-gnu/libpython3.4.so failed attempt to open //usr/local/lib/i386-linux-gnu/libpython3.4.a failed attempt to open //usr/local/lib/libpython3.4.so failed attempt to open //usr/local/lib/libpython3.4.a failed attempt to open //lib/i386-linux-gnu/libpython3.4.so failed attempt to open //lib/i386-linux-gnu/libpython3.4.a failed attempt to open //lib/libpython3.4.so failed attempt to open //lib/libpython3.4.a failed attempt to open //usr/lib/i386-linux-gnu/libpython3.4.so failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1482990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482433] Re: ubunt-bug aborts
Let's try and troubleshoot the specific problem of ubuntu-bug not working. Could you please describe in more detail from where you were trying to use ubuntu-bug and provide the exact command that you were using? e.g. ubuntu-bug apport would be used to report a bug about apport. ** Package changed: ubuntu = apport (Ubuntu) ** Changed in: apport (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1482433 Title: ubunt-bug aborts Status in apport package in Ubuntu: Incomplete Bug description: In a lot of places we are told to use ubunt-bug to trip apport to send bugged information somewhere. When you use the said app, it panics and exits out, not reporting anything. It produces no error code. I tried two different ways to report a kde-session bug and got thrown back to a terminal one time and told I was using non-standard X packages another time, which is an outright LIE as I am using kubuntu live media(14.04.3). Users will find this application difficult to use and therefore either not use it or not know where to turn to file bugs. Launchpad is suggested but filing a launchpad bug is bugged in itself.(another bug report) Then there is the method using errors.ubuntu.com instead of launchpad. The reporting method and such needs to be more centralized and standardized.There is no reason why errors have to sent in seperately, they can be attached to launchpad reports. Asking a user to reboot after updating is pointless on a live cd. It accomplishes nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1482433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1476433] Re: invisible pointer on boot
this does not happen in gnome. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1476433 Title: invisible pointer on boot Status in lightdm package in Ubuntu: New Status in xfce4-settings package in Ubuntu: New Bug description: Upon login to xfce, there is a pointer (as evidenced by right clicking with the touch pad) but it is invisible. Plugging a mouse in makes the pointer visible again. xfce: 4.12.1 ubuntu: wily werewolf [60.751] (**) ETPS/2 Elantech Touchpad: Applying InputClass evdev touchpad catchall [60.751] (**) ETPS/2 Elantech Touchpad: Applying InputClass touchpad catchall [60.751] (**) ETPS/2 Elantech Touchpad: Applying InputClass Default clickpad buttons [60.751] (II) LoadModule: synaptics [60.751] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xfce4 4.12.1 Uname: Linux 4.1.0-040100rc1-generic x86_64 ApportVersion: 2.18-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 20:02:19 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (376 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140708) PackageArchitecture: all SourcePackage: xfce4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1476433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
We should get sign off on this from the ubuntu-devel mailing list before making this change, as it changes behaviour. The new behaviour makes sense, as there does not seem to be an advantage to blanking the screen like this, but there might be some people who object -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: In Progress Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482433] [NEW] ubunt-bug aborts
You have been subscribed to a public bug: In a lot of places we are told to use ubunt-bug to trip apport to send bugged information somewhere. When you use the said app, it panics and exits out, not reporting anything. It produces no error code. I tried two different ways to report a kde-session bug and got thrown back to a terminal one time and told I was using non-standard X packages another time, which is an outright LIE as I am using kubuntu live media(14.04.3). Users will find this application difficult to use and therefore either not use it or not know where to turn to file bugs. Launchpad is suggested but filing a launchpad bug is bugged in itself.(another bug report) Then there is the method using errors.ubuntu.com instead of launchpad. The reporting method and such needs to be more centralized and standardized.There is no reason why errors have to sent in seperately, they can be attached to launchpad reports. Asking a user to reboot after updating is pointless on a live cd. It accomplishes nothing. ** Affects: apport (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment -- ubunt-bug aborts https://bugs.launchpad.net/bugs/1482433 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport 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 1248642] Re: dynamic library inconsistencies with OpenGL/C++
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glibc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1248642
Title:
dynamic library inconsistencies with OpenGL/C++
Status in binutils package in Ubuntu:
Fix Released
Status in glibc package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-319 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-331 package in Ubuntu:
Confirmed
Status in binutils source package in Trusty:
Fix Released
Status in glibc source package in Trusty:
Confirmed
Status in nvidia-graphics-drivers-319 source package in Trusty:
Confirmed
Status in nvidia-graphics-drivers-331 source package in Trusty:
Confirmed
Status in binutils package in Debian:
Fix Released
Bug description:
While using the nvidia-319 driver, the following C++ program won't
run:
$ cat test.cpp EOF
#include string
#include GL/gl.h
int main(int argc, char *argv[]) {
std::string s;
glEnable(GL_LIGHT0);
}
EOF
Instead, it fails with the following error message:
$ g++ test.cpp -lGL
$ ./a.out
Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions:
Assertion `needed != ((void *)0)' failed!
Using the xserver-xorg-video-nouveau driver, the problem does not
occur. Also, when std::string is not used, the program runs without
problems. Using OpenGL from pure C programs is also not a problem. The
problem can be reproduced with both g++-4.6 and g++-4.8.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: nvidia-319 319.32-0ubuntu7
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: openafs nvidia
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Wed Nov 6 18:25:48 2013
InstallationDate: Installed on 2013-11-01 (5 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64
(20131017)
MarkForUpload: True
SourcePackage: nvidia-graphics-drivers-319
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.modprobe.d.nvidia.319.hybrid.conf: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1248642/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1478115] Re: running whoopsie during tests causes test failures
Martin - Thanks for fixing this. Do you have any more information about whoopsie-upload-all crashing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1478115 Title: running whoopsie during tests causes test failures Status in apport package in Ubuntu: Fix Released Bug description: I've switched the apport-noui.path systemd file from: PathChanged=/var/crash to PathExistsGlob=/var/crash/*.crash I've done this because with PathChanged it seemed to me that the whoopsie-upload-all, called by apport-noui.service, would be called when any file (e.g. .upload, .uploaded) were created in /var/crash. Naturally, this seemed excessive to me and PathExistsGlob seems like a better fit. Additionally, it is worth noting that the following from the systemd.path documentation: If a path already exists (in case of PathExists= and PathExistsGlob=) or a directory already is not empty (in case of DirectoryNotEmpty=) at the time the path unit is activated, then the configured unit is immediately activated as well. Something similar does not apply to PathChanged= and PathModified=. Given that it appears with PathChanged the apport-noui service would never be run during boot up, again not what we want. However, making these changes seems to have caused some strange test failures with the apport's tests. https://jenkins.qa.ubuntu.com/job/wily-adt-apport/ runs 47 through 55 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1478115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334860] Re: EmergencyNumbers not correctly filled for brazilian operators
** Package changed: ofono (Ubuntu) = telephony-service (Ubuntu) ** Changed in: telephony-service (Ubuntu) Status: Incomplete = In Progress ** Changed in: telephony-service (Ubuntu) Assignee: Gustavo Pichorim Boiko (boiko) = Tiago Salem Herrmann (tiagosh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1334860 Title: EmergencyNumbers not correctly filled for brazilian operators Status in telephony-service package in Ubuntu: In Progress Bug description: Using a SIM card from VIVO, I get the following list of emergency numbers: [ org.ofono.VoiceCallManager ] EmergencyNumbers = 08 000 999 110 112 911 118 119 And on a SIM card from OI, the same list is returned: [ org.ofono.VoiceCallManager ] EmergencyNumbers = 08 000 999 110 112 911 118 119 But those are not the emergency numbers for Brazil, they should be similar to the numbers listed in ServiceNumbers: [ org.ofono.SimManager ] ServiceNumbers = [Ambulancia] = '192' [Defesa Civil] = '199' [Policia] = '190' [Bombeiros] = '193' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1334860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481913] Re: UI volume warnings need revision
This bug was fixed in the package indicator-sound - 12.10.2+15.10.20150807.6-0ubuntu1 --- indicator-sound (12.10.2+15.10.20150807.6-0ubuntu1) wily; urgency=medium [ CI Train Bot ] * New rebuild forced. [ Charles Kerr ] * Revised UI volume warnings to comply with EU requirements. (LP: #1481913) -- CI Train Bot ci-train-...@canonical.com Fri, 07 Aug 2015 22:35:58 + ** Changed in: indicator-sound (Ubuntu) Status: Confirmed = Fix Released -- 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/1481913 Title: UI volume warnings need revision Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Fix Released Bug description: As raised in OEM bug #1474364 (the title there is poor), the warning scheme used by Ubuntu does not currently follow the letter of the EU regulations for mobile devices (it seems to follow the spirit). Design have now reviewed the regulations (bug #1480912), and propose: https://wiki.ubuntu.com/Sound#limits This is the diff: https://wiki.ubuntu.com/Sound?action=diffrev2=146rev1=145 The UI notification scheme needs to be updated to match the new design. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480877] Re: Access points' PropertiesChanged dbus signals freeze UI on mobile devices
@awe I'm sorry if the two things are mixing up :( I should probably file another bug for the connection loop... When I filed this bug the softAP didn't exist yet, so that can't have been the cause. We have two (related) problems here: 1) when you're in an area with many access points, many PropertiesChanged signals are fired and they slow down the device for 2-3 seconds 2) when NM gets stuck connecting to a network which doesn't exist, PropertiesChanged signals are fired in an endless loop (well, it pauses 2-3 secs every time before firing all signals again) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' PropertiesChanged dbus signals freeze UI on mobile devices Status in indicator-network package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: Krillin, rc-proposed, r83 DESCRIPTION: I've been trying to track down the cause of the occasional UI freezes on my Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I get a burst of PropertiesChanged signals in dbus-monitor Here's a log of what's shown in dbus-monitor: http://pastebin.ubuntu.com/11992322/ I'd guess the problem is in the code that actually catches the signals and acts accordingly. HOW TO REPRODUCE: 1) Move to a place where many wifi hotspots are available 2) Connect the device via USB and run phablet-shell and then dbus-monitor 3) Use the device while keeping an eye on dbus-monitor output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1480877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483388] [NEW] Boot gets stuck at purple Ubuntu .... screen forever if running from battery
Public bug reported: I am not sure at all what package this bug is; I report it against Unity because I get to see the purple screen... Steps to reproduce: - turn on the laptop while not connected to AC power, but with more than enough battery charge (tested with battery completely charged) Expected result: should boot fine Observed result: When the purple Ubuntu loading screen appears and the four dots below the word Ubuntu are all filled in red, the system gets stuck at that screen for fucking ever. No matter how many times I retry, it will always remain stuck there. If I connect the charger and reboot, then it works fine. This REGRESSION has appeared after some recent automatic updates. This didn't use to happen before. I had booted with battery power thousands of time, though it's not something that I do very often so i can't tell exactly when the regression appeared. Before the purple screen appears, for a fraction of a second I've been able to see a black screen full of messages, probably error messages, while normally (when boot works fine) there would only be one usb-related error message. Please let me know from which log I can retrieve those error messages so that I can post them here. Don't tell me to update the bios, because this used to work on the very same machine, so the issue is obviously in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.5+14.04.20150603-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Aug 10 21:15:32 2015 InstallationDate: Installed on 2013-10-11 (668 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (443 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1483388 Title: Boot gets stuck at purple Ubuntu screen forever if running from battery Status in unity package in Ubuntu: New Bug description: I am not sure at all what package this bug is; I report it against Unity because I get to see the purple screen... Steps to reproduce: - turn on the laptop while not connected to AC power, but with more than enough battery charge (tested with battery completely charged) Expected result: should boot fine Observed result: When the purple Ubuntu loading screen appears and the four dots below the word Ubuntu are all filled in red, the system gets stuck at that screen for fucking ever. No matter how many times I retry, it will always remain stuck there. If I connect the charger and reboot, then it works fine. This REGRESSION has appeared after some recent automatic updates. This didn't use to happen before. I had booted with battery power thousands of time, though it's not something that I do very often so i can't tell exactly when the regression appeared. Before the purple screen appears, for a fraction of a second I've been able to see a black screen full of messages, probably error messages, while normally (when boot works fine) there would only be one usb-related error message. Please let me know from which log I can retrieve those error messages so that I can post them here. Don't tell me to update the bios, because this used to work on the very same machine, so the issue is obviously in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.5+14.04.20150603-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Aug 10 21:15:32 2015 InstallationDate: Installed on 2013-10-11 (668 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (443 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1483388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444162] Re: IPv6 default route present on ccmni0, even though no address assigned
** Changed in: network-manager (Ubuntu) Assignee: (unassigned) = Tony Espy (awe) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1444162 Title: IPv6 default route present on ccmni0, even though no address assigned Status in Canonical System Image: New Status in network-manager package in Ubuntu: Confirmed Bug description: $ system-image-cli -i current build number: 171 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-14 22:23:10 version version: 171 Upon boot, my v6 routes include a default via ccmni0: $ ip -6 route fe80::/64 dev wlan0 proto kernel metric 256 default dev ccmni0 proto static metric 1024 Even though there's no v6 address on the device: $ ip -6 addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 10: wlan0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 fe80::3abc:1aff:fe18:b68b/64 scope link valid_lft forever preferred_lft forever This means that hosts that have v6 addresses are tried to be reached via v6, which obviously fails: 29% [Connecting to ports.ubuntu.com (2001:67c:1360:8001::18)] Toggling GSM data loses the default route: $ ip -6 route fe80::/64 dev wlan0 proto kernel metric 256 And the connection succeeds via v4. Attached find a set of logs from network-test-session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu13 Uname: Linux 3.10.35+ armv7l ApportVersion: 2.17-0ubuntu2 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Apr 14 23:45:11 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2015-04-14 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150414-020204) IpRoute: default via 10.2.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 via 10.2.0.1 dev wlan0 proto dhcp metric 10 10.2.0.0/24 dev wlan0 proto kernel scope link src 10.2.0.66 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: SourcePackage: network-manager SystemImageInfo: current build number: 171 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-14 22:23:10 version version: 171 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 2015-04-14T04:33:56 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1444162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1426362] Re: logind session files fill up /run space
I'm noticing this as an issue as well. My scenario is in using Fabric or Ansible to do deployments. A large number of these dangling SSH files are in the /run/systemd/sessions/ folder and eventually cause the out of disk space issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1426362 Title: logind session files fill up /run space Status in systemd-shim package in Ubuntu: New Bug description: Under Ubuntu 14.10 (server), systemd fills up /run/systemd/sessions directory with files. The files are 240-260 bytes, but there are many As per default install, /run is on tmpfs with 50 MB size. After a couple of days, /run/ runs out of free space, which can cause not so funny errors, like failed kernel update (kernel postinst tries to create files here, then fails) As I see, thesefiles are releated to ssh sesssions, and yes there are plenty SSH connection to this host. Shouldn't systemd remove these old session files? # lsb_release -rd Description:Ubuntu 14.10 Release:14.10 # apt-cache policy systemd systemd: Installed: 208-8ubuntu8.2 Candidate: 208-8ubuntu8.2 Version table: *** 208-8ubuntu8.2 0 500 http://hu.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 Packages 100 /var/lib/dpkg/status 208-8ubuntu8 0 500 http://hu.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1426362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444162] Re: IPv6 default route present on ccmni0, even though no address assigned
** Changed in: network-manager (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1444162 Title: IPv6 default route present on ccmni0, even though no address assigned Status in Canonical System Image: New Status in network-manager package in Ubuntu: In Progress Bug description: $ system-image-cli -i current build number: 171 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-14 22:23:10 version version: 171 Upon boot, my v6 routes include a default via ccmni0: $ ip -6 route fe80::/64 dev wlan0 proto kernel metric 256 default dev ccmni0 proto static metric 1024 Even though there's no v6 address on the device: $ ip -6 addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 10: wlan0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 fe80::3abc:1aff:fe18:b68b/64 scope link valid_lft forever preferred_lft forever This means that hosts that have v6 addresses are tried to be reached via v6, which obviously fails: 29% [Connecting to ports.ubuntu.com (2001:67c:1360:8001::18)] Toggling GSM data loses the default route: $ ip -6 route fe80::/64 dev wlan0 proto kernel metric 256 And the connection succeeds via v4. Attached find a set of logs from network-test-session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu13 Uname: Linux 3.10.35+ armv7l ApportVersion: 2.17-0ubuntu2 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Apr 14 23:45:11 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2015-04-14 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150414-020204) IpRoute: default via 10.2.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 via 10.2.0.1 dev wlan0 proto dhcp metric 10 10.2.0.0/24 dev wlan0 proto kernel scope link src 10.2.0.66 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: SourcePackage: network-manager SystemImageInfo: current build number: 171 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-14 22:23:10 version version: 171 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 2015-04-14T04:33:56 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1444162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1466656] Re: [UbuntuShape] Rendering is aliased sometimes since the Shell implements the orientation
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1466656 Title: [UbuntuShape] Rendering is aliased sometimes since the Shell implements the orientation Status in Canonical System Image: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: $ adb shell system-image-cli --info current build number: 23 device name: krillin channel: ubuntu-touch/stable/bq-aquaris.en last update: 2015-06-15 19:22:22 version version: 23 version ubuntu: 20150611.3 version device: 20150529-8e13c5f version custom: 20150528-722-29-15-vivid Steps to reproduce:- 1. Swipe down indicators 2. Rotation 3. Switch rotation lock _off_, that is X 4. Hold phone in portrait and navigate to the top of the apps scope Observe normal icons 5. Rotate phone 90 degrees to landscape, pull the scope down (to the side) slightly to force a re-draw Observe poor anti-aliasing around the ubuntu shapes. Two screenshots attached. device-2015-06-18-220419.png - portait device-2015-06-18-220428.png - landscape The effect is most noticable if you open both of the attachments full- size and switch between them. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1466656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428779] Re: [SDK] Tooltips
Wrong status for Ubuntu UX - it is in progress and not won't fix! -- 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/1428779 Title: [SDK] Tooltips Status in Ubuntu UI Toolkit: New Status in Ubuntu UX: Won't Fix Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: Point Click UIs will need a tooltip component, positioning a popover next to the cursor when Hovering the originating component UX here Currently work in progress to go into the SDK project: https://docs.google.com/document/d/1a8KvcVkmYKxL42wgIRjUGo2xpXfdFvV3npETxcsG3UU/edit https://canonical.leankit.com/Boards/View/109386535/116403130 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445595] Re: Empty Trash Results in File Windows Opening
how do we repair this bug? -- 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/1445595 Title: Empty Trash Results in File Windows Opening Status in One Hundred Papercuts: New Status in Unity: New Status in nautilus package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: *Test case: Add a file to trash if none already Right click on Unity launcher trash icon click on Empty Trash option nautilus open a window @ home folder. When selecting 'empty trash' from the launcher I get a dialog to confirm the deletion and a file window. When emptying trash from nautilus window only get confirmation dialog as expected. Expected behavior: - Only confirm dialog pop up. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1445595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482317] Re: Unify code that turns screen on when a notification happens
Nevermind, I was confused by ubuntu-push not actually emitting a
displayable notification (one with popup=true on its card) when the
greeter is up. Which obscured my testing. It's an odd decision (to
me), but is a separate issue.
An MR is coming for this.
--
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/1482317
Title:
Unify code that turns screen on when a notification happens
Status in unity8 package in Ubuntu:
New
Bug description:
Right now, there are several places we ask USC to turn the screen on
when a notification happens:
- powerd for SMS, USSD, and incoming calls
- telephony-service for MMS and telephony messages
And we don't seem to be turning them on for ubuntu-push notifications,
but we should, right? Following the pattern above, we'd have ubuntu-
push itself turn the screen on, for a third location.
We don't turn the screen on at all for notifications that don't come
via those sources. For example, the following command line doesn't
turn the screen on, but I think it should:
gdbus call --session --dest org.freedesktop.Notifications --object-
path /org/freedesktop/Notifications --method
org.freedesktop.Notifications.Notify '' 0 '' 'Hello' 'World' '[]' '{}'
0
It feels weird to have telephony-service turning the screen on.
Logically, it is just emitting a notification. The presentation of
that notification is up to a higher layer (maybe we're on a raspberry
pi2 and we present notifications as LED morse code or whatever). It
just makes sense that unity8, which is drawing the notification, is
the one that knows that the screen needs to be on. It also knows what
form factor we are in (I assume we only want to turn screen on for
phones/tablets, not desktops).
So I'm proposing that we unify all those places into one code path in
unity8 that can turn the screen on when a notification is received.
(This is a breakout bug from bug 1426115.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1482317/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483427] [NEW] Possible to manually set display brightness to 0 on Ubuntu Touch
Public bug reported: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch Status in indicator-power package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1468130] Re: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:11:Change:QVector:resize:pop:QAbstractItemModel::endMoveRows
** Changed in: ubuntu-ui-toolkit (Ubuntu) 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/1468130 Title: /usr/lib/arm-linux- gnueabihf/qt5/bin/qmlscene:11:Change:QVector:resize:pop:QAbstractItemModel::endMoveRows Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding qtdeclarative-opensource-src. This problem was most recently seen with version 5.4.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/8cb1515635eda3760f6f6921d5418aa7eb454352 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1468130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471029] Re: ELF programs with R_386_RELATIVE blocks are badly mapped into memory
** Changed in: libxslt (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxslt in Ubuntu. https://bugs.launchpad.net/bugs/1471029 Title: ELF programs with R_386_RELATIVE blocks are badly mapped into memory Status in libxslt package in Ubuntu: Triaged Status in linux package in Ubuntu: Triaged Bug description: Running the Samba autobuild tests on a 15.04 openstack image results in a segfault in this command: /usr/bin/xsltproc --nonet -o default/docs-xml/manpages/smb.conf.5 /home/ubuntu/autobuild/b22271/samba/docs-xml/xslt/man.xsl default /docs-xml/manpages/smb.conf.5.xml I reported this upstream as a bug in xsltproc, but it was found to be impossible to reproduce using upstream source on the openstack instance: https://bugzilla.gnome.org/show_bug.cgi?id=751764 Comment 8 (https://bugzilla.gnome.org/show_bug.cgi?id=751764#c8) is particularly informative. The stack trace below shows the segfault actually occurs in libxml's xpath evaluation functions. I see no difference between xpath.c in upstream 2.9.2 and Ubuntu's version. (gdb) bt 12 #0 0xb760f874 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc818) at ../../xpath.c:13606 #1 0xb760f82e in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc890) at ../../xpath.c:13598 #2 0xb7610244 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc8b8) at ../../xpath.c:13529 #3 0xb760f9d6 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc8e0) at ../../xpath.c:13977 #4 0xb7612735 in xmlXPathCompOpEval (op=optimized out, ctxt=0xba25d3e8) at ../../xpath.c:14552 #5 xmlXPathRunEval (ctxt=0xba25d3e8, toBool=optimized out) at ../../xpath.c:14552 #6 0xb76171ed in xmlXPathCompiledEvalInternal (toBool=0, resObj=synthetic pointer, ctxt=optimized out, comp=optimized out) at ../../xpath.c:14915 #7 xmlXPathCompiledEval__internal_alias (comp=0xb866a948, ctx=0xb99bd308) at ../../xpath.c:14978 #8 0xb7787260 in xsltEvalVariable (ctxt=ctxt@entry=0xb9836560, variable=variable@entry=0xba25d3b0, castedComp=0xb86a4238) at ../../../libxslt/variables.c:903 #9 0xb778759a in xsltBuildVariable (ctxt=0xb9836560, castedComp=0xb86a4238, tree=0xb86a6978) at ../../../libxslt/variables.c:1759 #10 0xb7788bfa in xsltParseStylesheetCallerParam (ctxt=0xb86a6978, inst=0xb86a6978) at ../../../libxslt/variables.c:1975 #11 0xb779b9db in xsltCallTemplate (ctxt=0xb9836560, node=0xb85efed8, inst=0xb86a6880, castedComp=0xb86a4148) at ../../../libxslt/transform.c:4739 (More stack frames follow...) (gdb) bt -5 #3311 0xb779a7de in xsltProcessOneNode (ctxt=0xb9836560, contextNode=0xb97586a0, withParams=0x0) at ../../../libxslt/transform.c:2097 #3312 0xb779d818 in xsltApplyStylesheetInternal (style=0xba25d3e8, style@entry=0xb85ee200, doc=0xb86bc7f0, doc@entry=0xb97586a0, params=0xb77ed340 params, output=0xb85e13e0 default/docs-xml/manpages/smb.conf.5, profile=0x0, userCtxt=0xb9836560) at ../../../libxslt/transform.c:6159 #3313 0xb779df8d in xsltRunStylesheetUser (style=0xb85ee200, doc=0xb97586a0, params=0xb77ed340 params, output=0xb85e13e0 default/docs-xml/manpages/smb.conf.5, SAX=0x0, IObuf=0x0, profile=0x0, userCtxt=0xb9836560) at ../../../libxslt/transform.c:6449 #3314 0xb77ea12c in xsltProcess (doc=0xb97586a0, cur=0xb85ee200, filename=0xbfd59812 default/docs-xml/manpages/smb.conf.5.xml) at ../../../xsltproc/xsltproc.c:483 #3315 0xb77e9298 in main (argc=6, argv=0xbfd58f94) at ../../../xsltproc/xsltproc.c:903 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 9 00:13 seq crw-rw 1 root audio 116, 33 Jul 9 00:13 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 15.04 Ec2AMI: ami-012b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nz-por-1a Ec2InstanceType: c1.c4r4 Ec2Kernel: aki-0005 Ec2Ramdisk: ari-0005 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 3.19.0-20.20-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A
[Touch-packages] [Bug 1477445] Re: _nl_get_vtable: assertion 'vtable.handle' failed
** Changed in: network-manager (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1477445 Title: _nl_get_vtable: assertion 'vtable.handle' failed Status in network-manager package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl this is also met on https://bugzilla.redhat.com/show_bug.cgi?id=1211859 an upstream fix is available http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=d767fb160c36bd9dc339e343ebac58274204ad4f Please import that upstream fix ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 0.9.10.0-4ubuntu18 ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3 Uname: Linux 4.1.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu3 Architecture: i386 CurrentDesktop: GNOME Date: Thu Jul 23 10:17:41 2015 IpRoute: default via 192.168.1.1 dev eth1 proto static metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.1.0/24 dev eth1 proto kernel scope link metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-06-13T08:56:31.598901 nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 7086b2ff-1446-45fe-b8f3-cd333cd4cee1 802-3-ethernet 1437639256 jeu. 23 juil. 2015 10:14:16 CEST yes no /org/freedesktop/NetworkManager/Settings/0 yes eth1activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH eth1ethernet connected/org/freedesktop/NetworkManager/Devices/2 Wired connection 1 7086b2ff-1446-45fe-b8f3-cd333cd4cee1 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1477445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482317] Re: Unify code that turns screen on when a notification happens
** Branch linked: lp:~mterry/unity8/turn-on-screen-when-notifying
--
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/1482317
Title:
Unify code that turns screen on when a notification happens
Status in unity8 package in Ubuntu:
New
Bug description:
Right now, there are several places we ask USC to turn the screen on
when a notification happens:
- powerd for SMS, USSD, and incoming calls
- telephony-service for MMS and telephony messages
And we don't seem to be turning them on for ubuntu-push notifications,
but we should, right? Following the pattern above, we'd have ubuntu-
push itself turn the screen on, for a third location.
We don't turn the screen on at all for notifications that don't come
via those sources. For example, the following command line doesn't
turn the screen on, but I think it should:
gdbus call --session --dest org.freedesktop.Notifications --object-
path /org/freedesktop/Notifications --method
org.freedesktop.Notifications.Notify '' 0 '' 'Hello' 'World' '[]' '{}'
0
It feels weird to have telephony-service turning the screen on.
Logically, it is just emitting a notification. The presentation of
that notification is up to a higher layer (maybe we're on a raspberry
pi2 and we present notifications as LED morse code or whatever). It
just makes sense that unity8, which is drawing the notification, is
the one that knows that the screen needs to be on. It also knows what
form factor we are in (I assume we only want to turn screen on for
phones/tablets, not desktops).
So I'm proposing that we unify all those places into one code path in
unity8 that can turn the screen on when a notification is received.
(This is a breakout bug from bug 1426115.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1482317/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481525] Re: Left mouse stops working after some time.
** Changed in: xorg (Ubuntu) Importance: Undecided = Medium -- 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/1481525 Title: Left mouse stops working after some time. Status in xorg package in Ubuntu: Confirmed Bug description: As per https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316873 Also, sometimes, but not always, Alt-tab, for window switching, stops working at the same time. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-26.27-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Aug 4 17:12:37 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-05-05 (456 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed root=UUID=e55fd7ff-3130-4675-9cd8-e7739e4aa8c1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Aug 4 16:58:27 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 52005 vendor VSC xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1481525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482312] Re: After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to crash every few days
** Changed in: xorg (Ubuntu) Importance: Undecided = High -- 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/1482312 Title: After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to crash every few days Status in xorg package in Ubuntu: Confirmed Bug description: After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to crash every few days. Sometimes crash may happen few times per day. This crash is reproducible with packages from main repository and from Xorg Edgers PPA. Attached logs is crated with Xorg Edgers PPA. Please look into attached xorgcrash file. Other relevant logs is Xorglog2 and gdb-Xorg2.txt. If this matter, Xorg also crash on login if I trying to start with glamor or modesetting driver (but I doesn't sure it's a same crash). I didn't tried modesetting driver in Kubuntu 15.04, but glamor works for sure (with some issues, but at least it doesn't crash on login). Currently radeon driver is used (GPU is Radeon HD 6620G). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1482312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
** Changed in: systemd (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1480310 Title: systemctl link request failed for service FOO: Unit name FOO is not valid. Status in juju-core: Triaged Status in systemd package in Ubuntu: In Progress Bug description: As seen in http://reports.vapour.ws/releases/2936/job/local-deploy-wily-amd64/attempt/136 Juju cannot bootstrap on wily because ERROR juju.service.systemd service.go:149 dbus link request failed for service juju-db-jenkins-local-deploy-wily-amd64: Unit name /var/lib/juju/init/juju-db-jenkins-local-deploy-wily-amd64/juju-db-jenkins-local-deploy-wily-amd64.service is not valid. This error first occurred after the wily-slave got package updates. The released jujus get the same errors as the jujus under test. This issue is probably an Ubuntu packaging break. I am making the test non-voting since we can see table 1.24.3 no longer works. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1480310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483437] [NEW] Mouse cursor disappears permanently after watching full screen videos
Public bug reported: Sometimes after watching a YouTube video in Google Chrome in full screen mode, my mouse pointer disappears. I can move mouse, scroll using mouse wheel, click everywhere, but I can't see a cursor. I can only guess where it is. This drives me mad because the only solution is to restart PC. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Aug 11 02:36:08 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13bd] InstallationDate: Installed on 2015-05-06 (96 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: ASUSTeK COMPUTER INC. UX301LAA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=b9c815db-e4fe-4e08-8d62-0c68991fa8be ro quiet splash rootfstype=ext4 pcie_aspm=force acpi_osi= vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX301LAA.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX301LAA 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.:bvrUX301LAA.209:bd05/08/2014:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX301LAA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Aug 11 02:34:47 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5126 vendor SHP xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid ** Summary changed: - Mouse cursor dissapears permanently after watching fullscreen videos + Mouse cursor disappears permanently after watching full screen videos -- 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/1483437 Title: Mouse cursor disappears permanently after watching full screen videos Status in xorg package in Ubuntu: New Bug description: Sometimes after watching a YouTube video in Google Chrome in full screen mode, my mouse pointer disappears. I can move mouse, scroll using mouse wheel, click everywhere, but I can't see a cursor. I can only guess where it is. This drives me mad because the only solution is to restart PC. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Aug 11 02:36:08 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem:
[Touch-packages] [Bug 1444162] Re: IPv6 default route present on ccmni0, even though no address assigned
** Branch linked: lp:~phablet-team/network-manager/lp1444162 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1444162 Title: IPv6 default route present on ccmni0, even though no address assigned Status in Canonical System Image: New Status in network-manager package in Ubuntu: In Progress Bug description: $ system-image-cli -i current build number: 171 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-14 22:23:10 version version: 171 Upon boot, my v6 routes include a default via ccmni0: $ ip -6 route fe80::/64 dev wlan0 proto kernel metric 256 default dev ccmni0 proto static metric 1024 Even though there's no v6 address on the device: $ ip -6 addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 10: wlan0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 fe80::3abc:1aff:fe18:b68b/64 scope link valid_lft forever preferred_lft forever This means that hosts that have v6 addresses are tried to be reached via v6, which obviously fails: 29% [Connecting to ports.ubuntu.com (2001:67c:1360:8001::18)] Toggling GSM data loses the default route: $ ip -6 route fe80::/64 dev wlan0 proto kernel metric 256 And the connection succeeds via v4. Attached find a set of logs from network-test-session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu13 Uname: Linux 3.10.35+ armv7l ApportVersion: 2.17-0ubuntu2 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Apr 14 23:45:11 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2015-04-14 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150414-020204) IpRoute: default via 10.2.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 via 10.2.0.1 dev wlan0 proto dhcp metric 10 10.2.0.0/24 dev wlan0 proto kernel scope link src 10.2.0.66 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: SourcePackage: network-manager SystemImageInfo: current build number: 171 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-14 22:23:10 version version: 171 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 2015-04-14T04:33:56 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1444162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1468184] Re: package linux-image-3.19.0-21-generic 3.19.0-21.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Changed in: initramfs-tools (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1468184 Title: package linux-image-3.19.0-21-generic 3.19.0-21.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Impossible to install/update ProblemType: Package DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-21-generic 3.19.0-21.21 ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matthieu 2131 F pulseaudio /dev/snd/controlC0: matthieu 2131 F pulseaudio Date: Wed Jun 24 07:18:35 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DuplicateSignature: package:linux-image-3.19.0-21-generic:3.19.0-21.21:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=b2512ccb-b2a9-4fdb-91cc-724153a452d8 InstallationDate: Installed on 2015-06-01 (22 days ago) InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-55-generic root=UUID=4e184db3-5efa-419d-82a5-4b8983839a78 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 acpi_osi=Windows 2013 init=/sbin/upstart PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-3.19.0-21-generic 3.19.0-21.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to vivid on 2015-06-23 (0 days ago) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1468184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470730] Re: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work
** Changed in: alsa-driver (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1470730 Title: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: When I plug in external speakers to line in/line out combo on the laptop the internal speakers are turned off but when I plug the speakers into the docking station (HP UltraSlim Dock 2013 EURO, D9Y32AA) music keeps playing in the internal speakers. Similar behaviour (nothing happens) is experienced with microphone connected to line in on docking station. ### Expected behaviour Plugging in external speakers to docking station should turn off sound from laptop internal speakers. Plugging in microphone to line in on docking station should switch from internal microphone to microphone in Ubuntu sound settings. ### Current behaviour Sound keeps playing in internal speakers when plugging in external speakers to docking station. Plugging in microphone to line in on docking station, nothing happens. ### Hardware Laptop: HP EliteBook 840 G2 Product number: H9W19EA#AK8 Docking station: HP UltraSlim Dock 2013 EURO Product number: D9Y32AA ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: chol 2001 F pulseaudio /dev/snd/controlC0: chol 2001 F pulseaudio /dev/snd/controlC1: chol 2001 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 2 08:16:15 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-05 (26 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HP EliteBook 840 G2, Realtek ALC3228, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M71 Ver. 01.04 dmi.board.name: 2216 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.54 dmi.chassis.asset.tag: 5CG5093YZ7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM71Ver.01.04:bd02/24/2015:svnHewlett-Packard:pnHPEliteBook840G2:pvrA3009D410303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.54:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G2 dmi.product.version: A3009D410303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1470730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470748] Re: Corrupted displays when hot plugging second monitor
** Changed in: unity (Ubuntu) Importance: Undecided = Medium -- 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/1470748 Title: Corrupted displays when hot plugging second monitor Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: On up to date Wily running on a laptop, when a second monitor is hot plugged in, the image on the laptop monitor is cropped so only lower two thirds are visible and the second monitor shows a black screen with occasional flashes. If the machine is booted with both monitors connected the displays work as expected. Same setup works ok on Vivid. This report generated with the system in the error condition. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20150627.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.17.3-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jul 2 08:34:19 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:17a9] InstallationDate: Installed on 2015-07-01 (0 days ago) InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha i386 (20150609) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=4ab50317-49e7-45c9-b675-d9391fbfd0e3 ro quiet splash SourcePackage: unity UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1 version.libdrm2: libdrm2 2.4.60-3 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.8-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.8-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Thu Jul 2 08:25:52 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13890 vendor SEC xserver.version: 2:1.17.1-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1470748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483205] Re: unity-control-center needs bluetooth packages
This is because unity-control-center needs the GSettings schema from indicator-bluetooth and schemas need to be installed otherwise the control center would crash. Otherwise indicator-bluetooth would just be a recommends. A solution would be to make an indicator-bluetooth-schemas package that just contained the schema. ** Also affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1483205 Title: unity-control-center needs bluetooth packages Status in indicator-bluetooth package in Ubuntu: New Status in unity-control-center package in Ubuntu: New Bug description: Hi, unity-control-center seems to require indicator-bluetooth which then pulls in a bunch of bluetooth packages. Any chance of updating it so bluetooth is optional? I don't have bluetooth enabled, and would prefer not to have bluetooth packages installed (indicator-bluetooth, bluez, indicator-bluetooth, gir1.2-gnomebluetooth-1.0, libbluetooth3, etc.) Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1483205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440157] Re: WARNING **: Could not connect to geoname lookup server: Operation was cancelled
Did not fix it for me. I still just see the drop-down options for the first 3 characters and nothing when more characters are entered. Enabled -proposed and installed: sudo apt-get install libtimezonemap1:amd64=0.4.3.1 ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtimezonemap in Ubuntu. https://bugs.launchpad.net/bugs/1440157 Title: WARNING **: Could not connect to geoname lookup server: Operation was cancelled Status in One Hundred Papercuts: Confirmed Status in libtimezonemap package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Invalid Status in libtimezonemap source package in Vivid: Fix Committed Status in unity-control-center source package in Vivid: Invalid Bug description: * Impact the dialog to add location doesn't work in a reliable way * Test Case open Date Time panel Clock Enable Time in other locations Click Choose Locations... Try to add a location, delete the name and type it again, it should work every time * Regression potential The entry to add location should work every time To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1440157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483490] [NEW] Bluetooth sound card not detected
Public bug reported: I can connect with bluetooth to my harman kardon stereo, but it doesn't show up as an output sound device. Works on all released Ubuntus. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomasc2143 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 11 10:57:39 2015 InstallationDate: Installed on 2013-04-11 (851 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Alpha amd64 (20130410) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to wily on 2015-08-04 (7 days ago) dmi.bios.date: 03/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V1.22 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-431 dmi.board.vendor: Acer dmi.board.version: V1.22 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V1.22 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV1.22:bd03/15/2013:svnAcer:pnAspireV5-431:pvrV1.22:rvnAcer:rnAspireV5-431:rvrV1.22:cvnAcer:ct9:cvrV1.22: dmi.product.name: Aspire V5-431 dmi.product.version: V1.22 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1483490 Title: Bluetooth sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I can connect with bluetooth to my harman kardon stereo, but it doesn't show up as an output sound device. Works on all released Ubuntus. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomasc2143 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 11 10:57:39 2015 InstallationDate: Installed on 2013-04-11 (851 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Alpha amd64 (20130410) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to wily on 2015-08-04 (7 days ago) dmi.bios.date: 03/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V1.22 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-431 dmi.board.vendor: Acer dmi.board.version: V1.22 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V1.22 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV1.22:bd03/15/2013:svnAcer:pnAspireV5-431:pvrV1.22:rvnAcer:rnAspireV5-431:rvrV1.22:cvnAcer:ct9:cvrV1.22: dmi.product.name: Aspire V5-431 dmi.product.version: V1.22 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1483490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1463033] Re: package openssh-server 1:6.7p1-5ubuntu1 failed to install/upgrade: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1463033 Title: package openssh-server 1:6.7p1-5ubuntu1 failed to install/upgrade: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました Status in openssh package in Ubuntu: Expired Bug description: sudo apt-get install openssh-server ・ ・ ・ useradd: existing lock file /etc/gshadow.lock without a PID useradd: /etc/gshadow をロックできません。後でもう一度試してください。 adduser: `/usr/sbin/useradd -d /var/run/sshd -g nogroup -s /usr/sbin/nologin -u 120 sshd' はエラーコード 10 を返しました。終了します。 dpkg: パッケージ openssh-server の処理中にエラーが発生しました (--configure): サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました ssh-import-id (4.1-0ubuntu1) を設定しています ... 処理中にエラーが発生しました: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 15.04 Package: openssh-server 1:6.7p1-5ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 Date: Mon Jun 8 22:23:42 2015 DuplicateSignature: package:openssh-server:1:6.7p1-5ubuntu1:サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました ErrorMessage: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Privilege separation user sshd does not exist SourcePackage: openssh Title: package openssh-server 1:6.7p1-5ubuntu1 failed to install/upgrade: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1463033/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452204] Re: evdev device for retro-bit NES controller adapter isn't set up as a joystick
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1452204
Title:
evdev device for retro-bit NES controller adapter isn't set up as a
joystick
Status in systemd package in Ubuntu:
Expired
Bug description:
Games which rely on SDL2 (and tools like antimicro) can't see the
retro-bit NES controller adapter by default because SDL2 has dropped
support for the old /dev/input/jsX API and udev lacks a rule to
permission the /dev/input/eventX node appropriately and set the
ID_INPUT_JOYSTICK flag.
The following rule (or equivalent) needs to be added to the system-
provided udev rules.
SUBSYSTEM==input, ATTRS{name}==INNEX NES Controller USB,
MODE=0666, ENV{ID_INPUT_JOYSTICK}=1
I come to this conclusion because:
1. Until the mode is changed, feeding evtest with an explicit input device
number results in a permissions error.
2. Globally allowing users to read joystick input poses no security risk and
the data is already mirrored via /dev/input/jsX which is 0666 already.
3. Once the mode is changed, sdl2-jstest and antimicro still cannot see it.
4. Once ID_INPUT_JOYSTICK=1 is set, sdl2-jstest and antimicro work just as
well as sdl-jstest and jstest-gtk, which use the old API.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: udev 204-5ubuntu20.11
ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
Uname: Linux 3.13.0-48-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
CurrentDesktop: LXDE
CustomUdevRuleFiles: 99-escpos.rules 49-teensy.rules 99-nes-controller.rules
99-TrueRNG.rules
Date: Wed May 6 05:39:13 2015
InstallationDate: Installed on 2014-08-01 (278 days ago)
InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64
(20140416.2)
MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-USB3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic
root=UUID=d8313afd-996d-4d2c-9764-02e9336e03fd ro verbose
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/07/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-880GMA-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/07/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-880GMA-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452204/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1464032] Re: [842GM, Realtek ALC880, Line Out, N/A] Pulseaudio fails to detect card
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1464032 Title: [842GM, Realtek ALC880, Line Out, N/A] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: Expired Bug description: There is no audio coming from speakers. Typed aplay -l and showed no soundcard. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Jun 10 17:32:26 2015 InstallationDate: Installed on 2014-07-19 (326 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Line Out, N/A Title: [842GM, Realtek ALC880, Line Out, N/A] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2005 dmi.bios.vendor: Intel Corp. dmi.bios.version: AG91510J.15A.0816.2005.0214.1818 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D915GAG dmi.board.vendor: Intel Corporation dmi.board.version: AAC77881-306 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnIntelCorp.:bvrAG91510J.15A.0816.2005.0214.1818:bd02/14/2005:svnGateway:pn842GM:pvr:rvnIntelCorporation:rnD915GAG:rvrAAC77881-306:cvnGateway:ct3:cvr: dmi.product.name: 842GM dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1464032/+subscriptions -- Mailing list: https://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 1481781] Re: package linux-image-extra-3.19.0-26-generic 3.19.0-26.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
update-initramfs: Generating /boot/initrd.img-3.19.0-26-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.19.0-26-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-3.19.0-26-generic (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-extra-3.19.0-26-generic; however: Package linux-image-extra-3.19.0-26-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 3.19.0.26.25); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for initramfs-tools (0.103ubuntu15) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. update-initramfs: Generating /boot/initrd.img-3.19.0-26-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.19.0-26-generic with 1. dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-image-extra-3.19.0-26-generic linux-image-generic linux-generic initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) On Sat, Aug 8, 2015 at 10:01 AM, Andy Whitcroft a...@canonical.com wrote: This is a disk full event: update-initramfs: Generating /boot/initrd.img-3.19.0-26-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.19.0-26-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ** Changed in: initramfs-tools (Ubuntu) Status: New = Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1481781 Title: package linux-image-extra-3.19.0-26-generic 3.19.0-26.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: Boot partition full. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: linux-image-extra-3.19.0-26-generic 3.19.0-26.27 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cousin-it 8691 F pulseaudio Date: Wed Aug 5 10:10:30 2015 DuplicateSignature: package:linux-image-extra-3.19.0-26-generic:3.19.0-26.27:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=eb6e190f-536d-484f-bc29-a885b614a7ca InstallationDate: Installed on 2015-06-04 (61 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Hewlett-Packard Presario CQ56 Notebook PC ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-22ubuntu1.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: initramfs-tools Title: package linux-image-extra-3.19.0-26-generic 3.19.0-26.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1604 dmi.board.vendor: Hewlett-Packard dmi.board.version: 88.17 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias:
[Touch-packages] [Bug 1479001] Re: OTA update: lower user click not updated by custom tarball higher click
Correct me if I'm wrong, but this seems to be by design. Notice if you go check for available updates, Ubuntu is listed as a separate update to Facebook Photos. It seems reasonable to expect that if I update Ubuntu, Facebook Photos will not be updated, since I didn't select it. Indeed, after the OTA update, if you go back to view available updates, Facebook Photos is still listed there, and if you update there, the user will now be on 1.26. Colin, are you suggesting adding another system hook, then? Aren't those run on each boot? I can't think of a way to write a system hook that will only force-ably update user-installed apps upon OTA and not on each boot. Thoughts? -- 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/1479001 Title: OTA update: lower user click not updated by custom tarball higher click Status in Canonical System Image: Confirmed Status in click package in Ubuntu: Confirmed Bug description: A user in the field has OTA5 installed. But one click in OTA 5 (com.canonical.scopes.fbphotos_fbphotos 1.26) did not get updated and is at the pre OTA5 version: 1.24. Expectations: if OTA custom tarball has a higher version click package than the user's, that higher click package is installed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462489] Re: Allow apps to keep the screen on
It should be working on Nexus 4, 7 and 10 It's not working on my Nexus 7, but presumably that's because the flo devel channel hasn't seen an update since April. Has it been abandoned again? -- 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/1462489 Title: Allow apps to keep the screen on Status in Canonical System Image: Fix Released Status in Canonical Click Reviewers tools: Fix Released Status in Ubuntu Developer Portal: New Status in apparmor-easyprof-ubuntu package in Ubuntu: Fix Released Status in qtsystems-opensource-src package in Ubuntu: Fix Released Status in qtubuntu package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in qtsystems-opensource-src package in Ubuntu RTM: Fix Released Bug description: Support an interface in QML and HTML to allow an app to keep the screen on while the app is active. This has come up in several scenarios, such as an ebook reader, a clock in night mode. First step is to hook up QtSystemInfo screenSaverEnabled One solution to inhibit the screen blanking: Add a new dbus rule to the default template Provide a mediator (unity8) to control this, so it can restore the screen blanking when the app is not active or has been closed Prompt the user for confirmation the first time the app accesses it use the trust store to avoid prompts each time add to the System settings Other app access panel an entry for Screen or Display so the setting could be revoked To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470235] Re: PolicyKit high memory usage
Just to keep this alive and to add a new data point, I upgraded to the 3.19.0-21 kernel and after 6 days polkitd has grown to 1.4+G memory usage. I don't think the kernel version has anything to do with the problem. On the plus side, my WIFI connection has stabilized since the upgrade. Thx, Jon. p.s. I'm putting together a new system so I'll be able to know if this will affect a absolutely clean install in a couple of weeks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1470235 Title: PolicyKit high memory usage Status in policykit-1 package in Ubuntu: Confirmed Bug description: Periodically I install updates on my computer and reboot without logging in. When I come back to my computer and log in, polkitd is using a large chunk of memory. At the moment it's using 2.3 GiB of memory on a machine with 8 GB RAM: $ ps aux | grep polkit root 1229 0.4 29.8 2652532 2420916 ? Sl Jun19 67:38 /usr/lib/policykit-1/polkitd --no-debug Killing the process frees the memory until I reboot again. I'm currently using the latest version of policykit-1: $ apt-file search /usr/lib/policykit-1/polkitd policykit-1: /usr/lib/policykit-1/polkitd $ apt-cache policy policykit-1 policykit-1: Installed: 0.105-4ubuntu2.14.04.1 Candidate: 0.105-4ubuntu2.14.04.1 Version table: *** 0.105-4ubuntu2.14.04.1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.105-4ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ sudo apt-get upgrade policykit-1 Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done policykit-1 is already the newest version. Other information: $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Jun 30 16:14:51 2015 InstallationDate: Installed on 2014-08-25 (309 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1470235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437719] Re: [Dell Inspiron 5547] Black Screen on user switch
I was hesitant to install the daily build again since I felt I was being run around in circles. An acquaintance has pointed out that doing it would server a useful purpose. So I have completed that task. Once again I was unable to reproduce the issue with a live-usb containing the daily build. There were occasions when I thought the screen was going to go black - but then it did recover. And once again I did try a live-usb with 14.04.1 and was also not able to reproduce the issue: making me once again consider that it might be a configuration issue. So I looked at the parameters being used by the i915 driver. These parameters were in common between the my system and the 14.04.1 live-usb that works so well: /sys/module/i915/parameters/disable_power_well:1 /sys/module/i915/parameters/fastboot:N /sys/module/i915/parameters/invert_brightness:0 /sys/module/i915/parameters/lvds_channel_mode:0 /sys/module/i915/parameters/lvds_downclock:0 /sys/module/i915/parameters/lvds_use_ssc:-1 /sys/module/i915/parameters/modeset:-1 /sys/module/i915/parameters/panel_ignore_lid:1 /sys/module/i915/parameters/powersave:1 /sys/module/i915/parameters/prefault_disable:N /sys/module/i915/parameters/preliminary_hw_support:1 /sys/module/i915/parameters/reset:Y /sys/module/i915/parameters/semaphores:-1 /sys/module/i915/parameters/vbt_sdvo_panel_type:-1 /sys/module/i915/parameters/enable_ips:1 /sys/module/i915/parameters/enable_psr:0 /sys/module/i915/parameters/enable_hangcheck:Y These parameters seem to have been renamed: /sys/module/i915/parameters/enable_rc6:1 /sys/module/i915/parameters/enable_fbc:-1 /sys/module/i915/parameters/enable_ppgtt:1 /* Power Saving features? */ /sys/module/i915/parameters/enable_pc8:1 /sys/module/i915/parameters/pc8_timeout:5000 /* Defunct LVDS setting? *? /sys/module/i915/parameters/fbpercrtc:0 /* New parameters? */ /sys/module/i915/parameters/disable_display:N /sys/module/i915/parameters/disable_vtd_wa:N /sys/module/i915/parameters/enable_cmd_parser:1 I tried to change some of these at bootup to see if they affected the behaviour: they didn't. It seems possibly tied to power saving: on the 14.04.1 live-usb buffering seemed to work better on user switching so perhaps the system never though it was entering a power saving mode and thus never turned off the screen. Next week I will install the HWE Stack for 14.04.3 that has the Vivid kernel/drivers to see if that fixes things. My acquaintance is a retired software engineer - application level stuff on Windows and Macs. But has played with Linux a bit and even though he has never dug into drivers or kernel code he has said he would be willing to help me out (already showed me how to build the kernel). So I'll up my level interest in debugging. What next steps do you suggest? ** Changed in: xorg (Ubuntu) Status: Incomplete = New -- 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/1437719 Title: [Dell Inspiron 5547] Black Screen on user switch Status in xorg package in Ubuntu: New Bug description: When switching users (primarly using Ctrl-Alt-F(7-10) the monitor will sometimes go black. This happens once or twice a day, although on occasion it doesn't occur for several days. It has occurred at least once a week since I installed Ubuntu 14.04.1. It seems to be more of a problem since moving to 14.04.2 - I did perform installation of the Utopic Kernel, X, and MesaGL packages, but this is only perception. At the same time I switched from Unity to Cinnamon (Jeremy Clarkson isn't the only dinosaur roaming the world) - but I have confirmed that just running Unity desktops is vunerable. The display can be restored by sudo service lightdm restart - run from an ssh login from another system. Steps to consistently reproduce the problem is simply to perform abusive user stress testing: switching from one user to another rapidly: as soon as the display switches go back to the other. Usually I can get a black screen with this method in under a minute with Unity desktops. I have the same issue with another system (Dell Vostro 3550) reported in Bug #1437557 - submitting a new defect since this is different hardware and even though the defects look the same there might be differences underneath the hood causing the problem. 14.04.2 Trusty 3.16.0-33-generic. I'll edit this report shortly with additional system info. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Mar 28 14:45:26 2015 DistUpgraded:
[Touch-packages] [Bug 1483443] [NEW] package libsqlite3-0:i386 3.8.2-1ubuntu2.1 failed to install/upgrade: package libsqlite3-0:i386 is already installed and configured
Public bug reported: This just started with the last set of updates a few days ago. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libsqlite3-0:i386 3.8.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14 Uname: Linux 3.16.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 AptdaemonVersion: 1.1.1-1ubuntu5.2 Architecture: amd64 CrashReports: 600:111:116:0:2015-08-10 18:47:28.496304334 -0500:2015-08-10 18:47:28.496304334 -0500:/var/crash/libssl1.0.0:i386.0.uploaded 640:0:116:391835:2015-08-10 18:46:37.943830490 -0500:2015-08-10 18:46:38.943830490 -0500:/var/crash/libssl1.0.0:i386.0.crash 644:0:116:0:2015-08-10 18:47:24.892269864 -0500:2015-08-10 18:47:24.892269864 -0500:/var/crash/libssl1.0.0:i386.0.upload 600:0:116:140723:2015-08-09 20:53:44.104056835 -0500:2015-08-09 20:53:45.104056835 -0500:/var/crash/libsqlite3-0:i386.0.crash 600:0:116:140712:2015-08-09 20:53:45.156058027 -0500:2015-08-09 20:53:45.148057858 -0500:/var/crash/libdb5.3:i386.0.crash Date: Sun Aug 9 20:53:44 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libsqlite3-0:i386:3.8.2-1ubuntu2.1:package libsqlite3-0:i386 is already installed and configured ErrorMessage: package libsqlite3-0:i386 is already installed and configured InstallationDate: Installed on 2015-05-11 (91 days ago) InstallationMedia: Ubuntu MATE 14.04.2 Trusty Tahr - LTS amd64 (20150323) PackageArchitecture: i386 SourcePackage: sqlite3 Title: package libsqlite3-0:i386 3.8.2-1ubuntu2.1 failed to install/upgrade: package libsqlite3-0:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sqlite3 (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1483443 Title: package libsqlite3-0:i386 3.8.2-1ubuntu2.1 failed to install/upgrade: package libsqlite3-0:i386 is already installed and configured Status in sqlite3 package in Ubuntu: New Bug description: This just started with the last set of updates a few days ago. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libsqlite3-0:i386 3.8.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14 Uname: Linux 3.16.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 AptdaemonVersion: 1.1.1-1ubuntu5.2 Architecture: amd64 CrashReports: 600:111:116:0:2015-08-10 18:47:28.496304334 -0500:2015-08-10 18:47:28.496304334 -0500:/var/crash/libssl1.0.0:i386.0.uploaded 640:0:116:391835:2015-08-10 18:46:37.943830490 -0500:2015-08-10 18:46:38.943830490 -0500:/var/crash/libssl1.0.0:i386.0.crash 644:0:116:0:2015-08-10 18:47:24.892269864 -0500:2015-08-10 18:47:24.892269864 -0500:/var/crash/libssl1.0.0:i386.0.upload 600:0:116:140723:2015-08-09 20:53:44.104056835 -0500:2015-08-09 20:53:45.104056835 -0500:/var/crash/libsqlite3-0:i386.0.crash 600:0:116:140712:2015-08-09 20:53:45.156058027 -0500:2015-08-09 20:53:45.148057858 -0500:/var/crash/libdb5.3:i386.0.crash Date: Sun Aug 9 20:53:44 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libsqlite3-0:i386:3.8.2-1ubuntu2.1:package libsqlite3-0:i386 is already installed and configured ErrorMessage: package libsqlite3-0:i386 is already installed and configured InstallationDate: Installed on 2015-05-11 (91 days ago) InstallationMedia: Ubuntu MATE 14.04.2 Trusty Tahr - LTS amd64 (20150323) PackageArchitecture: i386 SourcePackage: sqlite3 Title: package libsqlite3-0:i386 3.8.2-1ubuntu2.1 failed to install/upgrade: package libsqlite3-0:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1483443/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483454] Re: Invisble cursor on wake from suspend
** Description changed: I'm using xubuntu 14.04 clean install with updates. Whenever I wake from suspend, my mouse cursor is invisible, although still functional. Sometimes suspending and resuming again fixes the problem but not always. + + I've also noticed that if I use lightlocker to lock the screen on + suspend, then the problem will not occur. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Aug 11 01:52:57 2015 InstallationDate: Installed on 2015-08-10 (0 days ago) InstallationMedia: Xubuntu 14.04.3 LTS Trusty Tahr - Beta amd64 (20150805) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1483454 Title: Invisble cursor on wake from suspend Status in xorg package in Ubuntu: New Bug description: I'm using xubuntu 14.04 clean install with updates. Whenever I wake from suspend, my mouse cursor is invisible, although still functional. Sometimes suspending and resuming again fixes the problem but not always. I've also noticed that if I use lightlocker to lock the screen on suspend, then the problem will not occur. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Aug 11 01:52:57 2015 InstallationDate: Installed on 2015-08-10 (0 days ago) InstallationMedia: Xubuntu 14.04.3 LTS Trusty Tahr - Beta amd64 (20150805) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1483454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444162] Re: IPv6 default route present on ccmni0, even though no address assigned
@Renato I pushed my first attempt at fixing this to my PPA. The fix involves telling NM that ofono connections should ignore IPv6. https://launchpad.net/~awe/+archive/ubuntu/ppa I confirmed that Default6 is set to false, however it appears that the route still is added.Can you give it a try and see if it resolves the problem for you? If not, I may need to dig deeper into the code. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1444162 Title: IPv6 default route present on ccmni0, even though no address assigned Status in Canonical System Image: New Status in network-manager package in Ubuntu: In Progress Bug description: $ system-image-cli -i current build number: 171 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-14 22:23:10 version version: 171 Upon boot, my v6 routes include a default via ccmni0: $ ip -6 route fe80::/64 dev wlan0 proto kernel metric 256 default dev ccmni0 proto static metric 1024 Even though there's no v6 address on the device: $ ip -6 addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 10: wlan0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 fe80::3abc:1aff:fe18:b68b/64 scope link valid_lft forever preferred_lft forever This means that hosts that have v6 addresses are tried to be reached via v6, which obviously fails: 29% [Connecting to ports.ubuntu.com (2001:67c:1360:8001::18)] Toggling GSM data loses the default route: $ ip -6 route fe80::/64 dev wlan0 proto kernel metric 256 And the connection succeeds via v4. Attached find a set of logs from network-test-session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu13 Uname: Linux 3.10.35+ armv7l ApportVersion: 2.17-0ubuntu2 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Apr 14 23:45:11 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2015-04-14 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150414-020204) IpRoute: default via 10.2.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 via 10.2.0.1 dev wlan0 proto dhcp metric 10 10.2.0.0/24 dev wlan0 proto kernel scope link src 10.2.0.66 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: SourcePackage: network-manager SystemImageInfo: current build number: 171 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-14 22:23:10 version version: 171 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 2015-04-14T04:33:56 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1444162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483443] Re: package libsqlite3-0:i386 3.8.2-1ubuntu2.1 failed to install/upgrade: package libsqlite3-0:i386 is already installed and configured
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1483443 Title: package libsqlite3-0:i386 3.8.2-1ubuntu2.1 failed to install/upgrade: package libsqlite3-0:i386 is already installed and configured Status in sqlite3 package in Ubuntu: New Bug description: This just started with the last set of updates a few days ago. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libsqlite3-0:i386 3.8.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14 Uname: Linux 3.16.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 AptdaemonVersion: 1.1.1-1ubuntu5.2 Architecture: amd64 CrashReports: 600:111:116:0:2015-08-10 18:47:28.496304334 -0500:2015-08-10 18:47:28.496304334 -0500:/var/crash/libssl1.0.0:i386.0.uploaded 640:0:116:391835:2015-08-10 18:46:37.943830490 -0500:2015-08-10 18:46:38.943830490 -0500:/var/crash/libssl1.0.0:i386.0.crash 644:0:116:0:2015-08-10 18:47:24.892269864 -0500:2015-08-10 18:47:24.892269864 -0500:/var/crash/libssl1.0.0:i386.0.upload 600:0:116:140723:2015-08-09 20:53:44.104056835 -0500:2015-08-09 20:53:45.104056835 -0500:/var/crash/libsqlite3-0:i386.0.crash 600:0:116:140712:2015-08-09 20:53:45.156058027 -0500:2015-08-09 20:53:45.148057858 -0500:/var/crash/libdb5.3:i386.0.crash Date: Sun Aug 9 20:53:44 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libsqlite3-0:i386:3.8.2-1ubuntu2.1:package libsqlite3-0:i386 is already installed and configured ErrorMessage: package libsqlite3-0:i386 is already installed and configured InstallationDate: Installed on 2015-05-11 (91 days ago) InstallationMedia: Ubuntu MATE 14.04.2 Trusty Tahr - LTS amd64 (20150323) PackageArchitecture: i386 SourcePackage: sqlite3 Title: package libsqlite3-0:i386 3.8.2-1ubuntu2.1 failed to install/upgrade: package libsqlite3-0:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1483443/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305438] Re: hot corners stop working time to time
I had the same problem with a clean 14.04 installation. However, I changed my drivers from the open source (xserver-xorg-video-ati) to the propietary driver (fglrx-updates), and the hot corners seem to work everytime I reboot. I have a HD Radeon 7670M graphics card. -- 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/1305438 Title: hot corners stop working time to time Status in compiz package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: After upgrading to ubuntu 14.04, time to time hot corners stop working. I have to disable and enable again from unity tweak tool to make it working again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11+14.04.20140408-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 10 11:38:48 2014 DistUpgraded: 2014-04-07 11:18:00,385 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-23-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-23-generic, x86_64: installed ExecutablePath: /usr/bin/compiz GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0434] Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0c45:6461 Microdia Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 1464 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=63447271-280d-41b9-8d35-1670541ea71c ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: Upgraded to trusty on 2014-04-07 (3 days ago) dmi.bios.date: 03/29/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0C6HFD dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A13 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/29/2011:svnDellInc.:pnInspiron1464:pvrA13:rvnDellInc.:rn0C6HFD:rvrA13:cvnDellInc.:ct8:cvrA13: dmi.product.name: Inspiron 1464 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140408-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-4ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu2 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: Thu Apr 10 11:32:23 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4156 vendor AUO xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1305438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473825] Re: Update to 0.4.0
** Branch linked: lp:~ubuntu-branches/ubuntu/wily/xcb-util/wily-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xcb-util in Ubuntu. https://bugs.launchpad.net/bugs/1473825 Title: Update to 0.4.0 Status in xcb-util package in Ubuntu: Triaged Bug description: Update to 0.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xcb-util/+bug/1473825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483454] [NEW] Invisble cursor on wake from suspend
Public bug reported: I'm using xubuntu 14.04 clean install with updates. Whenever I wake from suspend, my mouse cursor is invisible, although still functional. Sometimes suspending and resuming again fixes the problem but not always. I've also noticed that if I use lightlocker to lock the screen on suspend, then the problem will not occur. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Aug 11 01:52:57 2015 InstallationDate: Installed on 2015-08-10 (0 days ago) InstallationMedia: Xubuntu 14.04.3 LTS Trusty Tahr - Beta amd64 (20150805) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1483454 Title: Invisble cursor on wake from suspend Status in xorg package in Ubuntu: New Bug description: I'm using xubuntu 14.04 clean install with updates. Whenever I wake from suspend, my mouse cursor is invisible, although still functional. Sometimes suspending and resuming again fixes the problem but not always. I've also noticed that if I use lightlocker to lock the screen on suspend, then the problem will not occur. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Aug 11 01:52:57 2015 InstallationDate: Installed on 2015-08-10 (0 days ago) InstallationMedia: Xubuntu 14.04.3 LTS Trusty Tahr - Beta amd64 (20150805) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1483454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483327] Re: Crash in ~shared_ptr from usc::WindowManager::~WindowManager()
** Summary changed: - /usr/sbin/unity-system-compositor:11:__exchange_and_add:__exchange_and_add_dispatch:_M_release:~__shared_count:~__shared_ptr + Crash in ~shared_ptr from usc::WindowManager::~WindowManager() ** Also affects: unity-system-compositor Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1483327 Title: Crash in ~shared_ptr from usc::WindowManager::~WindowManager() Status in Unity System Compositor: New Status in unity-system-compositor package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with version 0.1.1+15.04.20150804-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1770fbadf225a96999bab768dd7c0b886fa3046d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-system-compositor/+bug/1483327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379777] Re: [Orientation] Allow applications to specify the orientations supported
@Laurie This bug is about enabling apps to tell the shell what orientations it supports (through that desktop file parameter). The shell deciding when to rotate them. What you want is the ability for an application to tell its current preferred orientation (at runtime), which overrides shell's decision on rotating an app (among its supported orientations) based on the device physical position etc. So this is a different topic and it's being tracked on https://bugs.launchpad.net/mir/+bug/1382209 -- 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/1379777 Title: [Orientation] Allow applications to specify the orientations supported Status in QtMir: Fix Released Status in Ubuntu UX: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: Currently unity8 shell has a partial implementation of orientation support. It trusts applications to rotate their own contents, if they want to. The shell doesn't reposition the panel (at the top) though, so a landscape app still has a portrait panel on the side. For proper orientation support in the shell, shell needs to know if the application wants to rotate its contents or not. To animate correctly, we really need shell to be responsible for rotating the app surface, not the app itself. Therefore an application needs to tell shell what orientations it supports, so shell can respect its wishes. A hint in the desktop file may be sufficient. --- Desired UX As described above. Application should be able to tell the system its possible orientations so that the shell can handle the actual rotation accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1379777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379777] Re: [Orientation] Allow applications to specify the orientations supported
Mir added support for it but qtubuntu (for qt based apps), qtmir and unity8 are not using it yet. -- 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/1379777 Title: [Orientation] Allow applications to specify the orientations supported Status in QtMir: Fix Released Status in Ubuntu UX: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: Currently unity8 shell has a partial implementation of orientation support. It trusts applications to rotate their own contents, if they want to. The shell doesn't reposition the panel (at the top) though, so a landscape app still has a portrait panel on the side. For proper orientation support in the shell, shell needs to know if the application wants to rotate its contents or not. To animate correctly, we really need shell to be responsible for rotating the app surface, not the app itself. Therefore an application needs to tell shell what orientations it supports, so shell can respect its wishes. A hint in the desktop file may be sufficient. --- Desired UX As described above. Application should be able to tell the system its possible orientations so that the shell can handle the actual rotation accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1379777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382209] Re: [Enhancement] Add an API to adjust preferred surface orientation at runtime
@lauriebradshaw thanks for the comment, this is on our todo list. As you're missing this, we'll try bump it up the list -G ** Summary changed: - [Enhancement] Add an API to lock surface orientation + [Enhancement] Add an API to adjust preferred surface orientation at runtime ** Also affects: qtmir Importance: Undecided Status: New ** Changed in: qtmir Status: New = Triaged ** Changed in: qtmir Importance: Undecided = High ** Changed in: qtmir (Ubuntu) Status: New = Confirmed ** Changed in: qtmir (Ubuntu) Importance: Undecided = High -- 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/1382209 Title: [Enhancement] Add an API to adjust preferred surface orientation at runtime Status in Mir: Fix Released Status in QtMir: Triaged Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Confirmed Bug description: Sometimes, applications are written to take advantage of the entire surface of screen. So they need a way to tell MIR, the orientation they want for drawing themselves. This can be portrait for some, landscape for others, or even combinations. Without this feature, portrait application get distorted when running in a landscape oriented device. So, it would be nice to have an API, in MIR client, to precisely lock the orientation of the MirSurface used for drawing. My use case is a full-screen game, that require always Portrait Orientation. Another is a full-screen game that requires always Landscape. Better (future): - allow this even for non full-screen applications - allow combination like Portait+PortraitUpsideDown, or LandscapeLeft+LandscapeRight - allow to change the orientation when the application run (so not only when creating/requesting the surface). Remarks : - touch event may need to be translated into the correct coordinates system! To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1382209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419645] Re: [Dialer] dialer screen focussed after receiving a call
The incoming call screen is currently a screen in the Phone app. Accepting the call switches to the app. How, then, could the desired behavior be implemented? Unity would have to remember where in the stack the Phone app was previously (if it was even running at all). The Phone app would have to tell Unity that the call was over. Then Unity would have to move it back to its previous position in the app stack. That's a lot of special-casing, and it's hard to see how any other VoIP app could do the same. (And on a PC where the app wasn't full-screen, that shuffling would look weird.) If the call window was a parentless dialog instead, whether full-screen or not, it could float on top of whatever app you happened to be using at the time (even if that happened to be the Phone app). Once the call finished, the dialog would go away, and you'd be back where you were without any app shuffling. -- 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/1419645 Title: [Dialer] dialer screen focussed after receiving a call Status in Canonical System Image: New Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Using rtm 228 on krillin - have your phone on the dash (nothing is running) or with an application in use (ie. the webbrowser) - receive a call - look at your phone after the call The dialer-app is open and focussed, it shouldn't, answering a phone shouldn't return the device in a state different from the one it was before talking. If you were using the webbrowser you probably want to keep doing that rather than dial a new number Opening against unity8 since that's an application management issue, not sure if that's the correct component though UX comment--- I agree, this is a bad user experience. As proposed in the bug description: After user hangs up an accepted call, the previously used app should be back in view. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483220] Re: [Gallery] Unable to launch Gallery app
** Description changed: - Ubuntu 15.04 (r90) + krillin, rc-proposed, 15.04 (r90) Steps to reproduce: 1. Tap on the Gallery app (via launcher / Apps scope) 2. Wait for it to launch Actual behaviour: Gallery header and spinner are shown indicating that the app is launching, but then these elements disappear and user is presented with a entire white screen. Expected behaviour: Gallery app to be launched. -- This is what the gallery log contains when I try to run the gallery app: Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' file:///usr/share/click/preinstalled/com.ubuntu.gallery/2.9.1.1209/rc/qml/GalleryApplication.qml:202:5: QML Binding: Binding loop detected for property target file:///usr/share/click/preinstalled/com.ubuntu.gallery/2.9.1.1209/rc/qml/MainScreen.qml:310:9: Cannot assign object to list UbuntuWindow - regular geometry UbuntuWindow::handleSurfaceFocusChange(focused=true) UbuntuWindow::handleSurfaceResize(width=540, height=919) Opening (/home/phablet/Pictures, /home/phablet/Videos) ... Opened (/home/phablet/Pictures, /home/phablet/Videos) 0 media files loaded in 7 ms - inf ms per media UbuntuClipboard - Got invalid serialized mime data. Ignoring it. libust[5483/5496]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:958) libust[5483/5495]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1483220 Title: [Gallery] Unable to launch Gallery app Status in gallery-app package in Ubuntu: New Bug description: krillin, rc-proposed, 15.04 (r90) Steps to reproduce: 1. Tap on the Gallery app (via launcher / Apps scope) 2. Wait for it to launch Actual behaviour: Gallery header and spinner are shown indicating that the app is launching, but then these elements disappear and user is presented with a entire white screen. Expected behaviour: Gallery app to be launched. -- This is what the gallery log contains when I try to run the gallery app: Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' file:///usr/share/click/preinstalled/com.ubuntu.gallery/2.9.1.1209/rc/qml/GalleryApplication.qml:202:5: QML Binding: Binding loop detected for property target file:///usr/share/click/preinstalled/com.ubuntu.gallery/2.9.1.1209/rc/qml/MainScreen.qml:310:9: Cannot assign object to list UbuntuWindow - regular geometry UbuntuWindow::handleSurfaceFocusChange(focused=true) UbuntuWindow::handleSurfaceResize(width=540, height=919) Opening (/home/phablet/Pictures, /home/phablet/Videos) ... Opened (/home/phablet/Pictures, /home/phablet/Videos) 0 media files loaded in 7 ms - inf ms per media UbuntuClipboard - Got invalid serialized mime data. Ignoring it. libust[5483/5496]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:958) libust[5483/5495]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1483220/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1293058] Re: compiz: PAM unable to dlopen(pam_usb.so): /lib/security/pam_usb.so: cannot open shared object file: No such file or directory
I missed to tell you that I created a symbolic link in /lib: $ ls -lh /lib | grep security lrwxrwxrwx 1 root root 30 Aug 10 10:33 security - /lib/x86_64-linux-gnu/security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1293058 Title: compiz: PAM unable to dlopen(pam_usb.so): /lib/security/pam_usb.so: cannot open shared object file: No such file or directory Status in Unity: Invalid Status in libpam-usb package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: after resume from suspend/sleep mode i can't login via usb-stick and cannot login via password because my keyboard is unresponsive — not possible to change the input language. apt-cache policy compiz compiz: Installed: 1:0.9.11+14.04.20140310-0ubuntu1 Candidate: 1:0.9.11+14.04.20140310-0ubuntu1 Version table: *** 1:0.9.11+14.04.20140310-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy libpam-usb libpam-usb: Installed: 0.5.0-4 Candidate: 0.5.0-4 Version table: *** 0.5.0-4 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status dpkg --listfiles libpam-usb /. /usr /usr/share /usr/share/pam-configs /usr/share/pam-configs/usb /usr/share/doc /usr/share/doc/libpam-usb /usr/share/doc/libpam-usb/README.Debian /usr/share/doc/libpam-usb/copyright /usr/share/doc/libpam-usb/NEWS.Debian.gz /lib /lib/x86_64-linux-gnu /lib/x86_64-linux-gnu/security /lib/x86_64-linux-gnu/security/pam_usb.so /usr/share/doc/libpam-usb/changelog.Debian.gz see also https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1309535 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1293058/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483176] [NEW] Dash killed by OOM killer, never comes back
Public bug reported: My retail krillin phone has been running for a couple of days. I just unlocked it and found a blank screen:- http://people.canonical.com/~alan/screenshots/device-2015-08-10-100928.png I checked dmesg and found entries about the oom killer and unity8-dash. I would expect unity8-dash to restart, but it doesn't seem like it did. My phone now needs a reboot to be usable. http://paste.ubuntu.com/12046823/ [Sun Aug 9 23:30:38 2015] Killing 'unity8-dash' (3554), adj 50, [Sun Aug 9 23:30:38 2015] to free 90268kB on behalf of 'whoopsie-upload' (17110) because [Sun Aug 9 23:30:38 2015] cache 38364kB is below limit 65536kB for oom_score_adj 12 [Sun Aug 9 23:30:38 2015] Free memory is -2784kB above reserved [gfp(0x200da)] [Sun Aug 9 23:30:38 2015] [Ker_PM][request_suspend_state]wakeup (3-0) at 217470460401699 (2015-08-09 22:38:13.212608292 UTC) [Sun Aug 9 23:30:38 2015] select 'terminal' (22023), adj 100, size 1151, to kill [Sun Aug 9 23:30:38 2015] Killing 'terminal' (22023), adj 100, [Sun Aug 9 23:30:38 2015] to free 4604kB on behalf of 'whoopsie-upload' (17110) because [Sun Aug 9 23:30:38 2015] cache 49004kB is below limit 65536kB for oom_score_adj 12 [Sun Aug 9 23:30:38 2015] Free memory is 460kB above reserved [gfp(0x200da)] [Sun Aug 9 23:30:38 2015] select 'unity8-dash' (22032), adj 50, size 1121, to kill [Sun Aug 9 23:30:38 2015] select 'upstart' (22040), adj 100, size 385, to kill [Sun Aug 9 23:30:38 2015] Killing 'upstart' (22040), adj 100, [Sun Aug 9 23:30:38 2015] to free 1540kB on behalf of 'unity8-dash' (22032) because [Sun Aug 9 23:30:38 2015] cache 51660kB is below limit 65536kB for oom_score_adj 12 [Sun Aug 9 23:30:38 2015] Free memory is -2260kB above reserved [gfp(0x200da)] [Sun Aug 9 23:30:38 2015] mtk-tpd: TPD wake up [Sun Aug 9 23:30:38 2015] mtk-tpd: TPD wake up done [Sun Aug 9 23:30:38 2015] MAGNETIC mag_context_obj ok---hwm_obj-early_suspend=0 [Sun Aug 9 23:30:39 2015] select 'unity8-dash' (22032), adj 50, size 1385, to kill [Sun Aug 9 23:30:39 2015] Killing 'unity8-dash' (22032), adj 50, [Sun Aug 9 23:30:39 2015] to free 5540kB on behalf of 'unity8-dash' (22032) because [Sun Aug 9 23:30:39 2015] cache 55312kB is below limit 65536kB for oom_score_adj 12 [Sun Aug 9 23:30:39 2015] Free memory is -2996kB above reserved [gfp(0x200da)] [Sun Aug 9 23:30:39 2015] select 'sh' (22044), adj 50, size 63, to kill [Sun Aug 9 23:30:39 2015] select 'initctl' (22047), adj 50, size 92, to kill [Sun Aug 9 23:30:39 2015] Killing 'initctl' (22047), adj 50, [Sun Aug 9 23:30:39 2015] to free 368kB on behalf of 'whoopsie-upload' (17110) because [Sun Aug 9 23:30:39 2015] cache 54868kB is below limit 65536kB for oom_score_adj 12 [Sun Aug 9 23:30:39 2015] Free memory is -1000kB above reserved [gfp(0x200da)] [Sun Aug 9 23:30:39 2015] select 'upstart' (22051), adj 110, size 391, to kill [Sun Aug 9 23:30:39 2015] Killing 'upstart' (22051), adj 110, [Sun Aug 9 23:30:39 2015] to free 1564kB on behalf of 'cgmanager' (693) because [Sun Aug 9 23:30:39 2015] cache 58912kB is below limit 65536kB for oom_score_adj 12 [Sun Aug 9 23:30:39 2015] Free memory is -3020kB above reserved [gfp(0x2d2)] [Sun Aug 9 23:30:40 2015] select 'sh' (22062), adj 110, size 114, to kill [Sun Aug 9 23:30:40 2015] select 'gdbus' (22075), adj 110, size 440, to kill [Sun Aug 9 23:30:40 2015] Killing 'gdbus' (22075), adj 110, [Sun Aug 9 23:30:40 2015] to free 1760kB on behalf of 'propertyservice' (22079) because [Sun Aug 9 23:30:40 2015] cache 60836kB is below limit 65536kB for oom_score_adj 12 [Sun Aug 9 23:30:40 2015] Free memory is -2568kB above reserved [gfp(0x200da)] ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1483176 Title: Dash killed by OOM killer, never comes back Status in unity8 package in Ubuntu: New Bug description: My retail krillin phone has been running for a couple of days. I just unlocked it and found a blank screen:- http://people.canonical.com/~alan/screenshots/device-2015-08-10-100928.png I checked dmesg and found entries about the oom killer and unity8-dash. I would expect unity8-dash to restart, but it doesn't seem like it did. My phone now needs a reboot to be usable. http://paste.ubuntu.com/12046823/ [Sun Aug 9 23:30:38 2015] Killing 'unity8-dash' (3554), adj 50, [Sun Aug 9 23:30:38 2015] to free 90268kB on behalf of 'whoopsie-upload' (17110) because [Sun Aug 9 23:30:38 2015] cache 38364kB is below limit 65536kB for oom_score_adj 12 [Sun Aug 9 23:30:38 2015] Free memory is -2784kB above reserved [gfp(0x200da)] [Sun Aug 9 23:30:38 2015] [Ker_PM][request_suspend_state]wakeup (3-0) at 217470460401699 (2015-08-09 22:38:13.212608292 UTC) [Sun
[Touch-packages] [Bug 1421623] Re: Welcome wizard claims GPS is less accurate than wifi based location
Ondrej, if you're going to strongly disagree, please at least explain why. Mislabelling it as Wifi based location gives the impression that you still think it is not supposed to use GPS. Why do you think that? -- 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/1421623 Title: Welcome wizard claims GPS is less accurate than wifi based location Status in Canonical System Image: New Status in Ubuntu UX: Invalid Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Incomplete Bug description: First boot welcome wizard in location sections claims GPS is less accurate than network based location service from HERE. While this can be theoretically true in some insane corner case, in normal life GPS is far more accurate. To help form correct text here are main differences. GPS - more accurate, but slow to acquire fix, does not work indoors, drains battery more, no need for internet connection, does not send any data out. Network based location - almost instant to get coarse location, works indoors, accuracy depends on network coverage in the area, more power efficient, requires internet connection. To get location data about visible GSM network and wifi networks needs to be send to 3rd party server. tested on krillin vivid-proposed r107 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1478157] Re: Hotspot password defaults to a hard-coded string
** Branch linked: lp:~pete-woods/indicator-network/seed-random-number- generator ** Changed in: ubuntu-system-settings (Ubuntu RTM) Status: New = In Progress ** Changed in: ubuntu-system-settings (Ubuntu RTM) Assignee: (unassigned) = Pete Woods (pete-woods) ** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-network (Ubuntu) Status: New = Invalid ** Changed in: indicator-network (Ubuntu) Status: Invalid = In Progress ** Changed in: ubuntu-system-settings (Ubuntu RTM) Status: In Progress = Invalid ** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) = Pete Woods (pete-woods) ** Changed in: indicator-network (Ubuntu) Importance: Undecided = High ** Changed in: ubuntu-system-settings (Ubuntu RTM) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1478157 Title: Hotspot password defaults to a hard-coded string Status in indicator-network package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu RTM: Invalid Bug description: While testing the touch hotspot feature ( currently in silo-046 ) on krillin ( stable, #24 ) and arale ( rc-proposed, #58 ), I noticed that a default password is populated for the hotspot, and it appears to be hard-coded to the string 89fjt93p. This is pretty easy to repeat. 1. Goto Hotspot screen 2. Click Change password/setup 3. Click show password Expected result: The password field has a hint, but is not pre-populated Actual result: The password field is populated with the string 89fjt93p To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1478157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1294303] Re: Mediascanner-service-2 process is killing HD and consumes lot of CPU
To everyone: please file new bugs rather than adding to bug reports that have been closed for more than a year. Cederic: your specific problem sounds a lot like bug 1436110, which was fixed in the 20150604 build. To others: mediascanner2 was a pretty young code base during the 14.04 time frame, and we haven't done any back ports since then. It is not a dependency of the base desktop, so it is probably easiest to just uninstall it there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1294303 Title: Mediascanner-service-2 process is killing HD and consumes lot of CPU Status in mediascanner2: Fix Released Status in mediascanner2 package in Ubuntu: Fix Released Bug description: I just connected external USB harddrive, when mediascanner-service-2 start scanning (?) over 15 min - even after unplug USB HD. CPU usage was very high (min 50%, sometimes 100%). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mediascanner2.0 0.100+14.04.20140314-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Mar 18 20:06:06 2014 SourcePackage: mediascanner2 UpgradeStatus: Upgraded to trusty on 2013-11-26 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mediascanner2/+bug/1294303/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482688] Re: Bluez reports quoted hostname
** Branch linked: lp:ubuntu/wily-proposed/bluez -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1482688 Title: Bluez reports quoted hostname Status in bluez package in Ubuntu: In Progress Bug description: At least on touch devices BlueZ reports a quoted hostname like Aquaris E4.5 Ubuntu Edition which is then send over to other devices including the quotes. bluetoothd[6402]: plugins/adaptername.c:set_pretty_name() Setting name 'Aquaris E4.5 Ubuntu Edition' for device 'hci0' bluetoothd[6402]: plugins/mgmtops.c:mgmt_set_name() index 0, name Aquaris E4.5 Ubuntu Edition BlueZ reads the hostname from /etc/machine-info on startup which has the following set PRETTY_HOSTNAME=Aquaris E4.5 Ubuntu Edition Code in BlueZ needs to be changed to ignore the quotes from the value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1482688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396361] Re: Double Mouse Cursor
*** This bug is a duplicate of bug 1390625 *** https://bugs.launchpad.net/bugs/1390625 Install (with synaptic) and boot from 3.19.0-25 kernel resolve this bug on 14.04.x versions. -- 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/1396361 Title: Double Mouse Cursor Status in xorg package in Ubuntu: Incomplete Bug description: When dragging with the mouse cursor often it creates a double cursor side by side about 10 cm apart on the screen. Only one cursor works. Using print screen does not show the cursor in the resulting image. Rebooting corrects the problem. This is similar to the double mouse cursor reported as a result of flash in a browser, however the current problem will occur without the browser open. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: LXDE Date: Tue Nov 25 15:58:51 2014 InstallationDate: Installed on 2014-10-24 (32 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted
Install (with synaptic) and boot from 3.19.0-25 kernel resolve this bug on 14.04.x 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/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Fix Committed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482688] Re: Bluez reports quoted hostname
** Changed in: bluez (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1482688 Title: Bluez reports quoted hostname Status in bluez package in Ubuntu: In Progress Bug description: At least on touch devices BlueZ reports a quoted hostname like Aquaris E4.5 Ubuntu Edition which is then send over to other devices including the quotes. bluetoothd[6402]: plugins/adaptername.c:set_pretty_name() Setting name 'Aquaris E4.5 Ubuntu Edition' for device 'hci0' bluetoothd[6402]: plugins/mgmtops.c:mgmt_set_name() index 0, name Aquaris E4.5 Ubuntu Edition BlueZ reads the hostname from /etc/machine-info on startup which has the following set PRETTY_HOSTNAME=Aquaris E4.5 Ubuntu Edition Code in BlueZ needs to be changed to ignore the quotes from the value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1482688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483184] [NEW] spurious ] in configure script
Public bug reported: if you look at the configure.ac file you'll see: AM_SILENT_RULES([yes])] there's an extra ] at the end there leading to this warning at configure time: $ ./configure ... ./configure: line 2833: ]: command not found ** Affects: libindicator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/1483184 Title: spurious ] in configure script Status in libindicator package in Ubuntu: New Bug description: if you look at the configure.ac file you'll see: AM_SILENT_RULES([yes])] there's an extra ] at the end there leading to this warning at configure time: $ ./configure ... ./configure: line 2833: ]: command not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1483184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475205] Re: Random Chinese character missing with Ubuntu font
On desktop I can see the PPA fixing the issue, see the attached
screenshots.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1475205
Title:
Random Chinese character missing with Ubuntu font
Status in Canonical System Image:
In Progress
Status in qtbase-opensource-src package in Ubuntu:
In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
Invalid
Status in ubuntu-font-family-sources package in Ubuntu:
Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu:
Invalid
Bug description:
After applied 50 GU setting in image, we started seeing randomly
missing Chinese characters across scopes and apps header, not clipped
at the begin or end of string, sometimes in the middle.
STEPS:
1. Switch display language to zh_CN in system settings
2. Reboot the phone
EXPECTED:
I should see all header strings displayed properly.
ACTUAL:
Randomly missing character.
VERSIONS:
current build number: 51
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.zh-proposed
last update: 2015-07-16 04:59:10
version version: 51
version ubuntu: 20150716
version device: 20150709-8965e37
version custom: 20150716-819-9-6
-- update --
The problem of missing characters can be reproduced even on a desktop,
outside of the header, without importing Ubuntu.Components:
import QtQuick 2.0
Item {
width: 800
height: 600
Text {
anchors.centerIn: parent
text: 系统设置 one two
font.family: Ubuntu
font.pixelSize: 69
font.weight: Font.Light
}
}
The problem only appears to occur with this specific combination of
font family, pixelSize and weight. Tim Peeters reproduced the problem
on vivid on a laptop without changing the default settings for the
language (LANGUAGE=en_US).
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1475205/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483140] [NEW] BQ (r24): package libsasl2-modules is not installed
Public bug reported: The Ubuntu r24 in the BG lacks correct support of SASL2, the package libsasl2-modules is not installed: phablet@ubuntu-phablet:~$ apt --installed list | fgrep sasl2 WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts. libsasl2-2/vivid,now 2.1.26.dfsg1-13 armhf [installed] libsasl2-modules-db/vivid,now 2.1.26.dfsg1-13 armhf [installed] in my jail I have it installed and it works fine: phablet@ubuntu-phablet:~$ sudo chroot myRoot/ root@ubuntu-phablet:/# root@ubuntu-phablet:/# apt-get install libsasl2-modules root@ubuntu-phablet:/# apt --installed list | fgrep sasl2 WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts. libsasl2-2/vivid,now 2.1.26.dfsg1-13 armhf [installed] libsasl2-modules/vivid,now 2.1.26.dfsg1-13 armhf [installed] libsasl2-modules-db/vivid,now 2.1.26.dfsg1-13 armhf [installed] ** Affects: ubuntu-touch-meta (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-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1483140 Title: BQ (r24): package libsasl2-modules is not installed Status in ubuntu-touch-meta package in Ubuntu: New Bug description: The Ubuntu r24 in the BG lacks correct support of SASL2, the package libsasl2-modules is not installed: phablet@ubuntu-phablet:~$ apt --installed list | fgrep sasl2 WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts. libsasl2-2/vivid,now 2.1.26.dfsg1-13 armhf [installed] libsasl2-modules-db/vivid,now 2.1.26.dfsg1-13 armhf [installed] in my jail I have it installed and it works fine: phablet@ubuntu-phablet:~$ sudo chroot myRoot/ root@ubuntu-phablet:/# root@ubuntu-phablet:/# apt-get install libsasl2-modules root@ubuntu-phablet:/# apt --installed list | fgrep sasl2 WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts. libsasl2-2/vivid,now 2.1.26.dfsg1-13 armhf [installed] libsasl2-modules/vivid,now 2.1.26.dfsg1-13 armhf [installed] libsasl2-modules-db/vivid,now 2.1.26.dfsg1-13 armhf [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1483140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475205] Re: Random Chinese character missing with Ubuntu font
@Timo
I run the citrain to install your patch, and then try the test qml but the
missing letter is still missing.
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 73
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.zh-proposed
last update: 2015-08-10 06:45:07
version version: 73
version ubuntu: 20150807.1
version device: 20150709-8965e37
version custom: 20150729-849-849-9
** Attachment added: qml.png
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1475205/+attachment/4442056/+files/qml.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1475205
Title:
Random Chinese character missing with Ubuntu font
Status in Canonical System Image:
In Progress
Status in qtbase-opensource-src package in Ubuntu:
In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
Invalid
Status in ubuntu-font-family-sources package in Ubuntu:
Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu:
Invalid
Bug description:
After applied 50 GU setting in image, we started seeing randomly
missing Chinese characters across scopes and apps header, not clipped
at the begin or end of string, sometimes in the middle.
STEPS:
1. Switch display language to zh_CN in system settings
2. Reboot the phone
EXPECTED:
I should see all header strings displayed properly.
ACTUAL:
Randomly missing character.
VERSIONS:
current build number: 51
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.zh-proposed
last update: 2015-07-16 04:59:10
version version: 51
version ubuntu: 20150716
version device: 20150709-8965e37
version custom: 20150716-819-9-6
-- update --
The problem of missing characters can be reproduced even on a desktop,
outside of the header, without importing Ubuntu.Components:
import QtQuick 2.0
Item {
width: 800
height: 600
Text {
anchors.centerIn: parent
text: 系统设置 one two
font.family: Ubuntu
font.pixelSize: 69
font.weight: Font.Light
}
}
The problem only appears to occur with this specific combination of
font family, pixelSize and weight. Tim Peeters reproduced the problem
on vivid on a laptop without changing the default settings for the
language (LANGUAGE=en_US).
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1475205/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483144] [NEW] Problem with screen resoultion with 2 monitors after restart
Public bug reported: I have two monitors. One is laptop another one is stationary monitor. Laptop is on the right of the additional monitor. For some reason, this setup does not work correctly. After system restart Screen has wrong resolution. Small screen has large screen resolution and large screen has small screen resolution. Result is as in photo. Quick workaround: disable large screen. Enable large screen. Move large screen to left side of small screen. Save settings after every step. If you enable large screen and move it to the left in one step, sometimes it works, and sometimes it does not. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Aug 10 09:10:44 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2015-03-09 (153 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 4391BB6 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic root=/dev/mapper/ubuntu--vg-root ro acpi=force irqpoll splash quiet SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4391BB6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4391BB6:pvrThinkPadW510:rvnLENOVO:rn4391BB6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4391BB6 dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Aug 10 09:05:49 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption trusty 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/1483144 Title: Problem with screen resoultion with 2 monitors after restart Status in xorg package in Ubuntu: New Bug description: I have two monitors. One is laptop another one is stationary monitor. Laptop is on the right of the additional monitor. For some reason, this setup does not work correctly. After system restart Screen has wrong resolution. Small screen has large screen resolution and large screen has small screen resolution. Result is as in photo. Quick workaround: disable large screen. Enable large screen. Move large screen to left side of small screen. Save settings after every step. If you enable large screen and move it to the left in one step, sometimes it works, and sometimes it does not. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/gpus/0'
[Touch-packages] [Bug 1427995] Re: lscpu -p is showing wrong values for Node component
** Tags removed: severity-high ** Tags added: severity-medium -- 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/1427995 Title: lscpu -p is showing wrong values for Node component Status in util-linux package in Ubuntu: Triaged Bug description: ---Problem Description--- lscpu -p is showing wrong values for Node component ---uname output--- Linux ubuntu 3.16.0-25-generic #14-Ubuntu ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P8 machine with Ubuntu 14.04.02 ISO image in Power NV mode. Then execute the below test scenario. root@ubuntu-daily:~# lscpu -p # The following is the parsable format, which can be fed to other # programs. Each different item in every column has an unique ID # starting from zero. # CPU,Core,Socket,Node,,L1d,L1i,L2,L3 0,0,0,0,,0,0,0,0 1,0,0,1,,0,0,0,0 2,0,0,16,,0,0,0,0 3,0,0,17,,0,0,0,0 4,0,0,0,,0,0,0,0 5,0,0,0,,0,0,0,0 6,0,0,33,,0,0,0,0 7,0,0,0,,0,0,0,0 8,1,0,0,,1,1,1,1 9,1,0,0,,1,1,1,1 10,1,0,-1429431768,,1,1,1,1 11,1,0,16383,,1,1,1,1 12,1,0,1852125029,,1,1,1,1 13,1,0,777213279,,1,1,1,1 14,1,0,81,,1,1,1,1 15,1,0,0,,1,1,1,1 16,2,0,1920169263,,2,2,2,2 17,2,0,1634235183,,2,2,2,2 18,2,0,1815045490,,2,2,2,2 19,2,0,1818321775,,2,2,2,2 20,2,0,1852125029,,2,2,2,2 21,2,0,777213279,,2,2,2,2 22,2,0,759583829,,2,2,2,2 23,2,0,1953836600,,2,2,2,2 24,3,0,1278163046,,3,3,3,3 25,3,0,1162698563,,3,3,3,3 26,3,0,1195463507,,3,3,3,3 27,3,0,1966035781,,3,3,3,3 28,3,0,762079604,,3,3,3,3 29,3,0,1970170220,,3,3,3,3 30,3,0,1869426296,,3,3,3,3 31,3,0,0,,3,3,3,3 32,4,1,0,,4,4,4,4 33,4,1,0,,4,4,4,4 34,4,1,177,,4,4,4,4 35,4,1,0,,4,4,4,4 36,4,1,269092192,,4,4,4,4 37,4,1,256,,4,4,4,4 38,4,1,1,,4,4,4,4 39,4,1,16383,,4,4,4,4 40,5,1,0,,5,5,5,5 41,5,1,0,,5,5,5,5 42,5,1,269096544,,5,5,5,5 43,5,1,256,,5,5,5,5 44,5,1,269092512,,5,5,5,5 45,5,1,256,,5,5,5,5 46,5,1,269097536,,5,5,5,5 47,5,1,256,,5,5,5,5 48,6,1,269092688,,6,6,6,6 49,6,1,256,,6,6,6,6 50,6,1,269098208,,6,6,6,6 51,6,1,256,,6,6,6,6 52,6,1,269096960,,6,6,6,6 53,6,1,256,,6,6,6,6 54,6,1,269097456,,6,6,6,6 55,6,1,256,,6,6,6,6 56,7,1,269096544,,7,7,7,7 57,7,1,256,,7,7,7,7 58,7,1,269098592,,7,7,7,7 59,7,1,256,,7,7,7,7 60,7,1,269097344,,7,7,7,7 61,7,1,256,,7,7,7,7 62,7,1,269098016,,7,7,7,7 63,7,1,256,,7,7,7,7 64,8,2,269096880,,8,8,8,8 65,8,2,256,,8,8,8,8 66,8,2,269098400,,8,8,8,8 67,8,2,256,,8,8,8,8 68,8,2,269097184,,8,8,8,8 69,8,2,256,,8,8,8,8 70,8,2,269097856,,8,8,8,8 71,8,2,256,,8,8,8,8 72,9,2,269096672,,9,9,9,9 73,9,2,256,,9,9,9,9 74,9,2,0,,9,9,9,9 75,9,2,0,,9,9,9,9 76,9,2,0,,9,9,9,9 77,9,2,0,,9,9,9,9 78,9,2,65,,9,9,9,9 79,9,2,0,,9,9,9,9 80,10,2,1920169263,,10,10,10,10 81,10,2,1634235183,,10,10,10,10 82,10,2,1815045490,,10,10,10,10 83,10,2,1818321775,,10,10,10,10 84,10,2,1852125029,,10,10,10,10 85,10,2,777213279,,10,10,10,10 86,10,2,759583829,,10,10,10,10 87,10,2,1129066296,,10,10,10,10 88,11,2,1397050719,,11,11,11,11 89,11,2,1162297683,,11,11,11,11 90,11,2,1953836883,,11,11,11,11 91,11,2,1814916201,,11,11,11,11 92,11,2,2020961897,,11,11,11,11 93,11,2,7302446,,11,11,11,11 94,11,2,113,,11,11,11,11 95,11,2,0,,11,11,11,11 96,12,3,269092448,,12,12,12,12 97,12,3,256,,12,12,12,12 98,12,3,1,,12,12,12,12 99,12,3,16383,,12,12,12,12 100,12,3,0,,12,12,12,12 101,12,3,0,,12,12,12,12 102,12,3,269092272,,12,12,12,12 103,12,3,256,,12,12,12,12 104,13,3,269092688,,13,13,13,13 105,13,3,256,,13,13,13,13 106,13,3,269096960,,13,13,13,13 107,13,3,256,,13,13,13,13 108,13,3,269096544,,13,13,13,13 109,13,3,256,,13,13,13,13 110,13,3,269097344,,13,13,13,13 111,13,3,256,,13,13,13,13 112,14,3,269096880,,14,14,14,14 113,14,3,256,,14,14,14,14 114,14,3,269097184,,14,14,14,14 115,14,3,256,,14,14,14,14 116,14,3,269096672,,14,14,14,14 117,14,3,256,,14,14,14,14 118,14,3,0,,14,14,14,14 119,14,3,0,,14,14,14,14 120,15,3,0,,15,15,15,15 121,15,3,0,,15,15,15,15 122,15,3,65,,15,15,15,15 123,15,3,0,,15,15,15,15 124,15,3,1920169263,,15,15,15,15 125,15,3,1634235183,,15,15,15,15 126,15,3,1815045490,,15,15,15,15 127,15,3,1818321775,,15,15,15,15 root@ubuntu-daily:~# dpkg --list | grep util-linux ii util-linux 2.20.1-5.1ubuntu20.4 ppc64el Miscellaneous system utilities Contact Information = pavsu...@in.ibm.com Userspace tool common name: /usr/bin/lscpu The userspace tool has the following bit modes: 64-bit Userspace package: util-linux Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1427995/+subscriptions -- Mailing
[Touch-packages] [Bug 1475205] Re: Random Chinese character missing with Ubuntu font
** Attachment added: withoutppa.png
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1475205/+attachment/4442047/+files/withoutppa.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1475205
Title:
Random Chinese character missing with Ubuntu font
Status in Canonical System Image:
In Progress
Status in qtbase-opensource-src package in Ubuntu:
In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
Invalid
Status in ubuntu-font-family-sources package in Ubuntu:
Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu:
Invalid
Bug description:
After applied 50 GU setting in image, we started seeing randomly
missing Chinese characters across scopes and apps header, not clipped
at the begin or end of string, sometimes in the middle.
STEPS:
1. Switch display language to zh_CN in system settings
2. Reboot the phone
EXPECTED:
I should see all header strings displayed properly.
ACTUAL:
Randomly missing character.
VERSIONS:
current build number: 51
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.zh-proposed
last update: 2015-07-16 04:59:10
version version: 51
version ubuntu: 20150716
version device: 20150709-8965e37
version custom: 20150716-819-9-6
-- update --
The problem of missing characters can be reproduced even on a desktop,
outside of the header, without importing Ubuntu.Components:
import QtQuick 2.0
Item {
width: 800
height: 600
Text {
anchors.centerIn: parent
text: 系统设置 one two
font.family: Ubuntu
font.pixelSize: 69
font.weight: Font.Light
}
}
The problem only appears to occur with this specific combination of
font family, pixelSize and weight. Tim Peeters reproduced the problem
on vivid on a laptop without changing the default settings for the
language (LANGUAGE=en_US).
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1475205/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
