[Touch-packages] [Bug 1495553] Re: [System settings] VPN configuration not possible

2015-12-08 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: backlog => ww08-2016

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1495553

Title:
  [System settings] VPN configuration not possible

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  Reproduce:
  Try configuring VPN

  What happens:
  You can't.

  What should happen:
  You should be able to.

  Current specification: https://wiki.ubuntu.com/Networking#VPNs

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495553/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1495553] Re: [System settings] VPN configuration not possible

2015-12-08 Thread Jean-Baptiste Lallement
@Matthew, yes please file a bug to add support for L2TP and PPTP to the
phone. This report is about the lack of UI to configure the VPN.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1495553

Title:
  [System settings] VPN configuration not possible

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  Reproduce:
  Try configuring VPN

  What happens:
  You can't.

  What should happen:
  You should be able to.

  Current specification: https://wiki.ubuntu.com/Networking#VPNs

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495553/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523929] [NEW] "No such schema 'org.gtk.Settings.Debug'" error upon trying to activate GTKInspector shortcuts

2015-12-08 Thread Nikita Yerenkov-Scott
Public bug reported:

I have been following the Ubuntu GNOME newcomers guide, and in the
GTKInspector section (https://wiki.gnome.org/Projects/GTK%2B/Inspector)
it says:

"To enable the debugger, either start your app with
GTK_DEBUG=interactive in your environment, or run gsettings set
org.gtk.Settings.Debug enable-inspector-keybinding true and launch the
debugger with the Control-Shift-I or Control-Shift-D keyboard
shortcuts."

However, upon running that code I just get this error:

No such schema 'org.gtk.Settings.Debug'

And the keyboard shortcuts don't work... I have checked in
"org.gtk.Settings" and there is no "Debug" section.

---

OS Information:

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 15.10
Release:15.10
Codename:   wily
Flavour: GNOME
GNOME Version: 3.18

Package Information:

libgtk-3-0:
  Installed: 3.18.5-1ubuntu2~wily1
  Candidate: 3.18.5-1ubuntu2~wily1
  Version table:
 *** 3.18.5-1ubuntu2~wily1 0
500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ 
wily/main amd64 Packages
100 /var/lib/dpkg/status
 3.16.7-0ubuntu3 0
500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

** Affects: ubuntu-gnome
 Importance: Undecided
 Status: New

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  I have been following the Ubuntu GNOME newcomers guide, and in the
  GTKInspector section (https://wiki.gnome.org/Projects/GTK%2B/Inspector)
  it says:
  
- "To enable the debugger, either start your app with
+ "To enable the debugger, either start your app with
  GTK_DEBUG=interactive in your environment, or run gsettings set
  org.gtk.Settings.Debug enable-inspector-keybinding true and launch the
  debugger with the Control-Shift-I or Control-Shift-D keyboard
  shortcuts."
  
  However, upon running that code I just get this error:
  
  No such schema 'org.gtk.Settings.Debug'
  
  And the keyboard shortcuts don't work... I have checked in
- o"rg.gtk.Settings" and there is no "Debug" section.
+ "org.gtk.Settings" and there is no "Debug" section.
  
  ---
  
  OS Information:
  
- No LSB modules are available.
- Distributor ID:   Ubuntu
- Description:  Ubuntu 15.10
- Release:  15.10
- Codename: wily
- Flavour: GNOME
- GNOME Version: 3.18
+ No LSB modules are available.
+ Distributor ID:   Ubuntu
+ Description:  Ubuntu 15.10
+ Release:  15.10
+ Codename: wily
+ Flavour: GNOME
+ GNOME Version: 3.18
  
  Package Information:
  
- libgtk-3-0:
-   Installed: 3.18.5-1ubuntu2~wily1
-   Candidate: 3.18.5-1ubuntu2~wily1
-   Version table:
-  *** 3.18.5-1ubuntu2~wily1 0
- 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ 
wily/main amd64 Packages
- 100 /var/lib/dpkg/status
-  3.16.7-0ubuntu3 0
- 500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
+ libgtk-3-0:
+   Installed: 3.18.5-1ubuntu2~wily1
+   Candidate: 3.18.5-1ubuntu2~wily1
+   Version table:
+  *** 3.18.5-1ubuntu2~wily1 0
+ 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ 
wily/main amd64 Packages
+ 100 /var/lib/dpkg/status
+  3.16.7-0ubuntu3 0
+ 500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1523929

Title:
  "No such schema 'org.gtk.Settings.Debug'" error upon trying to
  activate GTKInspector shortcuts

Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I have been following the Ubuntu GNOME newcomers guide, and in the
  GTKInspector section
  (https://wiki.gnome.org/Projects/GTK%2B/Inspector) it says:

  "To enable the debugger, either start your app with
  GTK_DEBUG=interactive in your environment, or run gsettings set
  org.gtk.Settings.Debug enable-inspector-keybinding true and launch the
  debugger with the Control-Shift-I or Control-Shift-D keyboard
  shortcuts."

  However, upon running that code I just get this error:

  No such schema 'org.gtk.Settings.Debug'

  And the keyboard shortcuts don't work... I have checked in
  "org.gtk.Settings" and there is no "Debug" section.

  ---

  OS Information:

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.10
  Release:  15.10
  Codename: wily
  Flavour: GNOME
  GNOME Version: 3.18

  Package Information:

  libgtk-3-0:
    Installed: 3.18.5-1ubuntu2~wily1
    Candidate: 3.18.5-1ubuntu2~wily1
    Version table:
   *** 3.18.5-1ubuntu2~wily1 0
     

[Touch-packages] [Bug 1521737] Re: Cannot enable bluetooth

2015-12-08 Thread Jean-Baptiste Lallement
** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Committed

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
Milestone: None => ww02-2016

-- 
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/1521737

Title:
  Cannot enable bluetooth

Status in Canonical System Image:
  Fix Committed
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  MX4 running propsoed 181 with debug enabled kernel

  Paired to car and saw signal strength indicated
  Left car, renetered car and noticed not paried and BT disabled in the 
indicator
  tried to enable, 1 min later it resets to disabled

  Bluetoothd is no longer running
  there was a previous crash file in /var/crash

  see syslog attached

  /var/lib/urfkill/saved-states:
  [BLUETOOTH]
  soft=false
  prev-soft=false

  /var/log/upstart/bluetooth-touch.log
  start: Unknown job: bluetooth-touch-arale

  Reboot and bt is enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521737/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1512290] Re: gnome-screenshot produces very low quality blurry screenshots

2015-12-08 Thread Sebastien Bacher
I did another upload reverting that change for now to unblock the other
fixes

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1512290

Title:
  gnome-screenshot produces very low quality blurry screenshots

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in gtk+3.0 source package in Wily:
  Triaged

Bug description:
  I believe, this is because I am using a HiDPI display. Every time I
  take a screenshot, I get a blurry image. This is not what I want when
  making a screenshot. Everywhere else when I make a screenshot, I get a
  100% copy of my screen, pixel-perfect.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-screenshot 3.16.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  2 13:11:55 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-22 (10 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1512290/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523929] Re: "No such schema 'org.gtk.Settings.Debug'" error upon trying to activate GTKInspector shortcuts

2015-12-08 Thread Nikita Yerenkov-Scott
I already have that package installed.

** Changed in: gtk+3.0 (Ubuntu)
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1523929

Title:
  "No such schema 'org.gtk.Settings.Debug'" error upon trying to
  activate GTKInspector shortcuts

Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I have been following the Ubuntu GNOME newcomers guide, and in the
  GTKInspector section
  (https://wiki.gnome.org/Projects/GTK%2B/Inspector) it says:

  "To enable the debugger, either start your app with
  GTK_DEBUG=interactive in your environment, or run gsettings set
  org.gtk.Settings.Debug enable-inspector-keybinding true and launch the
  debugger with the Control-Shift-I or Control-Shift-D keyboard
  shortcuts."

  However, upon running that code I just get this error:

  No such schema 'org.gtk.Settings.Debug'

  And the keyboard shortcuts don't work... I have checked in
  "org.gtk.Settings" and there is no "Debug" section.

  ---

  OS Information:

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.10
  Release:  15.10
  Codename: wily
  Flavour: GNOME
  GNOME Version: 3.18

  Package Information:

  libgtk-3-0:
    Installed: 3.18.5-1ubuntu2~wily1
    Candidate: 3.18.5-1ubuntu2~wily1
    Version table:
   *** 3.18.5-1ubuntu2~wily1 0
  500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ 
wily/main amd64 Packages
  100 /var/lib/dpkg/status
   3.16.7-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1523929/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1247216] Re: Support for XMPP

2015-12-08 Thread flohack
Plus add OTR to the conversation and you got a rock solid IM solution
that I would like much more to use on my mobile than WhatsApp or
Telegram. Different XEP coverage by some clients can be a pain, but that
should be not a reason not to try to get this done for Ubuntu Touch.
People started hating Skype, so some of them might get interested in
Jabber again.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1247216

Title:
  Support for XMPP

Status in messaging-app package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Hi All,

  basically there are three things that block me to move to Ubuntu
  Touch. A missing spotify app (already in developement :) ), a missing
  mail app (planned for 14.04 :)  ) and finally a missing IM app --
  especially for XMPP.

  Thusly, I propose adding support for XMPP to the messaging-app. It
  already uses telepathy so we should be able to add this functionality.
  I would also be willing to work on this if somebody points me out
  where to start.

  I guess we would have to break this down into several work packages:
  setting up accounts, online/offline handling of friends, choosing
  protocols when composing a message etc. But first I would like to get
  some feedback if you would be okay with such a feature. Maybe it is
  already planned?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1247216/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523975] [NEW] [desktop] system-settings crashes on startup with 5.4.1+dfsg-2ubuntu11~vivid1

2015-12-08 Thread Ken VanDine
Public bug reported:

The patch introduced in 5.4.1+dfsg-2ubuntu11~vivid1 causes system-
settings to crash on startup for desktop users.  See stack trace at
http://pastebin.ubuntu.com/13825552/

** Affects: canonical-devices-system-image
 Importance: Critical
 Assignee: John McAleely (john.mcaleely)
 Status: New

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: High
 Assignee: Tony Espy (awe)
 Status: New

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Tony Espy (awe)

