[Touch-packages] [Bug 1408481] Re: Header contents not full width after navigating to a page with more actions
** 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/1408481 Title: Header contents not full width after navigating to a page with more actions Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: I have a page with 1 action (search which shows a textfield filling the header) and another with multiple actions causing an overflow. If you select the search action after navigating to the other tab its right anchor is moved to where the left most action from the other page is, not the current page. I have an example branch here [0] Steps: * Select search * Note the search bar fills the width * Select back * Switch to the other tab and back again * Select search * Notice its right anchor point has moved 0 - lp:~andrew-hayzen/+junk/header-not-full-width-example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1408481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409307] Re: attributes dont show without title
@thomas product team asked to bump priority
** Changed in: unity-scopes-api (Ubuntu)
Importance: Undecided = High
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) = Thomas Strehl (strehl-t)
--
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/1409307
Title:
attributes dont show without title
Status in The Savilerow project:
New
Status in unity-scopes-api package in Ubuntu:
New
Bug description:
I want to display category attributes but not titles (for the number
of Likes under each picture in Facebook Photos scope).
But, it seems attributes do not display unless I add a title
component.
So with this catrenderer, attributes do NOT display:
{
schema-version : 1,
template : {
category-layout : grid,
card-size: small
},
components : {
art : art,
attributes: attrs
}
}
And with this one attributes DO display:
{
schema-version : 1,
template : {
category-layout : grid,
card-size: small
},
components : {
title: title,
art : art,
attributes: attrs
}
}
phablet@ubuntu-phablet:~$ apt-cache policy libunity-scopes3
libunity-scopes3:
Instalados: 0.6.9+15.04.20141216.2~rtm-0ubuntu
See images.
To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1409307/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391501] Re: Calendar reminders should mute if phone is muted
*** This bug is a duplicate of bug 1410874 *** https://bugs.launchpad.net/bugs/1410874 proposed solution described in the dupe -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1391501 Title: Calendar reminders should mute if phone is muted Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-datetime package in Ubuntu: New Bug description: Calendar reminders seem to use the alarm role, which means muting your phone does not impact them. It should either use the same role as the ringer, or maybe a completely separate one. This is related to bug #1291458. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-datetime 13.10.0+15.04.20141103-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 11 13:06:24 2014 SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) UX Solution: I would use a separate role. Calendar reminders are lower in priority than Ringer and Alarms and users should be able to silence them. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1391501/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391501] Re: Calendar reminders should mute if phone is muted
*** This bug is a duplicate of bug 1410874 *** https://bugs.launchpad.net/bugs/1410874 ** This bug has been marked a duplicate of bug 1410874 Alarm sounds vs Calendar sounds -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1391501 Title: Calendar reminders should mute if phone is muted Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-datetime package in Ubuntu: New Bug description: Calendar reminders seem to use the alarm role, which means muting your phone does not impact them. It should either use the same role as the ringer, or maybe a completely separate one. This is related to bug #1291458. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-datetime 13.10.0+15.04.20141103-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 11 13:06:24 2014 SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) UX Solution: I would use a separate role. Calendar reminders are lower in priority than Ringer and Alarms and users should be able to silence them. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1391501/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410874] Re: Alarm sounds vs Calendar sounds
From bug 1391501 it seems we really should be using the role alert, as calendar events are not really alarms. That would also mean that the alert volume (default when nothing is playing) will also affect the calendar events, which is also good. ** Also affects: indicator-datetime (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1410874 Title: Alarm sounds vs Calendar sounds Status in the base for Ubuntu mobile products: Confirmed Status in indicator-datetime package in Ubuntu: Triaged Status in indicator-datetime package in Ubuntu RTM: New Bug description: As discussed with rsalveti and pmcgowan in #phablet on 14 Jan There are two issues in the datetime notification code that need to be changed. 1. Right now we only set role=alarm if the sound is looping; ie if it's an alarm clock event rather than calendar event. Set calendar event role to alert 2. Calendar events shouldn't play in silent mode. We can test for silent mode on the bus, http://bazaar.launchpad.net/~phablet-team /telephony- service/trunk/view/head:/libtelephonyservice/greetercontacts.cpp has an example: getUserValue(com.ubuntu.touch.AccountsService.Sound, SilentMode); To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410946] [NEW] Task Switching between Workspaces Fails if Window placement overflows
Public bug reported: To reproduce this bug you must enable workspaces: System Settings Appearance Behavior Enable Workspaces. Now, I'm assuming you have firefox open in this current workspace (from where you are reading this message). It doesn't matter if it is chrome, but later we will switch back to this web browser. Hit ctrl-alt-downArrow to switch to another workspace. Launch Gimp (for example) into this new workspace SuperKey type gimp (no quotes) and hit the enter key. Now, make sure that gimp's window is not maximized, and then move the window so that any part of is clipped by the workspace, meaning, drag the window down so that the bottom 10 pixels of the window are not viewable on the workspace. Now, on the launcher bar, click on an icon that is open in another workspace (firefox or chromium for example). Then try to go back to gimp by clicking on its launcher icon. For me, unless the workspace encapsulates the gimp window 100%, I am not able to switch back to gimp by clicking its launcher icon. I was using Gimp as an example, but the same is true for any other application whose window is not completely encapsulated by the workspace that it primarily resides. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Jan 14 13:27:15 2015 InstallationDate: Installed on 2014-11-23 (52 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1410946 Title: Task Switching between Workspaces Fails if Window placement overflows Status in unity package in Ubuntu: New Bug description: To reproduce this bug you must enable workspaces: System Settings Appearance Behavior Enable Workspaces. Now, I'm assuming you have firefox open in this current workspace (from where you are reading this message). It doesn't matter if it is chrome, but later we will switch back to this web browser. Hit ctrl-alt-downArrow to switch to another workspace. Launch Gimp (for example) into this new workspace SuperKey type gimp (no quotes) and hit the enter key. Now, make sure that gimp's window is not maximized, and then move the window so that any part of is clipped by the workspace, meaning, drag the window down so that the bottom 10 pixels of the window are not viewable on the workspace. Now, on the launcher bar, click on an icon that is open in another workspace (firefox or chromium for example). Then try to go back to gimp by clicking on its launcher icon. For me, unless the workspace encapsulates the gimp window 100%, I am not able to switch back to gimp by clicking its launcher icon. I was using Gimp as an example, but the same is true for any other application whose window is not completely encapsulated by the workspace that it primarily resides. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Jan 14 13:27:15 2015 InstallationDate: Installed on 2014-11-23 (52 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1410946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391501] Re: Calendar reminders should mute if phone is muted
*** This bug is a duplicate of bug 1410874 *** https://bugs.launchpad.net/bugs/1410874 Having a separated role would be a bit of rework on the rest of the stack (pulse, etc), so we should just use the role 'alert' for now (same as ringtone, camera click, etc). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1391501 Title: Calendar reminders should mute if phone is muted Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-datetime package in Ubuntu: New Bug description: Calendar reminders seem to use the alarm role, which means muting your phone does not impact them. It should either use the same role as the ringer, or maybe a completely separate one. This is related to bug #1291458. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-datetime 13.10.0+15.04.20141103-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 11 13:06:24 2014 SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) UX Solution: I would use a separate role. Calendar reminders are lower in priority than Ringer and Alarms and users should be able to silence them. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1391501/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410961] [NEW] Incoming calls show the Emergency Call version of the dialer
Public bug reported: Both just before answering and just after hanging up the user sees Emergency Call in the header. We could go directly to the active call when answering, and directly back to welcome screen after hangup. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: dialer-app (Ubuntu) Importance: High Status: Confirmed ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1410961 Title: Incoming calls show the Emergency Call version of the dialer Status in the base for Ubuntu mobile products: New Status in dialer-app package in Ubuntu: Confirmed Bug description: Both just before answering and just after hanging up the user sees Emergency Call in the header. We could go directly to the active call when answering, and directly back to welcome screen after hangup. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1156607] Re: Log Out no longer warns about updates that require restart
** Tags removed: ubuntu-desktop-trusty ** Tags added: 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/1156607 Title: Log Out no longer warns about updates that require restart Status in Unity: Triaged Status in indicator-session package in Ubuntu: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Problem occurs in: unity 6.12.0daily13.03.13.1-0ubuntu1, indicator- session 12.10.5daily13.03.08-0ubuntu1, Ubuntu R Does not occur in: Ubuntu 12.10 1. Install updates that require restarting the computer to complete installation. 2. From the system menu, choose Log Out What happens: The Log out dialog appears as normal. What should happen: The Log Out dialog has secondary text, “Some updates won’t apply until the computer next restarts., and has a Restart Instead button. https://wiki.ubuntu.com/SessionHandling#Log_Out To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1156607/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store
** Changed in: canonical-devices-system-image Milestone: ww03-2015 = ww05-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1224756 Title: Pulseaudio should integrate with trust-store Status in the base for Ubuntu mobile products: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Currently the 'audio' policy group allows access to pulseaudio which allows apps to use the microphone and eavesdrop on the user. Pulseaudio needs to be modified to use trust-store, like location- service does. Integrating with trust-store means that when an app tries use the microphone via pulseaudio, pulseaudio will contact trust-store, the trust-store will prompt the user (Foo wants to use the microphone. Is this ok? Yes|No), optionally cache the result and return the result to pulseaudio. In this manner the user is given a contextual prompt at the time of access by the app. Using caching this decision can be remembered the next time. If caching is used, there should be a method to change the decision in settings. Targeting to T-Series for now, since the trust-store is not in a reusable form yet. Original description: David and the security team (inspired by an observation from Rick) discussed that when recording, pulseaudio should somehow unobtrusively show the user that it is recording. The easiest thing to do would be for pulseaudio to alert indicator-sound which would then turn its icon red (similar to indicator-message turning blue with new messages). Marking 'high' because apps with access to pulseaudio can currently eavedrop on users. If the app is allowed to do networking (the default for apps), then it can ship that information off to a server somewhere. Note 1, the alert to indicator-sound must happen via the out of process pulseaudio server and not the confined app itself to be effective. Note 2, we should consider how to enforce this for foreground apps only. Application lifecycle should probably handle this for 13.10 (apps are suspended if not in foreground or if the screensaver is on), but we don't want an app on the converged device to record in the background when the user isn't paying attention. Example eavesdropping attack: start recording only when the screensaver is on (perhaps inhibiting the screensaver during recording would be enough). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1224756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410937] Re: logrotate limit of 10mb for /var/log/syslog is not so useful for debugging
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1410937
Title:
logrotate limit of 10mb for /var/log/syslog is not so useful for
debugging
Status in the base for Ubuntu mobile products:
Confirmed
Status in lxc-android-config package in Ubuntu:
New
Status in lxc-android-config package in Ubuntu RTM:
New
Bug description:
current build number: 194
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-01-14 14:01:42
version version: 194
version ubuntu: 20150114
version device: 20150113-2a2e4c5
version custom: 20150112-494-23-173
/var/log/syslog {
# don't use time based rotation, but size-based
size 10M
# do not keep old files at all
rotate 0
# don't use compression
nocompress
postrotate
service rsyslog reload /dev/null 21 || true
endscript
}
Only 10MB makes it harder to debug as sometimes we need a bit more
data in order to get useful results from the debug log. One example is
looking for suspend failures, since we can't really go back much in
time when investigating syslog.
20MB would already be enough for now.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410937/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410874] Re: Alarm sounds vs Calendar sounds
** Description changed: As discussed with rsalveti and pmcgowan in #phablet on 14 Jan There are two issues in the datetime notification code that need to be changed. - 1. Right now we only set role=alarm if the sound is looping; ie if it's - an alarm clock event rather than calendar event. We should - unconditionally set role=alarm for both cases + 1. Right now we only set role=alarm if the sound is looping; ie if it's an alarm clock event rather than calendar event. + Set calendar event role to alert 2. Calendar events shouldn't play in silent mode. We can test for silent mode on the bus, http://bazaar.launchpad.net/~phablet-team/telephony- service/trunk/view/head:/libtelephonyservice/greetercontacts.cpp has an example: getUserValue(com.ubuntu.touch.AccountsService.Sound, SilentMode); -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1410874 Title: Alarm sounds vs Calendar sounds Status in the base for Ubuntu mobile products: Confirmed Status in indicator-datetime package in Ubuntu: Triaged Status in indicator-datetime package in Ubuntu RTM: New Bug description: As discussed with rsalveti and pmcgowan in #phablet on 14 Jan There are two issues in the datetime notification code that need to be changed. 1. Right now we only set role=alarm if the sound is looping; ie if it's an alarm clock event rather than calendar event. Set calendar event role to alert 2. Calendar events shouldn't play in silent mode. We can test for silent mode on the bus, http://bazaar.launchpad.net/~phablet-team /telephony- service/trunk/view/head:/libtelephonyservice/greetercontacts.cpp has an example: getUserValue(com.ubuntu.touch.AccountsService.Sound, SilentMode); To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410937] Re: logrotate limit of 10mb for /var/log/syslog is not so useful for debugging
** Changed in: canonical-devices-system-image
Status: New = Confirmed
** Changed in: canonical-devices-system-image
Milestone: None = ww05-2015
** Changed in: canonical-devices-system-image
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1410937
Title:
logrotate limit of 10mb for /var/log/syslog is not so useful for
debugging
Status in the base for Ubuntu mobile products:
Confirmed
Status in lxc-android-config package in Ubuntu:
New
Status in lxc-android-config package in Ubuntu RTM:
New
Bug description:
current build number: 194
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-01-14 14:01:42
version version: 194
version ubuntu: 20150114
version device: 20150113-2a2e4c5
version custom: 20150112-494-23-173
/var/log/syslog {
# don't use time based rotation, but size-based
size 10M
# do not keep old files at all
rotate 0
# don't use compression
nocompress
postrotate
service rsyslog reload /dev/null 21 || true
endscript
}
Only 10MB makes it harder to debug as sometimes we need a bit more
data in order to get useful results from the debug log. One example is
looking for suspend failures, since we can't really go back much in
time when investigating syslog.
20MB would already be enough for now.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410937/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410967] Re: package shared-mime-info 1.1-0ubuntu2 failed to install/upgrade: cannot copy extracted data for './usr/share/mime/packages/freedesktop.org.xml' to '/usr/share/mime/p
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1410967 Title: package shared-mime-info 1.1-0ubuntu2 failed to install/upgrade: cannot copy extracted data for './usr/share/mime/packages/freedesktop.org.xml' to '/usr/share/mime/packages/freedesktop.org.xml.dpkg-new': unexpected end of file or stream Status in shared-mime-info package in Ubuntu: New Bug description: tengo problemas desde antes de instalar la versión 14.04, que no me reconocian el disco en el arranque, teniendo que pulsar la tecla de reset y posteriormente pulsar s para que arrancara, ahora ademas de esto no puedo actualizar el sofware pues para salir del paso reinstale la versión 13.04 que es la unica con la que ha arrancado, :( , en fin entre mi inesperiencia y estas cosas . muchas gracias de antemano por su ayuda. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: shared-mime-info 1.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 AptOrdering: shared-mime-info: Install shared-mime-info: Configure Architecture: i386 Date: Wed Jan 14 16:32:40 2015 DuplicateSignature: package:shared-mime-info:1.1-0ubuntu2:cannot copy extracted data for './usr/share/mime/packages/freedesktop.org.xml' to '/usr/share/mime/packages/freedesktop.org.xml.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/share/mime/packages/freedesktop.org.xml' to '/usr/share/mime/packages/freedesktop.org.xml.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2015-01-14 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True SourcePackage: shared-mime-info Title: package shared-mime-info 1.1-0ubuntu2 failed to install/upgrade: cannot copy extracted data for './usr/share/mime/packages/freedesktop.org.xml' to '/usr/share/mime/packages/freedesktop.org.xml.dpkg-new': unexpected end of file or stream UpgradeStatus: Upgraded to saucy on 2015-01-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1410967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410500] Re: Selecting matched numbers from Recent should use the full contact's number
** Also affects: history-service Importance: Undecided Status: New ** Also affects: history-service (Ubuntu) Importance: Undecided Status: New ** Also affects: history-service (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1410500 Title: Selecting matched numbers from Recent should use the full contact's number Status in the base for Ubuntu mobile products: New Status in Dialer app for Ubuntu Touch: New Status in Telephony History Service: New Status in dialer-app package in Ubuntu: New Status in history-service package in Ubuntu: New Status in dialer-app package in Ubuntu RTM: New Status in history-service package in Ubuntu RTM: New Bug description: Steps: * store a number with the country code * call the contact without using the country code * interrupt the call * swipe from the bottom * tap on the call just made Expected: * you get the dialer keypad with the full number, including the country code Current: * you get the short number without the country code This was a problem for me when travelling, I couldn't use the Recent list to call home because it wouldn't include the country code. Somehow it's also remembered permanently, so now even if I call the full number with country code, tapping that Recent entry won't have the country code still. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20150108-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu2 Architecture: armhf Date: Tue Jan 13 19:32:43 2015 InstallationDate: Installed on 2015-01-13 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150113-020204) SourcePackage: dialer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1030810] Re: package ubuntu-standard 1.267 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured
*** This bug is a duplicate of bug 951783 *** https://bugs.launchpad.net/bugs/951783 ** This bug has been marked a duplicate of bug 951783 package ubuntu-standard 1.264 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1030810 Title: package ubuntu-standard 1.267 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured Status in ubuntu-meta package in Ubuntu: New Bug description: Using wubi ubuntu installer and performing an upgrade from 10.04 LTS to 12.04, the system reported bugs related to linux image and memtest+. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: ubuntu-standard ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 Date: Mon Jul 30 11:29:15 2012 ErrorMessage: ErrorMessage: dependency problems - leaving unconfigured InstallationMedia: Ubuntu 10.04.4 LTS Lucid Lynx - Release amd64 (20120214.2) SourcePackage: ubuntu-meta Title: package ubuntu-standard 1.267 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured UpgradeStatus: Upgraded to precise on 2012-07-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1030810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408103] Re: Telephony seems to think I'm on a permanent call, ringer never plays, just the beep-beep of an awaiting call
** Changed in: canonical-devices-system-image Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1408103 Title: Telephony seems to think I'm on a permanent call, ringer never plays, just the beep-beep of an awaiting call Status in the base for Ubuntu mobile products: Fix Released Status in Telephony Service: In Progress Status in telephony-service package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu RTM: Fix Released Bug description: For some time now, on both rtm and vivid, I don't get incoming call or message sounds, just the beep beep of the awaiting call, as if I was on a permanent call. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20141212-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 22:10:47 2015 InstallationDate: Installed on 2014-12-17 (20 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141217-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) Steps to reproduce: - Reboot the phone - From another phone, call the device Expected results: - The incoming call ringtone should be played and the snap decision should appear What happens: - The snap decision dialog appears, but the ringtone is not played. Instead a beep beep sound is heard. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1408103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353855] Re: Explicit g++ 4.9 dependency breaks cross-building
** Branch linked: lp:ubuntu/qtmir -- 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/1353855 Title: Explicit g++ 4.9 dependency breaks cross-building Status in Mir: Confirmed Status in mir package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: With the new explicit g++ 4.9 dependency apt falls over when trying to install cross-dependencies for e.g. Mir: The following packages have unmet dependencies: g++-4.9:armhf : Depends: gcc-4.9:armhf (= 4.9.1-4ubuntu3) but it is not going to be installed E: Build-dependencies for sbuild-build-depends-mir-dummy could not be satisfied. This means cross-building doesn't work for any packages that have that dependency added. We were told it's going to be fine due to 4.9 becoming default, but it is now, and the situation remains. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1353855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1308037] Re: No results from application scope
This got for me to the point that I always don't get any results in Dash Home after opening it. Fortunately there is a workaround in my case. If I open the applications lens directly with shortcut (Super + A) or with quicklist it gets results and then the Dash Home starts working. I'm now on fully updated Vivid which was upgraded directly from Trusty (sudo sed -i 's/trusty/vivid/g' /etc/apt/sources.list). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1308037 Title: No results from application scope Status in LibUnity: Confirmed Status in Unity: Confirmed Status in Unity Applications Lens: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Unity is in a state where I don't get any results from the applications lens. This sometimes happens for one search but either re-entering the search or toggling the lens has always fixed it in the past for me. This time neither of these steps work. I'm attaching a bustle log of the problem in case that's helpful. I searched for spotify, which I've got installed, and got 0 results. The only way to fix the issue is to log out and back in. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 13:29:40 2014 InstallationDate: Installed on 2012-10-07 (554 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1308037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330405] Re: Unity top panel turns transparent with dual screen. Garbage shadow leftovers appear.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- 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/1330405 Title: Unity top panel turns transparent with dual screen. Garbage shadow leftovers appear. Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: To reproduce this problem using Ubuntu 14.04: 1- Reduce unity transparency to minimum (I did this using Unity tweak) 2- Connect second screen. External screen is the main one, with unity launcher; 3- Maximize a window in the laptop screen (non main). 4- Drag the window out of maximization. The result is that the panel background will become 100% transparent. The text from the window title will have disappeared, but a black shadow will be left in it's place. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1330405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330405] Re: Unity top panel turns transparent with dual screen. Garbage shadow leftovers appear.
Same deal here. 14.04.1, fully updated, etc. Running on a Dell Latitude E7440 that even came with Ubuntu on it. If I plug in a second display after the system is booted, the top panel on the secondary monitor goes transparent. If I boot the system up with the monitor plugged in, no issue. If I issue a restart to unity (ALT + F2, unity --replace), then it comes back fine. This does not happen if your panel is default transparency, though it does happen if the transparency of the panel has been adjusted (at least in my experience). ** Attachment added: dualscreen2.png https://bugs.launchpad.net/unity/+bug/1330405/+attachment/4298631/+files/dualscreen2.png -- 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/1330405 Title: Unity top panel turns transparent with dual screen. Garbage shadow leftovers appear. Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: To reproduce this problem using Ubuntu 14.04: 1- Reduce unity transparency to minimum (I did this using Unity tweak) 2- Connect second screen. External screen is the main one, with unity launcher; 3- Maximize a window in the laptop screen (non main). 4- Drag the window out of maximization. The result is that the panel background will become 100% transparent. The text from the window title will have disappeared, but a black shadow will be left in it's place. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1330405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372646] Re: Can't correct SMS number after entering it wrong once
** Also affects: telepathy-ofono (Ubuntu) Importance: Undecided Status: New ** Also affects: telepathy-ofono (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: history-service (Ubuntu) Importance: Undecided Status: New ** Also affects: history-service (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1372646 Title: Can't correct SMS number after entering it wrong once Status in Telephony History Service: New Status in Messaging App: Confirmed Status in Telepathy Ofono: New Status in history-service package in Ubuntu: New Status in messaging-app package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Status in history-service package in Ubuntu RTM: New Status in messaging-app package in Ubuntu RTM: New Status in telepathy-ofono package in Ubuntu RTM: New Bug description: Steps to reproduce (example, I suspect more number combinations are possible to reproduce): * Using the bottom edge, write a new SMS to a foreign number which is not stored to your address book, but omit the country code. Eg, 01791234567 * Wait for the SMS delivery to fail. * Go back to the conversations list and use the bottom edge to start writing a new SMS. enter the same number again, this time including the country code. eg +491791234567 * The second SMS will be grouped with the first one and the first SMS's number will be used for the second SMS too causing all attempts to fail again. This does not recover after clearing the conversation. dbus-monitor always shows HistoryService bringing back the old wrong number. Also the conversation's header will revert to the old number after exiting and re-entering the conversation. To manage notifications about this bug go to: https://bugs.launchpad.net/history-service/+bug/1372646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366829] Re: 7.4.4-1ubuntu2.1 makes rsyslogd to take all the CPU in OpenVZ
** Tags added: amd64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1366829 Title: 7.4.4-1ubuntu2.1 makes rsyslogd to take all the CPU in OpenVZ Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Trusty: Fix Committed Status in rsyslog source package in Utopic: Fix Committed Bug description: Test Case - * Install rsyslog 7.4.4-1ubuntu2.1 on an Ubuntu system that runs inside an OpenVZ container (If necessary, use ProxMox to quickly establish an OpenVZ container environment) * Verify that '$KLogPermitNonKernelFacility on' is set in /etc/rsyslog.conf * Restart rsyslog to make sure any changes to the binaries/config are picked up * Run 'top' and observe that the rsyslogd process is running at 100% CPU. When working properly, the rsyslogd process should generally be idle. - After updating rsyslog from 7.4.4-1ubuntu2 to 7.4.4-1ubuntu2.1 the rsyslogd process started to take all the CPU on my machine. The modification made by this release is described in #127, it is the activation of KLogPermitNonKernelFacility option. I don't know exactly the effect of this option but it seems to have a permanent effect : even after downgrading the package or manually removing the option from /etc/rsyslog.conf the issue remains. My syslog is full of : Sep 8 10:28:40 sentry rsyslogd: imklog: error reading kernel log - shutting down: Bad file descriptor Sep 8 10:28:40 sentry rsyslogd: message repeated 498 times: [imklog: error reading kernel log - shutting down: Bad file descriptor] Sep 8 10:28:46 sentry rsyslogd-2177: rsyslogd[internal_messages]: 519517 messages lost due to rate-limiting I guess this is what causes the CPU load. I am running Ubuntu 14.04.1 LTS in an OpenVZ container on Proxmox 3.2. The kernel is 2.6.32-28-pve --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64DistroRelease: Ubuntu 14.04 Package: rsyslog 7.4.4-1ubuntu2.1 PackageArchitecture: amd64 Tags: trusty Uname: Linux 2.6.32-28-pve x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1366829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410506] Re: MTP looping between start and stopping causing constant ~10% cpu load
Backtrace I got:
(gdb) bt full
#0 __libc_do_syscall () at
../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
No locals.
#1 0xb6c77e5e in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
_a1 = 0
_a3tmp = 6
_a1tmp = 0
_a3 = 6
_nametmp = 268
_a2tmp = 4227
_a2 = 4227
_name = 268
_sys_result = optimized out
pd = 0xb6731450
pid = 0
selftid = 4227
#2 0xb6c78b4e in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0},
sa_mask = {__val = {0 repeats 32 times}}, sa_flags = 0, sa_restorer =
0xb6730c98}
sigs = {__val = {32, 0 repeats 31 times}}
#3 0xb6ca13f8 in __libc_message (do_abort=optimized out, fmt=0xb6d1f638 ***
Error in `%s': %s: 0x%s ***\n) at ../sysdeps/posix/libc_fatal.c:175
ap = {__ap = 0xb6730ce4}
fd = 2
on_2 = optimized out
list = optimized out
nlist = optimized out
cp = optimized out
written = optimized out
#4 0xb6ca5296 in malloc_printerr (action=1, str=0xb6d1f76c double free or
corruption (!prev), ptr=optimized out) at malloc.c:4996
buf = 01d78008
cp = optimized out
#5 0xb6ca5d76 in _int_free (av=optimized out, p=optimized out,
have_lock=0) at malloc.c:3840
size = optimized out
fb = optimized out
nextchunk = optimized out
nextsize = optimized out
nextinuse = optimized out
prevsize = optimized out
bck = optimized out
fwd = optimized out
errstr = optimized out
locked = optimized out
__func__ = _int_free
#6 0x0003a652 in deallocate (this=0x1d7f6a8, __p=optimized out) at
/usr/include/c++/4.9/ext/new_allocator.h:110
No locals.
#7 deallocate (__a=..., __n=optimized out, __p=optimized out) at
/usr/include/c++/4.9/bits/alloc_traits.h:383
No locals.
#8 _M_deallocate (this=0x1d7f6a8, __n=optimized out, __p=optimized out) at
/usr/include/c++/4.9/bits/stl_vector.h:178
No locals.
#9 std::vectorchar, std::allocatorchar ::_M_default_append
(this=this@entry=0x1d7f6a8, __n=__n@entry=896) at
/usr/include/c++/4.9/bits/vector.tcc:578
__new_start = 0xb3c00468 \350\235\327\001 \233\327\001
__new_finish = 0xb3c00868
#10 0x0004657e in _M_default_append (__n=896, this=0x1d7f6a8) at
/usr/include/c++/4.9/bits/vector.tcc:545
No locals.
#11 resize (__new_size=optimized out, this=0x1d7f6a8) at
/usr/include/c++/4.9/bits/stl_vector.h:676
No locals.
#12 boost::asio::basic_streambufstd::allocatorchar ::reserve
(this=this@entry=0x1d7f684, n=n@entry=1024) at
/usr/include/boost/asio/basic_streambuf.hpp:325
gnext = optimized out
pnext = 0
pend = 1024
#13 0x00049570 in prepare (n=1024, this=0x1d7f684) at
/usr/include/boost/asio/basic_streambuf.hpp:207
No locals.
#14 MtpDaemon::read_more_notify (this=0x1d7f628) at
/build/buildd/mtp-0.0.4+15.04.20141113/server/server.cpp:191
__PRETTY_FUNCTION__ = void MtpDaemon::read_more_notify()
#15 0xb6f035de in ?? () from
/usr/lib/arm-linux-gnueabihf/libboost_thread.so.1.55.0
No symbol table info available.
#16 0xb6ea7f98 in start_thread (arg=0xb6731450) at pthread_create.c:311
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mtp in Ubuntu.
https://bugs.launchpad.net/bugs/1410506
Title:
MTP looping between start and stopping causing constant ~10% cpu load
Status in mtp package in Ubuntu:
Confirmed
Bug description:
When unplugged from USB, I notice when running $ top that init, dbus-
daemon, mpdecision are constantly using in total ~10% CPU.
The steps I have performed to cause this:
1) Ensure the device is off
2) Plug a USB cable into the device and a computer with MTP support
3) Boot the device
4) Unlock the device, run the terminal and the command $ top
5) Wait until the CPU settles, then unplug the USB cable
6) Now notice that init, dbus-daemon, mpdecision start using ~10% CPU
This is the output from running dbus-monitor [0]
Note that when I plugged my device into a PC the CPU usage reduced
back to normal, but then when I unplugged it again it increased back
to ~10% again.
0 - http://pastebin.ubuntu.com/9734788/
$ system-image-cli -i
current build number: 161
device name: mako
channel: ubuntu-touch/ubuntu-rtm/devel-proposed
alias: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-01-13 18:37:40
version version: 161
version ubuntu: 20150113
version device: 20141119
version custom: mako-1.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1410506/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410937] Re: logrotate limit of 10mb for /var/log/syslog is not so useful for debugging
This bug was fixed in the package lxc-android-config - 0.213
---
lxc-android-config (0.213) vivid; urgency=medium
* Increase log size for syslog, useful for debugging (LP: #1410937)
-- Ricardo Salveti de Araujo ricardo.salv...@canonical.com Wed, 14 Jan
2015 17:46:18 -0200
** Changed in: lxc-android-config (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1410937
Title:
logrotate limit of 10mb for /var/log/syslog is not so useful for
debugging
Status in the base for Ubuntu mobile products:
Confirmed
Status in lxc-android-config package in Ubuntu:
Fix Released
Status in lxc-android-config package in Ubuntu RTM:
New
Bug description:
current build number: 194
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-01-14 14:01:42
version version: 194
version ubuntu: 20150114
version device: 20150113-2a2e4c5
version custom: 20150112-494-23-173
/var/log/syslog {
# don't use time based rotation, but size-based
size 10M
# do not keep old files at all
rotate 0
# don't use compression
nocompress
postrotate
service rsyslog reload /dev/null 21 || true
endscript
}
Only 10MB makes it harder to debug as sometimes we need a bit more
data in order to get useful results from the debug log. One example is
looking for suspend failures, since we can't really go back much in
time when investigating syslog.
20MB would already be enough for now.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410937/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410506] Re: MTP looping between start and stopping causing constant ~10% cpu load
There was a crash and then mtp-server restarting in loop, which caused it to show on top: phablet@ubuntu-phablet:~$ cat ./.cache/upstart/mtp-server.log I0114 20:04:11.081110 2914 server.cpp:419] MTP server starting... E0114 20:04:11.103268 2914 server.cpp:440] Could not start the MTP server:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.UnityGreeter was not provided by any .service files I0114 20:04:21.545111 3012 server.cpp:419] MTP server starting... E0114 20:04:21.571146 3012 server.cpp:440] Could not start the MTP server:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.UnityGreeter was not provided by any .service files I0114 20:04:32.033162 3334 server.cpp:419] MTP server starting... E0114 20:55:23.626266 3334 MtpServer.cpp:174] request read returned -1: Input/output error [5] I0114 20:55:27.263805 5108 server.cpp:419] MTP server starting... I0114 20:56:21.600800 3143 server.cpp:419] MTP server starting... E0114 21:02:16.476572 3143 MtpServer.cpp:174] request read returned -1: Input/output error [5] I0114 21:02:16.623710 4157 server.cpp:419] MTP server starting... E0114 21:02:16.651300 4157 MtpServer.cpp:174] request read returned -1: Input/output error [5] I0114 21:02:17.229143 4175 server.cpp:419] MTP server starting... E0114 21:02:17.250813 4175 MtpServer.cpp:174] request read returned -1: Input/output error [5] I0114 21:02:17.651392 4196 server.cpp:419] MTP server starting... E0114 21:02:17.668025 4196 MtpServer.cpp:174] request read returned -1: Input/output error [5] I0114 21:02:17.769384 4212 server.cpp:419] MTP server starting... E0114 21:02:17.790657 4212 MtpServer.cpp:174] request read returned -1: Input/output error [5] I0114 21:02:18.251240 4226 server.cpp:419] MTP server starting... E0114 21:02:18.267659 4226 MtpServer.cpp:174] request read returned -1: Input/output error [5] *** Error in `/usr/bin/mtp-server': double free or corruption (!prev): 0x01d78008 *** I0114 21:02:21.462715 4249 server.cpp:419] MTP server starting... E0114 21:02:21.476754 4249 MtpServer.cpp:174] request read returned -1: Input/output error [5] I0114 21:02:21.872237 4259 server.cpp:419] MTP server starting... E0114 21:02:21.888077 4259 MtpServer.cpp:174] request read returned -1: Input/output error [5] I0114 21:02:22.478128 4276 server.cpp:419] MTP server starting... E0114 21:02:22.494457 4276 MtpServer.cpp:174] request read returned -1: Input/output error [5] I0114 21:02:22.977716 4292 server.cpp:419] MTP server starting... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1410506 Title: MTP looping between start and stopping causing constant ~10% cpu load Status in mtp package in Ubuntu: Confirmed Bug description: When unplugged from USB, I notice when running $ top that init, dbus- daemon, mpdecision are constantly using in total ~10% CPU. The steps I have performed to cause this: 1) Ensure the device is off 2) Plug a USB cable into the device and a computer with MTP support 3) Boot the device 4) Unlock the device, run the terminal and the command $ top 5) Wait until the CPU settles, then unplug the USB cable 6) Now notice that init, dbus-daemon, mpdecision start using ~10% CPU This is the output from running dbus-monitor [0] Note that when I plugged my device into a PC the CPU usage reduced back to normal, but then when I unplugged it again it increased back to ~10% again. 0 - http://pastebin.ubuntu.com/9734788/ $ system-image-cli -i current build number: 161 device name: mako channel: ubuntu-touch/ubuntu-rtm/devel-proposed alias: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-13 18:37:40 version version: 161 version ubuntu: 20150113 version device: 20141119 version custom: mako-1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1410506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410968] Re: In image 195 krillin 163 mako system settings is not showing updates
** Also affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-touch-meta (Ubuntu) Importance: Undecided = Critical ** Also affects: ubuntu-touch-meta (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ubuntu-touch-meta (Ubuntu RTM) Importance: Undecided = Critical -- 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/1410968 Title: In image 195 krillin 163 mako system settings is not showing updates Status in Libqtelegram - a qt library to access telegram.: New Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu RTM: New Status in ubuntu-touch-meta package in Ubuntu RTM: New Bug description: STEPS: Setup 1 Enable developer mode 2 from pc phablet-config writable-image 3 adb shell 4 sudo vim.tiny /etc/system-image/channel.ini 5 last 2 lines change the number to be back 10 images i.e. change the 195 to 185 6 sudo rm /userdata/.writable_image 7 rm .local/share/ubuntu-push-client/level.db 8 sudo reboot Test 1 Wait for the announcement of a new image 2 Drag down the indicator 3 Click on the image notification 4 Setting page opens on updates but is blank EXPECTED: The updates page is shown and you can click on update ACTUAL: The header is shown other wise it is a blank page after the spinner finishes spinning. To manage notifications about this bug go to: https://bugs.launchpad.net/libqtelegram/+bug/1410968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410506] Re: MTP looping between start and stopping causing constant ~10% cpu load
Able to confirm the issue with latest vivid on mako: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 65 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2015-01-14 20:03:32 version version: 65 version ubuntu: 20150114.1 version device: 20141213 version custom: 20150114.1 phablet@ubuntu-phablet:~$ dpkg -l | grep mtp-server ii mtp-server 0.0.4+15.04.20141113-0ubuntu1 armhfSmall server implementation of MTP. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1410506 Title: MTP looping between start and stopping causing constant ~10% cpu load Status in mtp package in Ubuntu: Confirmed Bug description: When unplugged from USB, I notice when running $ top that init, dbus- daemon, mpdecision are constantly using in total ~10% CPU. The steps I have performed to cause this: 1) Ensure the device is off 2) Plug a USB cable into the device and a computer with MTP support 3) Boot the device 4) Unlock the device, run the terminal and the command $ top 5) Wait until the CPU settles, then unplug the USB cable 6) Now notice that init, dbus-daemon, mpdecision start using ~10% CPU This is the output from running dbus-monitor [0] Note that when I plugged my device into a PC the CPU usage reduced back to normal, but then when I unplugged it again it increased back to ~10% again. 0 - http://pastebin.ubuntu.com/9734788/ $ system-image-cli -i current build number: 161 device name: mako channel: ubuntu-touch/ubuntu-rtm/devel-proposed alias: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-13 18:37:40 version version: 161 version ubuntu: 20150113 version device: 20141119 version custom: mako-1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1410506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409483] Re: FTBFS: (package) on 32 bit arch's
** Also affects: flac (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774908 Importance: Unknown Status: Unknown ** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flac in Ubuntu. https://bugs.launchpad.net/bugs/1409483 Title: FTBFS: (package) on 32 bit arch's Status in flac package in Ubuntu: New Status in flac package in Debian: Unknown Bug description: libflac6++ produces a slightly different set of symbols for 64 32 bit. This currently causes 32 arch builds to fail as current symbols file is for 64 bit. This will not be confined to libflac++6, maybe? all future c++ with symbols files? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libflac++6 1.3.1-1 ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1 Uname: Linux 3.18.0-8-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 11 11:54:49 2015 InstallationDate: Installed on 2014-11-16 (56 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141114) SourcePackage: flac UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flac/+bug/1409483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1069965] Re: package hostname-standard 1.287 failed to install/upgrade: dependency problems - leaving unconfigured
*** This bug is a duplicate of bug 965697 *** https://bugs.launchpad.net/bugs/965697 ** This bug has been marked a duplicate of bug 965697 package hostname-standard 1.265 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1069965 Title: package hostname-standard 1.287 failed to install/upgrade: dependency problems - leaving unconfigured Status in ubuntu-meta package in Ubuntu: New Bug description: I have updated to Ubuntu 12.10 and get all sorts of error messages... :-( This is one of them. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: ubuntu-standard 1.287 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 ApportVersion: 2.6.1-0ubuntu4 Architecture: amd64 Date: Mon Oct 22 20:44:06 2012 ErrorMessage: dependency problems - leaving unconfigured InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: ubuntu-meta Title: package hostname-standard 1.287 failed to install/upgrade: dependency problems - leaving unconfigured UpgradeStatus: Upgraded to quantal on 2012-10-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1069965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410925] [NEW] [HDA-Intel - HDA Intel, playback] Playback problem, no sound in mini hi-fi component
Public bug reported: No hay sonido cuando el ordenador esta conectado a un equipo de sonido estereo, pero si hay sonido al conectar auriculares o con los parlantes propios del ordenador. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: odair 1835 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 14 12:52:31 2015 InstallationDate: Installed on 2015-01-14 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: LANGUAGE=es_HN:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_HN.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Audio Interno - HDA Intel Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1584 dmi.board.vendor: Hewlett-Packard dmi.board.version: 85.36 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.23:bd04/28/2011:svnHewlett-Packard:pnHPMini110-3700:pvr057E11A000202B0300100:rvnHewlett-Packard:rn1584:rvr85.36:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Mini 110-3700 dmi.product.version: 057E11A000202B0300100 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- 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/1410925 Title: [HDA-Intel - HDA Intel, playback] Playback problem, no sound in mini hi-fi component Status in alsa-driver package in Ubuntu: New Bug description: No hay sonido cuando el ordenador esta conectado a un equipo de sonido estereo, pero si hay sonido al conectar auriculares o con los parlantes propios del ordenador. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: odair 1835 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 14 12:52:31 2015 InstallationDate: Installed on 2015-01-14 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: LANGUAGE=es_HN:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_HN.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Audio Interno - HDA Intel Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1584 dmi.board.vendor: Hewlett-Packard dmi.board.version: 85.36 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.23:bd04/28/2011:svnHewlett-Packard:pnHPMini110-3700:pvr057E11A000202B0300100:rvnHewlett-Packard:rn1584:rvr85.36:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Mini 110-3700 dmi.product.version: 057E11A000202B0300100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1410925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1242572] Re: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts
** Tags removed: ubuntu-desktop-trusty ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1242572 Title: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts Status in central project for keyboard configuration: Fix Released Status in console-setup package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in xkeyboard-config package in Ubuntu: Fix Released Status in console-setup source package in Trusty: Confirmed Status in ubiquity source package in Trusty: Confirmed Status in xkeyboard-config source package in Trusty: In Progress Bug description: Super+Space is default combination for switching keyboard layouts in gnome3, unity, Mac OS X, Windows. Thus for consistently, Xorg; console-setup; and ubiquity should also use Super+Space combination for switching keyboard layouts. reading xkeyboard-config sources and documentations i don't see that xkeyboard-config can support grp:lwin_space and i guess that needs to be the first step to properly support super+space. Original bug report below: Recently I installed Ubuntu 13.10 and Ubuntu GNOME 13.10. I use two keyboard layouts - English and Russian. So I select them on the corresponding screen of ubiquity setup wizard. It quietly set the keyboard switching shortcut to Alt+Shift and wrote this setting to /etc/default/keyboard: # ... XKBMODEL=pc105 XKBLAYOUT=us,ru XKBVARIANT=, XKBOPTIONS=grp:alt_shift_toggle,grp_led:scroll # ... On first boot of installed system the small notification pop-up showed that Ibus will use Super+Space for layout switching. Please fix this configuration inconsistency. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Mon Oct 21 12:16:58 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- InstallationDate: Installed on 2013-10-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131017) MarkForUpload: True SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1242572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410968] Re: In image 195 krillin 163 mako system settings is not showing updates
** Changed in: ubuntu-system-settings (Ubuntu RTM) Assignee: (unassigned) = Ken VanDine (ken-vandine) ** Changed in: ubuntu-system-settings (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: ubuntu-system-settings (Ubuntu RTM) Status: New = Confirmed -- 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/1410968 Title: In image 195 krillin 163 mako system settings is not showing updates Status in Libqtelegram - a qt library to access telegram.: New Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu RTM: Confirmed Status in ubuntu-touch-meta package in Ubuntu RTM: New Bug description: STEPS: Setup 1 Enable developer mode 2 from pc phablet-config writable-image 3 adb shell 4 sudo vim.tiny /etc/system-image/channel.ini 5 last 2 lines change the number to be back 10 images i.e. change the 195 to 185 6 sudo rm /userdata/.writable_image 7 rm .local/share/ubuntu-push-client/level.db 8 sudo reboot Test 1 Wait for the announcement of a new image 2 Drag down the indicator 3 Click on the image notification 4 Setting page opens on updates but is blank EXPECTED: The updates page is shown and you can click on update ACTUAL: The header is shown other wise it is a blank page after the spinner finishes spinning. To manage notifications about this bug go to: https://bugs.launchpad.net/libqtelegram/+bug/1410968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 965697] Re: package hostname-standard 1.265 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/965697 Title: package hostname-standard 1.265 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Error occured after updating from 10 to 12 ubuntu package ProblemType: Package DistroRelease: Ubuntu 12.04 Package: ubuntu-standard 1.265 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 Date: Tue Mar 27 00:32:04 2012 ErrorMessage: ErrorMessage: dependency problems - leaving unconfigured InstallationMedia: Ubuntu 10.04.4 LTS Lucid Lynx - Release i386 (20120214.2) SourcePackage: ubuntu-meta Title: package hostname-standard 1.265 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured UpgradeStatus: Upgraded to precise on 2012-03-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/965697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410937] [NEW] logrotate limit of 10mb for /var/log/syslog is not so useful for debugging
Public bug reported:
current build number: 194
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-01-14 14:01:42
version version: 194
version ubuntu: 20150114
version device: 20150113-2a2e4c5
version custom: 20150112-494-23-173
/var/log/syslog {
# don't use time based rotation, but size-based
size 10M
# do not keep old files at all
rotate 0
# don't use compression
nocompress
postrotate
service rsyslog reload /dev/null 21 || true
endscript
}
Only 10MB makes it harder to debug as sometimes we need a bit more data
in order to get useful results from the debug log. One example is
looking for suspend failures, since we can't really go back much in time
when investigating syslog.
20MB would already be enough for now.
** Affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
** Affects: lxc-android-config (Ubuntu RTM)
Importance: Undecided
Status: New
** Also affects: lxc-android-config (Ubuntu RTM)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1410937
Title:
logrotate limit of 10mb for /var/log/syslog is not so useful for
debugging
Status in lxc-android-config package in Ubuntu:
New
Status in lxc-android-config package in Ubuntu RTM:
New
Bug description:
current build number: 194
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-01-14 14:01:42
version version: 194
version ubuntu: 20150114
version device: 20150113-2a2e4c5
version custom: 20150112-494-23-173
/var/log/syslog {
# don't use time based rotation, but size-based
size 10M
# do not keep old files at all
rotate 0
# don't use compression
nocompress
postrotate
service rsyslog reload /dev/null 21 || true
endscript
}
Only 10MB makes it harder to debug as sometimes we need a bit more
data in order to get useful results from the debug log. One example is
looking for suspend failures, since we can't really go back much in
time when investigating syslog.
20MB would already be enough for now.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1410937/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410960] [NEW] AIGLX error with i965 dri
Public bug reported: After upgrading to 14.10 i loose my hardware rendering. cat /var/log/Xorg.0.log | grep EE (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [11.090] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/i965_dri.so: undefined symbol: _glapi_tls_Dispatch) [11.090] (EE) AIGLX: reverting to software rendering [11.098] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: undefined symbol: _glapi_tls_Dispatch) [11.098] (EE) GLX: could not load software renderer dpkg -l | grep mesa ii libegl1-mesa:amd64 10.3.2-0ubuntu0.1 ii libegl1-mesa-dbg:amd64 10.3.2-0ubuntu0.1 ii libegl1-mesa-dev:amd64 10.3.2-0ubuntu0.1 ii libegl1-mesa-drivers:amd6410.3.2-0ubuntu0.1 ii libegl1-mesa-drivers-dbg:amd64 10.3.2-0ubuntu0.1 ii libgl1-mesa-dev:amd64 10.3.2-0ubuntu0.1 ii libgl1-mesa-dri:amd64 10.3.2-0ubuntu0.1 ii libgl1-mesa-dri:i386 10.3.2-0ubuntu0.1 ii libgl1-mesa-dri-dbg:amd64 10.3.2-0ubuntu0.1 ii libgl1-mesa-glx:amd64 10.3.2-0ubuntu0.1 ii libgl1-mesa-glx:i386 10.3.2-0ubuntu0.1 ii libgl1-mesa-glx-dbg:amd6410.3.2-0ubuntu0.1 ii libglapi-mesa:amd64 10.3.2-0ubuntu0.1 ii libglapi-mesa:i386 10.3.2-0ubuntu0.1 ii libgles1-mesa:amd64 10.3.2-0ubuntu0.1 ii libgles2-mesa:amd64 10.3.2-0ubuntu0.1 ii libglu1-mesa:amd64 9.0.0-2 ii libglu1-mesa:i386 9.0.0-2 ii libglu1-mesa-dev9.0.0-2 ii libmirclient8driver-mesa:amd64 0.8.0+14.10.20141010-0ubuntu1 ii libopenvg1-mesa:amd64 10.3.2-0ubuntu0.1 ii libosmesa6:amd64 10.3.2-0ubuntu0.1 ii libosmesa6:i386 10.3.2-0ubuntu0.1 ii libosmesa6-dev:amd64 10.3.2-0ubuntu0.1 ii libwayland-egl1-mesa:amd6410.3.2-0ubuntu0.1 ii mesa-common-dev:amd64 10.3.2-0ubuntu0.1 ii mesa-utils 8.2.0-1 lspci -nnk | grep VGA\|'Kern'\|3D\|Display -A2 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) Subsystem: Lenovo Device [17aa:2210] Kernel driver in use: i915 ldd -r /usr/lib/xorg/modules/dri/swrast_dri.so | grep undefined ldd: /usr/lib/xorg/modules/dri/swrast_dri.so: No such file or directory ldd -r /usr/lib/libGL.so.1.2.0 | grep undefined | wc -l 0 nm -CD --defined-only /usr/lib/libglapi.so.0.0.0 | grep glapi_tls_Context 0008 B _glapi_tls_Context objdump -x /usr/lib/libGL.so.1.2.0| grep NEEDED | grep libglapi NEEDED libglapi.so.0 ldd /usr/lib/xorg/modules/extensions/libglx.so linux-vdso.so.1 = (0x7fffbabfe000) libGL.so.1 = /usr/local/lib/libGL.so.1 (0x7f5e407e6000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f5e405c8000) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f5e403c3000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e3fffe000) libexpat.so.1 = /lib/x86_64-linux-gnu/libexpat.so.1 (0x7f5e3fdd5000) libglapi.so.0 = /usr/local/lib/libglapi.so.0 (0x7f5e3fb78000) libXext.so.6 = /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x7f5e3f966000) libXdamage.so.1 = /usr/lib/x86_64-linux-gnu/libXdamage.so.1 (0x7f5e3f763000) libXfixes.so.3 = /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x7f5e3f55c000) libX11-xcb.so.1 = /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 (0x7f5e3f35a000) libX11.so.6 =
[Touch-packages] [Bug 1410975] [NEW] alarm sometimes won't go off untill I turn on the screen
Public bug reported: Im on a N4 on the RTM devel r13 I had already noticed that the snooze time, what I set on 5 min, varied between 5 and 10 minutes. But this morning my alarm should have gone off at 7:22 AM but only went of after I woke up and took my phone to check it. That was at 8AM ** Affects: indicator-datetime (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-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1410975 Title: alarm sometimes won't go off untill I turn on the screen Status in indicator-datetime package in Ubuntu: New Bug description: Im on a N4 on the RTM devel r13 I had already noticed that the snooze time, what I set on 5 min, varied between 5 and 10 minutes. But this morning my alarm should have gone off at 7:22 AM but only went of after I woke up and took my phone to check it. That was at 8AM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1410975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1005209] Re: [Trusty] [SRU] app-install-data-partner package in Ubuntu 12.04 LTS, 13.10 and 14.04 is empty (no desktop and icon files)
I don't think it's useful for ubuntu-desktop to recommend app-install- data-partner. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1005209 Title: [Trusty] [SRU] app-install-data-partner package in Ubuntu 12.04 LTS, 13.10 and 14.04 is empty (no desktop and icon files) Status in app-install-data-partner package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in app-install-data-partner package in Baltix: In Progress Bug description: Looks like nobody re-enabled the installation of the .desktop files for 12.04. The current app-install-data-partner ships none, so the partners view in the Muon Software Center is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/app-install-data-partner/+bug/1005209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1132780] Re: [Lenovo X201 3323DAG, Conexant CX20585, Pink Mic, Right] Wrong input routing
I have a Lenovo x201 with Conexant CX20585 (learned it from codecat
/proc/asound/card0/codec#* | grep Codec/code
I have struggled for days to have my internal mic working, everything else
worked (external mic, audio, HDMI audio) though.
Here is what I did, which finally solved my problem (Ubuntu 14.10, alsa driver)
1. Installed the nightly alsa drivers for my distribution following this guide
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
2. ran alsamixer command from terminal to make sure my mic is not
muted (press m to mute/onmute on the device; also I disabled
automute here (up/down arrow)
3. After I looked up all entries matching my hardware Connexant by
scrolling over alsa docu file on my laptop:
codezless /usr/share/doc/alsa-base/driver/HD-Audio-
Models.txt.gz/code
I've tried adding different entries to alsa-base.conf file with command
codevi /etc/modprobe.d/alsa-base.conf/code
Finally this one was what I needed (but only turned out after step
4...):
codeoptions snd-hda-intel model=ideapad/code
4. !!! Most important!!!
None of the tricks worked until I have re-checked whether my internal mic is
enabled or disabled in BIOS.
It was ENABLED of course, but I've changed it to disable, then enabled again,
and saved with F10.
Then not only rebooted, but SHUT DOWN completely the laptop (the BIOS help says
to shutdown with AC power removed (!) to enable internal mic.
Then after power on again: mic worked!
(Tested and confimed in Skype as well, by calling Echo / Sound Test
service.)
--
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/1132780
Title:
[Lenovo X201 3323DAG, Conexant CX20585, Pink Mic, Right] Wrong input
routing
Status in alsa-driver package in Ubuntu:
New
Bug description:
Hardware: Lenovo X201, Intel 5 Series/3400 Series Chipset High
Definition Audio
On this laptop, PulseAudio detects three jacks:
chris@lap-x201:~/Dropbox/projects/ischool/network-scripts$ pacmd list-sources
| grep analog-input-microphone
analog-input-microphone-internal: Internal Microphone (priority
8900, available: no)
analog-input-microphone-dock: Dock Microphone (priority 7800,
available: no)
analog-input-microphone: Microphone (priority 8700, available:
yes)
active port: analog-input-microphone
The analog-input-microphone input does nothing as far as I can tell. I
have to manually switch the input to -dock to use the external mic.
The status above (available: no/no/yes) is when an external mic is
plugged in. When I unplug it, I get this instead:
analog-input-microphone-internal: Internal Microphone (priority
8900, available: unknown)
analog-input-microphone-dock: Dock Microphone (priority 7800,
available: no)
analog-input-microphone: Microphone (priority 8700, available:
no)
active port: analog-input-microphone-internal
I think the jack input routing is messed up: analog-input-microphone-
dock and analog-input-microphone are the wrong way around for audio
input, but not for jack selection (connection of a mic is correctly
detected on analog-input-microphone, but this input does not receive
sound from the external microphone)
I also think something is wrong with detection of -internal: it goes
to unknown when no external mic is plugged in. (but it's still
selected as the correct input in this case, so it does function).
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
Uname: Linux 3.6.0-030600rc6-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: chris 5478 F pulseaudio
/dev/snd/pcmC0D0c: chris 5478 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf252 irq 45'
Mixer name : 'Intel IbexPeak HDMI'
Components : 'HDA:14f15069,17aa2155,00100302
HDA:80862804,17aa21b5,0010'
Controls : 28
Simple ctrls : 11
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
6QHT31WW-1.12'
Mixer name : 'ThinkPad EC 6QHT31WW-1.12'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Mon Feb 25 12:27:00 2013
EcryptfsInUse: Yes
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
Re: [Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network
I tried that and it didn't work. This machine was upgraded and it only started after upgrading to 14.10 with no changes made to the network settings. Prior it was working as expected. On Wednesday, January 14, 2015 06:24:34 PM Søren Holm wrote: As state in a previous post: You can change whatever setting you'd like. It does not have to be the auto-connection setting. You can even change the IP-allocation policy from DHCP to Manual. -- 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/1354924 Title: Networkmanager does not autoconnect to wireless network Status in network-manager package in Ubuntu: Confirmed Bug description: When adding a net wireless network and enable connect automatically' networkmanager does not automatically connect to the network wenever possible. I'm running kubuntu 14.10 daily. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 21:30:03 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-11 (29 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710) IpRoute: default via 192.168.0.2 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.213 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410967] [NEW] package shared-mime-info 1.1-0ubuntu2 failed to install/upgrade: cannot copy extracted data for './usr/share/mime/packages/freedesktop.org.xml' to '/usr/share/mime
Public bug reported: tengo problemas desde antes de instalar la versión 14.04, que no me reconocian el disco en el arranque, teniendo que pulsar la tecla de reset y posteriormente pulsar s para que arrancara, ahora ademas de esto no puedo actualizar el sofware pues para salir del paso reinstale la versión 13.04 que es la unica con la que ha arrancado, :( , en fin entre mi inesperiencia y estas cosas . muchas gracias de antemano por su ayuda. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: shared-mime-info 1.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 AptOrdering: shared-mime-info: Install shared-mime-info: Configure Architecture: i386 Date: Wed Jan 14 16:32:40 2015 DuplicateSignature: package:shared-mime-info:1.1-0ubuntu2:cannot copy extracted data for './usr/share/mime/packages/freedesktop.org.xml' to '/usr/share/mime/packages/freedesktop.org.xml.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/share/mime/packages/freedesktop.org.xml' to '/usr/share/mime/packages/freedesktop.org.xml.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2015-01-14 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True SourcePackage: shared-mime-info Title: package shared-mime-info 1.1-0ubuntu2 failed to install/upgrade: cannot copy extracted data for './usr/share/mime/packages/freedesktop.org.xml' to '/usr/share/mime/packages/freedesktop.org.xml.dpkg-new': unexpected end of file or stream UpgradeStatus: Upgraded to saucy on 2015-01-14 (0 days ago) ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 saucy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1410967 Title: package shared-mime-info 1.1-0ubuntu2 failed to install/upgrade: cannot copy extracted data for './usr/share/mime/packages/freedesktop.org.xml' to '/usr/share/mime/packages/freedesktop.org.xml.dpkg-new': unexpected end of file or stream Status in shared-mime-info package in Ubuntu: New Bug description: tengo problemas desde antes de instalar la versión 14.04, que no me reconocian el disco en el arranque, teniendo que pulsar la tecla de reset y posteriormente pulsar s para que arrancara, ahora ademas de esto no puedo actualizar el sofware pues para salir del paso reinstale la versión 13.04 que es la unica con la que ha arrancado, :( , en fin entre mi inesperiencia y estas cosas . muchas gracias de antemano por su ayuda. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: shared-mime-info 1.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 AptOrdering: shared-mime-info: Install shared-mime-info: Configure Architecture: i386 Date: Wed Jan 14 16:32:40 2015 DuplicateSignature: package:shared-mime-info:1.1-0ubuntu2:cannot copy extracted data for './usr/share/mime/packages/freedesktop.org.xml' to '/usr/share/mime/packages/freedesktop.org.xml.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/share/mime/packages/freedesktop.org.xml' to '/usr/share/mime/packages/freedesktop.org.xml.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2015-01-14 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True SourcePackage: shared-mime-info Title: package shared-mime-info 1.1-0ubuntu2 failed to install/upgrade: cannot copy extracted data for './usr/share/mime/packages/freedesktop.org.xml' to '/usr/share/mime/packages/freedesktop.org.xml.dpkg-new': unexpected end of file or stream UpgradeStatus: Upgraded to saucy on 2015-01-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1410967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353855] Re: Explicit g++ 4.9 dependency breaks cross-building
This bug was fixed in the package qtmir - 0.4.4+15.04.20150114-0ubuntu1 --- qtmir (0.4.4+15.04.20150114-0ubuntu1) vivid; urgency=low [ Gerry Boland ] * Depend on :native version of g++ to allow cross-compiling to work. (LP: #1353855) [ Michał Sawicz ] * Declare the QByteArray in callDispatcher so it doesn't get deleted before it's copied. (LP: #1408819) [ Josh Arenson ] * Assign touch events area to the correct values. [ Albert Astals ] * Move the creation of the surface observer to SessionListener::surface_created -- Ubuntu daily release ps-jenk...@lists.canonical.com Wed, 14 Jan 2015 09:07:53 + ** Changed in: qtmir (Ubuntu) Status: Confirmed = Fix Released -- 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/1353855 Title: Explicit g++ 4.9 dependency breaks cross-building Status in Mir: Confirmed Status in mir package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: With the new explicit g++ 4.9 dependency apt falls over when trying to install cross-dependencies for e.g. Mir: The following packages have unmet dependencies: g++-4.9:armhf : Depends: gcc-4.9:armhf (= 4.9.1-4ubuntu3) but it is not going to be installed E: Build-dependencies for sbuild-build-depends-mir-dummy could not be satisfied. This means cross-building doesn't work for any packages that have that dependency added. We were told it's going to be fine due to 4.9 becoming default, but it is now, and the situation remains. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1353855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400827] Re: BlueZ crashing when connecting input channel to a keyboard
** Changed in: bluez (Ubuntu) Status: New = In Progress ** Changed in: bluez (Ubuntu) Importance: Undecided = High ** Also affects: bluez (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu RTM) Status: New = In Progress ** Changed in: bluez (Ubuntu RTM) Importance: Undecided = High ** Changed in: bluez (Ubuntu RTM) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) ** Changed in: bluez (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) -- 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/1400827 Title: BlueZ crashing when connecting input channel to a keyboard Status in bluez package in Ubuntu: In Progress Status in bluez package in Ubuntu RTM: In Progress Bug description: On the phone, pairing a keyboard makes BlueZ crash when connecting the input channel (either by calling org.bluez.Input.Connect() on D-Bus or by pressing some keys on the keyboard to make the keyboard open the channel. In order to pair a keyboard with an Ubuntu phone, you need to either apply this branch to ubuntu-system-settings [1] or do it manually with bluez-simple-agent and dbus-send/qdbus. [1] https://code.launchpad.net/~mzanetti/ubuntu-system-settings/bt-input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1400827/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407680] Re: Preview details area does not match design
** Branch linked: lp:~alecu/unity-scope-click/preview-tables -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1407680 Title: Preview details area does not match design Status in unity-scope-click package in Ubuntu: Triaged Status in unity8 package in Ubuntu: New Bug description: The details area of the preview does not match the design for the scope, which has more white space and a table layout for some elements, such as last updated date. To attain a table layout, a table widget is required (per the designs), but there is no table widget type available in the Unity 8 scopes API currently: http://developer.ubuntu.com/api/scopes/sdk-14.10/previewwidgets/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1407680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410961] Re: Incoming calls show the Emergency Call version of the dialer
set for next milestone while we see if its feasible ** Changed in: canonical-devices-system-image Importance: Undecided = High ** Changed in: canonical-devices-system-image Status: New = Confirmed ** Changed in: canonical-devices-system-image Milestone: None = ww05-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1410961 Title: Incoming calls show the Emergency Call version of the dialer Status in the base for Ubuntu mobile products: Confirmed Status in dialer-app package in Ubuntu: Confirmed Bug description: Both just before answering and just after hanging up the user sees Emergency Call in the header. We could go directly to the active call when answering, and directly back to welcome screen after hangup. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372413] Re: Extensive battery drain on RTM
Reviving this bug based on recent anecdotal reports that battery life has degraded Folks who experience it can do several things to provide data: 1 - check the battery page in settings and see the battery level history, for example did it discharge overnight 2 - provide the syslog which will show whether the system is properly suspending 3 - install suspend-blocker on your desktop sudo add-apt-repository ppa:colin-king/white sudo apt-get update sudo apt-get install suspend-blocker Copy the syslog from the phone adb pull /var/log/syslog and run the command suspend-blocker -b -r -H syslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1372413 Title: Extensive battery drain on RTM Status in powerd package in Ubuntu: Confirmed Bug description: Mako, RTM 1 Since upgrading to RTM the battery life is really poor. What used to be a battery drain of 5-10% per hour (which is still high) is now 10-15% per hour. Sometimes the phone runs really hot, so there seem to be something going on in the background that is consuming power. I mostly have bluetooth, GPS (which isn't always working), wifi and cellular on, but that's no difference from when I was running 'devel- proposed' with MultiROM with much less battery consumption. As an example, I started with a full charge at 7am. After some web surfing (15 mins) and watching a couple of youtube videos (on wifi) battery was down to 66% at 9:15. That's 34% in just over two hours! I recharged again before lunch and had the phone idle until coming back 1 hour and 45 mins later to find only 75% of battery left, this time without the phone running particularly hot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1372413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1320880] Re: Calendar notifications are treated the same as an alarm notification
This already landed ** Changed in: canonical-devices-system-image Status: Confirmed = Fix Released ** Changed in: canonical-devices-system-image Milestone: ww05-2015 = ww03-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1320880 Title: Calendar notifications are treated the same as an alarm notification Status in the base for Ubuntu mobile products: Fix Released Status in Calendar application for Ubuntu devices: In Progress Status in indicator-datetime package in Ubuntu: Fix Released Bug description: If an alarm fires, the alarm sound seemingly will persist forever. This seems like perhaps the right choice for an alarm clock, but seems inappropriate for a calendar reminder. I would expect a calendar reminder to sound for only a short period. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1320880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393008] Re: Horizontal cards with summary don't get backgrounds
** Branch linked: lp:ubuntu/unity8
--
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/1393008
Title:
Horizontal cards with summary don't get backgrounds
Status in Ubuntu App Developer site:
Invalid
Status in Ubuntu UX bugs:
New
Status in unity8 package in Ubuntu:
Fix Released
Status in unity8 package in Ubuntu RTM:
New
Bug description:
If I change the WEATHER_TEMPLATE in the scopes example to:
const static string WEATHER_TEMPLATE =
R(
{
schema-version: 1,
template: {
category-layout: carousel,
card-layout: horizontal,
card-size: small,
card-background:color:///#0F0F0F
},
components: {
title: title,
art : {
field: art
},
subtitle: subtitle,
summary: summary
}
}
);
The cards are placed in carousel style, but the background color is
simply omitted, the color of the card stays black.
If the card-layout is changed from horizontal to vertical, the
color is there, and the cards in a carousel style, but the bottom 10%
of the cards seem to be clipped. (Screenshot attached)
This is my first bug report ever, so please let me know what else I
should add, or if I am at the right place at all.
Reported from: http://developer.ubuntu.com/scopes/cookbook/
To manage notifications about this bug go to:
https://bugs.launchpad.net/developer-ubuntu-com/+bug/1393008/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410989] Re: SSL_connect:unknown state
There are significant problems with the configurations of both sites: https://www.ssllabs.com/ssltest/analyze.html?d=tm3.com https://www.ssllabs.com/ssltest/analyze.html?d=ws.myfax.com That said, I was able to establish a connection to both sites by manually requesting SSL3 on the command line: The following commands worked fine for me on my 14.04 LTS machine: openssl s_client -ssl3 -verify 10 -CApath /etc/ssl/certs/ -connect ws.myfax.com:443 openssl s_client -ssl3 -verify 10 -CApath /etc/ssl/certs/ -connect www.tm3.com:443 Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1410989 Title: SSL_connect:unknown state Status in openssl package in Ubuntu: New Bug description: Running openssl s_client, I'm getting some websites (www.tm3.com, ws.myfax.com) that cause requests to hang. I compiled openssl-1.0.1k and it seems to be working now. Is there a more correct fix other than compiling the newest openssl? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1410989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410584] Re: please stop greeter gracefully when stopping lightdm
A similar thing happens when you switch to a second user, and then switch back to the original user. In this case the greeter actually is sent SIGTERM, but the display server is stopped soon after, before the cleanup has finished. lightdm.log says: [+43.64s] DEBUG: Seat seat0: Returning to existing user session userone [+43.64s] DEBUG: Unlocking login1 session c8 [+43.64s] DEBUG: Activating VT 7 [+43.64s] WARNING: Error using VT_WAITACTIVE 7 on /dev/console: Interrupted system call [+43.64s] DEBUG: Seat seat0: Stopping greeter [+43.64s] DEBUG: Session pid=4468: Sending SIGTERM [+43.64s] DEBUG: Activating login1 session c8 [+43.64s] DEBUG: Session pid=4993: Exited with return value 0 [+43.64s] DEBUG: Seat seat0: Session stopped [+43.66s] DEBUG: Session pid=4468: Exited with return value 0 [+43.66s] DEBUG: Seat seat0: Session stopped [+43.66s] DEBUG: Seat seat0: Stopping display server, no sessions require it [+43.66s] DEBUG: Sending signal 15 to process 4463 [+43.81s] DEBUG: Seat seat0 changes active session to c8 [+43.92s] DEBUG: Process 4463 exited with return value 0 [+43.92s] DEBUG: DisplayServer x-1: X server stopped [+43.92s] DEBUG: Releasing VT 8 [+43.92s] DEBUG: DisplayServer x-1: Removing X server authority /var/run/lightdm/root/:1 [+43.92s] DEBUG: Seat seat0: Display server stopped and x-1-greeter.log says: [+22.94s] DEBUG: unity-greeter.vala:605: Got a SIGTERM [+22.94s] DEBUG: settings-daemon.vala:78: Failed to acquire name org.gnome.SessionManager [+22.94s] DEBUG: settings-daemon.vala:105: Failed to acquire name org.gnome.ScreenSaver [+22.94s] DEBUG: unity-greeter.vala:135: Failed to acquire name com.canonical.Unity g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. upstart: indicator-sound main process ended, respawning upstart: indicator-keyboard main process ended, respawning upstart: indicator-power main process ended, respawning [...] Note the SIGTERM handler is hit, but Cleaning up after the end of the main loop is not. After that second display server has been shut down, its session upstart and some indicator processes are still running. ** Summary changed: - please stop greeter gracefully when stopping lightdm + please stop greeter gracefully when stopping a display server -- 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/1410584 Title: please stop greeter gracefully when stopping a display server Status in lightdm package in Ubuntu: New Bug description: Dear maintainer, When lightdm is stopped or restarted, unity-greeter does not get a chance to run its cleanup code, but simply aborts due to the X server going away. Most of the greeter session components die the same way, but the session upstart does not. It keeps running and attempting to respawn services, which results in these few processes and the logind session staying around. I'm not sure whether this bug belongs properly to lightdm or unity- greeter. It's possible the greeter should react more gracefully when the X server vanishes. I'm filing this against lightdm right now because I feel like all the necessary code for this already exists, it just needs to be called in the right order at the right time. Maybe it just needs to wait for the sessions attached to a particular display server to finish before stopping that server. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1410584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410989] Re: SSL_connect:unknown state
These are my test cases and the final solution user@test0:~$ uname -a Linux test0 3.11.0-26-generic #45-Ubuntu SMP Tue Jul 15 04:02:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux user@test0:~$ openssl version -a OpenSSL 1.0.1e 11 Feb 2013 built on: Fri Jun 20 18:52:46 UTC 2014 platform: debian-amd64 options: bn(64,64) rc4(16x,int) des(idx,cisc,16,int) blowfish(idx) compiler: cc -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -DL_ENDIAN -DTERMIO -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack -Wall -DOPENSSL_NO_TLS1_2_CLIENT -DOPENSSL_MAX_TLS1_2_CIPHER_LENGTH=50 -DMD32_REG_T=int -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM OPENSSLDIR: /usr/lib/ssl user@test0:~$ openssl s_client -CApath /etc/ssl/certs -connect www.tm3.com:443 -state CONNECTED(0003) SSL_connect:before/connect initialization SSL_connect:unknown state SSL_connect:SSLv3 read server hello A (truncated) Verify return code: 0 (ok) user@test1:~$ uname -a Linux test1 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux user@test1:~$ lsb_release -a | grep Code Codename: saucy user@test1:~$ openssl version -a OpenSSL 1.0.1f 6 Jan 2014 built on: Fri Jun 20 18:54:02 UTC 2014 platform: debian-amd64 options: bn(64,64) rc4(16x,int) des(idx,cisc,16,int) blowfish(idx) compiler: cc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -DL_ENDIAN -DTERMIO -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack -Wall -DMD32_REG_T=int -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM OPENSSLDIR: /usr/lib/ssl user@test1:~$ openssl s_client -CApath /etc/ssl/certs -connect www.tm3.com:443 -state (hangs) user@test1:~$ openssl s_client -CApath /etc/ssl/certs -connect www.tm3.com:443 -state -ssl3 (hangs) user@test1:~$ openssl s_client -CApath /etc/ssl/certs -connect www.tm3.com:443 -state -tls1 (hangs) user@test2:~$ uname -a Linux test2 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux user@test2:~$ lsb_release -a | grep Code Codename: trusty user@test2:~$ openssl version -a OpenSSL 1.0.1f 6 Jan 2014 built on: Fri Jan 9 17:52:48 UTC 2015 platform: debian-amd64 options: bn(64,64) rc4(16x,int) des(idx,cisc,16,int) blowfish(idx) compiler: cc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -DL_ENDIAN -DTERMIO -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack -Wall -DMD32_REG_T=int -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM OPENSSLDIR: /usr/lib/ssl user@test2:~$ openssl s_client -CApath /etc/ssl/certs -connect www.tm3.com:443 -state CONNECTED(0003) SSL_connect:before/connect initialization SSL_connect:unknown state (hangs) user@test2:~$ openssl s_client -CApath /etc/ssl/certs -connect www.tm3.com:443 -state -ssl3 CONNECTED(0003) SSL_connect:before/connect initialization SSL_connect:SSLv3 write client hello A (truncated) Verify return code: 0 (ok) apt-get -y install build-essential libssl-dev wget https://www.openssl.org/source/openssl-1.0.1k.tar.gz tar -xvzf openssl-1.0.1k.tar.gz cd openssl-1.0.1k make dclean make clean export CFLAGS=-fPIC ./config -fstack-protector -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -DOPENSSL_MAX_TLS1_2_CIPHER_LENGTH=50 -DMD32_REG_T=int shared zlib make depend make make install user@test3:~$ uname -a Linux test3 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux user@test3:~$ lsb_release -a | grep Code Codename: trusty user@test3:~$ /usr/local/ssl/bin/openssl version -a OpenSSL 1.0.1k 8 Jan 2015 built on: Wed Jan 14 16:01:29 2015 platform: linux-x86_64 options: bn(64,64) rc4(16x,int) des(idx,cisc,16,int) idea(int) blowfish(idx) compiler: -I. -I.. -I../include -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -fstack-protector -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -DOPENSSL_MAX_TLS1_2_CIPHER_LENGTH=50 -DMD32_REG_T=int -Wa,--noexecstack -m64 -DL_ENDIAN -DTERMIO -O3 -Wall -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM
[Touch-packages] [Bug 1410989] [NEW] SSL_connect:unknown state
Public bug reported: Running openssl s_client, I'm getting some websites (www.tm3.com, ws.myfax.com) that cause requests to hang. I compiled openssl-1.0.1k and it seems to be working now. Is there a more correct fix other than compiling the newest openssl? ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: libssl openssl -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1410989 Title: SSL_connect:unknown state Status in openssl package in Ubuntu: New Bug description: Running openssl s_client, I'm getting some websites (www.tm3.com, ws.myfax.com) that cause requests to hang. I compiled openssl-1.0.1k and it seems to be working now. Is there a more correct fix other than compiling the newest openssl? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1410989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372413] Re: Extensive battery drain on RTM
adding here to track ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New = Confirmed ** Changed in: canonical-devices-system-image Milestone: None = ww03-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1372413 Title: Extensive battery drain on RTM Status in the base for Ubuntu mobile products: Confirmed Status in powerd package in Ubuntu: Confirmed Bug description: Mako, RTM 1 Since upgrading to RTM the battery life is really poor. What used to be a battery drain of 5-10% per hour (which is still high) is now 10-15% per hour. Sometimes the phone runs really hot, so there seem to be something going on in the background that is consuming power. I mostly have bluetooth, GPS (which isn't always working), wifi and cellular on, but that's no difference from when I was running 'devel- proposed' with MultiROM with much less battery consumption. As an example, I started with a full charge at 7am. After some web surfing (15 mins) and watching a couple of youtube videos (on wifi) battery was down to 66% at 9:15. That's 34% in just over two hours! I recharged again before lunch and had the phone idle until coming back 1 hour and 45 mins later to find only 75% of battery left, this time without the phone running particularly hot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1372413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372413] Re: Extensive battery drain on RTM
Also, it would be useful to capture activity of the system using the following over a 10 minute period Still using ppa:colin-king/white: sudo apt-get install eventstat cpustat fnotifystat forkstat sudo eventstat 10 60 eventstat.log (10 seconds of sampling, 60 x a second) And see if the CPU is busy: sudo cpustat 10 60 cpustat.log And see if the file system is busy: sudo fnotifystat 10 60 fnotifystat.log And see if there is excessive thread or process creation: sudo forkstat -D 600 forkstat.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1372413 Title: Extensive battery drain on RTM Status in the base for Ubuntu mobile products: Confirmed Status in powerd package in Ubuntu: Confirmed Bug description: Mako, RTM 1 Since upgrading to RTM the battery life is really poor. What used to be a battery drain of 5-10% per hour (which is still high) is now 10-15% per hour. Sometimes the phone runs really hot, so there seem to be something going on in the background that is consuming power. I mostly have bluetooth, GPS (which isn't always working), wifi and cellular on, but that's no difference from when I was running 'devel- proposed' with MultiROM with much less battery consumption. As an example, I started with a full charge at 7am. After some web surfing (15 mins) and watching a couple of youtube videos (on wifi) battery was down to 66% at 9:15. That's 34% in just over two hours! I recharged again before lunch and had the phone idle until coming back 1 hour and 45 mins later to find only 75% of battery left, this time without the phone running particularly hot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1372413/+subscriptions -- Mailing list: https://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 1410762] [NEW] undefined ref to few functions.
Have you made sure you have all the build dependencies for libcanberra installed? You can do this from the command-line with sudo apt-get build-dep libcanberra -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1410762 Title: undefined ref to few functions. Status in libcanberra package in Ubuntu: New Bug description: make[4]: Entering directory '/home/sagarghuge/checkout/gnome/gtk+/demos/widget-factory' CCLD gtk3-widget-factory /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/libcanberra-gtk3.so: undefined reference to `gdk_x11_window_get_xid' /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/libcanberra-gtk3.so: undefined reference to `gdk_x11_get_xatom_by_name_for_display' /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/libcanberra-gtk3.so: undefined reference to `gdk_x11_display_get_xdisplay' collect2: error: ld returned 1 exit status Makefile:634: recipe for target 'gtk3-widget-factory' failed make[4]: *** [gtk3-widget-factory] Error 1 make[4]: Leaving directory '/home/sagarghuge/checkout/gnome/gtk+/demos/widget-factory' Makefile:548: recipe for target 'all' failed make[3]: *** [all] Error 2 make[3]: Leaving directory '/home/sagarghuge/checkout/gnome/gtk+/demos/widget-factory' Makefile:525: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/sagarghuge/checkout/gnome/gtk+/demos' Makefile:707: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/sagarghuge/checkout/gnome/gtk+' Makefile:600: recipe for target 'all' failed make: *** [all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1410762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371764] Re: Screen does not lock when an unity indicator is open
** Tags removed: verification-needed-trusty ** Tags added: verification-done -- 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/1371764 Title: Screen does not lock when an unity indicator is open Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Screen does not lock when a Unity indicator is open. [ Test Case ] 1. Open an unity Indicator 2. Close the laptop lid¹ Expected behavior: 3. The indicator menu should be closed and the screen is locked Actual behavior: 3. The screen is not locked with the menu visible, it gets locked as soon as the menu is closed. [1] instead of this action, you can also run the script below just before opening an indicator: sleep 3 gdbus call --session --dest com.canonical.Unity \ --object-path /com/canonical/Unity/Session \ --method com.canonical.Unity.Session.Lock [ Regression Potential ] Worst case is the lock screen still does not come up if an indicator is open, which could be a potential security problem. [ Other Info ] The fix for Ubuntu 14.04 LTS is cherry-picked from Ubuntu 14.10 where it has been in production use for some time without apparent regression. This is a special case of bug #49579, although this applies only to the unity indicators. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1371764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410830] Re: Shutdown dialog appears on resume, after a long delay in screen turning on
jibel's method for repro'ing 1) connect to wifi 2) toggle wifi from network indicator 3) suspend 4) wait until the phone really suspends 5) resume -- 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/1410830 Title: Shutdown dialog appears on resume, after a long delay in screen turning on Status in unity8 package in Ubuntu: In Progress Bug description: Sometimes, if you press the power button to resume your device, the screen will stay black for a long time. When it does come on again, the shutdown dialog is likely showing instead of the greeter. You might press the power button again while the screen is black, thinking you didn't actually press it the first time. This will immediately turn the screen on and then off again. At which point a third power button press will turn the screen on for good. This bug is very similar to bug 1383277 (fixed), which involves a shutdown dialog appearing on resume, but for a different reason. This is also very similar to (and may be a dup of) bug 1409003. But since bug 1409003 currently involves an incoming text and this bug does not, I'm treating them as separate for now. This bug is hard to reproduce. It seems to involve leaving and entering wifi/3G zones (or maybe simply toggling the wifi indicator button). But no reliable steps have been recorded yet. I'm guessing that like bug 1383277, it involves some resume-event handler blocking the input stack so that Qt doesn't notice the power- button-release event. And since it takes so long to resume, Qt thinks the user held down the power button long enough to trigger the shutdown dialog. A trivial band-aid for this is to not start the shutdown-dialog timer if the screen is off. But that wouldn't address the source cause of a blocking event handler. So I think this still merits investigation. But if this is a critical/time-sensitive bug, we could slap a band-aid on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1410830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410968] Re: In image 195 krillin 163 mako system settings is not showing updates
** Changed in: ubuntu-system-settings (Ubuntu RTM) Status: Confirmed = In Progress ** Changed in: ubuntu-system-settings (Ubuntu) Status: Confirmed = In Progress -- 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/1410968 Title: In image 195 krillin 163 mako system settings is not showing updates Status in Libqtelegram - a qt library to access telegram.: New Status in ubuntu-system-settings package in Ubuntu: In Progress Status in ubuntu-touch-meta package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu RTM: In Progress Status in ubuntu-touch-meta package in Ubuntu RTM: New Bug description: STEPS: Setup 1 Enable developer mode 2 from pc phablet-config writable-image 3 adb shell 4 sudo vim.tiny /etc/system-image/channel.ini 5 last 2 lines change the number to be back 10 images i.e. change the 195 to 185 6 sudo rm /userdata/.writable_image 7 rm .local/share/ubuntu-push-client/level.db 8 sudo reboot Test 1 Wait for the announcement of a new image 2 Drag down the indicator 3 Click on the image notification 4 Setting page opens on updates but is blank EXPECTED: The updates page is shown and you can click on update ACTUAL: The header is shown other wise it is a blank page after the spinner finishes spinning. To manage notifications about this bug go to: https://bugs.launchpad.net/libqtelegram/+bug/1410968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400827] Re: BlueZ crashing when connecting input channel to a keyboard
** Branch linked: lp:ubuntu/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/1400827 Title: BlueZ crashing when connecting input channel to a keyboard Status in bluez package in Ubuntu: Fix Released Status in bluez package in Ubuntu RTM: In Progress Bug description: On the phone, pairing a keyboard makes BlueZ crash when connecting the input channel (either by calling org.bluez.Input.Connect() on D-Bus or by pressing some keys on the keyboard to make the keyboard open the channel. In order to pair a keyboard with an Ubuntu phone, you need to either apply this branch to ubuntu-system-settings [1] or do it manually with bluez-simple-agent and dbus-send/qdbus. [1] https://code.launchpad.net/~mzanetti/ubuntu-system-settings/bt-input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1400827/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 769147] Re: Insert Smiley menu in Empathy is missing icons
This is affecting me as well on 14.04.1 LTS. Attaching screenshot. ** Attachment added: Empathy-No-Smiley.png https://bugs.launchpad.net/libdbusmenu/+bug/769147/+attachment/4298667/+files/Empathy-No-Smiley.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu in Ubuntu. https://bugs.launchpad.net/bugs/769147 Title: Insert Smiley menu in Empathy is missing icons Status in DBus Menu: Confirmed Status in libdbusmenu package in Ubuntu: Confirmed Bug description: In a conversation with Empathy, open the Conversation menu and go to Insert Smiley. Note that every menu item is _blank_! Each item is supposed to have an icon corresponding to the smiley to be inserted. To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/769147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network
Same problem here on Kubuntu 14.10 on a Dell Latitude E6410 (Intel 5 Series Chipset). Everything worked flawlessly before the upgrade from 14.04 to 14.10. I also tried the supposed fix from #51, but that didn't help. -- 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/1354924 Title: Networkmanager does not autoconnect to wireless network Status in network-manager package in Ubuntu: Confirmed Bug description: When adding a net wireless network and enable connect automatically' networkmanager does not automatically connect to the network wenever possible. I'm running kubuntu 14.10 daily. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 21:30:03 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-11 (29 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710) IpRoute: default via 192.168.0.2 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.213 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390191] Re: Department not shown if there is only one app and it uses X-Ubuntu-Default-Department-ID key
** Changed in: canonical-devices-system-image Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1390191 Title: Department not shown if there is only one app and it uses X-Ubuntu- Default-Department-ID key Status in the base for Ubuntu mobile products: Fix Released Status in unity-scope-click package in Ubuntu: Fix Released Status in unity-scope-click package in Ubuntu RTM: Fix Released Bug description: Department is not shown in Apps department drop-down menu if it has only one application which declares X-Ubuntu-Default-Department-ID=... department mapping (and is preinstalled, ie. wasn't installed from store). This is caused by too restrictive behavior of DepartmentsDb::get_children_departments(..), which filters out subdepartments that don't have any apps in the local departments db (which means that department will never be shown in the departments menu if it has no app installed from the store). This restriction should probably be removed from that method after careful verification if it has no undesired side effects. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390191/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401869] Re: bottom edge arrow label comes in when it shouldn't
This bug was fixed in the package unity8 - 8.02+15.04.20150113.1-0ubuntu1 --- unity8 (8.02+15.04.20150113.1-0ubuntu1) vivid; urgency=low [ Andrea Cimitan ] * support background on horizontal cards with summary (LP: #1393008) [ Gerry Boland ] * DashCommunicator: replace QDBusInterface with a non-blocking simplification which does not introspect the service on creation (LP: #1403508) [ Leo Arias ] * Added an autopilot test for the edges demo. [ Albert Astals ] * Don't show the manage dash pull up arrow on temp scopes (LP: #1401869) * Remove hack, newer Qt already support keyClick(char) * Tests: Add Qt 5.5 removal TODOs * Make sure we use fPIC when compiling files for the static library too * Make sure changing a scope doesn't trigger creation/destruction of delegates until it's finished (LP: #1410122) [ Michael Zanetti ] * patch debian/control file before using it to make it work with mk- build-deps -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 13 Jan 2015 20:58:08 + ** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1401869 Title: bottom edge arrow label comes in when it shouldn't Status in unity8 package in Ubuntu: Fix Released Bug description: Pull the manage dash from the bottom edge, click on a temporary scope. = the bottom edge label slides in for a second and fades out again. It shouldn't appear at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1401869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410122] Re: Dash should not update visibility ranges/buffer when switching scopes
This bug was fixed in the package unity8 - 8.02+15.04.20150113.1-0ubuntu1 --- unity8 (8.02+15.04.20150113.1-0ubuntu1) vivid; urgency=low [ Andrea Cimitan ] * support background on horizontal cards with summary (LP: #1393008) [ Gerry Boland ] * DashCommunicator: replace QDBusInterface with a non-blocking simplification which does not introspect the service on creation (LP: #1403508) [ Leo Arias ] * Added an autopilot test for the edges demo. [ Albert Astals ] * Don't show the manage dash pull up arrow on temp scopes (LP: #1401869) * Remove hack, newer Qt already support keyClick(char) * Tests: Add Qt 5.5 removal TODOs * Make sure we use fPIC when compiling files for the static library too * Make sure changing a scope doesn't trigger creation/destruction of delegates until it's finished (LP: #1410122) [ Michael Zanetti ] * patch debian/control file before using it to make it work with mk- build-deps -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 13 Jan 2015 20:58:08 + ** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1410122 Title: Dash should not update visibility ranges/buffer when switching scopes Status in unity8 package in Ubuntu: Fix Released Bug description: So that switching scopes is as smooth as possible we should not update the visibility ranges/buffer of Dash Category items when switching scopes, that way less creations/destructions of items will happen meaning a smoother animation between scopes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1410122/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403508] Re: Dash startup causes unity8 GUI thread to block for 500ms+
This bug was fixed in the package unity8 - 8.02+15.04.20150113.1-0ubuntu1 --- unity8 (8.02+15.04.20150113.1-0ubuntu1) vivid; urgency=low [ Andrea Cimitan ] * support background on horizontal cards with summary (LP: #1393008) [ Gerry Boland ] * DashCommunicator: replace QDBusInterface with a non-blocking simplification which does not introspect the service on creation (LP: #1403508) [ Leo Arias ] * Added an autopilot test for the edges demo. [ Albert Astals ] * Don't show the manage dash pull up arrow on temp scopes (LP: #1401869) * Remove hack, newer Qt already support keyClick(char) * Tests: Add Qt 5.5 removal TODOs * Make sure we use fPIC when compiling files for the static library too * Make sure changing a scope doesn't trigger creation/destruction of delegates until it's finished (LP: #1410122) [ Michael Zanetti ] * patch debian/control file before using it to make it work with mk- build-deps -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 13 Jan 2015 20:58:08 + ** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1403508 Title: Dash startup causes unity8 GUI thread to block for 500ms+ Status in unity8 package in Ubuntu: Fix Released Bug description: Dash Unity8 communicate via DBus, so unity8 can tell Dash to switch to a scope when needed. This implemented by a DashCommunicator plugin. DashCommunicator inherits AbstractDBusServiceMonitor, which monitors the DBus bus for when the Dash service appears, and when it does, creates a QDBusInterface object for it, which DashCommunicator uses to call methods on the service. All good. QDBusInterface, on creation, introspects the Dash's DBus interface, and this is performed on the GUI thread (see qtbase/src/dbus/qdbusconnection.cpp, there is a moveToThread(GUI Thread) call). If the service is busy/blocked, this will hang the Unity8 GUI thread until unblock/timeout. This is undesirable. We tried to avoid this by having DashCommunicator in its own thread, but that moveToThread is unavoidable. But it's also happening to unity8 on every startup, it's just not noticeable visually as the QML engine is also busy creating objects. It's easier to see by running in a shell: stop unity8-dash start unity8-dash and watching the spinner. You will see the spinner block for 500ms+ before the Dash appears. Here is the DBus traffic during this time: QDBusConnectionPrivate(0xe53c80) got message (signal): QDBusMessage(type=Signal, service=org.freedesktop.DBus, path=/org/freedesktop/DBus, interface=org.freedesktop.DBus, member=NameOwnerChanged, signature=sss, contents=(com.canonical.UnityDash, , :1.124) ) QDBusConnectionPrivate(0xe53c80) sending message (blocking): QDBusMessage(type=MethodCall, service=org.freedesktop.DBus, path=/org/freedesktop/DBus, interface=org.freedesktop.DBus, member=GetNameOwner, signature=, contents=(com.canonical.UnityDash) ) QDBusConnectionPrivate(0xe53c80) got message reply (blocking): QDBusMessage(type=MethodReturn, service=org.freedesktop.DBus, signature=s, contents=(:1.124) ) QDBusConnectionPrivate(0xe53c80) sending message (blocking): QDBusMessage(type=MethodCall, service=com.canonical.UnityDash, path=/com/canonical/UnityDash, interface=org.freedesktop.DBus.Introspectable, member=Introspect, signature=, contents=() ) BLOCK and here is the backtrace of unity8 during this blockage: 38../sysdeps/unix/sysv/linux/x86_64/syscall.S: No such file or directory. (gdb) bt #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f4d03a39470 in _q_futex (op=optimized out, val=optimized out, timeout=optimized out, addr=optimized out) at thread/qmutex_linux.cpp:154 #2 lockInternal_helperfalse (timeout=optimized out, elapsedTimer=optimized out, d_ptr=...) at thread/qmutex_linux.cpp:195 #3 QBasicMutex::lockInternal (this=this@entry=0xe8f9c8) at thread/qmutex_linux.cpp:211 #4 0x7f4d03a39548 in lock (this=0xe8f9c8) at thread/qmutex.h:67 #5 lock (timeout=-1, this=0xe8f9b0) at thread/qmutex.cpp:628 #6 QMutex::lock (this=this@entry=0xe8fd30) at thread/qmutex.cpp:223 #7 0x7f4d02000d5e in QDBusMutexLocker (m=0xe8fd30, s=0xe8fcf0, a=RealAddTimeoutAction, this=synthetic pointer) at qdbusthreaddebug_p.h:191 #8 QDBusDispatchLocker (s=0xe8fcf0, a=RealAddTimeoutAction, this=synthetic pointer) at qdbusthreaddebug_p.h:206 #9 QDBusConnectionPrivate::customEvent (this=0xe8fcf0, e=optimized out) at qdbusintegrator.cpp:1149 #10 0x7f4d03cae9c3 in QObject::event (this=0xe8fcf0, e=optimized out) at kernel/qobject.cpp:1263 #11 0x7f4d03c7e7c5 in QCoreApplication::notify (this=optimized out, receiver=optimized out,
[Touch-packages] [Bug 1393008] Re: Horizontal cards with summary don't get backgrounds
This bug was fixed in the package unity8 -
8.02+15.04.20150113.1-0ubuntu1
---
unity8 (8.02+15.04.20150113.1-0ubuntu1) vivid; urgency=low
[ Andrea Cimitan ]
* support background on horizontal cards with summary (LP: #1393008)
[ Gerry Boland ]
* DashCommunicator: replace QDBusInterface with a non-blocking
simplification which does not introspect the service on creation
(LP: #1403508)
[ Leo Arias ]
* Added an autopilot test for the edges demo.
[ Albert Astals ]
* Don't show the manage dash pull up arrow on temp scopes (LP:
#1401869)
* Remove hack, newer Qt already support keyClick(char)
* Tests: Add Qt 5.5 removal TODOs
* Make sure we use fPIC when compiling files for the static library
too
* Make sure changing a scope doesn't trigger creation/destruction of
delegates until it's finished (LP: #1410122)
[ Michael Zanetti ]
* patch debian/control file before using it to make it work with mk-
build-deps
-- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 13 Jan 2015
20:58:08 +
** Changed in: unity8 (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1393008
Title:
Horizontal cards with summary don't get backgrounds
Status in Ubuntu App Developer site:
Invalid
Status in Ubuntu UX bugs:
New
Status in unity8 package in Ubuntu:
Fix Released
Status in unity8 package in Ubuntu RTM:
New
Bug description:
If I change the WEATHER_TEMPLATE in the scopes example to:
const static string WEATHER_TEMPLATE =
R(
{
schema-version: 1,
template: {
category-layout: carousel,
card-layout: horizontal,
card-size: small,
card-background:color:///#0F0F0F
},
components: {
title: title,
art : {
field: art
},
subtitle: subtitle,
summary: summary
}
}
);
The cards are placed in carousel style, but the background color is
simply omitted, the color of the card stays black.
If the card-layout is changed from horizontal to vertical, the
color is there, and the cards in a carousel style, but the bottom 10%
of the cards seem to be clipped. (Screenshot attached)
This is my first bug report ever, so please let me know what else I
should add, or if I am at the right place at all.
Reported from: http://developer.ubuntu.com/scopes/cookbook/
To manage notifications about this bug go to:
https://bugs.launchpad.net/developer-ubuntu-com/+bug/1393008/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362346] Re: Dash/Hud/Spread search bar text doesn't honour the font scaling settings
Fixed in Unity 7.2.4. Thnx for the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1362346 Title: Dash/Hud/Spread search bar text doesn't honour the font scaling settings Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Text scaling value is ignored by the dash search bar and the spread filter bar. - From u-c-c → accessibility → enable Big Text option Text should size should be increased in both search bar hint and content. [ Test Case ] See above. [ Regression Potential ] Any code change to the Unity desktop shell has the potential to introduce new crashes or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time without apparent regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1362346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373695] Re: Not resizable windows can be moved by dragging them on every edge
** Tags removed: verification-needed-trusty ** Tags added: verification-done -- 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/1373695 Title: Not resizable windows can be moved by dragging them on every edge Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] 1. Open a non resizable window such as Calculator or Unity Control Center 2. Move the mouse to the edge of the window, outside the window itself but in the area that is close at least 10 px. 3. Press the mouse and start to drag Expected behavior: 4. nothing happens Actual behavior 5. the hand cursor is shown and window can be dragged around As side effect, if LIMs are enabled, moving the mouse over a window edge makes the menus to show. [ Test Case ] See above. [ Regression Potential ] Any change to the Unity desktop shell could potentially introduce new crashed or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1373695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411055] [NEW] ubuntu-phone recurring alarm gets disabled after 1st event
Public bug reported: Hi, This started some weeks before christmass (not sure exact image). Currently running vivid image #61 on Mako and the issue is still present. To reproduce: 1. Create an alarm that has to be set for Week-days (Most probably any recurring setup should work) Observed Behavior: The alarm indicator icon will show up until the first alarm event is reached, then the alarm indicator disappears and the alarm will no longer be triggered. If the user tries to re-enable the alarm, it stays enabled for a second, then gets automatically disabled. Only way to set the alarm again is to delete it and create a new one that will also sound only once. Expected Behavior: The alarm indicator must persist until the alarm is manually disabled by the user or no more events are programmed to occur. Let me know if more information is needed. Thanks, Felipe. ** Affects: indicator-datetime (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-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1411055 Title: ubuntu-phone recurring alarm gets disabled after 1st event Status in indicator-datetime package in Ubuntu: New Bug description: Hi, This started some weeks before christmass (not sure exact image). Currently running vivid image #61 on Mako and the issue is still present. To reproduce: 1. Create an alarm that has to be set for Week-days (Most probably any recurring setup should work) Observed Behavior: The alarm indicator icon will show up until the first alarm event is reached, then the alarm indicator disappears and the alarm will no longer be triggered. If the user tries to re-enable the alarm, it stays enabled for a second, then gets automatically disabled. Only way to set the alarm again is to delete it and create a new one that will also sound only once. Expected Behavior: The alarm indicator must persist until the alarm is manually disabled by the user or no more events are programmed to occur. Let me know if more information is needed. Thanks, Felipe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1411055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411059] [NEW] slow system and 3d not working - compiz
Public bug reported: Fujitsu T730 Tablet 2gb ram. 160gb hard drive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 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 Date: Wed Jan 14 20:10:36 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:1508] InstallationDate: Installed on 2015-01-12 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) MachineType: FUJITSU LIFEBOOK T730 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=5200a231-e750-46e1-a8ca-1f010d37ca89 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2010 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB219 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: A4XA6CE501LE1001 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd06/07/2010:svnFUJITSU:pnLIFEBOOKT730:pvr:rvnFUJITSU:rnFJNB219:rvr:cvnA4XA6CE501LE1001:ct10:cvr: dmi.product.name: LIFEBOOK T730 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1~ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jan 13 16:47:15 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14658 vendor SEC xserver.version: 2:1.15.1-0ubuntu2.6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 package-from-proposed 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/1411059 Title: slow system and 3d not working - compiz Status in xorg package in Ubuntu: New Bug description: Fujitsu T730 Tablet 2gb ram. 160gb hard drive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 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 Date: Wed Jan 14 20:10:36 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:1508] InstallationDate: Installed on 2015-01-12 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) MachineType: FUJITSU LIFEBOOK T730 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=5200a231-e750-46e1-a8ca-1f010d37ca89 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2010 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB219 dmi.board.vendor: FUJITSU dmi.chassis.type: 10
[Touch-packages] [Bug 1299741] Re: Shadows shouldn't wrap around to other workspaces/monitors
** Changed in: compiz (Ubuntu Trusty) Status: New = Invalid -- 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/1299741 Title: Shadows shouldn't wrap around to other workspaces/monitors Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in compiz package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Status in compiz source package in Trusty: Invalid Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Window shadows can be seen on adjacent workspaces. [ Test Case ] To reproduce, launch a whole bunch (10, 20, a lot) of windows on workspace 2, and position them on or near the right edge. Then switch to workspace 1, and observe the massive black blob on the left of the screen. [ Regression Potential ] Any code change to the Unity desktop shell could potentially introduce a new crash or lockup. [ Other Info ] The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299741/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410961] Re: Incoming calls show the Emergency Call version of the dialer
Couple of ideas: When answering a call, seems we first switch to dialer which shows the previous page (the keypad view), then the Live Call view is displayed. Can we instead switch to the Live call view before making the dialer visible? I don't know if we get the active signal before or after we are displayed. If before, we should load the Live Call view first. On hangup: if we are in Emergency Mode and the call is ended, can we just transition from the call ended page back to the lockscreen and skip showing the keypad page completely (which shows Emergency Calls in header). ** Also affects: dialer-app (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: dialer-app Importance: Undecided Status: New ** Changed in: dialer-app Importance: Undecided = High ** Tags added: ww05 -- 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/1410961 Title: Incoming calls show the Emergency Call version of the dialer Status in the base for Ubuntu mobile products: Confirmed Status in Dialer app for Ubuntu Touch: New Status in dialer-app package in Ubuntu: Confirmed Status in dialer-app package in Ubuntu RTM: New Bug description: Both just before answering and just after hanging up the user sees Emergency Call in the header. We could go directly to the active call when answering, and directly back to welcome screen after hangup. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386706] Re: [vivid+] Remove totem-mozilla from recommends
Seb, could you or somebody on your team take a look at this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1386706 Title: [vivid+] Remove totem-mozilla from recommends Status in ubuntu-meta package in Ubuntu: New Bug description: Totem upstream removed this plugin [1]. I'm not sure if we plan to pull a newer version of totem, but in any case we should drop totem- mozilla from being on the desktop cd. [1] http://www.hadess.net/2014/04/good-bye-totem-browser-plugin.html More reasons: https://panopticlick.eff.org/ https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/xEbgvWE7wMk/D_07G2lftacJ https://blog.mozilla.org/security/2014/02/28/update-on-plugin-activation/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1386706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361713] Re: Launcher icon count does not honour the text scaling
Bug fixed in Unity 7.2.4 proposed. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1361713 Title: Launcher icon count does not honour the text scaling Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Text scaling value is ignored by icon count (emblem). - From u-c-c → accessibility → enable Big Text option Icon count text should be bigger. [ Test Case ] See above. [ Regression Potential ] Any modification to Unity desktop shell sources has the potential to introduce desktop shell crashes or lockups. [ Addition Info ] The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time with no apparent regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1361713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410968] Re: In image 195 krillin 163 mako system settings is not showing updates
This bug was fixed in the package ubuntu-system-settings - 0.3+15.04.20150114.1~rtm-0ubuntu1 --- ubuntu-system-settings (0.3+15.04.20150114.1~rtm-0ubuntu1) 14.09; urgency=low [ Ken VanDine ] * Added missing depends for qml-module-ubuntu-connectivity (LP: #1410968) -- Ubuntu daily release ps-jenk...@lists.canonical.com Wed, 14 Jan 2015 21:01:31 + ** Changed in: ubuntu-system-settings (Ubuntu RTM) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1410968 Title: In image 195 krillin 163 mako system settings is not showing updates Status in Libqtelegram - a qt library to access telegram.: New Status in ubuntu-system-settings package in Ubuntu: In Progress Status in ubuntu-touch-meta package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu RTM: Fix Released Status in ubuntu-touch-meta package in Ubuntu RTM: New Bug description: STEPS: Setup 1 Enable developer mode 2 from pc phablet-config writable-image 3 adb shell 4 sudo vim.tiny /etc/system-image/channel.ini 5 last 2 lines change the number to be back 10 images i.e. change the 195 to 185 6 sudo rm /userdata/.writable_image 7 rm .local/share/ubuntu-push-client/level.db 8 sudo reboot Test 1 Wait for the announcement of a new image 2 Drag down the indicator 3 Click on the image notification 4 Setting page opens on updates but is blank EXPECTED: The updates page is shown and you can click on update ACTUAL: The header is shown other wise it is a blank page after the spinner finishes spinning. To manage notifications about this bug go to: https://bugs.launchpad.net/libqtelegram/+bug/1410968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409235] Re: Unity8 started failing to build against Qt 5.4.0 on armhf
** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1409235 Title: Unity8 started failing to build against Qt 5.4.0 on armhf Status in unity8 package in Ubuntu: Fix Released Bug description: A no-change rebuild of the newest Unity8 version seems to reliably fail on armhf: https://launchpadlibrarian.net/194468263/buildlog_ubuntu-vivid- armhf.unity8_8.02%2B15.04.20150109.2-0ubuntu2~test1_FAILEDTOBUILD.txt.gz --- /usr/bin/ld: ../../tests/mocks/LightDM/demo/libMockLightDM-demo.a(Greeter.cpp.o): relocation R_ARM_THM_MOVW_ABS_NC against `a local symbol' can not be used when making a shared object; recompile with -fPIC ../../tests/mocks/LightDM/demo/libMockLightDM-demo.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status --- Note that this is now also the first rebuild after reduce-relocations option was dropped from qtbase to workaround bug #1403758. https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1409235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384910] Re: Switching maximized windows using the spread might lead to wrong title and positioning
This bug is fixed in 7.2.4. Thnx for the fix. ** Tags removed: verification-needed-trusty ** Tags added: verification-done -- 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/1384910 Title: Switching maximized windows using the spread might lead to wrong title and positioning Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] 1. Open at least two maximized windows 2. Select one of the windows (last opened seems better) 3. Hit Super + W 4. Start writing to select the other(s) window opened 5. Select it, hitting enter. The title will be wrong (the one of the previous title) while the window buttons will be in the wrong position (see attached sreenshot, in LIM mode, or empty panel otherwise). [ Test Case ] See above. [ Regression Potential ] Any change to the Unity desktop shell could potentially introducer a new crash or lockup. [ Additional Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream Unity where it has been included in the Ubuntu Vivid Vervet dev release for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1384910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385285] Re: Clicking in panel elements when the expo is active, performs to the maximized windows
Tested on trusty and bug seems to be fixed with 7.2.4. ** Tags removed: verification-needed-trusty ** Tags added: verification-done -- 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/1385285 Title: Clicking in panel elements when the expo is active, performs to the maximized windows Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] 1. Open a maximized window (it must be focused when using global menus, not with LIMs) 2. Hit Super+s to enter in expo mode 3. Click in the panel, in different areas and you'll get: - top-left corner buttons will work (although when not visible) - grab area will make possible to grab and focus (when in LIM mode) a window [ Test Case ] See above. [ Regression Potential ] Any code change to the Unity desktop shell could potentially introduce new crashes or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream Unity where it has been in the Ubuntu Vivid Vervet dev release form several weeks without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1385285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384958] Re: Ubuntu Desktop title is moved right as if the window buttons were there
Works as expected ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty ** Tags removed: verification-done-trusty ** Tags added: verification-done -- 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/1384958 Title: Ubuntu Desktop title is moved right as if the window buttons were there Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] 1. Open a maximized window 2. Hit Super+s 3. The Ubuntu Desktop title is moved some pixels to the right, as shown in the attached screenshot. [ Test Case ] See above. [ Regression Potential ] Any code change to the Unity desktop shell has the potential to introduce new crashes or lockups. [ Additional Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream Unity where it has been included in the Ubuntu Vivid Vervet dev release for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1384958/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383468] Re: Windows in non-focused workspaces have not decorations in expo
This bug does seem to be fixed with Unity 7.2.4 proposed update. However it introduces a visual regression that has been reported at https://bugs.launchpad.net/unity/+bug/1411041. I have thereby marked this as verification-failed as per https://wiki.ubuntu.com/QATeam/PerformingSRUVerification. ** Tags removed: verification-needed-trusty ** Tags added: verification-failed -- 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/1383468 Title: Windows in non-focused workspaces have not decorations in expo Status in Unity: Fix Committed Status in Unity 7.2 series: New Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] 1. Open multiple windows and put them in different workspaces 2. Hit Super+S to open the expo 3. Notice that windows that are not in the focused workspaces have no decorations [ Test Case ] See above: decorations should be present with fix. [ Regression Potential ] Decorations in the Spread could be drawn incorrectly. [ Other Info ] Fix for Ubuntu 14.01 LTS was cherry-picked from upstream Unity where it has been in production testing in Ubuntu Vivid Vervet dev release for a few months with no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1383468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359849] Re: call notifications show unknown briefly before showing contact name
** Changed in: canonical-devices-system-image Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1359849 Title: call notifications show unknown briefly before showing contact name Status in the base for Ubuntu mobile products: Fix Released Status in Telephony Service: In Progress Status in telephony-service package in Ubuntu: Fix Released Status in unity-notifications package in Ubuntu: Invalid Status in telephony-service package in Ubuntu RTM: Fix Released Bug description: build 203 on krillin When receing a call from a contact in your address book that has an avatar, the notification is first shown with Unknown caller and default avatar before switching to the correct name and avatar. The name and avatar should be fetched before displaying the notification such that when it's shown it's correct right away. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1359849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394297] Re: quick reply should be disabled for unknown numbers
** Changed in: canonical-devices-system-image Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1394297 Title: quick reply should be disabled for unknown numbers Status in the base for Ubuntu mobile products: Fix Released Status in Telephony Service: In Progress Status in telephony-service package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu RTM: Fix Released Bug description: testing latest vivid build - call the ubuntu phone from a blocked number or unknown number - use one of the quick reply's from the snap decision - you end up wtih a x-ofono-unknown in the messaging app with a failed message Expected result: - disable the quick reply (or don't show at all) if the caller is blocked or unknown To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361751] Re: Launcher Icon shortcut labels don't honor text scaling
Fixed in Unity 7.2.4. Thnx for the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1361751 Title: Launcher Icon shortcut labels don't honor text scaling Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Text scaling value is ignored by icons overlay text. - From u-c-c → accessibility → enable Big Text option Icons overlay text should honor that setting. [ Test Case ] See above. [ Regression Potential ] Any code change to the Unity desktop shell has the potential to introduce new crashes or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for several weeks without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1361751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349281] Re: The exposed open windows are not displayed in the geometric order
The placement of windows in the spread is much more logical now. Thnx for the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1349281 Title: The exposed open windows are not displayed in the geometric order Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] When multiple non-maximised windows of the same program are open and one clicks on the icon of the program in the launcher, they are all shown one next to each other but in an unexpected, difficult-to- predict order: windows that are in the top-left corner of the workspace can be shown in the exposé in the right bottom position or on the left bottom corner. This makes very hard to switch between similarly looking windows like terminals. [ Test Case ] * launch four or so terminal windows; * write something different on each of them to be able to tell them apart; * move each window to a different corner, possibly using the auto-resizing feature of Unity; * click on the terminal icon in the launcher; * many terminal windows are displayed; * choose the thumbnail in the right-top corner; * very likely a window that was in another corner has been selected; * try again various time and realize how confusing this all is. [ Potential Regressions ] An invalid ordering calculation might still position windows in the exposé in unexpected ways. This is not a serious regression and has not been observed under production situations. [ Additional Info ] The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity as released in Ubuntu 14.10 where it demonstrated stability under daily use. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362162] Re: Dash buttons do not honour the text scaling
Fixed in Unity 7.2.4. Thnx for the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1362162 Title: Dash buttons do not honour the text scaling Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Text scaling value is ignored by dash buttons (filters and preview actions). - From u-c-c → accessibility → enable Big Text option Filters and preview action buttons should match this option. [ Test Case ] See above. [ Regression Potential ] Any code change in the Unity desktop shell has the potential to introduce new crashes or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1362162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1237132] Re: Change Show Desktop icon option label when this option is in the state where it will reverse the prior show desktop action.
Fixed in Unity 7.2.4. Thnx for the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1237132 Title: Change Show Desktop icon option label when this option is in the state where it will reverse the prior show desktop action. Status in Ayatana Design: Fix Committed Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] The label on the show desktop / show windows icon in the Unity Switcher does not change even when the function of the button has changed. This can be just a little bit confusing. [ Test Case ] (1) Open several applications with windows. (2) Using Alt-Tab, bring up the Switcher and keeping the Alt key depressed and using the Tab key, navigate to the leftmost icon, which should be labeled Show Desktop. Release all keys. Only the desktop should be displayed. (3) Again using Alt-Tab, navigate back to the leftmost icon. Its label should have changed to Restore Windows to indicate its changed function. [ Regression Potential ] About the worst that could happen is the incorrect label is applied to the icon in the Switcher. [ Other Info ] The Ubuntu 14.04 LTS SRU has been cherry-picked from the Ubuntu 14.04 release where it has shown to be stable. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1237132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1332509] Re: Lockscreen misses arrow activator.
Fixed in Unity 7.2.4. Thnx for the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1332509 Title: Lockscreen misses arrow activator. Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] Unity lock screen password entry should have an activator arrow like unity-greeter. [Test Case] Using the Unity desktop shell, lock the screen using Super-L (or you favourite method). When the lockscreen is displayed, a little wedgie should be displayed at the right-hand end of the password entry field, and clicking on that wedgie should perform the authentication action. [Regression Potential] This is a cosmetic change to allow click-clicky mouse interaction to work just like hitting [Enter]. The biggest potential for regression is that the asset (artwork) does not get displayed or the mouse click does not work just like hitting Enter does. [Other Info] The Ubuntu 14.04 LTS SRU was cherry-picked from Ubuntu 14.10 whwere it has been in production use for some months without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1332509/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383468] Re: Windows in non-focused workspaces have not decorations in expo
The problem reported in #141104 was present previous to this fix going in. I can verify seeing it in Ubuntu 14.04 without -proposed and in 14.10 (which does not have this fix yet). -- 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/1383468 Title: Windows in non-focused workspaces have not decorations in expo Status in Unity: Fix Committed Status in Unity 7.2 series: New Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] 1. Open multiple windows and put them in different workspaces 2. Hit Super+S to open the expo 3. Notice that windows that are not in the focused workspaces have no decorations [ Test Case ] See above: decorations should be present with fix. [ Regression Potential ] Decorations in the Spread could be drawn incorrectly. [ Other Info ] Fix for Ubuntu 14.01 LTS was cherry-picked from upstream Unity where it has been in production testing in Ubuntu Vivid Vervet dev release for a few months with no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1383468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 359741] Re: [needs-packaging] printer lexmark x4650 not supported ( driver needed )
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/359741 Title: [needs-packaging] printer lexmark x4650 not supported ( driver needed ) Status in cups package in Ubuntu: Expired Bug description: No driver is available for printer lexmark x4650, driver is needed. And btw printer configurator offen is crashing ( ubuntu 9.04 ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/359741/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411075] [NEW] bluez-simple-agent crashes
Public bug reported: bluez-simple-agent crashes, in utopic, on a fresh install and fresh boot. same crash after updating packages and reboot: $ bluez-simple-agent hci0 00:0C:8A:AA:FE:70 x Traceback (most recent call last): File /usr/bin/bluez-simple-agent, line 127, in module device = adapter.FindDevice(args[1]) File /usr/lib/python3/dist-packages/dbus/proxies.py, line 70, in __call__ return self._proxy_method(*args, **keywords) File /usr/lib/python3/dist-packages/dbus/proxies.py, line 145, in __call__ **keywords) File /usr/lib/python3/dist-packages/dbus/connection.py, line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.bluez.Error.DoesNotExist: Does Not Exist this appears similar to Bug #1227584, but the dbus exception is not the same. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluez 4.101-0ubuntu20 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: LXDE Date: Wed Jan 14 20:30:08 2015 InstallationDate: Installed on 2015-01-11 (3 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro root=UUID=9212f425-c8f3-4c80-8d62-41faf2b27d30 panic=30 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: K8M800-8237 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/09/2008:svn:pn:pvr:rvn:rnK8M800-8237:rvr:cvn:ct3:cvr: hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:15:83:6A:58:96 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:1170 acl:0 sco:0 events:65 errors:0 TX bytes:1056 acl:0 sco:0 commands:65 errors:0 mtime.conffile..etc.bluetooth.audio.conf: 2015-01-11T15:59:05.078489 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 utopic -- 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/1411075 Title: bluez-simple-agent crashes Status in bluez package in Ubuntu: New Bug description: bluez-simple-agent crashes, in utopic, on a fresh install and fresh boot. same crash after updating packages and reboot: $ bluez-simple-agent hci0 00:0C:8A:AA:FE:70 x Traceback (most recent call last): File /usr/bin/bluez-simple-agent, line 127, in module device = adapter.FindDevice(args[1]) File /usr/lib/python3/dist-packages/dbus/proxies.py, line 70, in __call__ return self._proxy_method(*args, **keywords) File /usr/lib/python3/dist-packages/dbus/proxies.py, line 145, in __call__ **keywords) File /usr/lib/python3/dist-packages/dbus/connection.py, line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.bluez.Error.DoesNotExist: Does Not Exist this appears similar to Bug #1227584, but the dbus exception is not the same. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluez 4.101-0ubuntu20 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: LXDE Date: Wed Jan 14 20:30:08 2015 InstallationDate: Installed on 2015-01-11 (3 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro root=UUID=9212f425-c8f3-4c80-8d62-41faf2b27d30 panic=30 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: K8M800-8237 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/09/2008:svn:pn:pvr:rvn:rnK8M800-8237:rvr:cvn:ct3:cvr: hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:15:83:6A:58:96 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:1170 acl:0 sco:0 events:65 errors:0 TX bytes:1056 acl:0 sco:0 commands:65 errors:0 mtime.conffile..etc.bluetooth.audio.conf: 2015-01-11T15:59:05.078489 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1411075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411084] [NEW] My sound doesn't work and all my output devices in sound settings are gone.
Public bug reported: I was working on installing different themes for my desktop and after uninstalling one of them my sound stopped working. I check the sound settings and all my output devices disappeared. The icon disappeared unless i refreshed the toggle on the sound settings menu, but its just the speaker icon and there's no sound waves or x coming out of it, yet it says that it's muted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Jan 14 22:14:17 2015 InstallationDate: Installed on 2014-12-04 (41 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2013 dmi.bios.vendor: Alienware dmi.bios.version: A06 dmi.board.name: 07MJ2Y dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A06 dmi.modalias: dmi:bvnAlienware:bvrA06:bd10/16/2013:svnAlienware:pnAlienware14:pvrA06:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA06: dmi.product.name: Alienware 14 dmi.product.version: A06 dmi.sys.vendor: Alienware ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1411084 Title: My sound doesn't work and all my output devices in sound settings are gone. Status in pulseaudio package in Ubuntu: New Bug description: I was working on installing different themes for my desktop and after uninstalling one of them my sound stopped working. I check the sound settings and all my output devices disappeared. The icon disappeared unless i refreshed the toggle on the sound settings menu, but its just the speaker icon and there's no sound waves or x coming out of it, yet it says that it's muted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Jan 14 22:14:17 2015 InstallationDate: Installed on 2014-12-04 (41 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2013 dmi.bios.vendor: Alienware dmi.bios.version: A06 dmi.board.name: 07MJ2Y dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A06 dmi.modalias: dmi:bvnAlienware:bvrA06:bd10/16/2013:svnAlienware:pnAlienware14:pvrA06:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA06: dmi.product.name: Alienware 14 dmi.product.version: A06 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1411084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1332947] Re: HDPI: unity randomly turns on large text in universal access
Verified on a Ubuntu 14.04.1, before the upgrade I can reproduce the issue easily with unity 7.2.3+14.04.20140826-0ubuntu1. Then I reset the settings and upgrade to unity 7.2.4+14.04.20141217-0ubuntu1, now the issue hasn't been reproduced yet after more than 50 log outin. Thanks guys. I'll update the tags now. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1332947 Title: HDPI: unity randomly turns on large text in universal access Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Using a display scaling factor of 1.0 the 'large text' setting is sometimes enabled automatically on session start, doubling the scaling factor. [ Test Case ] (1) Using the System Settings Displays Scale for menu and title bars slider, set the scaling to a value 1 (for example, 1.88). (2) Log out and in several times. Since this problem occurs as a result of a race condition somewhere, it is not reliably reproducable. [ Regression Potential ] Any code change to the Unity desktop shell could introduce a new crash or lockup. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time without demonstrating regression. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1332947/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411100] Re: guest user not removed after guest session ends
Sorry, this is the real patch. ** Patch added: Patch to use non-conflicting variable names https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1411100/+attachment/4298811/+files/guest-account_variable_names.patch -- 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/1411100 Title: guest user not removed after guest session ends Status in lightdm package in Ubuntu: New Bug description: The /usr/sbin/giest-account script contains a bug which prevents the removal of guest accounts: $ sudo /usr/sbin/guest-account remove guest-Hhiook /usr/sbin/guest-account: line 129: UID: readonly variable Maybe this is related to /bin/sh actually beeing a Bash: $ ll -d /bin/sh lrwxrwxrwx 1 root root 4 Jan 1 01:44 /bin/sh - bash* But since using Bash as default sh is still a feature of Ubuntu, all scripts should work with both. Running the script with dash actually works: $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva umount: /tmp/guest-ZWCtva: mountpoint not found umount: /tmp/guest-ZWCtva: mountpoint not found Removing user `guest-ZWCtva' ... Warning: group `guest-ZWCtva' has no more members. Done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1411100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411100] Re: guest user not removed after guest session ends
This patch renames the variables in the remove part of the script so that they cannot conflict with reserved Bash variables -- 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/1411100 Title: guest user not removed after guest session ends Status in lightdm package in Ubuntu: New Bug description: The /usr/sbin/giest-account script contains a bug which prevents the removal of guest accounts: $ sudo /usr/sbin/guest-account remove guest-Hhiook /usr/sbin/guest-account: line 129: UID: readonly variable Maybe this is related to /bin/sh actually beeing a Bash: $ ll -d /bin/sh lrwxrwxrwx 1 root root 4 Jan 1 01:44 /bin/sh - bash* But since using Bash as default sh is still a feature of Ubuntu, all scripts should work with both. Running the script with dash actually works: $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva umount: /tmp/guest-ZWCtva: mountpoint not found umount: /tmp/guest-ZWCtva: mountpoint not found Removing user `guest-ZWCtva' ... Warning: group `guest-ZWCtva' has no more members. Done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1411100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410762] Re: undefined ref to few functions.
Hi Luke, Thanks for replying, Yes I have all dependencies for libcanberra installed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1410762 Title: undefined ref to few functions. Status in libcanberra package in Ubuntu: New Bug description: make[4]: Entering directory '/home/sagarghuge/checkout/gnome/gtk+/demos/widget-factory' CCLD gtk3-widget-factory /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/libcanberra-gtk3.so: undefined reference to `gdk_x11_window_get_xid' /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/libcanberra-gtk3.so: undefined reference to `gdk_x11_get_xatom_by_name_for_display' /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/libcanberra-gtk3.so: undefined reference to `gdk_x11_display_get_xdisplay' collect2: error: ld returned 1 exit status Makefile:634: recipe for target 'gtk3-widget-factory' failed make[4]: *** [gtk3-widget-factory] Error 1 make[4]: Leaving directory '/home/sagarghuge/checkout/gnome/gtk+/demos/widget-factory' Makefile:548: recipe for target 'all' failed make[3]: *** [all] Error 2 make[3]: Leaving directory '/home/sagarghuge/checkout/gnome/gtk+/demos/widget-factory' Makefile:525: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/sagarghuge/checkout/gnome/gtk+/demos' Makefile:707: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/sagarghuge/checkout/gnome/gtk+' Makefile:600: recipe for target 'all' failed make: *** [all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1410762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 447374] Re: Ubuntu restarted the session during high activity
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/447374 Title: Ubuntu restarted the session during high activity Status in xorg package in Ubuntu: Expired Bug description: Was encoding a video and working on several other things when the machine just logged out. Hoping this thing will attach all the logs necessary... ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 HibernationDevice: RESUME=UUID=1e90ca36-1c73-46f0-8699-61c4cc7e4f21 MachineType: - N/A NonfreeKernelModules: nvidia Package: linux-image-2.6.28-15-generic 2.6.28-15.52 ProcCmdLine: root=UUID=bb0503a4-ae25-4eea-b442-03a8bc98ff22 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.28-15.52-generic SourcePackage: linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/447374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 373452] Re: Hp DV5 audio noise
[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/373452 Title: Hp DV5 audio noise Status in alsa-driver package in Ubuntu: Expired Bug description: When reboot the speakers/headphones make a very noisy cracking noise. Under vista is ok. I use: Ubuntu 9.04 hp dv5 1115el Thank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/373452/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 925401] Re: [HP Pavilion dv5-1199el Entertainment Notebook PC] Reboot audio noise
[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/925401 Title: [HP Pavilion dv5-1199el Entertainment Notebook PC] Reboot audio noise Status in alsa-driver package in Ubuntu: Expired Bug description: With my HP DV5-1199el precise pangolin makes a crackling noise on reboot. I didn't have this in prior releases. sudo lspci |grep Audio 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.24+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.91-0ubuntu1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zombx 2190 F xfce4-volumed zombx 2202 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xdf30 irq 50' Mixer name : 'Nvidia MCP77/78 HDMI' Components : 'HDA:111d76b2,103c3603,00100302 HDA:10de0006,10de0101,0010' Controls : 29 Simple ctrls : 15 Date: Thu Feb 2 11:53:23 2012 InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: Upgraded to precise on 2012-01-27 (5 days ago) dmi.bios.date: 08/20/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3603 dmi.board.vendor: Quanta dmi.board.version: 02.26 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.21:bd08/20/2009:svnHewlett-Packard:pnHPPaviliondv5NotebookPC:pvrRev1:rvnQuanta:rn3603:rvr02.26:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv5 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/925401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 449196] Re: High Xorg CPU usage?
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/449196 Title: High Xorg CPU usage? Status in xorg package in Ubuntu: Expired Bug description: Binary package hint: xorg Xorg is usually using about 25% of CPU, sometimes it reaches 30-40%. It doesn't hurt but as I have a Core2 Duo P8600 CPU which is quite fast I assume 25% is quite a large amount of resources. Or am I wrong? ProblemType: Bug Architecture: amd64 Date: Mon Oct 12 03:36:20 2009 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Alpha amd64 (20091008) MachineType: Dell Inc. Latitude E6500 Package: xorg 1:7.4+3ubuntu5 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-13-generic root=UUID=e53695eb-254d-4e3f-a123-fbad8c303dd9 ro ProcVersionSignature: Ubuntu 2.6.31-13.44-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu5 libgl1-mesa-glx 7.6.0-1ubuntu2 libdrm2 2.4.14-1ubuntu1 xserver-xorg-video-intel 2:2.9.0-1ubuntu1 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu3 SourcePackage: xorg Uname: Linux 2.6.31-13-generic x86_64 XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 05/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0NY667 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/08/2009:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0NY667:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6500 dmi.sys.vendor: Dell Inc. fglrx: Not loaded system: distro: Ubuntu architecture: x86_64kernel: 2.6.31-13-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/449196/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 586749] Re: ubuntu restart send me to login screen random
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/586749 Title: ubuntu restart send me to login screen random Status in xorg package in Ubuntu: Expired Bug description: The problem has been happing every day on a Ubuntu 10.04 LTS (i386). The gdm restart random...send me to the login screen The output from /var/log/syslog : May 27 08:51:31 mycomputer gdm-simple-greeter[31894]: Gtk-WARNING: /build/buildd/gtk+2.0-2.20.0/gtk/gtkwidget.c:5636: widget not within a GtkWindow May 27 08:51:33 mycomputer gdm-session-worker[31896]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed May 27 08:51:34 mycomputer bonobo-activation-server (muser-31933): could not associate with desktop session: Failed to connect to socket /tmp/dbus-jjkAdpxeCV: Connection refused Anybody ? Regards ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 CurrentDmesg: [ 27.436021] eth1: no IPv6 routers present [ 27.444507] eth0: no IPv6 routers present Date: Fri May 28 11:48:55 2010 DkmsStatus: Error: [Errno 2] No such file or directory InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) Lsusb: Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Compaq dx2200 MT ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=dc424e26-4d34-41bb-86a8-eea9f3d6c188 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.iso88591 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg crash dmi.bios.date: 08/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: MS7254 1.05 dmi.board.name: 0A48 dmi.board.vendor: MSI dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrMS72541.05:bd08/14/2006:svnHewlett-Packard:pnHPCompaqdx2200MT:pvr:rvnMSI:rn0A48:rvr:cvnMSI:ct3:cvr: dmi.product.name: HP Compaq dx2200 MT dmi.sys.vendor: Hewlett-Packard glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/586749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