** Changed in: qtbase-opensource-src (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1523975

Title:
  [desktop] system-settings crashes on startup with 5.4.1+dfsg-
  2ubuntu11~vivid1

Status in Canonical System Image:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  The patch introduced in 5.4.1+dfsg-2ubuntu11~vivid1 causes system-
  settings to crash on startup for desktop users.  See stack trace at
  http://pastebin.ubuntu.com/13825552/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523975/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523975] Re: [desktop] system-settings crashes on startup with 5.4.1+dfsg-2ubuntu11~vivid1

2015-12-08 Thread Tony Espy
** Summary changed:

- system-settings crashes on startup with 5.4.1+dfsg-2ubuntu11~vivid1 
+ [desktop] system-settings crashes on startup with 5.4.1+dfsg-2ubuntu11~vivid1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1523975

Title:
  [desktop] system-settings crashes on startup with 5.4.1+dfsg-
  2ubuntu11~vivid1

Status in Canonical System Image:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  The patch introduced in 5.4.1+dfsg-2ubuntu11~vivid1 causes system-
  settings to crash on startup for desktop users.  See stack trace at
  http://pastebin.ubuntu.com/13825552/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523975/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1522150] Re: Cut off messages

2015-12-08 Thread Krzysztof Tataradziński
Okey, so should I report that bug anywhere else or leave here?

** Changed in: canonical-devices-system-image
   Status: Incomplete => New

** Changed in: messaging-app (Ubuntu)
   Status: Incomplete => 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/1522150

Title:
  Cut off messages

Status in Canonical System Image:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  Hello,

  My girlfriend send me some SMS with text: 'Umiem. Skoro się pytam to chcę 
(emoticon) bo miałeś wczoraj rację, że dawno nie wychodziliśmy', but I've 
received 'nie wychodzilismy'.
  We tested that exact text few times - all the time I'm receiving 'nie 
wychodzilismy'. Could anyone test that text? Please look at 'ś' that 
disappeared in my phone.
  We test that without emoticon and - magic, I've received all text, but 
without polish special signs (like ł ś ę, etc.). Inserted other emoticon - 
received 'ie wychodzilismy'.
  I must also admin that I'm getting 's', 'e', etc. instead of 'ś', 'ę', etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1522150/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

2015-12-08 Thread Tony Espy
Just a quick update to mention that the change to the NM bearer plugin
seems to have caused a regression when qtbase is installed from the PPA
onto a desktop ( for UI development work ).

To reproduce, the overlay PPA needs to be added as a software source,
then ubuntu-system-settings installed/upgraded ( which pulls in qtbase
).  See bug #1523975 for details.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Fix Committed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1522150] Re: Cut off messages

2015-12-08 Thread Tony Espy
@Krystoff

So to summarize:

1. If SwiftKey is used on an Android device to send a message containing
diacritics, the message is displayed on Ubuntu minus the diacritics.

2. If a SwiftKey emoticon is included in the sent message, the received
message is truncated ( and still lacks the diacritics ).

So far, the traces to date have shown that the IncomingMessage DBus
signals from ofono show the same text as displayed by the messaging app.

The next check is to get traces of the raw contents of the incoming SMS
messages.  To do this:

 - as root, edit the file /etc/init/ofono.override on the phone
 - add the line "env OFONO_RIL_TRACE=y" to the file, just below the line "env 
OFONO_RIL_NUM_SIM_SLOTS=1"
 - reboot the phone
 - re-try sending the various messages to the phone
 - when finished, please attach the file /var/log/syslog to this bug

Also, if it's possible to send the same message with diacritics and no
emoticon via the Hangouts app, please give this a try.  If this works,
then the blame probably lies with the encoding specified by SwiftKey.

-- 
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/1522150

Title:
  Cut off messages

Status in Canonical System Image:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  Hello,

  My girlfriend send me some SMS with text: 'Umiem. Skoro się pytam to chcę 
(emoticon) bo miałeś wczoraj rację, że dawno nie wychodziliśmy', but I've 
received 'nie wychodzilismy'.
  We tested that exact text few times - all the time I'm receiving 'nie 
wychodzilismy'. Could anyone test that text? Please look at 'ś' that 
disappeared in my phone.
  We test that without emoticon and - magic, I've received all text, but 
without polish special signs (like ł ś ę, etc.). Inserted other emoticon - 
received 'ie wychodzilismy'.
  I must also admin that I'm getting 's', 'e', etc. instead of 'ś', 'ę', etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1522150/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1518420] Re: There is no way to unset action 'shortcut' property

2015-12-08 Thread Bill Filler
** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
Milestone: None => ww02-2016

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

** Changed in: canonical-devices-system-image
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1518420

Title:
  There is no way to unset action 'shortcut' property

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Since all the actions are enabled and active by default (causing the
  Ambiguous bug#1514856) I implement a workaround in my app to disable
  action shortcuts if the page is not active. Something like:

  shortcut: page.active ? "Esc" : ""

  The problem is, that I am receiving  serveral  error messages on
  terminal while running the app:

  "QML Action: Invalid shortcut:"

  -
  Note: the shortcut (and any property that can be reset) should be 
cleared/reset using undefined. So the above binding should look like:
  shortcut: page.active ? "Esc" : undefined

  Note2: actions added to any ActionItem derived type will automatically
  activate/deactivate depending on the page or dialog activation. This
  means that those Actions which are in an inactive Page will not be
  active, so there will be no need for the above binding.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518420/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523975] Re: [desktop] system-settings crashes on startup with 5.4.1+dfsg-2ubuntu11~vivid1

2015-12-08 Thread Tony Espy
** Changed in: qtbase-opensource-src (Ubuntu)
   Importance: Critical => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1523975

Title:
  [desktop] system-settings crashes on startup with 5.4.1+dfsg-
  2ubuntu11~vivid1

Status in Canonical System Image:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  The patch introduced in 5.4.1+dfsg-2ubuntu11~vivid1 causes system-
  settings to crash on startup for desktop users.  See stack trace at
  http://pastebin.ubuntu.com/13825552/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523975/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523985] [NEW] evolution-source-registery needs a restart to pick newly activated uoa accounts

2015-12-08 Thread Sebastien Bacher
Public bug reported:

Using current xenial version
- go to the uoa settings
- add a google account

- > you get a notification that there is an auth issue (that's a weird
workflow but needed because the application needs to auth but e-d-s
can't do UI prompting)

- auth e-d-s in the settings

-> the new account should be active/listed in the indicator or gnome-
calendar but is not


The issue is probably that e-d-s connect to the "account-created" signal on a 
AgManager object and adds the account correctly, but at this point the 
authentification/confirmation is not done yet so the account fails to active, 
and there is no following callback after the authentification is done. 

It seems that AgManager doesn't provide an appropriate signal that can
be used there so some work might be needed on the signon side

** Affects: evolution-data-server
 Importance: Unknown
 Status: Unknown

** Affects: evolution-data-server (Ubuntu)
 Importance: High
 Assignee: Alberto Mardegan (mardy)
 Status: Triaged


** Tags: rls-x-incoming

** Changed in: evolution-data-server (Ubuntu)
   Importance: Undecided => High

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Triaged

** Changed in: evolution-data-server (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Bug watch added: GNOME Bug Tracker #759187
   https://bugzilla.gnome.org/show_bug.cgi?id=759187

** Also affects: evolution-data-server via
   https://bugzilla.gnome.org/show_bug.cgi?id=759187
   Importance: Unknown
   Status: Unknown

** Tags added: rls-x-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1523985

Title:
  evolution-source-registery needs a restart to pick newly activated uoa
  accounts

Status in evolution-data-server:
  Unknown
Status in evolution-data-server package in Ubuntu:
  Triaged

Bug description:
  Using current xenial version
  - go to the uoa settings
  - add a google account

  - > you get a notification that there is an auth issue (that's a weird
  workflow but needed because the application needs to auth but e-d-s
  can't do UI prompting)

  - auth e-d-s in the settings

  -> the new account should be active/listed in the indicator or gnome-
  calendar but is not

  
  The issue is probably that e-d-s connect to the "account-created" signal on a 
AgManager object and adds the account correctly, but at this point the 
authentification/confirmation is not done yet so the account fails to active, 
and there is no following callback after the authentification is done. 

  It seems that AgManager doesn't provide an appropriate signal that can
  be used there so some work might be needed on the signon side

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1523985/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523975] Re: [desktop] system-settings crashes on startup with 5.4.1+dfsg-2ubuntu11~vivid1

2015-12-08 Thread Bill Filler
** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

** Changed in: canonical-devices-system-image
Milestone: None => ww02-2016

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1523975

Title:
  [desktop] system-settings crashes on startup with 5.4.1+dfsg-
  2ubuntu11~vivid1

Status in Canonical System Image:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  The patch introduced in 5.4.1+dfsg-2ubuntu11~vivid1 causes system-
  settings to crash on startup for desktop users.  See stack trace at
  http://pastebin.ubuntu.com/13825552/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523975/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523975] Re: system-settings crashes on startup with 5.4.1+dfsg-2ubuntu11~vivid1

2015-12-08 Thread Bill Filler
** 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 qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1523975

Title:
  [desktop] system-settings crashes on startup with 5.4.1+dfsg-
  2ubuntu11~vivid1

Status in Canonical System Image:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  The patch introduced in 5.4.1+dfsg-2ubuntu11~vivid1 causes system-
  settings to crash on startup for desktop users.  See stack trace at
  http://pastebin.ubuntu.com/13825552/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523975/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

2015-12-08 Thread Marc Deslauriers
Uploaded same fix to Wily for processing by the SRU team.

** Description changed:

+ [Impact]
+ 
+ On systems with a long hostname, nano either segfaults or refuses to
+ work properly.
+ 
+ [Test Case]
+ 1- set a long hostname with "hostname thisisareallyreallyreallylonghostname"
+ 2- try and edit a file: "nano /etc/hosts"
+ 3- make sure there is no segfault, or error in nano window: "Couldn't 
determine host name..."
+ 
+ [Regression Potential]
+ 
+ Patch is quite simple an obvious. A regression would mean lock files
+ wouldn't work properly.
+ 
+ 
+ 
+ 
+ 
+ Original description:
+ 
  Description:  Ubuntu 15.10
  Release:  15.10
  
  nano:
-   Installed: 2.4.2-1
-   Candidate: 2.4.2-1
-   Version table:
-  *** 2.4.2-1 0
- 500 http://mirror.bytemark.co.uk/ubuntu/ wily/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 2.4.2-1
+   Candidate: 2.4.2-1
+   Version table:
+  *** 2.4.2-1 0
+ 500 http://mirror.bytemark.co.uk/ubuntu/ wily/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
- 
- After upgrading Ubuntu 15.04 to 15.10, when I run nano as root on a file it 
just segfaults. I'm not having this problem on other 15.04->15.10 upgrades
+ After upgrading Ubuntu 15.04 to 15.10, when I run nano as root on a file
+ it just segfaults. I'm not having this problem on other 15.04->15.10
+ upgrades
  
  strace is https://p.defau.lt/?q7xGwt3HoqB74xTawUUHDA
  catchsegv is https://p.defau.lt/?0SPQY_bDj6F6j1ZKeToQoA
- 
  
  Under gdb with nano-dbgsym installed, it gives
  
  #0  main (argc=2, argv=0x7fffe688) at ../../src/nano.c:2768
  
- 
- If I run it as sudo nano filename.txt, it gives an error as below rather than 
segfaulting
+ If I run it as sudo nano filename.txt, it gives an error as below rather
+ than segfaulting
  
  [ Couldn't determine hostname for lock file: File name too long ]
  
- 
  Both my user and root have the same locale settings. I've tried
  regenerating the locales

** Changed in: nano (Ubuntu Wily)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bugs/1509081

Title:
  nano segfaults as root after upgrade to 15.10

Status in nano package in Ubuntu:
  Fix Released
Status in nano source package in Wily:
  In Progress

Bug description:
  [Impact]

  On systems with a long hostname, nano either segfaults or refuses to
  work properly.

  [Test Case]
  1- set a long hostname with "hostname thisisareallyreallyreallylonghostname"
  2- try and edit a file: "nano /etc/hosts"
  3- make sure there is no segfault, or error in nano window: "Couldn't 
determine host name..."

  [Regression Potential]

  Patch is quite simple an obvious. A regression would mean lock files
  wouldn't work properly.

  
  

  
  Original description:

  Description:  Ubuntu 15.10
  Release:  15.10

  nano:
    Installed: 2.4.2-1
    Candidate: 2.4.2-1
    Version table:
   *** 2.4.2-1 0
  500 http://mirror.bytemark.co.uk/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  After upgrading Ubuntu 15.04 to 15.10, when I run nano as root on a
  file it just segfaults. I'm not having this problem on other
  15.04->15.10 upgrades

  strace is https://p.defau.lt/?q7xGwt3HoqB74xTawUUHDA
  catchsegv is https://p.defau.lt/?0SPQY_bDj6F6j1ZKeToQoA

  Under gdb with nano-dbgsym installed, it gives

  #0  main (argc=2, argv=0x7fffe688) at ../../src/nano.c:2768

  If I run it as sudo nano filename.txt, it gives an error as below
  rather than segfaulting

  [ Couldn't determine hostname for lock file: File name too long ]

  Both my user and root have the same locale settings. I've tried
  regenerating the locales

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1509081/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1522150] Re: Cut off messages

2015-12-08 Thread Tiago Salem Herrmann
In this case I believe the bug is in ofono/ril, since the
IncomingMessage signal we get from ofono already contains the message
cut off.

-- 
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/1522150

Title:
  Cut off messages

Status in Canonical System Image:
  Incomplete
Status in messaging-app package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  My girlfriend send me some SMS with text: 'Umiem. Skoro się pytam to chcę 
(emoticon) bo miałeś wczoraj rację, że dawno nie wychodziliśmy', but I've 
received 'nie wychodzilismy'.
  We tested that exact text few times - all the time I'm receiving 'nie 
wychodzilismy'. Could anyone test that text? Please look at 'ś' that 
disappeared in my phone.
  We test that without emoticon and - magic, I've received all text, but 
without polish special signs (like ł ś ę, etc.). Inserted other emoticon - 
received 'ie wychodzilismy'.
  I must also admin that I'm getting 's', 'e', etc. instead of 'ś', 'ę', etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1522150/+subscriptions

-- 
Mailing list: https://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 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

2015-12-08 Thread Serge Hallyn
Quoting Mike Gabriel (mike.gabr...@das-netzwerkteam.de):
> Hi all,
> 
> today I worked on backporting available fixes for CVE-2015-1335 to LXC
> 0.7.x (as found in Debian squeeze-lts).
> 
> The patch is attached, I am still in the testing-for-regressions phase.
> Can any of the LXC devs take a look at the patch and maybe see if it is
> suitable for Ubuntu 12.04, as well?

Hi,

So the thing to look for is any unconverted "mount" calls.  It
looks like the lxc_setup_fs() calls to mount_fs() are not being
protected.  So the contianer admin could attack through a /proc
symlink.

> Greets,
> Mike (aka sunweaver at debian.org)
> 
> ** Patch added: "Backport fix for CVE-2015-1335 to LXC 0.7.x (Ubuntu 12.04 / 
> Debian squeeze-lts)"
>
> https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+attachment/4529631/+files/CVE-2015-1335.patch
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> Matching subscriptions: lxc
> https://bugs.launchpad.net/bugs/1476662
> 
> Title:
>   lxc-start symlink vulnerabilities may allow guest to read host
>   filesystem, interfere with apparmor
> 
> Status in lxc package in Ubuntu:
>   Fix Released
> 
> Bug description:
>   lxc-start shuffles around mounts using helper directory
>   /usr/lib/x86_64-linux-gnu/lxc (guest root fs is mounted here)
> 
>   It then modifies mounts operating in guest root directory before
>   invoking init. As it does not check if all mount points are
>   directories, a malicious guest may modify its internal structure
>   before shutdown (or was created using manipulated image) and then when
>   started again, guest may
> 
>   * Access  the whole host root filesystem
> 
>   * Block switching from lxc-start apparmor profile to lxc-container-
>   default
> 
>   
>   # Real putold before pivot-root (root fs will end here)
>   mkdir -p /x/lxc_putold
> 
>   # Faked putold
>   ln -s /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold lxc_putold
>   mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc
>   touch /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc/mounts
> 
>   
>   # proc fake
>   mkdir -p /x/proc
>   umount /proc
>   rmdir /proc
>   ln -s /usr/lib/x86_64-linux-gnu/lxc/x/proc proc
> 
>   mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr 
> /usr/lib/x86_64-linux-gnu/lxc/x/proc/self
>   touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr/current
>   touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/self/status
> 
> 
>   The  issue was also found during
>   https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.html
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1476662

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  lxc-start shuffles around mounts using helper directory
  /usr/lib/x86_64-linux-gnu/lxc (guest root fs is mounted here)

  It then modifies mounts operating in guest root directory before
  invoking init. As it does not check if all mount points are
  directories, a malicious guest may modify its internal structure
  before shutdown (or was created using manipulated image) and then when
  started again, guest may

  * Access  the whole host root filesystem

  * Block switching from lxc-start apparmor profile to lxc-container-
  default

  
  # Real putold before pivot-root (root fs will end here)
  mkdir -p /x/lxc_putold

  # Faked putold
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold lxc_putold
  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc
  touch /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc/mounts

  
  # proc fake
  mkdir -p /x/proc
  umount /proc
  rmdir /proc
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/proc proc

  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr 
/usr/lib/x86_64-linux-gnu/lxc/x/proc/self
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr/current
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/self/status


  The  issue was also found during
  https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1446906] Re: lxc container with postfix, permission denied on mailq

2015-12-08 Thread Anton Statutov
I encountered this problem too on Ubuntu 15.04 running 3.19.0-39 kernel.
Fixed  it by turned off apparmor profile for LXC container by adding
"lxc.aa_profile = unconfined" into container's config. In my case
increased security risk is acceptable, but it's desirable to fix it the
right way.  Is there any information in what kernel version it will be
fixed and when this updates will be available in standartd ubuntu
repositories?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1446906

Title:
  lxc container with postfix, permission denied on mailq

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  on three Vivid host, all of them up-to-date, I have the problem
  described here:

  https://bugs.launchpad.net/ubuntu/utopic/+source/linux/+bug/1390223

  That bug report shows the problem was fixed, but it is not (at least
  on current Vivid)

  
  ii  linux-image-generic 3.19.0.15.14   amd64  Generic Linux kernel 
image
  ii  lxc 1.1.2-0ubuntu3 amd64  Linux Containers 
userspace tools
  ii  apparmor2.9.1-0ubuntu9 amd64  User-space parser 
utility for AppArmor

  
  Reproducible with:

  $ sudo lxc-create -n test -t ubuntu
  $ sudo lxc-start -n test

  (inside container)

  $ sudo apt-get install postfix
  $ mailq
  postqueue: warning: close: Permission denied

  
  dmesg shows:
  [82140.386109] audit: type=1400 audit(1429661150.086:17067): 
apparmor="DENIED" operation="file_perm" profile="lxc-container-default" 
name="public/showq" pid=27742 comm="postqueue" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zoolook1913 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=aa25401d-0553-43dc-b7c8-c530fe245fb6
  InstallationDate: Installed on 2015-02-27 (53 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 20150
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-03-29 (24 days ago)
  UserGroups: adm docker libvirtd lpadmin sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN95WW(V9.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3194WIN8 STD SGL
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN95WW(V9.00):bd12/19/2012:svnLENOVO:pn20150:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 20150
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446906/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1524016] [NEW] Xorg crash

2015-12-08 Thread Lior Goikhburg
Public bug reported:

Trusty under KVM

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9
Uname: Linux 3.19.0-39-generic x86_64
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Dec  8 17:25:39 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100]
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-39-generic 
root=UUID=a22fcb14-fd0c-4f7f-8d95-67434d8c2e47 ro console=tty1 console=ttyS0
Renderer: Software
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Dec  8 17:24:33 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputAT Translated Set 2 keyboard KEYBOARD, id 7
 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8
xserver.errors:
 cirrus: The PCI device 0xb8 at 00@00:02:0 has a kernel module claiming it.
 cirrus: This driver cannot operate until it has been unloaded.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output   VGA-0
xserver.version: 2:1.15.1-0ubuntu2.7
xserver.video_driver: modesetting

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug crash 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/1524016

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Trusty under KVM

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-39-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Dec  8 17:25:39 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100]
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-39-generic 
root=UUID=a22fcb14-fd0c-4f7f-8d95-67434d8c2e47 ro console=tty1 console=ttyS0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-trusty
  dmi.sys.vendor: QEMU
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  

[Touch-packages] [Bug 1498129] Re: Asus Xonar U7 S/PDIF output not recognized by pulseaudio

2015-12-08 Thread g0ukb
** Attachment added: "default.pa"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+attachment/4531525/+files/default.pa

-- 
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/1498129

Title:
  Asus Xonar U7 S/PDIF output not recognized by pulseaudio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The external USB audio card Asus Xonar U7 is capable of both analog and 
digital output.
  ALSA name for the digital (S/PDIF) output is hw:1,1, and it is listed in 
aplay -l output, and aplay can output to it:
  aplay -D plughw:1,1 sample.wav. So, direct alsa sound works fine.

  However, pulseadio does not recognize the digital output of Xonar U7,
  it offers only analog output.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25
  Uname: Linux 3.13.0-63-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aoand  3756 F pulseaudio
   /dev/snd/controlC0:  aoand  3756 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 21 21:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-02-20 (1674 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-05-19 (490 days ago)
  dmi.bios.date: 11/29/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET71WW (3.21 )
  dmi.board.name: 7448CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7448CTO
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1498129] Re: Asus Xonar U7 S/PDIF output not recognized by pulseaudio

2015-12-08 Thread g0ukb
** Attachment added: "USB-Audio.conf"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+attachment/4531526/+files/USB-Audio.conf

** Changed in: alsa-driver (Ubuntu)
   Status: Expired => New

-- 
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/1498129

Title:
  Asus Xonar U7 S/PDIF output not recognized by pulseaudio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The external USB audio card Asus Xonar U7 is capable of both analog and 
digital output.
  ALSA name for the digital (S/PDIF) output is hw:1,1, and it is listed in 
aplay -l output, and aplay can output to it:
  aplay -D plughw:1,1 sample.wav. So, direct alsa sound works fine.

  However, pulseadio does not recognize the digital output of Xonar U7,
  it offers only analog output.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25
  Uname: Linux 3.13.0-63-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aoand  3756 F pulseaudio
   /dev/snd/controlC0:  aoand  3756 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 21 21:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-02-20 (1674 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-05-19 (490 days ago)
  dmi.bios.date: 11/29/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET71WW (3.21 )
  dmi.board.name: 7448CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7448CTO
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

2015-12-08 Thread Alberto Salvia Novella
** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

** No longer affects: nss (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Latest libnss3 upgrade have broken all the browser's queries; no
  matter of which is used. For example: url auto-completion fails

  ERR_SSL_PROTOCOL_ERROR
  Unable to make a secure connection to the server. This may be a problem with 
the server or it may be requiring a client authentication certificate that you 
don't have.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libnss3 2:3.21-1ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-0.8-generic 4.3.0
  Uname: Linux 4.3.0-0-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 27 13:50:26 2015
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1498129] Re: Asus Xonar U7 S/PDIF output not recognized by pulseaudio

2015-12-08 Thread g0ukb
I will change the status from 'expired' to 'new' to see if anyone has
any thoughts on this

** Attachment added: "pactl_list.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+attachment/4531524/+files/pactl_list.txt

-- 
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/1498129

Title:
  Asus Xonar U7 S/PDIF output not recognized by pulseaudio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The external USB audio card Asus Xonar U7 is capable of both analog and 
digital output.
  ALSA name for the digital (S/PDIF) output is hw:1,1, and it is listed in 
aplay -l output, and aplay can output to it:
  aplay -D plughw:1,1 sample.wav. So, direct alsa sound works fine.

  However, pulseadio does not recognize the digital output of Xonar U7,
  it offers only analog output.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25
  Uname: Linux 3.13.0-63-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aoand  3756 F pulseaudio
   /dev/snd/controlC0:  aoand  3756 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 21 21:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-02-20 (1674 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-05-19 (490 days ago)
  dmi.bios.date: 11/29/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET71WW (3.21 )
  dmi.board.name: 7448CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7448CTO
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1498129] Re: Asus Xonar U7 S/PDIF output not recognized by pulseaudio

2015-12-08 Thread g0ukb
I have now proven that everything works if I manually set the iec958
sink via:

pactl load-module module-alsa-sink device=plughw:3,1

and as a workaround have added the load-module to my local default.pa
file

I don't have the skill to figure out why pulseaudio isn't picking this
up correctly

** Attachment added: "aplay -L"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+attachment/4531523/+files/aplay-L.txt

-- 
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/1498129

Title:
  Asus Xonar U7 S/PDIF output not recognized by pulseaudio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The external USB audio card Asus Xonar U7 is capable of both analog and 
digital output.
  ALSA name for the digital (S/PDIF) output is hw:1,1, and it is listed in 
aplay -l output, and aplay can output to it:
  aplay -D plughw:1,1 sample.wav. So, direct alsa sound works fine.

  However, pulseadio does not recognize the digital output of Xonar U7,
  it offers only analog output.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25
  Uname: Linux 3.13.0-63-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aoand  3756 F pulseaudio
   /dev/snd/controlC0:  aoand  3756 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 21 21:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-02-20 (1674 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-05-19 (490 days ago)
  dmi.bios.date: 11/29/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET71WW (3.21 )
  dmi.board.name: 7448CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7448CTO
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1524000] Re: PyGIWarning: UbuntuAppLaunch was imported without specifying a version first

2015-12-08 Thread Andrew Hayzen
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

This is an issue that is related to python gi on Xenial (16.04),
therefore I am adding pygobject to this bug and as it affects all the
core apps which use this kind of import I'm marking this as invalid for
music specifically.

** Also affects: pygobject (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: music-app
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1524000

Title:
  PyGIWarning: UbuntuAppLaunch was imported without specifying a version
  first

Status in Ubuntu Music App:
  Invalid
Status in pygobject package in Ubuntu:
  New

Bug description:
  When launching Autopilot tests for Music App you get an error indicating that 
UbuntuAppLaunch was imported without specifying a version first.
  This is the error:

  autopilot run music_app
  /usr/lib/python2.7/dist-packages/autopilot/application/_launcher.py:23: 
PyGIWarning: UbuntuAppLaunch was imported without specifying a version first. 
Use gi.require_version('UbuntuAppLaunch', '2') before import to ensure that the 
right version gets loaded.
from gi.repository import GLib, UbuntuAppLaunch
  Loading tests from: /home/victor/Development/music-app/tests/autopilot

  Failed to import test module: music_app.tests.test_music
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
  __import__(name)
File 
"/home/victor/Development/music-app/tests/autopilot/music_app/__init__.py", 
line 9, in 
  from ubuntuuitoolkit import (
  ImportError: No module named ubuntuuitoolkit

  Tests running...
  ==
  ERROR: unittest.loader.ModuleImportFailure.music_app.tests.test_music
  --
  Traceback (most recent call last):
  ImportError: Failed to import test module: music_app.tests.test_music
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
  __import__(name)
File 
"/home/victor/Development/music-app/tests/autopilot/music_app/__init__.py", 
line 9, in 
  from ubuntuuitoolkit import (
  ImportError: No module named ubuntuuitoolkit

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1524000/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1467790] Re: Location settings inconsistent between first-run setup + System Settings

2015-12-08 Thread Lukáš Tinkl
** Branch linked: lp:~lukas-kde/unity8/oobe

-- 
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/1467790

Title:
  Location settings inconsistent between first-run setup + System
  Settings

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 15.04 r35

  1. Go through the first-run setup, paying particular attention to the 
"Location" step.
  2. In System Settings, open "Security & Privacy" > "Location access".

  What you see:
  1. The options are presented using checkboxes.
  2. Exactly the same options are presented using an ItemSelector.

  What you should see: The options are presented in exactly the same
  way, except for their color scheme, on both screens. Any design
  changes always show up on both screens.

  This bug occurs because the screens are implemented separately:
  

  

  Even if the implementations were synced, it is almost inevitable that 
sometime later, designers and/or engineers would forget to update one when 
updating the other.

  It may save time to fix bug 1388178 at the same time as this bug.

  The equivalent for Wi-Fi settings is bug 1467438.

  --- Design Comment ---
   11/08/2015

  Please see designs are attached below comments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1467790/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1446906] Re: lxc container with postfix, permission denied on mailq

2015-12-08 Thread Serge Hallyn
@astatutov,

Could you please test the kernels posted in comment #28?

@jjohansen, confused, why is this bug not marked as affecting linux?  Is
there a reason?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1446906

Title:
  lxc container with postfix, permission denied on mailq

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  on three Vivid host, all of them up-to-date, I have the problem
  described here:

  https://bugs.launchpad.net/ubuntu/utopic/+source/linux/+bug/1390223

  That bug report shows the problem was fixed, but it is not (at least
  on current Vivid)

  
  ii  linux-image-generic 3.19.0.15.14   amd64  Generic Linux kernel 
image
  ii  lxc 1.1.2-0ubuntu3 amd64  Linux Containers 
userspace tools
  ii  apparmor2.9.1-0ubuntu9 amd64  User-space parser 
utility for AppArmor

  
  Reproducible with:

  $ sudo lxc-create -n test -t ubuntu
  $ sudo lxc-start -n test

  (inside container)

  $ sudo apt-get install postfix
  $ mailq
  postqueue: warning: close: Permission denied

  
  dmesg shows:
  [82140.386109] audit: type=1400 audit(1429661150.086:17067): 
apparmor="DENIED" operation="file_perm" profile="lxc-container-default" 
name="public/showq" pid=27742 comm="postqueue" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zoolook1913 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=aa25401d-0553-43dc-b7c8-c530fe245fb6
  InstallationDate: Installed on 2015-02-27 (53 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 20150
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-03-29 (24 days ago)
  UserGroups: adm docker libvirtd lpadmin sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN95WW(V9.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3194WIN8 STD SGL
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN95WW(V9.00):bd12/19/2012:svnLENOVO:pn20150:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 20150
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446906/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1351534] Re: device doesn't detect current time zone

2015-12-08 Thread Lukáš Tinkl
** Branch linked: lp:~lukas-kde/unity8/oobe

-- 
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/1351534

Title:
  device doesn't detect current time zone

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  On first phone boot, or after flashing a new image, the user's time
  zone isn't auto-detected.  Instead, the system always defaults to UTC.

  It should probably default instead to checking the cell provider for
  time zone information, or GPS (if enabled), or if there is a network
  connection, get an approximate location from that (look up the current
  access point, in case it has been mapped).

  I'm not entirely sure which system component or launchpad project this
  belongs in, so some re-targeting help would be appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1351534/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1475023] Re: Wifi for Enterprise APs cause the welcome wizard to exit into the main system

2015-12-08 Thread Lukáš Tinkl
** Branch linked: lp:~lukas-kde/unity8/oobe

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1475023

Title:
  Wifi for Enterprise APs cause the welcome wizard to exit into the main
  system

Status in indicator-network package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  1. Install a fresh image (post ota5)
  2. Start running the wizard
  3. Get to the wifi page and select an enterprise AP

  EXPECTED:
  I expect the wifi setup to return me to the welcome wizard

  ACTUAL:
  The DUT exits the welcome wizard, enters into system settings and on exit has 
you on the logged in phone.  Also pin setup is failed to be activated so the 
phone is insecure.

  VERSION:
  current build number: 4
  device name: arale
  channel: ubuntu-touch/rc/meizu.en
  last update: 2015-07-15 20:25:41
  version version: 4
  version ubuntu: 20150710
  version device: 20150709-8965e37
  version custom: 20150709-814-6-40

  MODIFICATION:
  OTA'd from image 2 to image 4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1475023/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1438003] Re: (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-glib.

2015-12-08 Thread Kike
Also suffering this issue. Same as Daan Wilmer and Krupier123. Specially
if torrent is on (probably excessive connections) but also using browser
as usual. Connection stops (even appears connected but can't access the
web) then sometimes restarting connection works until a point when
restarting the system is the only solution. It's very annoying. Please
do something about it!!!

-- 
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/1438003

Title:
  (1) Creating object for path
  '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-
  glib.

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  While attempting to connect to an SSID for the first time, it fails, and I 
consistently get:
  (1) Creating object for path 
'/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-glib.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Mar 29 23:08:37 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-03-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlan0   wifi  connected /org/freedesktop/NetworkManager/Devices/4  
www.ubuntu.com  71c36534-c491-4479-aa91-9238b10f3945  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlan1   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   eth0ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1438003/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1515712] Re: maliit-server becomes deadlocked

2015-12-08 Thread Tony Espy
@Bill

Can you have someone re-test with the latest rc-proposed?  As mentioned
in my previous comment, we removed a large amount of NM related DBus
code from the Qt Bearer Management plugin as a fix for bug #1480877.
This work all landed in the PPA and is being tested by QA for release as
OTA8.5.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to maliit-framework in
Ubuntu.
https://bugs.launchpad.net/bugs/1515712

Title:
  maliit-server becomes deadlocked

Status in Canonical System Image:
  Confirmed
Status in maliit-framework package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  on krillin, rc-proposed 175

  I'm experiencing keyboard not popping up on any application. Can't
  remember if this was after a reboot or if it was working for a while
  and then stopped. I believe it's after a reboot.

  Upon inspection, it appears maliit-server process is deadlocked (see
  thread dump below). Also, there is no log in .cache/upstart/maliit-
  server.log only old logs maliit-server.log.1.gz etc, which leads me to
  believe this problem happens after reboot.

  Seems that some QNetwork initialization is happening and this is
  causing an issue (see Threads 3, 2, and 1). We should figure out why
  we are even doing any network stuff at all, as we probably shouldn't
  be.

  (gdb) t a a bt

  Thread 14 (Thread 0xb2cc2440 (LWP 2844)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb3d03cdc in ?? () from /usr/lib/arm-linux-gnueabihf/libmircommon.so.5
  #2  0xb3d04c96 in ?? () from /usr/lib/arm-linux-gnueabihf/libmircommon.so.5
  #3  0xb67ec2a0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #4  0xb6010490 in start_thread () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #5  0xb66e0c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 13 (Thread 0xb2197440 (LWP 3128)):
  #0  0xb435a840 in ?? ()
  #1  0xb436e29c in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 12 (Thread 0xb240fb40 (LWP 3129)):
  #0  0xb5c61836 in ?? () from /lib/arm-linux-gnueabihf/librt.so.1
  #1  0xb5c618a4 in ?? () from /lib/arm-linux-gnueabihf/librt.so.1
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 11 (Thread 0xb1976440 (LWP 3130)):
  #0  0xb6018d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #1  0xb60146b0 in pthread_cond_wait@@GLIBC_2.4 () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #2  0xb225e0a8 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 10 (Thread 0xb1176440 (LWP 3131)):
  ---Type  to continue, or q  to quit---
  #0  0xb6018d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #1  0xb60146b0 in pthread_cond_wait@@GLIBC_2.4 () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #2  0xb225e0a8 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 9 (Thread 0xb0697440 (LWP 3143)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 8 (Thread 0xafcff440 (LWP 3144)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 7 (Thread 0xaeaff440 (LWP 3146)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 6 (Thread 0xae1ff440 (LWP 3148)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 5 (Thread 0xacb49440 (LWP 3167)):
  #0  0xb66e1132 in epoll_wait () from /lib/arm-linux-gnueabihf/libc.so.6
  ---Type  to continue, or q  to quit---
  #1  0xb3b62312 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #2  0xb3b642ea in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #3  0xb3b6484a in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #4  0xb3b4d678 in core::dbus::Bus::run() () from 
/usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #5  0xb67ec2a0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #6  0xb6010490 in start_thread () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #7  0xb66e0c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  Backtrace stopped: 

[Touch-packages] [Bug 1505328] Re: Cups SSL is vulernable to POODLE

2015-12-08 Thread Bryan Quigley
New debdiff with fix for C#15

** Patch added: "cups_1.7.2-0ubuntu1.7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1505328/+attachment/4531562/+files/cups_1.7.2-0ubuntu1.7.debdiff

-- 
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/1505328

Title:
  Cups SSL is vulernable to POODLE

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Trusty:
  Triaged

Bug description:
  [Impact]

   * Cups in Trusty is vulnerbable to the Poodle SSLv3. This disables it by 
default.
   * Users who have clients that don't support TLS1.0 will not be able to 
connect, unless
   they specify the additional options in cupsd.conf.

  [Test Case]

   * Install cupsd with /etc/cups/cupsd.conf SSL options SSLPort 443 and 
SSLOptions None
     * This should show up as having RC4 and SSLv3 disabled via a test like 
ssllabs.
   * Same but specify SSLOptions to AllowSSL3 or AllowRC4.

  [Regression Potential]

   * One assumption was this should only affect WinXP and even then only
  IE6 winxp users.  If incorrect more could be affected.

   * The biggest issue could be that AllowSSL3 or AllowRC4 don't work in
  some unknown corner case.  There's no evidence of this and other
  distros have deployed a very similar patch.

  [Other Info]

   * Only targetting 14.04 because of my assumption that if you're on
  12.04 you are more likely to have older clients connecting to it.

  Original description:

  On 12.04 and 14.04 if you enable cups ssl you are vulnerable to
  poodle, and there does not appear to be any way to mitigate it in Cups
  config.

  Ubuntu 14.04 - 
https://www.ssllabs.com/ssltest/analyze.html?d=190.35.213.162.lcy-02.canonistack.canonical.com=on
  Ubuntu 12.04 - 
https://www.ssllabs.com/ssltest/analyze.html?d=191.35.213.162.lcy-02.canonistack.canonical.com=on

  Fixed in wily - 
https://www.ssllabs.com/ssltest/analyze.html?d=192.35.213.162.lcy-02.canonistack.canonical.com=on
  Upstream fix - https://www.cups.org/str.php?L4476

  Should we disable ssvl3 in the 12.04/14.04 cups by default and
  backport the option to turn it back on?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1505328/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1522150] Re: Cut off messages

2015-12-08 Thread Krzysztof Tataradziński
I'm getting 'error writing /etc/... : Read-only file system' while trying to 
save file. Could anyone with writable file system test that?
Regarding 1. I think that is not SwiftKey related - if you see at my logs, 
sometimes there are diacritics, sometimes not, maybe randomly?

-- 
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/1522150

Title:
  Cut off messages

Status in Canonical System Image:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  Hello,

  My girlfriend send me some SMS with text: 'Umiem. Skoro się pytam to chcę 
(emoticon) bo miałeś wczoraj rację, że dawno nie wychodziliśmy', but I've 
received 'nie wychodzilismy'.
  We tested that exact text few times - all the time I'm receiving 'nie 
wychodzilismy'. Could anyone test that text? Please look at 'ś' that 
disappeared in my phone.
  We test that without emoticon and - magic, I've received all text, but 
without polish special signs (like ł ś ę, etc.). Inserted other emoticon - 
received 'ie wychodzilismy'.
  I must also admin that I'm getting 's', 'e', etc. instead of 'ś', 'ę', etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1522150/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1449555] Re: password request for cryptswap1 during boot when encrypted home directory selected

2015-12-08 Thread Piet Stevens
*** This bug is a duplicate of bug 1453738 ***
https://bugs.launchpad.net/bugs/1453738

Note: I am not using LVM.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1449555

Title:
  password request for cryptswap1 during boot when encrypted home
  directory selected

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  On a system freshly installed (haven't tried the upgrade route) where
  the user selects to encrypt their home directory, they will get a
  password prompt during boot and at other times on the command-line
  requesting a password for cryptswap1.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: cryptsetup 2:1.6.1-1ubuntu7
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 28 09:02:12 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-28 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  crypttab: cryptswap1 UUID=c9d10691-df3f-49ae-a734-cdf2cbbaee8e /dev/urandom 
swap,offset=1024,cipher=aes-xts-plain64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449555/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1449555] Re: password request for cryptswap1 during boot when encrypted home directory selected

2015-12-08 Thread Piet Stevens
*** This bug is a duplicate of bug 1453738 ***
https://bugs.launchpad.net/bugs/1453738

Just did a clean install of 15.10 with encrypted /home and can confirm I
have the problem, too.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1449555

Title:
  password request for cryptswap1 during boot when encrypted home
  directory selected

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  On a system freshly installed (haven't tried the upgrade route) where
  the user selects to encrypt their home directory, they will get a
  password prompt during boot and at other times on the command-line
  requesting a password for cryptswap1.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: cryptsetup 2:1.6.1-1ubuntu7
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 28 09:02:12 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-28 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  crypttab: cryptswap1 UUID=c9d10691-df3f-49ae-a734-cdf2cbbaee8e /dev/urandom 
swap,offset=1024,cipher=aes-xts-plain64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449555/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523985] Re: evolution-source-registery needs a restart to pick newly activated uoa accounts

2015-12-08 Thread Bug Watch Updater
** Changed in: evolution-data-server
   Status: Unknown => Confirmed

** Changed in: evolution-data-server
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1523985

Title:
  evolution-source-registery needs a restart to pick newly activated uoa
  accounts

Status in evolution-data-server:
  Confirmed
Status in evolution-data-server package in Ubuntu:
  Triaged

Bug description:
  Using current xenial version
  - go to the uoa settings
  - add a google account

  - > you get a notification that there is an auth issue (that's a weird
  workflow but needed because the application needs to auth but e-d-s
  can't do UI prompting)

  - auth e-d-s in the settings

  -> the new account should be active/listed in the indicator or gnome-
  calendar but is not

  
  The issue is probably that e-d-s connect to the "account-created" signal on a 
AgManager object and adds the account correctly, but at this point the 
authentification/confirmation is not done yet so the account fails to active, 
and there is no following callback after the authentification is done. 

  It seems that AgManager doesn't provide an appropriate signal that can
  be used there so some work might be needed on the signon side

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1523985/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

2015-12-08 Thread Richard Hansen
** Changed in: initramfs-tools
 Assignee: Joe (jrhodgeneo74) => (unassigned)

** No longer affects: initramfs-tools

** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

** Changed in: initramfs-tools
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/798414

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1521618] Re: wrong subnet in DHCP answer when multiple networks are present

2015-12-08 Thread Mike Pontillo
As an aside, Zoltan, I'm curious what symptoms you see due to this
issue. Since the gateway is off-link, it should not be reachable from
the provisioning network. What errors occur in your environment due to
this bug?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1521618

Title:
  wrong subnet in DHCP answer when multiple networks are present

Status in MAAS:
  Triaged
Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  So I have 3 interfaces with 3, non-overlapping subnets defined in my
  maas cluster controller.

  The idea would be that there is a provisioning network (10.6.0.0/16)
  to do the actual provisioning and once the node gets deployed it is
  using a different network (because the provisioning network is only
  1x1Gbit while the production network is bonded (LACP) 10Gbit).

  However, when I boot up a fresh, new node to add to MAAS, it gets the
  following DHCP reply:

  ip=10.6.239.3:10.6.250.250:9.4.113.254:255.255.255.0

  So instead of picking up the /16 subnet correctly for the 10.6.239.3
  IP, it picks up the /24 from the network where it gets it's default
  gateway from.

  Is this a bug or my understanding of how MAAS should behave when there
  are multiple networks flawed?

  Here is my /var/lib/maas/dhcpd.conf:

  subnet 9.4.113.0 netmask 255.255.255.0 {
 if option arch = 00:0E {
filename "pxelinux.0";
option path-prefix "ppc64el/";
 } elsif option arch = 00:07 {
filename "bootx64.efi";
 } elsif option arch = 00:0B {
filename "grubaa64.efi";
 } elsif option arch = 00:0C {
filename "bootppc64.bin";
 } else {
filename "pxelinux.0";
 }
 interface "eth0";
 ignore-client-uids true;
 option subnet-mask 255.255.255.0;
 option broadcast-address 9.4.113.255;
 option domain-name-servers 9.4.113.251;
 option domain-name "i.zc2.ibm.com";
 option routers 9.4.113.254;
 option ntp-servers ntp.ubuntu.com;
 range dynamic-bootp 9.4.113.150 9.4.113.190;
 class "PXE" {
match if substring (option vendor-class-identifier, 0, 3) = "PXE";
default-lease-time 30;
max-lease-time 30;
 }
  }
  subnet 10.6.0.0 netmask 255.255.0.0 {
 if option arch = 00:0E {
filename "pxelinux.0";
option path-prefix "ppc64el/";
 } elsif option arch = 00:07 {
filename "bootx64.efi";
 } elsif option arch = 00:0B {
filename "grubaa64.efi";
 } elsif option arch = 00:0C {
filename "bootppc64.bin";
 } else {
filename "pxelinux.0";
 }
 interface "eth1";
 ignore-client-uids true;
 option subnet-mask 255.255.0.0;
 option broadcast-address 10.6.255.255;
 option domain-name-servers 9.4.113.251;
 option domain-name "i.zc2.ibm.com";
 option ntp-servers ntp.ubuntu.com;
 range dynamic-bootp 10.6.239.0 10.6.239.239;
 class "PXE" {
match if substring (option vendor-class-identifier, 0, 3) = "PXE";
default-lease-time 30;
max-lease-time 30;
 }
  }

  Here is "subnets read":

  [
  {
  "dns_servers": [],
  "name": "9.4.113.0/24",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/0/",
  "fabric": "fabric-0",
  "vid": 0,
  "id": 0
  },
  "gateway_ip": "9.4.113.254",
  "cidr": "9.4.113.0/24",
  "id": 1,
  "resource_uri": "/MAAS/api/1.0/subnets/1/"
  },
  {
  "dns_servers": [],
  "name": "10.7.0.0/16",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/5001/",
  "fabric": "fabric-1",
  "vid": 0,
  "id": 5001
  },
  "gateway_ip": null,
  "cidr": "10.7.0.0/16",
  "id": 2,
  "resource_uri": "/MAAS/api/1.0/subnets/2/"
  },
  {
  "dns_servers": [],
  "name": "10.6.0.0/16",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/5002/",
  "fabric": "fabric-2",
  "vid": 0,
  "id": 5002
  },
  "gateway_ip": null,
  "cidr": "10.6.0.0/16",
  "id": 3,
  "resource_uri": "/MAAS/api/1.0/subnets/3/"
  }
  ]

  Running 1.9.0~rc2+bzr4509-0ubuntu1~trusty1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1521618/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to   

[Touch-packages] [Bug 1523975] Re: [desktop] system-settings crashes on startup with 5.4.1+dfsg-2ubuntu11~vivid1

2015-12-08 Thread Tony Espy
As it's not clear from the description, reproducing this requires adding
the overlay PPA as a software source to a vivid desktop, then installing
ubuntu-system-settings, which in turn will pull in all the required Qt
bits.

Also, for reference see bug #1480877 for the gory details.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1523975

Title:
  [desktop] system-settings crashes on startup with 5.4.1+dfsg-
  2ubuntu11~vivid1

Status in Canonical System Image:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  The patch introduced in 5.4.1+dfsg-2ubuntu11~vivid1 causes system-
  settings to crash on startup for desktop users.  See stack trace at
  http://pastebin.ubuntu.com/13825552/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523975/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1495531] Re: Hide unused account plugins

2015-12-08 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Fix Released => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1495531

Title:
  Hide unused account plugins

Status in Canonical System Image:
  Fix Committed
Status in Online Accounts setup for Ubuntu Touch:
  Fix Released
Status in Ubuntu UX:
  Fix Released
Status in webapps-sprint:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  This is a proposal to hide unused account plugins, in particular
  default system account plugins, until an application is installed that
  can make use of them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495531/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523975] Re: [desktop] system-settings crashes on startup with 5.4.1+dfsg-2ubuntu11~vivid1

2015-12-08 Thread Lorn Potter
quick patch to fix this.

** Patch added: "nmbearer-system-settings-fix.diff"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1523975/+attachment/4531606/+files/nmbearer-system-settings-fix.diff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1523975

Title:
  [desktop] system-settings crashes on startup with 5.4.1+dfsg-
  2ubuntu11~vivid1

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  The patch introduced in 5.4.1+dfsg-2ubuntu11~vivid1 causes system-
  settings to crash on startup for desktop users.  See stack trace at
  http://pastebin.ubuntu.com/13825552/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1523975/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1301015] Re: Networking does not restart

2015-12-08 Thread Tim Carmean
This is affecting me as well. I don't care about the bug/feature
argument, but I know other folks are running into this in Puppet managed
environments. Has anyone come up with a graceful workaround for the
following:

class networking {

file { 'interfaces':
source => 'puppet:///modules/networking/interfaces',
path => '/etc/network/interfaces',
notify => Service['networking'],
}

service { 'networking':
ensure => 'running',
enable => 'true',
}

}

Off the top of my head a solution that requires running ifdown followed
by ifup would require the use of 2 exec types in a specific order. I'm
far from a Puppet expert, but I know that this would be fairly complex
to code and quite error prone.

Any help would be appreciated. I know that many of you are volunteers
and I appreciate the time and effort you put into making Ubuntu a great
distribution.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1301015

Title:
  Networking does not restart

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu Server 14.04 it appears it is not possible to restart
  networking. This is fresh install from ISO.

  wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
  wirehive@ubuntu:~$ echo $?
  1
  wirehive@ubuntu:~$ sudo service networking restart
  stop: Job failed while stopping
  start: Job is already running: networking
  wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
  + PATH=/sbin:/bin
  + RUN_DIR=/run/network
  + IFSTATE=/run/network/ifstate
  + STATEDIR=/run/network/state
  + '[' -x /sbin/ifup ']'
  + '[' -x /sbin/ifdown ']'
  + . /lib/lsb/init-functions
  +++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
  ++ . /lib/lsb/init-functions.d/20-left-info-blocks
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
  ++ . /lib/lsb/init-functions.d/50-ubuntu-logging
  +++ LOG_DAEMON_MSG=
  ++ FANCYTTY=
  ++ '[' -e /etc/lsb-base-logging.sh ']'
  ++ true
  + CONFIGURE_INTERFACES=yes
  + EXCLUDE_INTERFACES=
  + VERBOSE=no
  + '[' -f /etc/default/networking ']'
  + verbose=
  + '[' no = yes ']'
  + case "$1" in
  + init_is_upstart
  + '[' -x /sbin/initctl ']'
  + /bin/grep -q upstart
  + /sbin/initctl version
  + return 0
  + exit 1
  wirehive@ubuntu:~$ sudo bash -x service networking restart
  ++ basename service
  + VERSION='service ver. 0.91-ubuntu1'
  ++ basename service
  + USAGE='Usage: service < option > | --status-all | [ service_name [ command 
| --full-restart ] ]'
  + SERVICE=
  + ACTION=
  + SERVICEDIR=/etc/init.d
  + OPTIONS=
  + '[' 2 -eq 0 ']'
  + cd /
  + '[' 2 -gt 0 ']'
  + case "${1}" in
  + '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
  + '[' 2 -eq 2 -a restart = --full-restart ']'
  + '[' -z '' ']'
  + SERVICE=networking
  + shift
  + '[' 1 -gt 0 ']'
  + case "${1}" in
  + '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
  + '[' 1 -eq 2 -a '' = --full-restart ']'
  + '[' -z networking ']'
  + '[' -z '' ']'
  + ACTION=restart
  + shift
  + '[' 0 -gt 0 ']'
  + '[' -r /etc/init/networking.conf ']'
  + which initctl
  + grep -q upstart
  + initctl version
  + case "${ACTION}" in
  + stop networking
  stop: Job failed while stopping
  + :
  + exec start networking
  start: Job is already running: networking
  wirehive@ubuntu:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523975] Re: [desktop] system-settings crashes on startup with 5.4.1+dfsg-2ubuntu11~vivid1

2015-12-08 Thread Pat McGowan
Removing the c-d-s-i task as its not really an issue for that

** No longer affects: canonical-devices-system-image

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1523975

Title:
  [desktop] system-settings crashes on startup with 5.4.1+dfsg-
  2ubuntu11~vivid1

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  The patch introduced in 5.4.1+dfsg-2ubuntu11~vivid1 causes system-
  settings to crash on startup for desktop users.  See stack trace at
  http://pastebin.ubuntu.com/13825552/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1523975/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523722] Re: /usr/bin/telephony-service-approver:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_wit

2015-12-08 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1523722

Title:
  /usr/bin/telephony-service-
  
approver:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_block_for_at_most

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding telephony-service.  This problem was most recently seen with
  version 0.1+16.04.20151119-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/8f663af0b140859566ab5cf21a4ad6e5eb7b6fc0
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523722/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1522150] Re: Cut off messages

2015-12-08 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1522150

Title:
  Cut off messages

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  New

Bug description:
  Hello,

  My girlfriend send me some SMS with text: 'Umiem. Skoro się pytam to chcę 
(emoticon) bo miałeś wczoraj rację, że dawno nie wychodziliśmy', but I've 
received 'nie wychodzilismy'.
  We tested that exact text few times - all the time I'm receiving 'nie 
wychodzilismy'. Could anyone test that text? Please look at 'ś' that 
disappeared in my phone.
  We test that without emoticon and - magic, I've received all text, but 
without polish special signs (like ł ś ę, etc.). Inserted other emoticon - 
received 'ie wychodzilismy'.
  I must also admin that I'm getting 's', 'e', etc. instead of 'ś', 'ę', etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1522150/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1524000] Re: PyGIWarning: UbuntuAppLaunch was imported without specifying a version first

2015-12-08 Thread Christopher Lee
** Changed in: autopilot
 Assignee: (unassigned) => Christopher Lee (veebers)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1524000

Title:
  PyGIWarning: UbuntuAppLaunch was imported without specifying a version
  first

Status in Autopilot:
  In Progress
Status in Ubuntu Music App:
  Invalid
Status in pygobject package in Ubuntu:
  New

Bug description:
  When launching Autopilot tests for Music App you get an error indicating that 
UbuntuAppLaunch was imported without specifying a version first.
  This is the error:

  autopilot run music_app
  /usr/lib/python2.7/dist-packages/autopilot/application/_launcher.py:23: 
PyGIWarning: UbuntuAppLaunch was imported without specifying a version first. 
Use gi.require_version('UbuntuAppLaunch', '2') before import to ensure that the 
right version gets loaded.
from gi.repository import GLib, UbuntuAppLaunch
  Loading tests from: /home/victor/Development/music-app/tests/autopilot

  Failed to import test module: music_app.tests.test_music
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
  __import__(name)
File 
"/home/victor/Development/music-app/tests/autopilot/music_app/__init__.py", 
line 9, in 
  from ubuntuuitoolkit import (
  ImportError: No module named ubuntuuitoolkit

  Tests running...
  ==
  ERROR: unittest.loader.ModuleImportFailure.music_app.tests.test_music
  --
  Traceback (most recent call last):
  ImportError: Failed to import test module: music_app.tests.test_music
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
  __import__(name)
File 
"/home/victor/Development/music-app/tests/autopilot/music_app/__init__.py", 
line 9, in 
  from ubuntuuitoolkit import (
  ImportError: No module named ubuntuuitoolkit

To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1524000/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1518925] Re: Buttons disappear in camera after taking a picture

2015-12-08 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: ww02-2016 => backlog

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1518925

Title:
  Buttons disappear in camera after taking a picture

Status in Canonical System Image:
  Incomplete
Status in camera-app package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when I'm trying to take a picture, after I click the shutter
  the first time, every button in the screen disappears, rendering the
  camera unusable. Then I need to reboot the phone to get the camera to
  a working state again.

  My phone is a BQ Aquaris E4.5 with Ubuntu 15.04 (OTA-8)

  Camera version 3.0.0.595

  What you expected to happen: I expect to take pictures with the
  camera.

  What happened instead: I can't take pictures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518925/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

2015-12-08 Thread Uranicus
Knowing that this bug is in progress, I want to share an interesting
finding (at least for me).

I am on rc-proposed (with bluez5, see details below). When SIM 1 is
(randomly picked) used, the battery status is shown in the car display.
When SIM 2 is used, the battery status shows 100% loading.

system-image-cli -i:

current build number: 196
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-12-05 18:28:01
version version: 196
version ubuntu: 20151204.1
version device: 20151028-869191d
version custom: 2015–36-46-vivid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1418040

Title:
  Calling from car using bluetooth, call is placed on ril_0, even though
  ril_1 is default

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Triaged
Status in telephony-service package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu RTM:
  Triaged

Bug description:
  What happened
  Placed call from car over bluetooth
  Call was placed on my first SIM card, even though I selected my second SIM as 
default for calls

  What should have happened
  The call should have been placed on my second SIM

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: telephony-service 0.1+15.04.20150124-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: armhf
  Date: Wed Feb  4 14:25:44 2015
  InstallationDate: Installed on 2015-02-02 (2 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150202-020204)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Touch-packages] [Bug 1523223] Re: error in man page

2015-12-08 Thread rm damerell
Thank you for your reply. I am happy for the bug to
be marked as fixed. I could not find any earlier report.
Please is there any way to discover whether the rule
files in/lib/udev/rules.dare being read? Thank you.



On Mon, Dec 7, 2015 at 3:59 PM, Martin Pitt  wrote:

> This was fixed in Ubuntu 15.10 at least, and is not a severe error, so
> I'm closing this now. Thanks for your report!
>
> ** Changed in: systemd (Ubuntu)
>Status: New => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1523223
>
> Title:
>   error in man page
>
> Status in systemd package in Ubuntu:
>   Fix Released
>
> Bug description:
>
>   L-Ubuntu 14.04,  udev  204-5ubuntu20.15 (latest).   man udev  says that
>   udev reads rules from
>
>   /usr/lib/udev/rules.d
>   /run/udev/rules.d
>
>   and
>
>   /etc/udev/rules.d
>
>   The first 2 do not exist. There are rule files in
>
>   /lib/udev/rules.d
>
>   but I do not know any way to find out whether or not these are being
> read.
>   (if any human reads this, I would be grateful if you could tell me).
>   I was advised to file a bug report.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: udev 204-5ubuntu20.15
>   ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
>   Uname: Linux 3.13.0-66-generic i686
>   NonfreeKernelModules: wl
>   ApportVersion: 2.14.1-0ubuntu3.16
>   Architecture: i386
>   CurrentDesktop: LXDE
>   Date: Sun Dec  6 11:50:36 2015
>   InstallationDate: Installed on 2015-07-19 (140 days ago)
>   InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386
> (20140722.2)
>   MachineType: Dell Inc. Inspiron 1525
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic
> root=UUID=30c969c8-8299-4020-8ecc-bc228a671810 ro quiet splash vt.handoff=7
>   SourcePackage: systemd
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/27/2009
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A17
>   dmi.board.vendor: Dell Inc.
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
>   dmi.product.name: Inspiron 1525
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1523223/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1523223

Title:
  error in man page

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  
  L-Ubuntu 14.04,  udev  204-5ubuntu20.15 (latest).   man udev  says that 
  udev reads rules from 

  /usr/lib/udev/rules.d
  /run/udev/rules.d 

  and

  /etc/udev/rules.d

  The first 2 do not exist. There are rule files in

  /lib/udev/rules.d

  but I do not know any way to find out whether or not these are being read.
  (if any human reads this, I would be grateful if you could tell me).
  I was advised to file a bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu20.15
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Dec  6 11:50:36 2015
  InstallationDate: Installed on 2015-07-19 (140 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: Dell Inc. Inspiron 1525
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=30c969c8-8299-4020-8ecc-bc228a671810 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1523223/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1524000] Re: PyGIWarning: UbuntuAppLaunch was imported without specifying a version first

2015-12-08 Thread Nicholas Skaggs
** Branch linked: lp:~canonical-platform-
qa/autopilot/fix_vuild_for_x_incl_datetime

** Also affects: autopilot
   Importance: Undecided
   Status: New

** Changed in: autopilot
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1524000

Title:
  PyGIWarning: UbuntuAppLaunch was imported without specifying a version
  first

Status in Autopilot:
  In Progress
Status in Ubuntu Music App:
  Invalid
Status in pygobject package in Ubuntu:
  New

Bug description:
  When launching Autopilot tests for Music App you get an error indicating that 
UbuntuAppLaunch was imported without specifying a version first.
  This is the error:

  autopilot run music_app
  /usr/lib/python2.7/dist-packages/autopilot/application/_launcher.py:23: 
PyGIWarning: UbuntuAppLaunch was imported without specifying a version first. 
Use gi.require_version('UbuntuAppLaunch', '2') before import to ensure that the 
right version gets loaded.
from gi.repository import GLib, UbuntuAppLaunch
  Loading tests from: /home/victor/Development/music-app/tests/autopilot

  Failed to import test module: music_app.tests.test_music
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
  __import__(name)
File 
"/home/victor/Development/music-app/tests/autopilot/music_app/__init__.py", 
line 9, in 
  from ubuntuuitoolkit import (
  ImportError: No module named ubuntuuitoolkit

  Tests running...
  ==
  ERROR: unittest.loader.ModuleImportFailure.music_app.tests.test_music
  --
  Traceback (most recent call last):
  ImportError: Failed to import test module: music_app.tests.test_music
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
  __import__(name)
File 
"/home/victor/Development/music-app/tests/autopilot/music_app/__init__.py", 
line 9, in 
  from ubuntuuitoolkit import (
  ImportError: No module named ubuntuuitoolkit

To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1524000/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)

2015-12-08 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: ww02-2016 => backlog

-- 
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/1493574

Title:
  [vegeta] Phone app makes screen stay black during call (so you can't
  hang up)

Status in Canonical System Image:
  Incomplete
Status in powerd package in Ubuntu:
  Confirmed

Bug description:
  A similar, if not the same bug, has been reported to be fixed for
  OTA6. This bug report explains that it's no necessary to wait for a
  minute or so on the phone call, but the screen turns black
  immediately, and doesn't turn back on again to allow hanging up via a
  screen control.

  Potential duplicate: https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1483127

  Device: Aquaris E5 HD Ubuntu Edition
  OS version: 15.04 (r5)

  A) Incoming phone call:
     - Accept the incoming call by sliding the grey middle button to the 
green button
     - Watch the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (continued from above, screen stays black after taking it away from 
your ear)
     - Press the screen lock/unlock button (= button above volume control)
     - Screen with phone app shows for about half a second, then turns 
black again
     - Press the screen lock/unlock button again, and try to press the red 
hangup button quickly
     - Repeat the previous step until hanging up succeeds

  B) Outbound phone call:
     - Open the phone app
     - Slide up Recent calls list from bottom edge, select a phone number
     - Press green dial button to initiate the call
     - Watch the phone dialling and the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (same procedure as in A. above)
     - Difference in behavior:
   * In some calls after pressing the lock/unlock button for the first 
time the screen stays alight (doesn't turn black again after half a second).

  
  Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list:
  In both cases, covering/uncovering the proximity sensor should turn the 
screen on, if the screen has not been turned off with the power button. (This 
is not happening.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493574/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1521618] Re: wrong subnet in DHCP answer when multiple networks are present

2015-12-08 Thread Mike Pontillo
Ah, disregard my previous question. When I re-read this bug I missed the
part where you said "So instead of picking up the /16 subnet correctly
for the 10.6.239.3 IP, it picks up the /24 from the network where it
gets it's default gateway from."

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1521618

Title:
  wrong subnet in DHCP answer when multiple networks are present

Status in MAAS:
  Triaged
Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  So I have 3 interfaces with 3, non-overlapping subnets defined in my
  maas cluster controller.

  The idea would be that there is a provisioning network (10.6.0.0/16)
  to do the actual provisioning and once the node gets deployed it is
  using a different network (because the provisioning network is only
  1x1Gbit while the production network is bonded (LACP) 10Gbit).

  However, when I boot up a fresh, new node to add to MAAS, it gets the
  following DHCP reply:

  ip=10.6.239.3:10.6.250.250:9.4.113.254:255.255.255.0

  So instead of picking up the /16 subnet correctly for the 10.6.239.3
  IP, it picks up the /24 from the network where it gets it's default
  gateway from.

  Is this a bug or my understanding of how MAAS should behave when there
  are multiple networks flawed?

  Here is my /var/lib/maas/dhcpd.conf:

  subnet 9.4.113.0 netmask 255.255.255.0 {
 if option arch = 00:0E {
filename "pxelinux.0";
option path-prefix "ppc64el/";
 } elsif option arch = 00:07 {
filename "bootx64.efi";
 } elsif option arch = 00:0B {
filename "grubaa64.efi";
 } elsif option arch = 00:0C {
filename "bootppc64.bin";
 } else {
filename "pxelinux.0";
 }
 interface "eth0";
 ignore-client-uids true;
 option subnet-mask 255.255.255.0;
 option broadcast-address 9.4.113.255;
 option domain-name-servers 9.4.113.251;
 option domain-name "i.zc2.ibm.com";
 option routers 9.4.113.254;
 option ntp-servers ntp.ubuntu.com;
 range dynamic-bootp 9.4.113.150 9.4.113.190;
 class "PXE" {
match if substring (option vendor-class-identifier, 0, 3) = "PXE";
default-lease-time 30;
max-lease-time 30;
 }
  }
  subnet 10.6.0.0 netmask 255.255.0.0 {
 if option arch = 00:0E {
filename "pxelinux.0";
option path-prefix "ppc64el/";
 } elsif option arch = 00:07 {
filename "bootx64.efi";
 } elsif option arch = 00:0B {
filename "grubaa64.efi";
 } elsif option arch = 00:0C {
filename "bootppc64.bin";
 } else {
filename "pxelinux.0";
 }
 interface "eth1";
 ignore-client-uids true;
 option subnet-mask 255.255.0.0;
 option broadcast-address 10.6.255.255;
 option domain-name-servers 9.4.113.251;
 option domain-name "i.zc2.ibm.com";
 option ntp-servers ntp.ubuntu.com;
 range dynamic-bootp 10.6.239.0 10.6.239.239;
 class "PXE" {
match if substring (option vendor-class-identifier, 0, 3) = "PXE";
default-lease-time 30;
max-lease-time 30;
 }
  }

  Here is "subnets read":

  [
  {
  "dns_servers": [],
  "name": "9.4.113.0/24",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/0/",
  "fabric": "fabric-0",
  "vid": 0,
  "id": 0
  },
  "gateway_ip": "9.4.113.254",
  "cidr": "9.4.113.0/24",
  "id": 1,
  "resource_uri": "/MAAS/api/1.0/subnets/1/"
  },
  {
  "dns_servers": [],
  "name": "10.7.0.0/16",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/5001/",
  "fabric": "fabric-1",
  "vid": 0,
  "id": 5001
  },
  "gateway_ip": null,
  "cidr": "10.7.0.0/16",
  "id": 2,
  "resource_uri": "/MAAS/api/1.0/subnets/2/"
  },
  {
  "dns_servers": [],
  "name": "10.6.0.0/16",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/5002/",
  "fabric": "fabric-2",
  "vid": 0,
  "id": 5002
  },
  "gateway_ip": null,
  "cidr": "10.6.0.0/16",
  "id": 3,
  "resource_uri": "/MAAS/api/1.0/subnets/3/"
  }
  ]

  Running 1.9.0~rc2+bzr4509-0ubuntu1~trusty1.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1437005] Re: Example sshd_config file has bad path to sftp-server. Should be /usr/lib/openssh/sftp-server, not /usr/libexec/openssh/sftp-server

2015-12-08 Thread Bug Watch Updater
** Changed in: openssh (Debian)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1437005

Title:
  Example sshd_config file has bad path to sftp-server. Should be
  /usr/lib/openssh/sftp-server, not /usr/libexec/openssh/sftp-server

Status in openssh package in Ubuntu:
  Fix Committed
Status in openssh package in Debian:
  Fix Committed

Bug description:
  Silly error, can't believe it wasn't found or reported earlier.

  SFTP wasn't working, auth.log showed "cannot stat /usr/libexec/openssh
  /sftp-server: No such file or directory"

  I checked /etc/ssh/sshd_config and /usr/share/doc/openssh-
  server/examples/sshd_config, which is apparently the source file. Both
  had the "libexec" path to the file.

  I ran "locate openssh/sftp-server" and got "/usr/lib/openssh/sftp-
  server"

  Corrected the path in the config file & all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-server 1:6.6p1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 26 11:40:13 2015
  InstallationDate: Installed on 2014-07-24 (244 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1437005/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1524093] [NEW] dhclient operates on incorrect interface

2015-12-08 Thread Tessa Lau
Public bug reported:

I have a system with two internet connections, both configured using
DHCP. They are specified in /etc/network/interfaces roughly as follows:

iface lte0 inet dhcp
iface wlan0 inet dhcp
wpa-ssid 
wpa-psk 

I also have defined custom options for each interface in the
/etc/dhcp/dhclient.conf file:

interface "lte0" {
  send host-name "hostA";
}
interface "wlan0" {
  send host-name "hostB";
}

When I do "ifup wlan0", the wrong interface is brought up:

Listening on LPF/lte0/94:b9:b4:18:e5:ce
Sending on   LPF/lte0/94:b9:b4:18:e5:ce
Listening on LPF/wlan0/00:26:b6:e1:7c:64
Sending on   LPF/wlan0/00:26:b6:e1:7c:64
Sending on   Socket/fallback
DHCPDISCOVER on lte0 to 255.255.255.255 port 67 interval 3 (xid=0xbb4b7c57)
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0xbf50be57)
DHCPREQUEST of 100.70.63.250 on lte0 to 255.255.255.255 port 67 (xid=0x577c4bbb)
DHCPOFFER of 100.70.63.250 from 100.70.63.1
DHCPACK of 100.70.63.250 from 100.70.63.1
bound to 100.70.63.250 -- renewal in 270090 seconds.

Similarly, if I do "ifdown wlan0", both interfaces are released:

Listening on LPF/lte0/94:b9:b4:18:e5:ce
Sending on   LPF/lte0/94:b9:b4:18:e5:ce
Listening on LPF/wlan0/00:26:b6:e1:7c:64
Sending on   LPF/wlan0/00:26:b6:e1:7c:64
Sending on   Socket/fallback
DHCPRELEASE on lte0 to 100.70.63.1 port 67 (xid=0x2f4f2125)
DHCPRELEASE on wlan0 to 10.78.56.254 port 67 (xid=0x15a5a)

I expect that ifup/ifdown only operates on the interface specified on
the command line. Instead they are operating on other interfaces that I
did not want them to touch.

I believe the problem is related to this statement in the dhclient man page:
   It is also possible to specify interfaces by name in the dhclient.conf 
file.   If interfaces are  specified  in  this  way,
   then  the client will only configure interfaces that are either 
specified in the configuration file or on the command line,
   and will ignore all other interfaces.

So it's reading all interfaces from the configuration file and adding
them to the command line interfaces, and operating on all such
interfaces. If I remove the interface stanzas from the
/etc/dhcp/dhclient.conf file, then everything works as expected.

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1524093

Title:
  dhclient operates on incorrect interface

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  I have a system with two internet connections, both configured using
  DHCP. They are specified in /etc/network/interfaces roughly as
  follows:

  iface lte0 inet dhcp
  iface wlan0 inet dhcp
  wpa-ssid 
  wpa-psk 

  I also have defined custom options for each interface in the
  /etc/dhcp/dhclient.conf file:

  interface "lte0" {
send host-name "hostA";
  }
  interface "wlan0" {
send host-name "hostB";
  }

  When I do "ifup wlan0", the wrong interface is brought up:

  Listening on LPF/lte0/94:b9:b4:18:e5:ce
  Sending on   LPF/lte0/94:b9:b4:18:e5:ce
  Listening on LPF/wlan0/00:26:b6:e1:7c:64
  Sending on   LPF/wlan0/00:26:b6:e1:7c:64
  Sending on   Socket/fallback
  DHCPDISCOVER on lte0 to 255.255.255.255 port 67 interval 3 (xid=0xbb4b7c57)
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0xbf50be57)
  DHCPREQUEST of 100.70.63.250 on lte0 to 255.255.255.255 port 67 
(xid=0x577c4bbb)
  DHCPOFFER of 100.70.63.250 from 100.70.63.1
  DHCPACK of 100.70.63.250 from 100.70.63.1
  bound to 100.70.63.250 -- renewal in 270090 seconds.

  Similarly, if I do "ifdown wlan0", both interfaces are released:

  Listening on LPF/lte0/94:b9:b4:18:e5:ce
  Sending on   LPF/lte0/94:b9:b4:18:e5:ce
  Listening on LPF/wlan0/00:26:b6:e1:7c:64
  Sending on   LPF/wlan0/00:26:b6:e1:7c:64
  Sending on   Socket/fallback
  DHCPRELEASE on lte0 to 100.70.63.1 port 67 (xid=0x2f4f2125)
  DHCPRELEASE on wlan0 to 10.78.56.254 port 67 (xid=0x15a5a)

  I expect that ifup/ifdown only operates on the interface specified on
  the command line. Instead they are operating on other interfaces that
  I did not want them to touch.

  I believe the problem is related to this statement in the dhclient man page:
 It is also possible to specify interfaces by name in the dhclient.conf 
file.   If interfaces are  specified  in  this  way,
 then  the client will only configure interfaces that are either 
specified in the configuration file or on the command line,
 and will ignore all other interfaces.

  So it's reading all interfaces from the configuration file and adding
  them to the command line interfaces, and operating on all such
  interfaces. If I remove the interface stanzas from the
  /etc/dhcp/dhclient.conf file, then everything works as expected.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1523900] Re: mirscreencast crashes, fails to take screenshot

2015-12-08 Thread Daniel van Vugt
** Tags added: screencast

** Also affects: mir
   Importance: Undecided
   Status: New

-- 
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/1523900

Title:
  mirscreencast crashes, fails to take screenshot

Status in Mir:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  Nexus 4 running latest stable image -

  current build number: 25
  device name: mako
  channel: ubuntu-touch/stable/ubuntu
  last update: 2015-12-08 11:53:16
  version version: 25
  version ubuntu: 20151118.2
  version tag: OTA-8
  version device: 20150911
  version custom: 20151118.2

  I'm running the following command to capture a screenshot of a running
  app, the unity shell, the splash screen when apps load etc.

adb shell mirscreencast -m /var/run/mir_socket  -n1

  I'm doing this in a script, across many hundreds of apps, so I'm doing
  it a lot. I'm seeing my script get wedged fairly often with errors
  such as this one:-

  [1449575031.562843]  MirConnectionAPI: Caught exception at client 
library boundary (in release): 
/build/mir-AHj2eT/mir-0.17.1+15.04.20151105.1/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorE
  std::exception::what: Failed to send message to server: Broken pipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1523900/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1521618] Re: wrong subnet in DHCP answer when multiple networks are present

2015-12-08 Thread Zoltan Arnold Nagy
In the meantime I had to change the environment to get on with the
project so I don't have this setup anymore, but I could try to reproduce
it on a VMware environment later this week if you guys couldn't.

This is on trusty running isc-dhcp-server 4.2.4-7ubuntu12.3, with maas-
dhcp 1.9.0~rc2+bzr4509-0ubuntu1~trusty1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1521618

Title:
  wrong subnet in DHCP answer when multiple networks are present

Status in MAAS:
  Triaged
Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  So I have 3 interfaces with 3, non-overlapping subnets defined in my
  maas cluster controller.

  The idea would be that there is a provisioning network (10.6.0.0/16)
  to do the actual provisioning and once the node gets deployed it is
  using a different network (because the provisioning network is only
  1x1Gbit while the production network is bonded (LACP) 10Gbit).

  However, when I boot up a fresh, new node to add to MAAS, it gets the
  following DHCP reply:

  ip=10.6.239.3:10.6.250.250:9.4.113.254:255.255.255.0

  So instead of picking up the /16 subnet correctly for the 10.6.239.3
  IP, it picks up the /24 from the network where it gets it's default
  gateway from.

  Is this a bug or my understanding of how MAAS should behave when there
  are multiple networks flawed?

  Here is my /var/lib/maas/dhcpd.conf:

  subnet 9.4.113.0 netmask 255.255.255.0 {
 if option arch = 00:0E {
filename "pxelinux.0";
option path-prefix "ppc64el/";
 } elsif option arch = 00:07 {
filename "bootx64.efi";
 } elsif option arch = 00:0B {
filename "grubaa64.efi";
 } elsif option arch = 00:0C {
filename "bootppc64.bin";
 } else {
filename "pxelinux.0";
 }
 interface "eth0";
 ignore-client-uids true;
 option subnet-mask 255.255.255.0;
 option broadcast-address 9.4.113.255;
 option domain-name-servers 9.4.113.251;
 option domain-name "i.zc2.ibm.com";
 option routers 9.4.113.254;
 option ntp-servers ntp.ubuntu.com;
 range dynamic-bootp 9.4.113.150 9.4.113.190;
 class "PXE" {
match if substring (option vendor-class-identifier, 0, 3) = "PXE";
default-lease-time 30;
max-lease-time 30;
 }
  }
  subnet 10.6.0.0 netmask 255.255.0.0 {
 if option arch = 00:0E {
filename "pxelinux.0";
option path-prefix "ppc64el/";
 } elsif option arch = 00:07 {
filename "bootx64.efi";
 } elsif option arch = 00:0B {
filename "grubaa64.efi";
 } elsif option arch = 00:0C {
filename "bootppc64.bin";
 } else {
filename "pxelinux.0";
 }
 interface "eth1";
 ignore-client-uids true;
 option subnet-mask 255.255.0.0;
 option broadcast-address 10.6.255.255;
 option domain-name-servers 9.4.113.251;
 option domain-name "i.zc2.ibm.com";
 option ntp-servers ntp.ubuntu.com;
 range dynamic-bootp 10.6.239.0 10.6.239.239;
 class "PXE" {
match if substring (option vendor-class-identifier, 0, 3) = "PXE";
default-lease-time 30;
max-lease-time 30;
 }
  }

  Here is "subnets read":

  [
  {
  "dns_servers": [],
  "name": "9.4.113.0/24",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/0/",
  "fabric": "fabric-0",
  "vid": 0,
  "id": 0
  },
  "gateway_ip": "9.4.113.254",
  "cidr": "9.4.113.0/24",
  "id": 1,
  "resource_uri": "/MAAS/api/1.0/subnets/1/"
  },
  {
  "dns_servers": [],
  "name": "10.7.0.0/16",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/5001/",
  "fabric": "fabric-1",
  "vid": 0,
  "id": 5001
  },
  "gateway_ip": null,
  "cidr": "10.7.0.0/16",
  "id": 2,
  "resource_uri": "/MAAS/api/1.0/subnets/2/"
  },
  {
  "dns_servers": [],
  "name": "10.6.0.0/16",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/5002/",
  "fabric": "fabric-2",
  "vid": 0,
  "id": 5002
  },
  "gateway_ip": null,
  "cidr": "10.6.0.0/16",
  "id": 3,
  "resource_uri": "/MAAS/api/1.0/subnets/3/"
  }
  ]

  Running 1.9.0~rc2+bzr4509-0ubuntu1~trusty1.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1524099] [NEW] Problems with graphics video streaming

2015-12-08 Thread John Neufeld
Public bug reported:

as above

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Dec  8 15:06:11 2015
DistUpgraded: 2015-11-02 17:48:39,231 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 05) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:2b29]
InstallationDate: Installed on 2015-04-18 (234 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Hewlett-Packard 110-529
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=75bac6d1-3480-43df-a8ee-4f18d632225b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to wily on 2015-11-03 (35 days ago)
dmi.bios.date: 09/26/2014
dmi.bios.vendor: AMI
dmi.bios.version: 80.04
dmi.board.name: 2B29
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 1.00
dmi.chassis.asset.tag: 4CI5050N7P
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr80.04:bd09/26/2014:svnHewlett-Packard:pn110-529:pvr:rvnHewlett-Packard:rn2B29:rvr1.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: 110-529
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Tue Dec  8 16:03:05 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9.1
xserver.video_driver: radeon

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu wily

-- 
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/1524099

Title:
  Problems with graphics video streaming

Status in xorg package in Ubuntu:
  New

Bug description:
  as above

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Dec  8 15:06:11 2015
  DistUpgraded: 2015-11-02 17:48:39,231 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:2b29]
  InstallationDate: Installed on 2015-04-18 (234 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard 110-529
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=75bac6d1-3480-43df-a8ee-4f18d632225b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-11-03 (35 days ago)
  dmi.bios.date: 09/26/2014
  dmi.bios.vendor: AMI
  dmi.bios.version: 80.04
  dmi.board.name: 2B29
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: 4CI5050N7P
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr80.04:bd09/26/2014:svnHewlett-Packard:pn110-529:pvr:rvnHewlett-Packard:rn2B29:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: 110-529
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  

[Touch-packages] [Bug 1524098] [NEW] Problems with graphics video streaming

2015-12-08 Thread John Neufeld
Public bug reported:

as above

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Dec  8 15:06:11 2015
DistUpgraded: 2015-11-02 17:48:39,231 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 05) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:2b29]
InstallationDate: Installed on 2015-04-18 (234 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Hewlett-Packard 110-529
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=75bac6d1-3480-43df-a8ee-4f18d632225b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to wily on 2015-11-03 (35 days ago)
dmi.bios.date: 09/26/2014
dmi.bios.vendor: AMI
dmi.bios.version: 80.04
dmi.board.name: 2B29
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 1.00
dmi.chassis.asset.tag: 4CI5050N7P
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr80.04:bd09/26/2014:svnHewlett-Packard:pn110-529:pvr:rvnHewlett-Packard:rn2B29:rvr1.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: 110-529
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Tue Dec  8 16:03:05 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9.1
xserver.video_driver: radeon

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu wily

-- 
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/1524098

Title:
  Problems with graphics video streaming

Status in xorg package in Ubuntu:
  New

Bug description:
  as above

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Dec  8 15:06:11 2015
  DistUpgraded: 2015-11-02 17:48:39,231 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:2b29]
  InstallationDate: Installed on 2015-04-18 (234 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard 110-529
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=75bac6d1-3480-43df-a8ee-4f18d632225b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-11-03 (35 days ago)
  dmi.bios.date: 09/26/2014
  dmi.bios.vendor: AMI
  dmi.bios.version: 80.04
  dmi.board.name: 2B29
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: 4CI5050N7P
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr80.04:bd09/26/2014:svnHewlett-Packard:pn110-529:pvr:rvnHewlett-Packard:rn2B29:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: 110-529
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

2015-12-08 Thread Selene Scriven
Is it possible that this fix might cause a phone to wake up more often,
or to stay awake longer?  I'm seeing weird idle power behavior ever
since this fix landed in krillin rc-proposed 196.

Before: ~9 mA
http://people.canonical.com/~platform-qa/power-results/2015-12-08_03:19:30-krillin-195-power_usage_idle/graph.png

After: ~35 mA
http://people.canonical.com/~platform-qa/power-results/2015-12-08_07:36:16-krillin-196-power_usage_idle/graph.png

Here's the commit log for 196:

http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-
proposed/196.commitlog

Arale results look fine.  I don't know why krillin is different, but I'm
only seeing this behavior on krillin when wifi is connected...  and this
bug fix is a likely suspect.  I don't see additional forks or crashes in
the test logs, which suggests the issue is probably caused by a long-
running process.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Fix Committed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1524130] [NEW] /usr/bin/unity8:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write

2015-12-08 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity8.  This problem was most recently seen with version
8.11+15.04.20151208-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/2ab45fb8f212225ec5c93d8fe917c1c82cda2839
contains more details.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid

-- 
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/1524130

Title:
  
/usr/bin/unity8:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write

Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+15.04.20151208-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/2ab45fb8f212225ec5c93d8fe917c1c82cda2839
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1524130/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1524131] [NEW] /usr/bin/mediaplayer-app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write

2015-12-08 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding mediaplayer-app.  This problem was most recently seen with
version 0.20.5+15.04.20150701-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/a649a8d64746c3cce478208950c51611a06323cb
contains more details.

** Affects: mediaplayer-app (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1524131

Title:
  /usr/bin/mediaplayer-
  
app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mediaplayer-app.  This problem was most recently seen with
  version 0.20.5+15.04.20150701-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/a649a8d64746c3cce478208950c51611a06323cb
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1524131/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

2015-12-08 Thread Selene Scriven
I created bug 1524133 to track the issues I'm seeing.  I don't know if
it's related to this bug, but so far it looks probable.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Fix Committed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1516133] Re: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1

2015-12-08 Thread manukleart
i can run well with ubuntu 14.04.3 LTS in my laptop yett, i am
desperatted. Any idea??

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1516133

Title:
  package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el
  subproceso script pre-removal nuevo devolvió el código de salida de
  error 1

Status in apport package in Ubuntu:
  New

Bug description:
  I have a lot of problems in my laptop with ubuntu 14.04.3 LTS and 15.10 too.
  Actually Libre Office Writter doesn't work.

  Sometimes it depends when i put in on my laptop appairs ACPI PCC Probe failed
  and sometimes say don't find hard disk
   sometimes thunderbird fails
  ubuntu software center doesn't work
  and sometimes i can't write any file.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.18
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic i686
  ApportLog:

  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: i386
  Date: Fri Nov 13 20:38:45 2015
  DuplicateSignature: package:apport:2.14.1-0ubuntu3.18:el subproceso script 
pre-removal nuevo devolvió el código de salida de error 1
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2015-11-01 (12 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: apport
  Title: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1516133/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1509769] Re: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-12-08 Thread Joao
Same happened to me.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1509769

Title:
  package initramfs-tools 0.120ubuntu6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Error occured during UBUNTU Mate upgrade to 15.10 on Raspberry PI2 and
  once trying perform manual update getting:

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up initramfs-tools (0.120ubuntu6) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.120ubuntu6) ...
  update-initramfs: Generating /boot/initrd.img-3.18.0-25-rpi2
  Unsupported platform.
  run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 
1
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: initramfs-tools 0.120ubuntu6
  ProcVersionSignature: Ubuntu 3.18.0-25.26-rpi2 3.18.17
  Uname: Linux 3.18.0-25-rpi2 armv7l
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: armhf
  Date: Sun Oct 25 08:19:08 2015
  DuplicateSignature: package:initramfs-tools:0.120ubuntu6:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to wily on 2015-10-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1509769/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523823] Re: Dash touch scrolling is slower than web browser touch scrolling

2015-12-08 Thread Daniel van Vugt
Although I'm surprised you would use either the pixel density or grid
unit calculations. Accurate scrolling is all about exact pixels.

-- 
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/1523823

Title:
  Dash touch scrolling is slower than web browser touch scrolling

Status in unity8 package in Ubuntu:
  New

Bug description:
  Dash touch scrolling is slower than web browser touch scrolling. But
  obviously it should not be.

  This has been an issue for as long as I remember. Just upgraded mako
  to xenial and it's still there.

  Am I imagining things? Is this simply explained by the web browser
  using a different toolkit? Could it just be a side-effect of bug
  1494795?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1523823/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1521618] Re: wrong subnet in DHCP answer when multiple networks are present

2015-12-08 Thread Zoltan Arnold Nagy
Mike, the symptom was that the PXE boot just hang as can bee seen from
the packet capture. No idea why actually, but the first thing fishy was
the wrong DHCP reply :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1521618

Title:
  wrong subnet in DHCP answer when multiple networks are present

Status in MAAS:
  Triaged
Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  So I have 3 interfaces with 3, non-overlapping subnets defined in my
  maas cluster controller.

  The idea would be that there is a provisioning network (10.6.0.0/16)
  to do the actual provisioning and once the node gets deployed it is
  using a different network (because the provisioning network is only
  1x1Gbit while the production network is bonded (LACP) 10Gbit).

  However, when I boot up a fresh, new node to add to MAAS, it gets the
  following DHCP reply:

  ip=10.6.239.3:10.6.250.250:9.4.113.254:255.255.255.0

  So instead of picking up the /16 subnet correctly for the 10.6.239.3
  IP, it picks up the /24 from the network where it gets it's default
  gateway from.

  Is this a bug or my understanding of how MAAS should behave when there
  are multiple networks flawed?

  Here is my /var/lib/maas/dhcpd.conf:

  subnet 9.4.113.0 netmask 255.255.255.0 {
 if option arch = 00:0E {
filename "pxelinux.0";
option path-prefix "ppc64el/";
 } elsif option arch = 00:07 {
filename "bootx64.efi";
 } elsif option arch = 00:0B {
filename "grubaa64.efi";
 } elsif option arch = 00:0C {
filename "bootppc64.bin";
 } else {
filename "pxelinux.0";
 }
 interface "eth0";
 ignore-client-uids true;
 option subnet-mask 255.255.255.0;
 option broadcast-address 9.4.113.255;
 option domain-name-servers 9.4.113.251;
 option domain-name "i.zc2.ibm.com";
 option routers 9.4.113.254;
 option ntp-servers ntp.ubuntu.com;
 range dynamic-bootp 9.4.113.150 9.4.113.190;
 class "PXE" {
match if substring (option vendor-class-identifier, 0, 3) = "PXE";
default-lease-time 30;
max-lease-time 30;
 }
  }
  subnet 10.6.0.0 netmask 255.255.0.0 {
 if option arch = 00:0E {
filename "pxelinux.0";
option path-prefix "ppc64el/";
 } elsif option arch = 00:07 {
filename "bootx64.efi";
 } elsif option arch = 00:0B {
filename "grubaa64.efi";
 } elsif option arch = 00:0C {
filename "bootppc64.bin";
 } else {
filename "pxelinux.0";
 }
 interface "eth1";
 ignore-client-uids true;
 option subnet-mask 255.255.0.0;
 option broadcast-address 10.6.255.255;
 option domain-name-servers 9.4.113.251;
 option domain-name "i.zc2.ibm.com";
 option ntp-servers ntp.ubuntu.com;
 range dynamic-bootp 10.6.239.0 10.6.239.239;
 class "PXE" {
match if substring (option vendor-class-identifier, 0, 3) = "PXE";
default-lease-time 30;
max-lease-time 30;
 }
  }

  Here is "subnets read":

  [
  {
  "dns_servers": [],
  "name": "9.4.113.0/24",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/0/",
  "fabric": "fabric-0",
  "vid": 0,
  "id": 0
  },
  "gateway_ip": "9.4.113.254",
  "cidr": "9.4.113.0/24",
  "id": 1,
  "resource_uri": "/MAAS/api/1.0/subnets/1/"
  },
  {
  "dns_servers": [],
  "name": "10.7.0.0/16",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/5001/",
  "fabric": "fabric-1",
  "vid": 0,
  "id": 5001
  },
  "gateway_ip": null,
  "cidr": "10.7.0.0/16",
  "id": 2,
  "resource_uri": "/MAAS/api/1.0/subnets/2/"
  },
  {
  "dns_servers": [],
  "name": "10.6.0.0/16",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/5002/",
  "fabric": "fabric-2",
  "vid": 0,
  "id": 5002
  },
  "gateway_ip": null,
  "cidr": "10.6.0.0/16",
  "id": 3,
  "resource_uri": "/MAAS/api/1.0/subnets/3/"
  }
  ]

  Running 1.9.0~rc2+bzr4509-0ubuntu1~trusty1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1521618/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net

[Touch-packages] [Bug 1516133] Re: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1

2015-12-08 Thread manukleart
i cant open archives file and i can't install landscape and nothing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1516133

Title:
  package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el
  subproceso script pre-removal nuevo devolvió el código de salida de
  error 1

Status in apport package in Ubuntu:
  New

Bug description:
  I have a lot of problems in my laptop with ubuntu 14.04.3 LTS and 15.10 too.
  Actually Libre Office Writter doesn't work.

  Sometimes it depends when i put in on my laptop appairs ACPI PCC Probe failed
  and sometimes say don't find hard disk
   sometimes thunderbird fails
  ubuntu software center doesn't work
  and sometimes i can't write any file.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.18
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic i686
  ApportLog:

  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: i386
  Date: Fri Nov 13 20:38:45 2015
  DuplicateSignature: package:apport:2.14.1-0ubuntu3.18:el subproceso script 
pre-removal nuevo devolvió el código de salida de error 1
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2015-11-01 (12 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: apport
  Title: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1516133/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1516133] Re: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1

2015-12-08 Thread manukleart
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/aptdaemon/worker.py", line 325, in 
_process_transaction
self._apply_changes(trans)
  File "/usr/lib/python3/dist-packages/aptdaemon/pkcompat.py", line 3157, in 
_apply_changes
install_range)
  File "/usr/lib/python3/dist-packages/aptdaemon/worker.py", line 1151, in 
_apply_changes
with self._frozen_status():
  File "/usr/lib/python3.4/contextlib.py", line 59, in __enter__
return next(self.gen)
  File "/usr/lib/python3/dist-packages/aptdaemon/worker.py", line 1175, in 
_frozen_status
frozen_dir = tempfile.mkdtemp(prefix="aptdaemon-frozen-status")
  File "/usr/lib/python3.4/tempfile.py", line 426, in mkdtemp
dir = gettempdir()
  File "/usr/lib/python3.4/tempfile.py", line 370, in gettempdir
tempdir = _get_default_tempdir()
  File "/usr/lib/python3.4/tempfile.py", line 312, in _get_default_tempdir
dirlist)
FileNotFoundError: [Errno 2] No usable temporary directory found in ['/tmp', 
'/var/tmp', '/usr/tmp', '/']

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1516133

Title:
  package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el
  subproceso script pre-removal nuevo devolvió el código de salida de
  error 1

Status in apport package in Ubuntu:
  New

Bug description:
  I have a lot of problems in my laptop with ubuntu 14.04.3 LTS and 15.10 too.
  Actually Libre Office Writter doesn't work.

  Sometimes it depends when i put in on my laptop appairs ACPI PCC Probe failed
  and sometimes say don't find hard disk
   sometimes thunderbird fails
  ubuntu software center doesn't work
  and sometimes i can't write any file.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.18
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic i686
  ApportLog:

  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: i386
  Date: Fri Nov 13 20:38:45 2015
  DuplicateSignature: package:apport:2.14.1-0ubuntu3.18:el subproceso script 
pre-removal nuevo devolvió el código de salida de error 1
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2015-11-01 (12 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: apport
  Title: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1516133/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523975] Re: [desktop] system-settings crashes on startup with 5.4.1+dfsg-2ubuntu11~vivid1

2015-12-08 Thread Ubuntu Foundations Team Bug Bot
The attachment "nmbearer-system-settings-fix.diff" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1523975

Title:
  [desktop] system-settings crashes on startup with 5.4.1+dfsg-
  2ubuntu11~vivid1

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  The patch introduced in 5.4.1+dfsg-2ubuntu11~vivid1 causes system-
  settings to crash on startup for desktop users.  See stack trace at
  http://pastebin.ubuntu.com/13825552/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1523975/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1498129] Re: Asus Xonar U7 S/PDIF output not recognized by pulseaudio

2015-12-08 Thread Raymond
you have to find out name is U7 or Xonar U7

!!---Mixer controls for card 1 [U7]

-- 
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/1498129

Title:
  Asus Xonar U7 S/PDIF output not recognized by pulseaudio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The external USB audio card Asus Xonar U7 is capable of both analog and 
digital output.
  ALSA name for the digital (S/PDIF) output is hw:1,1, and it is listed in 
aplay -l output, and aplay can output to it:
  aplay -D plughw:1,1 sample.wav. So, direct alsa sound works fine.

  However, pulseadio does not recognize the digital output of Xonar U7,
  it offers only analog output.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25
  Uname: Linux 3.13.0-63-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aoand  3756 F pulseaudio
   /dev/snd/controlC0:  aoand  3756 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 21 21:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-02-20 (1674 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-05-19 (490 days ago)
  dmi.bios.date: 11/29/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET71WW (3.21 )
  dmi.board.name: 7448CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7448CTO
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1342208] Re: Scroll wheel uses inverted logic to switch between applications/windows in the switcher

2015-12-08 Thread Mathew Hodson
It seems wrong to me, because when you scroll down over the sound
indicator, which was also got an update at the same time in bug
#1342731, the cursor moves left. So it should move left when scrolling
down over the switcher.

Also there's a chance that this behaviour change was a mistake, since it
was back-ported in an SRU, and the Regression Potential explicitly said,
"Vertical scrolling code has not been touched by the change, so there's
no possibility to regress in this sense."

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nux in Ubuntu.
https://bugs.launchpad.net/bugs/1342208

Title:
  Scroll wheel uses inverted logic to switch between
  applications/windows in the switcher

Status in Nux:
  Fix Released
Status in Nux trusty series:
  Fix Committed
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in nux source package in Trusty:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  Scrolling on the Alt+Tab has invalid behavior:
  - Scrolling down, moves to the previous icon/window
  - Scrolling up, moves to the next icon/window
  - Scrolling left, moves to the next icon/window
  - Scrolling right, moves to the previous icon/window

  [Test case]
  1. Press Alt+Tab
  2. While pressing the keys, use mouse scroll wheel to scroll vertically (and, 
if possible, horizontally)

  Expected behavior:
  - Scrolling down, moves to the next icon/window
  - Scrolling up, moves to the previous icon/window
  - Scrolling left, moves to the previous icon/window
  - Scrolling right, moves to the next icon/window

  [Regression potential]
  Vertical scrolling code has not been touched by the change, so there's no 
possibility to regress in this sense.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/1342208/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1524182] [NEW] package rsyslog-mysql 5.8.6-1ubuntu8.9 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2015-12-08 Thread Dr. James F Schmidt
Public bug reported:

When I installed MySQL I use ')' in the password. The symbol does on work when 
the password is on the command line to start MySQL(I do this since I am the 
only one who uses this computer).
I forgot that I did not need to put the password on a command line ans started 
to uninstall MySQL. That is when I got this message.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: rsyslog-mysql 5.8.6-1ubuntu8.9
ProcVersionSignature: Ubuntu 3.13.0-71.114~precise1-generic 3.13.11-ckt29
Uname: Linux 3.13.0-71-generic i686
ApportVersion: 2.0.1-0ubuntu17.13
Architecture: i386
Date: Tue Dec  8 23:00:05 2015
DuplicateSignature: package:rsyslog-mysql:5.8.6-1ubuntu8.9:subprocess installed 
pre-removal script returned error exit status 1
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
MarkForUpload: True
SourcePackage: rsyslog
Title: package rsyslog-mysql 5.8.6-1ubuntu8.9 failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: rsyslog (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 need-duplicate-check precise

-- 
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/1524182

Title:
  package rsyslog-mysql 5.8.6-1ubuntu8.9 failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 1

Status in rsyslog package in Ubuntu:
  New

Bug description:
  When I installed MySQL I use ')' in the password. The symbol does on work 
when the password is on the command line to start MySQL(I do this since I am 
the only one who uses this computer).
  I forgot that I did not need to put the password on a command line ans 
started to uninstall MySQL. That is when I got this message.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: rsyslog-mysql 5.8.6-1ubuntu8.9
  ProcVersionSignature: Ubuntu 3.13.0-71.114~precise1-generic 3.13.11-ckt29
  Uname: Linux 3.13.0-71-generic i686
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: i386
  Date: Tue Dec  8 23:00:05 2015
  DuplicateSignature: package:rsyslog-mysql:5.8.6-1ubuntu8.9:subprocess 
installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MarkForUpload: True
  SourcePackage: rsyslog
  Title: package rsyslog-mysql 5.8.6-1ubuntu8.9 failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1524182/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1478231] Re: nexus10: unity-system-compositor crashes while turning display on with power key [std::exception::what: error turning display on. rc = fffffff0]

2015-12-08 Thread Daniel van Vugt
Dropped importance. N10 is likely not a supported device. And nobody
seems to have a problem with this bug having been mostly ignored for
over 100 days.

** Changed in: mir
   Importance: High => Medium

** Changed in: mir
Milestone: 0.19.0 => None

-- 
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/1478231

Title:
  nexus10: unity-system-compositor crashes while turning display on with
  power key [std::exception::what: error turning display on. rc =
  fff0]

Status in Mir:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  unity-system-compositor-log (still on top of 0.13.3 - without 0.14.0)
  with exception that causes the crash:

  [1437824578.379250] mirplatform: Found graphics driver: android
  [1437824578.379366] mirplatform: Found graphics driver: dummy
  [1437824578.390219] Server: Starting
  [1437824578.393296] Loader: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/server-platform
  [1437824578.393433] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/server-platform/input-stub.so
  [1437824578.394298] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.2
  [1437824578.394348] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-dummy.so
  [1437824578.399155] mirplatform: Found graphics driver: android
  [1437824578.399198] mirplatform: Found graphics driver: dummy
  [1437824578.399436] Platform Loader: Selected driver: android (version 0.13.3)
  [1437824579.150982] mirserver: Using software cursor
  GL_VENDOR = ARM
  GL_RENDERER = Mali-T604
  GL_VERSION = OpenGL ES 3.0
  dm_connection_start
  [1437824579.197658] GL: vendor: ARM
  [1437824579.197683] GL: renderer: Mali-T604
  [1437824579.197691] GL: version: OpenGL ES 3.0
  [1437824579.197699] GL: SL version: OpenGL ES GLSL ES 3.00
  [1437824579.197712] GL: max texture size = 8192
  [1437824579.197735] GL: framebuffer bits: RGBA=, depth=0, stencil=0
  [1437824579.203708] DisplayServer: Mir version 0.13.3
  set_active_session 'session-0'
  Opening session eglspinner
  Opening session session-0
  Closing session session-0
  Opening session session-0
  Closing session eglspinner
  Current active output is 2560x1600 +0+0
  Server supports 3 of 6 surface pixel formats. Using format: 1
  Signal 15 received. Good night.
  Closing session session-0
  ERROR: 
/build/buildd/mir-0.13.3+15.04.20150617/src/platforms/android/server/real_hwc_wrapper.cpp(156):
 Throw in function virtual void 
mir::graphics::android::RealHwcWrapper::display_on(mir::graphics::android::DisplayName)
 const
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
  std::exception::what: error turning display on. rc = fff0

  Can't get connection

  A manual restart of lightdm resolves the issue. usc starts up fine and
  is able to turn the display on. Sometimes afer waiting long enough
  lightdm seems to become aware of the situation and respawns unity-
  system-compositor. So we might derive another bug for lightdm - as it
  takes far too long to detect the crash.

  I havent tried yet 0.14.0 - but it should happen there too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1478231/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1521987] Re: Sound is not automatically switched back from headphones to speakers

2015-12-08 Thread Raymond
The volume control at those audio outputs should be named as "Front+HP"
or "Side+HP"

or give up grey jack by hdajackretask to get back Headphone Playback
Volume

-- 
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/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

2015-12-08 Thread Lorn Potter
patch #6 fixes crash in system-settings (#1523975) and removes wifi
scanning updates, which could potentially drain the battery (#1524133)


** Patch added: "net-bearer-nm-disconnect-ap-signals6.patch"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1480877/+attachment/4531735/+files/net-bearer-nm-disconnect-ap-signals6.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Fix Committed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1521917] Re: MouseWheel can push Flickable beyond the overshoot bound

2015-12-08 Thread Timo Jyrinki
** Also affects: qtdeclarative-opensource-src (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 qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1521917

Title:
  MouseWheel can push Flickable beyond the overshoot bound

Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  New

Bug description:
  This is a report to keep track of a long standing Flickable bug.

  More info at https://bugreports.qt.io/browse/QTBUG-21328

  You can find a copy of the bug description from that link below:

  Using the Mouse Wheel, at high velocities I manage to push the Flickable list 
beyond the overshoot boundary.
  Steps to reproduce :
  1. Run the code below in qmlviewer.exe
  2. Try to flick down the list using the mouse wheel, then flick up quickly. 
  3. Observe that you can move the list up so as to push everything off screen, 
far more than the hardcoded overshoot limit (see attached video).

  https://bugreports.qt.io/secure/attachment/25041/flickable.ogv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1521917/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1521987] Re: Sound is not automatically switched back from headphones to speakers

2015-12-08 Thread Raymond
you need to file upstream bug report as  VT1708S support independent HP
in previous version by sharing volume control with SIde jack

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_via.c?id=e5e14681404ec27a422d635284bf564dabde3f81

-- 
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/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1488413] Re: connected BT mouse should unblank screen (windowed mode)

2015-12-08 Thread Daniel van Vugt
I'm not familiar with our overall powerd/bus plan, but at a guess we
would want USC to action this. And in theory USC as the system
compositor will already see all input events even while the screen is
off. Thus comments #3 and #4 would be irrelevant. So I suspect this bug
will be no-action-required in Mir itself.

** Also affects: unity-system-compositor
   Importance: Undecided
   Status: New

** Changed in: mir
   Status: Triaged => Incomplete

** Changed in: mir
Milestone: None => 0.19.0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1488413

Title:
  connected BT mouse should unblank screen (windowed mode)

Status in canonical-pocket-desktop:
  New
Status in Mir:
  Incomplete
Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  when switching into windowed mode && a BT mouse is connected && screen
  is blanked (from time out or pwr key press) the BT mouse motion should
  unblank the screen

  this may effect multiple projects so sort of shotgunning the effected
  project list

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1488413/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1451554] Re: Every key is pressed twice on the desktop

2015-12-08 Thread Timo Jyrinki
** Also affects: qtdeclarative-opensource-src (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 qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1451554

Title:
  Every key is pressed twice on the desktop

Status in canonical-pocket-desktop:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  New

Bug description:
  If I launch an app with QT_IM_MODULE=MaliitPhablet system-settings, every key 
is pressed twice.
  Pressing h - a - l - l -o -  gives me:
  'Hhaaoo. '

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-keyboard 0.99.trunk.phablet2+15.04.20150326-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  4 21:43:00 2015
  InstallationDate: Installed on 2014-10-10 (206 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140922)
  SourcePackage: ubuntu-keyboard
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to vivid on 2015-01-02 (122 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1451554/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1524196] [NEW] Error on fetching several lists

2015-12-08 Thread Sworddragon
Public bug reported:

I'm using Ubuntu 16.04 dev with apt 1.1.4 and on executing "apt-get update" I'm 
seeing several times errors like "Err:10 http://archive.ubuntu.com/ubuntu 
xenial-updates InReleaseCouldn't create 
tempfiles for splitting up 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
  Could not execute 'apt-key' to verify signature (is gnupg installed?)" which 
results that these lists are not available. Downgrading to apt 1.0.10.2ubuntu1 
from Ubuntu 15.10 solves this issue.

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1524196

Title:
  Error on fetching several lists

Status in apt package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 16.04 dev with apt 1.1.4 and on executing "apt-get update" 
I'm seeing several times errors like "Err:10 http://archive.ubuntu.com/ubuntu 
xenial-updates InReleaseCouldn't create 
tempfiles for splitting up 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
Could not execute 'apt-key' to verify signature (is gnupg installed?)" 
which results that these lists are not available. Downgrading to apt 
1.0.10.2ubuntu1 from Ubuntu 15.10 solves this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1524196/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1498129] Re: Asus Xonar U7 S/PDIF output not recognized by pulseaudio

2015-12-08 Thread Raymond
# If a device does not use the first PCM device for digital data, the device
  # number for the iec958 device can be changed here.
  USB-Audio.pcm.iec958_device {
 # "NoiseBlaster 3000" 42
 "USB Sound Blaster HD" 1

-- 
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/1498129

Title:
  Asus Xonar U7 S/PDIF output not recognized by pulseaudio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The external USB audio card Asus Xonar U7 is capable of both analog and 
digital output.
  ALSA name for the digital (S/PDIF) output is hw:1,1, and it is listed in 
aplay -l output, and aplay can output to it:
  aplay -D plughw:1,1 sample.wav. So, direct alsa sound works fine.

  However, pulseadio does not recognize the digital output of Xonar U7,
  it offers only analog output.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25
  Uname: Linux 3.13.0-63-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aoand  3756 F pulseaudio
   /dev/snd/controlC0:  aoand  3756 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 21 21:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-02-20 (1674 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-05-19 (490 days ago)
  dmi.bios.date: 11/29/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET71WW (3.21 )
  dmi.board.name: 7448CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7448CTO
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1498129] Re: Asus Xonar U7 S/PDIF output not recognized by pulseaudio

2015-12-08 Thread Raymond
https://bugs.freedesktop.org/show_bug.cgi?id=74324

** Bug watch added: freedesktop.org Bugzilla #74324
   https://bugs.freedesktop.org/show_bug.cgi?id=74324

-- 
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/1498129

Title:
  Asus Xonar U7 S/PDIF output not recognized by pulseaudio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The external USB audio card Asus Xonar U7 is capable of both analog and 
digital output.
  ALSA name for the digital (S/PDIF) output is hw:1,1, and it is listed in 
aplay -l output, and aplay can output to it:
  aplay -D plughw:1,1 sample.wav. So, direct alsa sound works fine.

  However, pulseadio does not recognize the digital output of Xonar U7,
  it offers only analog output.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25
  Uname: Linux 3.13.0-63-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aoand  3756 F pulseaudio
   /dev/snd/controlC0:  aoand  3756 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 21 21:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-02-20 (1674 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-05-19 (490 days ago)
  dmi.bios.date: 11/29/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET71WW (3.21 )
  dmi.board.name: 7448CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7448CTO
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1490701] Re: BUG: soft lockup - CPU#3 stuck for 23s! [Xorg:11337]

2015-12-08 Thread Launchpad Bug Tracker
[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/1490701

Title:
  BUG: soft lockup - CPU#3 stuck for 23s! [Xorg:11337]

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I've ran into various other fglrx problems, but this is the first
  "soft lockup" after upgrading to kernel 3.16.0-46-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-46.62~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-46-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Aug 31 15:43:34 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.200, 3.16.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [1002:6649] (prog-if 00 [VGA 
controller])
 Subsystem: Dell Device [1028:230c]
  InstallationDate: Installed on 2015-04-04 (148 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:6827): WARNING **: Indicator "power": failed to load
   
   ** (lightdm-gtk-greeter:6827): WARNING **: Failed to load user image: Failed 
to open file '/home/jms/.face': No such file or directory
   init: indicator-application main process (6861) killed by TERM signal
  MachineType: Dell Inc. Precision Tower 5810
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-46-generic.efi.signed 
root=UUID=a1429ef6-c504-47a9-82fc-f4c80b480f55 ro rootflags=subvol=@ 
console=tty0 console=ttyS0,9600n8
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd01/19/2015:svnDellInc.:pnPrecisionTower5810:pvr01:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Aug 30 19:54:17 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDELL DELL USB Laser Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2
  xserver.video_driver: fglrx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1490701/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1485708] Re: fstab entry causes emergency mode to come up

2015-12-08 Thread Launchpad Bug Tracker
[Expired for mountall (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mountall (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1485708

Title:
  fstab entry causes emergency mode to come up

Status in mountall package in Ubuntu:
  Expired

Bug description:
  After upgrading from 14.04 to 14.10 and also from 14.10 to 15.04, the system 
goes into emergency mode when there is an entry in the /etc/fstab file for a 
 hard drive that isn't connected. Here's the fstab file that caused 
it and the HITACHI entry has been commented out which fixed the problem.
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  #
  # / was on /dev/sdb2 during installation
  UUID=b7b39e46-3fca-440b-b52e-ced5fa946ac2 /   ext4
errors=remount-ro 0   1
  # /boot/efi was on /dev/sdb1 during installation
  UUID=A0D7-CA74  /boot/efi   vfatdefaults0   1
  # swap was on /dev/sdb3 during installation
  UUID=156b7a15-d9a6-4d90-8f92-bacf916b7515 noneswapsw  
0   0

  #UUID=12EF-3326 /media/ben/HITACHI vfat rw,user,umask=0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-release-upgrader-core 1:15.04.14
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Aug 17 10:54:23 2015
  InstallationDate: Installed on 2014-09-03 (347 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to vivid on 2015-08-17 (0 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1485708/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1522012] Re: Error finalising statement: Could not finalize statement: database is locked

2015-12-08 Thread James Henstridge
Was there another instance of mediascanner-service-2.0 running at the
time?

The mediascanner is designed to run with only a single process writing
to the database and all other processes being read-only, so starting a
second copy of the daemon could cause this kind of problem.

Dumping core in this situation sounds like a bug, but it isn't a
supported mode of operation.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu.
https://bugs.launchpad.net/bugs/1522012

Title:
   Error finalising statement: Could not finalize statement: database is
  locked

Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  Hi,

  When i launch manually the mediascanner-service-2.0 command on freshly
  mounted folder, after several media scanned i got this error message :

  "Error finalising statement: Could not finalize statement: database is locked
  Error when indexing: database is locked
  terminate called after throwing an instance of 'std::runtime_error'
  what(): database is locked
  Aborted (core dumped)"

  Most of the medias are recognized in the picture app and music app

  My phone is a nexus 4 with Rc-proposed version.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1522012/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

2015-12-08 Thread Stéphane Graber
Also note that I'm removing the lxd task as this does appear to be a
systemd issue, ~ubuntu-lxc will remain subscribed to the issue though.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1519499

Title:
  Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at
  ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

Status in systemd package in Ubuntu:
  New

Bug description:
  This is a follow-up on this issue here:
  https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container
  gently and as it seems the issue lies within ubuntu/systemd which does
  not handle SIGPWR correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1519499/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

2015-12-08 Thread Stéphane Graber
As a reminder:
 - http://lists.freedesktop.org/archives/systemd-devel/2015-January/027246.html
 - http://lists.freedesktop.org/archives/systemd-devel/2015-January/027323.html

http://cgit.freedesktop.org/systemd/systemd/commit/?id=874d3404cbf2363604106c8f86683db4082691ea

The code change at that point was to ignore all mounts under /dev, /proc
and /sys, maybe things changed since and re-introduced the issue
somehow, or we missed a code path somewhere.

** No longer affects: lxd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1519499

Title:
  Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at
  ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

Status in systemd package in Ubuntu:
  New

Bug description:
  This is a follow-up on this issue here:
  https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container
  gently and as it seems the issue lies within ubuntu/systemd which does
  not handle SIGPWR correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1519499/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1442505] Re: /usr/sbin/unity-system-compositor:11:mir::frontend::SessionMediator::create_screencast:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor:

2015-12-08 Thread Daniel van Vugt
** Tags added: screencast

-- 
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/1442505

Title:
  /usr/sbin/unity-system-
  
compositor:11:mir::frontend::SessionMediator::create_screencast:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor::dispatch:mir::frontend::detail::SocketConnection::on_new_message:mir::frontend::detail::SocketConnection::on_read_size

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.0.5+15.04.20150227-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/f97c1aceb8c847481ec0aed856e113739a423e7b
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1442505/+subscriptions

-- 
Mailing list: https://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 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

2015-12-08 Thread Thomas Voß
Thanks for the graphs. One thing that stands out is the time that the
system stays active when occasionally waking up from deep sleep (right
hand side of the graph).
Do you have the raw data producing those graphs handy?

Thanks,

  Thomas

On Wed, Dec 9, 2015 at 1:23 AM, Selene Scriven
 wrote:
> Is it possible that this fix might cause a phone to wake up more often,
> or to stay awake longer?  I'm seeing weird idle power behavior ever
> since this fix landed in krillin rc-proposed 196.
>
> Before: ~9 mA
> http://people.canonical.com/~platform-qa/power-results/2015-12-08_03:19:30-krillin-195-power_usage_idle/graph.png
>
> After: ~35 mA
> http://people.canonical.com/~platform-qa/power-results/2015-12-08_07:36:16-krillin-196-power_usage_idle/graph.png
>
> Here's the commit log for 196:
>
> http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-
> proposed/196.commitlog
>
> Arale results look fine.  I don't know why krillin is different, but I'm
> only seeing this behavior on krillin when wifi is connected...  and this
> bug fix is a likely suspect.  I don't see additional forks or crashes in
> the test logs, which suggests the issue is probably caused by a long-
> running process.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1480877
>
> Title:
>   Access points' "PropertiesChanged" dbus signals freeze UI on mobile
>   devices
>
> Status in Canonical System Image:
>   Fix Committed
> Status in Unity 8:
>   New
> Status in dbus-cpp package in Ubuntu:
>   In Progress
> Status in network-manager package in Ubuntu:
>   Incomplete
> Status in qtbase-opensource-src package in Ubuntu:
>   Fix Committed
> Status in dbus-cpp package in Ubuntu RTM:
>   Fix Released
> Status in location-service package in Ubuntu RTM:
>   Fix Released
> Status in network-manager package in Ubuntu RTM:
>   Incomplete
>
> Bug description:
>   Krillin, rc-proposed, r83
>
>
>   DESCRIPTION:
>   I've been trying to track down the cause of the occasional UI freezes on my 
> Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
> get a burst of "PropertiesChanged" signals in dbus-monitor
>
>   Here's a log of what's shown in dbus-monitor:
>   http://pastebin.ubuntu.com/11992322/
>
>   I'd guess the problem is in the code that actually catches the signals
>   and acts accordingly.
>
>   HOW TO REPRODUCE:
>   1) Move to a place where many wifi hotspots are available
>   2) Connect the device via USB and run "phablet-shell" and then 
> "dbus-monitor"
>   3) Use the device while keeping an eye on dbus-monitor output
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Fix Committed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1479045] Re: E: Method gave invalid 103 Redirect message

2015-12-08 Thread Diego Rodríguez Baquero
+1 in Ubuntu 14.04

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1479045

Title:
  E: Method gave invalid 103 Redirect message

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when running `apt update` or equivalent, the progress stops
  with error "E: Method gave invalid 103 Redirect message". This seems
  to happen especially when http:://mirrors.ubuntu.com/mirrors.txt is
  used.

  Current sources.list on this laptop is below. This happens with other
  my devices running Ubuntu too which sources.list is
  https://raw.githubusercontent.com/Mikaela/shell-
  things/a5c9156eb41826e3c2cb05ce09f9981d01ce979d/etc/apt/sources.list/15.04

  ```
  # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
  # newer versions of the distribution.
  deb mirror://mirrors.ubuntu.com/mirrors.txt vivid main restricted universe 
multiverse

  ## Major bug fix updates produced after the final vivid of the
  ## distribution.
  deb mirror://mirrors.ubuntu.com/mirrors.txt vivid-updates main restricted 
universe multiverse

  ## N.B. software from this repository may not have been tested as
  ## extensively as that contained in the main vivid, although it includes
  ## newer versions of some applications which may provide useful features.
  ## Also, please note that software in backports WILL NOT receive any review
  ## or updates from the Ubuntu security team.
  deb mirror://mirrors.ubuntu.com/mirrors.txt vivid-backports main restricted 
universe multiverse
  deb mirror://mirrors.ubuntu.com/mirrors.txt vivid-security main restricted 
universe multiverse
  deb http://security.ubuntu.com/ubuntu vivid-security main restricted universe 
multiverse
  deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid main restricted 
universe multiverse
  deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid-updates main restricted 
universe multiverse
  deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid-backports main 
restricted universe multiverse
  deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid-security main 
restricted universe multiverse
  deb-src http://security.ubuntu.com/ubuntu vivid-security main restricted 
universe multiverse

  ## Uncomment the following two lines to add software from Canonical's
  ## 'partner' repository.
  ## This software is not part of Ubuntu, but is offered by Canonical and the
  ## respective vendors as a service to Ubuntu users.
  deb http://archive.canonical.com/ubuntu vivid partner
  deb-src http://archive.canonical.com/ubuntu vivid partner

  # https://wiki.ubuntu.com/DebuggingProgramCrash
  # sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  deb http://ddebs.ubuntu.com vivid main restricted universe multiverse
  deb http://ddebs.ubuntu.com vivid-updates main restricted universe multiverse
  # Ignore unless you have enabled proposed below
  #deb http://ddebs.ubuntu.com vivid-proposed main restricted universe 
multiverse

  # https://wiki.ubuntu.com/Testing/EnableProposed
  #deb mirror://mirrors.ubuntu.com/mirrors.txt vivid-proposed main restricted 
universe multiverse
  #deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid-proposed main 
restricted universe multiverse
  ```

  This has been happening for a long time, possibly years and I was
  surprised that I wasn't able to find bug report by searching bugs for
  package "apt" with search term "103" redirect.

  I have learned that workaround for this issue is `cd
  /var/lib/apt/lists;rm *;cd partial;rm *;cd`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop:
   
  Date: Tue Jul 28 19:25:58 2015
  InstallationDate: Installed on 2015-07-14 (14 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1479045/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1521618] Re: wrong subnet in DHCP answer when multiple networks are present

2015-12-08 Thread LaMont Jones
I'm having trouble reproducing this...

What version of isc-dhcp-server is running here?

Does it change anything if you (manually) reorder the 2 subnets in
dhcpd.conf and restart the dhcp server?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1521618

Title:
  wrong subnet in DHCP answer when multiple networks are present

Status in MAAS:
  Triaged
Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  So I have 3 interfaces with 3, non-overlapping subnets defined in my
  maas cluster controller.

  The idea would be that there is a provisioning network (10.6.0.0/16)
  to do the actual provisioning and once the node gets deployed it is
  using a different network (because the provisioning network is only
  1x1Gbit while the production network is bonded (LACP) 10Gbit).

  However, when I boot up a fresh, new node to add to MAAS, it gets the
  following DHCP reply:

  ip=10.6.239.3:10.6.250.250:9.4.113.254:255.255.255.0

  So instead of picking up the /16 subnet correctly for the 10.6.239.3
  IP, it picks up the /24 from the network where it gets it's default
  gateway from.

  Is this a bug or my understanding of how MAAS should behave when there
  are multiple networks flawed?

  Here is my /var/lib/maas/dhcpd.conf:

  subnet 9.4.113.0 netmask 255.255.255.0 {
 if option arch = 00:0E {
filename "pxelinux.0";
option path-prefix "ppc64el/";
 } elsif option arch = 00:07 {
filename "bootx64.efi";
 } elsif option arch = 00:0B {
filename "grubaa64.efi";
 } elsif option arch = 00:0C {
filename "bootppc64.bin";
 } else {
filename "pxelinux.0";
 }
 interface "eth0";
 ignore-client-uids true;
 option subnet-mask 255.255.255.0;
 option broadcast-address 9.4.113.255;
 option domain-name-servers 9.4.113.251;
 option domain-name "i.zc2.ibm.com";
 option routers 9.4.113.254;
 option ntp-servers ntp.ubuntu.com;
 range dynamic-bootp 9.4.113.150 9.4.113.190;
 class "PXE" {
match if substring (option vendor-class-identifier, 0, 3) = "PXE";
default-lease-time 30;
max-lease-time 30;
 }
  }
  subnet 10.6.0.0 netmask 255.255.0.0 {
 if option arch = 00:0E {
filename "pxelinux.0";
option path-prefix "ppc64el/";
 } elsif option arch = 00:07 {
filename "bootx64.efi";
 } elsif option arch = 00:0B {
filename "grubaa64.efi";
 } elsif option arch = 00:0C {
filename "bootppc64.bin";
 } else {
filename "pxelinux.0";
 }
 interface "eth1";
 ignore-client-uids true;
 option subnet-mask 255.255.0.0;
 option broadcast-address 10.6.255.255;
 option domain-name-servers 9.4.113.251;
 option domain-name "i.zc2.ibm.com";
 option ntp-servers ntp.ubuntu.com;
 range dynamic-bootp 10.6.239.0 10.6.239.239;
 class "PXE" {
match if substring (option vendor-class-identifier, 0, 3) = "PXE";
default-lease-time 30;
max-lease-time 30;
 }
  }

  Here is "subnets read":

  [
  {
  "dns_servers": [],
  "name": "9.4.113.0/24",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/0/",
  "fabric": "fabric-0",
  "vid": 0,
  "id": 0
  },
  "gateway_ip": "9.4.113.254",
  "cidr": "9.4.113.0/24",
  "id": 1,
  "resource_uri": "/MAAS/api/1.0/subnets/1/"
  },
  {
  "dns_servers": [],
  "name": "10.7.0.0/16",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/5001/",
  "fabric": "fabric-1",
  "vid": 0,
  "id": 5001
  },
  "gateway_ip": null,
  "cidr": "10.7.0.0/16",
  "id": 2,
  "resource_uri": "/MAAS/api/1.0/subnets/2/"
  },
  {
  "dns_servers": [],
  "name": "10.6.0.0/16",
  "space": "space-0",
  "vlan": {
  "name": "untagged",
  "resource_uri": "/MAAS/api/1.0/vlans/5002/",
  "fabric": "fabric-2",
  "vid": 0,
  "id": 5002
  },
  "gateway_ip": null,
  "cidr": "10.6.0.0/16",
  "id": 3,
  "resource_uri": "/MAAS/api/1.0/subnets/3/"
  }
  ]

  Running 1.9.0~rc2+bzr4509-0ubuntu1~trusty1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1521618/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1513933] Re: Page.head.sections.selectedIndex does not reset when changing model

2015-12-08 Thread Tim Peeters
I implemented the desired behavior in the attached MR. However, that
conflicts with this bug: https://bugs.launchpad.net/ubuntu/+source
/ubuntu-ui-toolkit/+bug/1511839

Internally, the application header has a single Sections instance, and
when the active Page changes, the PageHeadSections of that Page becomes
active and updates the model of the Sections. That will reset the
selectedIndex to 0. This is not a new problem with the new PageHeader,
because each Page has its own PageHeader, but with the old
PageHeadConfiguration and PageHeadSections the index must be reset to 0
with this behavior.

The solution is to use an old version of Sections in the (old)
application header (configured with Page.head), and to use the new
Sections with PageHeader. The new Sections (use PageHeader) always works
as desired, but when using the Page.head.sections, the index is not
reset to 0 when changing the model. So applications that change the
model and require this behavior need to update the app to make use of
the PageHeader (or implement a workaround where the app sets the new
selectedIndex for Page.head.sections after the model is updated).

-- 
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/1513933

Title:
  Page.head.sections.selectedIndex does not reset when changing model

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Changing Page.head.sections.model does not change the
  Page.head.sections.selectedIndex  even when the model has different
  size.

  I have a page that I need to update the ' Page.head.sections.model '
  dynamically and after change the model or make it empty the
  Page.head.sections.selectedIndex still point to last value used.

  I expect that to reset back to 0 if the model changes.

  Check attached example .

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513933/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1518955] Re: System image client log file grows indefinitely

2015-12-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: system-image (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system-image in Ubuntu.
https://bugs.launchpad.net/bugs/1518955

Title:
  System image client log file grows indefinitely

Status in Canonical System Image:
  Confirmed
Status in system-image package in Ubuntu:
  Confirmed

Bug description:
  From what I can tell the log file for system image at /var/log/system-
  image/client.log is continually appended to and is not rolled or
  truncated.

  My current log has entries from 8 months ago and is over 3MB.

  Another phone shows entries 5 months old and is over 1MB

  I assume those were since the last full data wipes and flash

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518955/+subscriptions

-- 
Mailing list: https://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 1523223] Re: error in man page

2015-12-08 Thread Martin Pitt
rm damerell [2015-12-08 21:03 -]:
> Please is there any way to discover whether the rule
> files in/lib/udev/rules.dare being read? Thank you.

Yes, of course they are as that's the directory where Ubuntu packages
ship all rules.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1523223

Title:
  error in man page

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  
  L-Ubuntu 14.04,  udev  204-5ubuntu20.15 (latest).   man udev  says that 
  udev reads rules from 

  /usr/lib/udev/rules.d
  /run/udev/rules.d 

  and

  /etc/udev/rules.d

  The first 2 do not exist. There are rule files in

  /lib/udev/rules.d

  but I do not know any way to find out whether or not these are being read.
  (if any human reads this, I would be grateful if you could tell me).
  I was advised to file a bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu20.15
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Dec  6 11:50:36 2015
  InstallationDate: Installed on 2015-07-19 (140 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: Dell Inc. Inspiron 1525
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=30c969c8-8299-4020-8ecc-bc228a671810 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1523223/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1489323] Re: Greeter not always being shown

2015-12-08 Thread Pat McGowan
@josh still seeing this occasionally so shoot me some qml or whatever

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1489323

Title:
  Greeter not always being shown

Status in Canonical System Image:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  On last few weeks of rc-proposed and ota6 on MX4
  On occasion when the phone resumes, either through a power button press or an 
incoming event, the greeter is not shown and either the passcode entry page or 
the last running app is shown directly.

  This is intermittent but once in this state it is very consistently behaving 
this way.
  Update: while that was originally true now (build 136) it seems to clear once 
the button is pressed, the greeter is shown next resume.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1447110] Re: location service fills disk with logs, needs to ship logrotate config

2015-12-08 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: None => backlog

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => Thomas Voß (thomas-voss)

** Changed in: canonical-devices-system-image
Milestone: backlog => ww08-2016

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1447110

Title:
  location service fills disk with logs, needs to ship logrotate config

Status in Canonical System Image:
  Confirmed
Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  phablet@ubuntu-phablet:~$ ls -l  /var/log/ubuntu-location-service/|wc -l
  664
  phablet@ubuntu-phablet:~$ sudo du -hcs /var/log/ubuntu-location-service/
  22M   /var/log/ubuntu-location-service/

  seems location service never cleans up its logs, while they are small, the 
sheer amount over time occupies a lot of diskspace ...
  ubuntu-location-service needs to ship a config in /etc/logrotate.d  to make 
sure the log subdir gets regulary flushed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447110/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1461444] Re: Doesn't clean out old logs

2015-12-08 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: backlog => ww08-2016

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-download-manager in
Ubuntu.
https://bugs.launchpad.net/bugs/1461444

Title:
  Doesn't clean out old logs

Status in Canonical System Image:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed

Bug description:
  Using a bq/rtm phone (now on vivid ota candidate), the u-d-m logs have
  files going back to octobre and uses 3.3M, it seems we stack those and
  never clean out/rotate. While it's not that much space used a few mbs
  would still better be available to the user than wasted by old logs...

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1461444/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


<    1   2   3   >