[Touch-packages] [Bug 1487103] Re: [PATCH] pam-auth-update - don't break because of trailing whitespace in /usr/share/pam-configs/* files

[Steve Langasek]

This patch didn't apply locally, and also warranted some style changes
to be consistent with the existing code.  I've committed an equivalent
of this patch to the pam bzr repo at http://bzr.debian.org/bzr/pkg-
pam/debian/sid/; feel free to test that it does what you expect.

** Changed in: pam (Ubuntu)
   Importance: Undecided => Low

** Changed in: pam (Ubuntu)
   Status: New => Triaged

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

Title:
  [PATCH] pam-auth-update - don't break because of trailing whitespace
  in /usr/share/pam-configs/* files

Status in pam package in Ubuntu:
  Triaged

Bug description:
  When a /usr/share/pam-configs/* file contains trailing whitespaces, the 
resulting entry in /etc/pam.d/* won't be written.
  The attached patch fixes this and strips leading/trailing whitespaces where 
appropriate.

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

-- 
Mailing list: https://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 1485708] Re: fstab entry causes emergency mode to come up

[Steve Langasek]

On Sat, Aug 22, 2015 at 02:25:48AM -, WhyteHorse wrote:
> It drops to a shell prompt with a motd that says "Emergency Mode please
> run  to review the boot logs or else run  command> to boot normally". I don't recall the exact text but it's a
> root shell...

Ok.  This appears to be the expected 'emergency' mode with systemd, so for
15.04 and later that is what you would see on a failure to mount a local
filesystem.

> In 14.04 it did display the "Press S to skip waiting for filesystem".

That is also expected.

> In 14.10 I went to the grub menu and switched to an older kernel and it
> worked with the skip message, but the newer kernel just dropped to the
> shell.

This behavior should not vary by kernel.  If you can reproduce this error on
a 14.10 system, this would be worth us investigating.

-- 
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:
  Incomplete

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 1487667] [NEW] Setting automaticOrientation to false does not take any effect

[XiaoGuo, Liu]

Public bug reported:

When the automaticOrientation is set to false, my app still rotates when
my app rotates. It does not take any effect.

MainView {
// objectName for functional testing purposes (autopilot-qt5)
objectName: "mainView"

// Note! applicationName needs to match the "name" field of the click 
manifest
applicationName: "com.ubuntu.developer.liu-xiao-guo.Memory"

/*
 This property enables the application to change orientation
 when the device is rotated. The default is false.
*/
automaticOrientation: false

width: units.gu(60)
height: units.gu(85)

Page {
title: i18n.tr("Memory Card")

Game {
anchors.fill: parent
anchors.horizontalCenter: parent.horizontalCenter
anchors.verticalCenter: parent.verticalCenter
}
}
}

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Setting automaticOrientation to false does not take any effect

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  When the automaticOrientation is set to false, my app still rotates
  when my app rotates. It does not take any effect.

  MainView {
  // objectName for functional testing purposes (autopilot-qt5)
  objectName: "mainView"

  // Note! applicationName needs to match the "name" field of the click 
manifest
  applicationName: "com.ubuntu.developer.liu-xiao-guo.Memory"

  /*
   This property enables the application to change orientation
   when the device is rotated. The default is false.
  */
  automaticOrientation: false

  width: units.gu(60)
  height: units.gu(85)

  Page {
  title: i18n.tr("Memory Card")

  Game {
  anchors.fill: parent
  anchors.horizontalCenter: parent.horizontalCenter
  anchors.verticalCenter: parent.verticalCenter
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1487667/+subscriptions

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

[Touch-packages] [Bug 1484697] Re: package libffi6:i386 3.2.1-2 failed to install/upgrade: package libffi6:i386 is already installed and configured

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 1407757 ***
https://bugs.launchpad.net/bugs/1407757

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libffi (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libffi6:i386 3.2.1-2 failed to install/upgrade: package
  libffi6:i386 is already installed and configured

Status in libffi package in Ubuntu:
  Confirmed

Bug description:
  Install error

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: libffi6:i386 3.2.1-2
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.2
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu3.1
  Architecture: amd64
  Date: Thu Aug 13 22:54:39 2015
  Dependencies:
   gcc-5-base 5.1~rc1-0ubuntu1
   libc6 2.21-0ubuntu4
   libgcc1 1:5.1~rc1-0ubuntu1
   multiarch-support 2.21-0ubuntu4
  DuplicateSignature: package:libffi6:i386:3.2.1-2:package libffi6:i386 is 
already installed and configured
  ErrorMessage: package libffi6:i386 is already installed and configured
  InstallationDate: Installed on 2015-08-13 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: libffi
  Title: package libffi6:i386 3.2.1-2 failed to install/upgrade: package 
libffi6:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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

[WhyteHorse]

It drops to a shell prompt with a motd that says "Emergency Mode please
run  to review the boot logs or else run  to boot normally". I don't recall the exact text but it's a
root shell... In 14.04 it did display the "Press S to skip waiting for
filesystem". In 14.10 I went to the grub menu and switched to an older
kernel and it worked with the skip message, but the newer kernel just
dropped to the shell. In 15.04 the newest kernel dropped to the shell
and the older kernel just hung indefinitely.

I removes the fstab entry and the newest kernel boots just fine. That's
all I know...

-- 
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:
  Incomplete

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 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Raymond]

** Also affects: virtualbox (Ubuntu)
   Importance: Undecided
   Status: 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/1487168

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in virtualbox package in Ubuntu:
  New

Bug description:
  Volume Slider is only controlling PCM channel and is not controlling
  Master. In effect, Master is restricting the audio level to the
  default of approximately 45 Percent. In order to raise the Master
  Volume Level, alsamixer is capable of changing Master. Without
  manually raising Master to Max Volume, Volume Slider can only control
  volume from 0-45% which is the default level of Master.

  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1330 F pulseaudio
gene   1922 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Aug 20 13:00:57 2015
  InstallationDate: Installed on 2015-08-19 (1 days ago)
  InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_Type: Volume slider, or mixer problems
  Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Raymond]

control.9 {
   iface MIXER
   name 'Master Playback Switch'
   value.0 true
   value.1 true
   comment {
access 'read write'
type BOOLEAN
count 2
   }
  }
  control.10 {
   iface MIXER
   name 'Master Playback Volume'
   value.0 27
   value.1 27
   comment {
access 'read write'
type INTEGER
count 2
range '0 - 31'
dbmin -4650
dbmax 0
dbvalue.0 -600
dbvalue.1 -600
   }
  }
  control.11 {
   iface MIXER
   name 'Master Mono Playback Switch'
   value true
   comment {
access 'read write'
type BOOLEAN
count 1
   }
  }
  control.12 {
   iface MIXER
   name 'Master Mono Playback Volume'
   value 23
   comment {
access 'read write'
type INTEGER
count 1
range '0 - 31'
dbmin -4650
dbmax 0
dbvalue.0 -1200
   }
  }


db range and no of steps of master mono playback volume are different



control.4 {
iface MIXER
name 'Master Mono Playback Volume'
value.0 0
value.1 0
comment {
access 'read write'
type INTEGER
count 2
range '0 - 63'
dbmin -9450
dbmax 0
dbvalue.0 -9450
dbvalue.1 -9450
}

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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in virtualbox package in Ubuntu:
  New

Bug description:
  Volume Slider is only controlling PCM channel and is not controlling
  Master. In effect, Master is restricting the audio level to the
  default of approximately 45 Percent. In order to raise the Master
  Volume Level, alsamixer is capable of changing Master. Without
  manually raising Master to Max Volume, Volume Slider can only control
  volume from 0-45% which is the default level of Master.

  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1330 F pulseaudio
gene   1922 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Aug 20 13:00:57 2015
  InstallationDate: Installed on 2015-08-19 (1 days ago)
  InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_Type: Volume slider, or mixer problems
  Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Raymond]

if you compare the amixer output of real ad1980 and emulated ad1980

the emulated ad1980 did not implement Master Playback Volume


Card hw:2 'ICH6'/'Intel ICH6 with AD1980 at irq 23'
   Mixer name : 'Analog Devices AD1980'
   Components : 'AC97a:41445370'
   Controls : 40
   Simple ctrls : 29
 Simple mixer control 'Master',0
   Capabilities: pvolume pswitch penum
   Playback channels: Front Left - Front Right
   Limits: Playback 0 - 31
   Mono:
   Front Left: Playback 27 [87%] [-6.00dB] [on]
   Front Right: Playback 27 [87%] [-6.00dB] [on]
Simple mixer control 'Master Mono',0
   Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
   Playback channels: Mono
   Limits: Playback 0 - 31
   Mono: Playback 23 [74%] [-12.00dB] [on]


Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with AD1980 at irq 21'
  Mixer name: 'Analog Devices AD1980'
  Components: 'AC97a:41445370'
  Controls  : 46
  Simple ctrls  : 32
Simple mixer control 'Master Mono',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 63
  Mono:
  Front Left: Playback 0 [0%] [-94.50dB] [off]
  Front Right: Playback 0 [0%] [-94.50dB] [off]

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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Volume Slider is only controlling PCM channel and is not controlling
  Master. In effect, Master is restricting the audio level to the
  default of approximately 45 Percent. In order to raise the Master
  Volume Level, alsamixer is capable of changing Master. Without
  manually raising Master to Max Volume, Volume Slider can only control
  volume from 0-45% which is the default level of Master.

  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1330 F pulseaudio
gene   1922 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Aug 20 13:00:57 2015
  InstallationDate: Installed on 2015-08-19 (1 days ago)
  InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_Type: Volume slider, or mixer problems
  Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1482887] Re: NetworkManager not setting given DNS in resolv.conf

[Bug Watch Updater]

** Changed in: network-manager
   Status: Confirmed => Incomplete

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

Title:
  NetworkManager not setting given DNS in resolv.conf

Status in NetworkManager:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
   SYSTEM INFOS 
  # lsb_release -rd
  Description:  Linux Mint 17 Qiana
  Release:  17

  # dpkg --list cinnamon resolvconf network-manager
  ii  cinnamon2.2.16 amd64  Cinnamon desktop
  ii  network-manager 0.9.8.8-0ubunt amd64  network management 
framework (daemon and userspace tools)
  ii  resolvconf  1.69ubuntu1.1  allname server information 
handler

  --

  So, it looks like a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/382161
  but this was on KDE in 2009 and I doubt it would have anything to do
  with it...

  Anyway, here is how to reproduce the problem:
  - Go to network-manager settings GUI (network indicator -> Network 
connections)
  - Edit current connection (wlan0 in my case)
  - Go to IPv4 settings
  - Select DHCP (addresses only)
  - Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC 
project)
  - Click save
  - Click disconnect
  - Click connect

  In the summary, you can see the DNS server you just typed. But if you
  # cat /etc/resolv.conf
  then you see the DNS server provided by your DHCP server (in my case 
192.168.1.1)

  So the only way to bypass DHCP's DNS settings is to hard-code the DNS
  in /etc/resolvconf/resolv.conf.d/head

  Since this can lead users to believe that they are using their
  favorite DNS server while they get answers from their ISP/Hotspot DNS,
  I checked the 'Security' box.

  This could also be related to
  - 
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
  - 
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
  - 
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
  - 
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437

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

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

[Touch-packages] [Bug 1487650] [NEW] /usr/bin/signond:*** Error in `/usr/bin/signond': corrupted double-linked list (not small): ADDR ***

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding signon.  This problem was most recently seen with version
8.57+15.04.20150204.1-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/18ae9c461f28b8641975ddb7a4aa878ffdae3d37
contains more details.

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


** Tags: wily

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

Title:
  /usr/bin/signond:*** Error in `/usr/bin/signond': corrupted double-
  linked list (not small): ADDR ***

Status in signon package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding signon.  This problem was most recently seen with version
  8.57+15.04.20150204.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/18ae9c461f28b8641975ddb7a4aa878ffdae3d37
  contains more details.

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

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

[Touch-packages] [Bug 1487649] [NEW] /usr/bin/unity8:11:assign:set_error:MirConnection::MirConnection:make_unique:connect

[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.10+15.10.20150804-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/073572aa56ec6f7f15553fe0287e99fb791097df
contains more details.

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


** Tags: wily

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

Title:
  
/usr/bin/unity8:11:assign:set_error:MirConnection::MirConnection:make_unique:connect

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.10+15.10.20150804-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/073572aa56ec6f7f15553fe0287e99fb791097df
  contains more details.

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

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

[Touch-packages] [Bug 1483127] Re: Proximity does not turn screen on during a call

[Launchpad Bug Tracker]

** Branch linked: lp:~albaguirre/unity-system-compositor/fix-1483127

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

Title:
  Proximity does not turn screen on during a call

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  This has regressed a week or two ago. It's not reliably reproducible,
  but bites me almost every time I want to end a call. It might be
  incoming calls only, or maybe only after a minute.

  Steps:
  * go on a call
  * cover the proximity sensor
  * uncover the proximity sensor

  Expected:
  * screen goes off/on as you cover/uncover the sensor

  Current:
  * screen goes off but not back on

  $ system-image-cli -i
  current build number: 90
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-08 21:08:55
  version version: 90
  version ubuntu: 20150807.1
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Steve Langasek]

What exactly do you mean when you say "emergency mode"?

The expected behavior, when you boot Ubuntu and have a filesystem
referenced in /etc/fstab for which the device is absent, is that the
system will prompt, via plymouth, whether to continue waiting for the
filesystem or to skip mounting it.  This should be the case up through
Ubuntu 14.10.  For Ubuntu 15.04, with the switch to systemd the behavior
will be different; but should still not result in the system booting to
anything that could be considered "emergency mode".

** Changed in: mountall (Ubuntu)
   Status: New => Incomplete

-- 
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:
  Incomplete

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 1487637] [NEW] Unable to resize/move window after XGrabKeyboard

[Cemil Azizoglu]

Public bug reported:

I'm experiencing this as described here :

http://stackoverflow.com/questions/14555703/x11-unable-to-move-window-
after-xgrabkeyboard

Move/resize both suffer from the same problem. This is on Wily.

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

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

Title:
  Unable to resize/move window after XGrabKeyboard

Status in unity package in Ubuntu:
  New

Bug description:
  I'm experiencing this as described here :

  http://stackoverflow.com/questions/14555703/x11-unable-to-move-window-
  after-xgrabkeyboard

  Move/resize both suffer from the same problem. This is on Wily.

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

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

[Touch-packages] [Bug 1290201] Re: haptic feedback / vibration audible during calls

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid)
   Status: New => Confirmed

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

Title:
  haptic feedback / vibration audible during calls

Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit source package in Vivid:
  Confirmed

Bug description:
  If I press any of the call control buttons during a call, the phone
  vibrates.  This vibration is audible to the person on the other end of
  the call.  This means people can hear when I toggle
  mute/pause/speaker, which can be considered rude or at least
  distracting.

  The dialer app seems to ignore audio for a while after each button
  press, but the mic starts working again before the vibration stops.
  Could we make the vibration shorter?

  This was on a nexus 4 (mako), image 228 (observed on older images
  too).

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

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

[Touch-packages] [Bug 411688] Re: pulseaudio floods network with multicast packets

[Solaris]

I launched "Pulseaudio preferences"   ---> under the tab
"multicast/RTP", disabled "Multicast/RTP sender" .

 problem solved!

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

Title:
  pulseaudio floods network with multicast packets

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Since a karmic update last week, when pulseaudio is running it floods
  the network with multicast packets, to the point where the wireless
  interface I'm using is so flooded that no other network traffic can be
  transfered.

  Here is a snippet of tcpdump -i wlan 0 -n:
  ---8<---
  01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d0f 4000 0111 2d6d 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e
0x0020:  0071 a980 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d10 4000 0111 2d6c 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f
0x0020:  0071 aac0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d11 4000 0111 2d6b 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f774 800a ee90
0x0020:  0071 ac00 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d12 4000 0111 2d6a 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f633 800a ee91
0x0020:  0071 ad40 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d13 4000 0111 2d69 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f4f2 800a ee92
0x0020:  0071 ae80 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d14 4000 0111 2d68 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f3b1 800a ee93
0x0020:  0071 afc0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d15 4000 0111 2d67 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f270 800a ee94
0x0020:  0071 b100 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d16 4000 0111 2d66 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f12f 800a ee95
0x0020:  0071 b240 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d17 4000 0111 2d65 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 efee 800a ee96
0x0020:  0071 b380 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.605081 IP (tos 0x10, ttl 1, id 23832, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d18 4000 0111 2d64 0a00 0001
0x0010:  e000 0038 b0

[Touch-packages] [Bug 1487632] [NEW] the phone shows "cell network indicator" ON but there is no telephony possible

[Chris]

Public bug reported:


I have had a stange bug on my Meizu Mx4 at least 5 times till ota 5 ...  but I 
wasn't able to reproduce it ...till yesterday
 
It generally occured after a screen freeze  ...

my tel connection in task bar was ok : cell network icon triangle "filled".. ON 
but in fact the telephony service was not functional 
- when making a phone call there was  "no connection available" when in the 
"phone call screen" .. 
- The people that called me during the problem heard the ring several times 
..but  I didn't receive any call or msg on the phone.. so i was probably 
connected to the cell network cause my account was receiving calls and they 
were not redirected to the message box directly.. but on my side the phone 
didn't ring nor receive msg

-> I have tried to use plane mode on/off / changing the sim card /reboot
... nothing worked .. then after some times it returned to normal ...

The main problem here is that you consider that the phone is working cause you 
see the triangle icon full in the indicator bar ...
But you don't receive the phone calls ... like if you were ignoring phone calls


Yesterday I found a way to reproduce the bug ... and the workaround that makes 
the telephony-service work again after the bug

how to reproduce the problem :


1. put wifi off and phone data off (2g/3g/4g)
 telephony triangle icon is filled

2. restart the phone

3. after restart the phone indicator bar shows full GSM cover with the triangle 
icon filled.
4. if you go in the phone dialer ... you have no network .. you can't make 
phone call .. and you can't receive phone calls nor sms

Workaround: (to get your gsm back to normal)
-

to make the telephony work again : 
it's odd put you must only put wifi "on"  from the indicator bar 
then telephony is  functional again... and you get the operator name  in phone 
app


Kind regards

** Affects: telephony-service (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  the phone shows "cell network indicator" ON but there is no telephony
  possible

Status in telephony-service package in Ubuntu:
  New

Bug description:
  
  I have had a stange bug on my Meizu Mx4 at least 5 times till ota 5 ...  but 
I wasn't able to reproduce it ...till yesterday
   
  It generally occured after a screen freeze  ...

  my tel connection in task bar was ok : cell network icon triangle "filled".. 
ON but in fact the telephony service was not functional 
  - when making a phone call there was  "no connection available" when in the 
"phone call screen" .. 
  - The people that called me during the problem heard the ring several times 
..but  I didn't receive any call or msg on the phone.. so i was probably 
connected to the cell network cause my account was receiving calls and they 
were not redirected to the message box directly.. but on my side the phone 
didn't ring nor receive msg

  -> I have tried to use plane mode on/off / changing the sim card
  /reboot  ... nothing worked .. then after some times it returned to
  normal ...

  The main problem here is that you consider that the phone is working cause 
you see the triangle icon full in the indicator bar ...
  But you don't receive the phone calls ... like if you were ignoring phone 
calls

  
  Yesterday I found a way to reproduce the bug ... and the workaround that 
makes the telephony-service work again after the bug

  how to reproduce the problem :
  

  1. put wifi off and phone data off (2g/3g/4g)
   telephony triangle icon is filled

  2. restart the phone

  3. after restart the phone indicator bar shows full GSM cover with the 
triangle icon filled.
  4. if you go in the phone dialer ... you have no network .. you can't make 
phone call .. and you can't receive phone calls nor sms

  Workaround: (to get your gsm back to normal)
  -

  to make the telephony work again : 
  it's odd put you must only put wifi "on"  from the indicator bar 
  then telephony is  functional again... and you get the operator name  in 
phone app

  
  Kind regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1487632/+subscriptions

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

[Touch-packages] [Bug 1458694] Re: [vivid-overlay] unity8 fails to start on the emulator

[Michael Terry]

> Sorry, but why do we need to disable the edge demo?

We disabled the tutorial in desktop mode only.  We had in the past
disabled part of it on the desktop (because certain drag-widgets didn't
work with mice).  But this change drops the whole thing (which was at
this point, just the left-edge drag).  To my knowledge, we're still
waiting on design for visuals for a desktop tutorial.

The real bug is that the emulator is starting in desktop mode.  And
seems to have some issues with using -mousetouch to emulate a touch
device.

But at least disabling the tutorial in desktop mode gets *some* sort of
emulator functionality in the short term.

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

Title:
  [vivid-overlay] unity8 fails to start on the emulator

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Committed

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 140
  device name: generic_x86
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-05-25 12:02:10
  version version: 140
  version ubuntu: 20150525
  version device: 20150210
  version custom: 20150525

  When starting unity8 (this started at image 136, probably when mir
  0.13 landed):

  phablet@ubuntu-phablet:~$ cat ./.cache/upstart/unity8.log
  ()
  [1432595001.896139] mirplatform: Found graphics driver: dummy
  [1432595001.898447] mirplatform: Found graphics driver: android
  qtmir.mir: MirServer created
  [1432595003.675225] Server: Starting
  [1432595003.679331] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/server-platform
  [1432595003.679501] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
  [1432595003.680673] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
  [1432595003.681107]  Loader: Failed to load module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error 
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined 
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
  [1432595003.684868] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
  [1432595003.685014] mirplatform: Found graphics driver: dummy
  [1432595003.685211] mirplatform: Found graphics driver: android
  [1432595003.685416] Platform Loader: Selected driver: android (version 0.13.0)
  qtmir.mir: PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0x9679764)
  qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x9676d24)
  qtmir.mir: MirShell::MirShell
  [1432595003.883766] DisplayServer: Mir version 0.13.0
  QtCompositor::setAllWindowsExposed true
  qtmir.clipboard: D-Bus registration successful.
  Mode argument was not provided or was set to an illegal value. Using default 
value of --mode= "full-greeter"
  Cannot create window: no screens available

  With version 135 it starts fine, but not fully functional, giving this
  error:

  QOpenGLShader::compile(Fragment): 0:2(12): warning: extension 
`GL_OES_standard_derivatives' unsupported in fragment shader
  0:2(1): error: #extension directive is not allowed in the middle of a shader

  *** Problematic Fragment shader source code ***
  #extension GL_OES_standard_derivatives : enable  // Enable dFdy() on OpenGL 
ES 2.
  #define lowp
  #define mediump
  #define highp

  // Copyright © 2015 Canonical Ltd.
  //
  // This program is free software; you can redistribute it and/or modify
  // it under the terms of the GNU Lesser General Public License as published by
  // the Free Software Foundation; version 3.
  //
  // This program is distributed in the hope that it will be useful,
  // but WITHOUT ANY WARRANTY; without even the implied warranty of
  // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  // GNU Lesser General Public License for more details.
  //
  // You should have received a copy of the GNU Lesser General Public License
  // along with this program.  If not, see .
  //
  // Author: Loïc Molinari 

  // Static flow control (branching on a uniform value) is fast on most GPUs 
(including ultra-low
  // power ones) because it allows to use the same shader execution path for an 
entire draw call. We
  // rely on that technique here (also known as "uber-shader" solution) to 
avoid the complexity of
  // dealing with a multiple shaders solution.
  // FIXME(loicm) Validate GPU behavior with regards to static flow control.

  uniform sampler2D shapeTexture;
  uniform sampler2D sourceTexture;
  uniform lowp vec2 dfdtFactors;
  uniform lowp vec2 opacityFactors;
  uniform lowp float sourceOpacity;
  uniform lowp float distanceAA;
  uniform bool textured;
  uniform mediump int aspect;

  

[Touch-packages] [Bug 1487111] Re: camera app unresponsive if trusted prompt left for some time

[Bill Filler]

Note, we've added a workaround in qtubuntu-camera (in silo 40) to make
this problem better (no hang) but does not fix it completely.

The following will occur:

1) try to record a video
2) don't press the trust prompt
3) let your phone go to sleep
4) wake it up and open camera
5) press on trust prompt (either decision)
6) now you'll have to press record button again as we detected the timeout and 
did not record the video
7) the videos after this will have no audio until you reboot regardless of 
prompt choice or settings change, as pulse is in a messed up state

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

Title:
  camera app unresponsive if trusted prompt left for some time

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

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select "accept"
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

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

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

[Touch-packages] [Bug 1482608] Re: ssh-add fails to add ed25519 keys

[TJ]

** Changed in: openssh (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  ssh-add fails to add ed25519 keys

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  $ ssh-add
  Identity added: /home/user/.ssh/id_rsa (/home/user/.ssh/id_rsa)
  Error reading response length from authentication socket.
  Could not add identity: /home/user/.ssh/id_ed25519

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.6p1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  7 14:11:29 2015
  InstallationDate: Installed on 2014-05-16 (448 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.6p1-2ubuntu2
  SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ssh.moduli: [modified]
  modified.conffile..etc.ssh.ssh.config: [modified]
  mtime.conffile..etc.ssh.moduli: 2015-01-07T04:30:12.433235
  mtime.conffile..etc.ssh.ssh.config: 2015-02-17T14:04:27.623708

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

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

[Touch-packages] [Bug 1487111] Re: camera app unresponsive if trusted prompt left for some time

[Bill Filler]

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

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
Milestone: None => ww34-2015

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

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

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

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => High

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

Title:
  camera app unresponsive if trusted prompt left for some time

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

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select "accept"
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

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

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

[Touch-packages] [Bug 1482608] Re: ssh-add fails to add ed25519 keys

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: openssh (Ubuntu)
   Status: New => Confirmed

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

Title:
  ssh-add fails to add ed25519 keys

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  $ ssh-add
  Identity added: /home/user/.ssh/id_rsa (/home/user/.ssh/id_rsa)
  Error reading response length from authentication socket.
  Could not add identity: /home/user/.ssh/id_ed25519

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.6p1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  7 14:11:29 2015
  InstallationDate: Installed on 2014-05-16 (448 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.6p1-2ubuntu2
  SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ssh.moduli: [modified]
  modified.conffile..etc.ssh.ssh.config: [modified]
  mtime.conffile..etc.ssh.moduli: 2015-01-07T04:30:12.433235
  mtime.conffile..etc.ssh.ssh.config: 2015-02-17T14:04:27.623708

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

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

[Touch-packages] [Bug 1487131] Re: Camera/mic trust: mic denial in camera-app freezes camera

[Jim Hodapp]

** Branch unlinked: lp:~fboucault/qtubuntu-camera/trust_fixes

** Branch linked: lp:~phablet-team/qtubuntu-camera/fix-trust-prompt-bugs

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

Title:
  Camera/mic trust: mic denial in camera-app freezes camera

Status in camera-app:
  In Progress
Status in Canonical System Image:
  New
Status in QtMir:
  Invalid
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  Similar, related to lp:1487126 , recording separately for the sake of
  thoroughness :) :

  TEST CASE
  1. Open camera, camera trust prompt appears
  2. Grant camera permission
  3. Switch to video
  4. Press record button, mic trust prompt appears from "qtubuntu-camera"
  5. *Deny* mic permission
  EXPECTED
  Returned to live preview
  ACTUAL
  Preview freezes

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

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

[Touch-packages] [Bug 1487159] Re: revoking mic permission in system-settings, camera appears to record but video is unplayable

[Jim Hodapp]

** Branch unlinked: lp:~fboucault/qtubuntu-camera/trust_fixes

** Branch linked: lp:~phablet-team/qtubuntu-camera/fix-trust-prompt-bugs

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

Title:
  revoking mic permission in system-settings, camera appears to record
  but video is unplayable

Status in Canonical System Image:
  New
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  with silo 16 on arale

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

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

[Touch-packages] [Bug 1487126] Re: Camera/mic trust: initial video corrupt

[Jim Hodapp]

** Branch unlinked: lp:~fboucault/qtubuntu-camera/trust_fixes

** Branch linked: lp:~phablet-team/qtubuntu-camera/fix-trust-prompt-bugs

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

Title:
  Camera/mic trust: initial video corrupt

Status in Canonical System Image:
  Confirmed
Status in QtMir:
  Incomplete
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  After granting camera and mic permission, able to record a video but
  the video is unplayable in media-player, media-player has to be
  killed.

  TEST CASE
  1. Open camera, camera trust prompt appears
  2. Grant camera permission
  3. Switch to video
  4. Press record button, mic trust prompt appears
  5. Grant mic permission
  6. Record video, press stop
  7. Swipe to photo roll, see video (preview being generated)
  8. Press play to watch video
  9. Media player opens
  EXPECTED
  Video plays
  ACTUAL
  Black screen

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

-- 
Mailing list: https://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 1458694] Re: [vivid-overlay] unity8 fails to start on the emulator

[Ricardo Salveti]

On Fri, Aug 21, 2015 at 6:52 AM, Timo Jyrinki
 wrote:
> As per QA report:
> "Needs a fix in unity8 so we can get past edges demo and confirm there are no 
> further issues with the silo before landing."

Sorry, but why do we need to disable the edge demo? It's still useful
during the first boot. If needed we could extend the flashing tool to
offer an option for that.

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

Title:
  [vivid-overlay] unity8 fails to start on the emulator

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Committed

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 140
  device name: generic_x86
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-05-25 12:02:10
  version version: 140
  version ubuntu: 20150525
  version device: 20150210
  version custom: 20150525

  When starting unity8 (this started at image 136, probably when mir
  0.13 landed):

  phablet@ubuntu-phablet:~$ cat ./.cache/upstart/unity8.log
  ()
  [1432595001.896139] mirplatform: Found graphics driver: dummy
  [1432595001.898447] mirplatform: Found graphics driver: android
  qtmir.mir: MirServer created
  [1432595003.675225] Server: Starting
  [1432595003.679331] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/server-platform
  [1432595003.679501] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
  [1432595003.680673] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
  [1432595003.681107]  Loader: Failed to load module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error 
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined 
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
  [1432595003.684868] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
  [1432595003.685014] mirplatform: Found graphics driver: dummy
  [1432595003.685211] mirplatform: Found graphics driver: android
  [1432595003.685416] Platform Loader: Selected driver: android (version 0.13.0)
  qtmir.mir: PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0x9679764)
  qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x9676d24)
  qtmir.mir: MirShell::MirShell
  [1432595003.883766] DisplayServer: Mir version 0.13.0
  QtCompositor::setAllWindowsExposed true
  qtmir.clipboard: D-Bus registration successful.
  Mode argument was not provided or was set to an illegal value. Using default 
value of --mode= "full-greeter"
  Cannot create window: no screens available

  With version 135 it starts fine, but not fully functional, giving this
  error:

  QOpenGLShader::compile(Fragment): 0:2(12): warning: extension 
`GL_OES_standard_derivatives' unsupported in fragment shader
  0:2(1): error: #extension directive is not allowed in the middle of a shader

  *** Problematic Fragment shader source code ***
  #extension GL_OES_standard_derivatives : enable  // Enable dFdy() on OpenGL 
ES 2.
  #define lowp
  #define mediump
  #define highp

  // Copyright © 2015 Canonical Ltd.
  //
  // This program is free software; you can redistribute it and/or modify
  // it under the terms of the GNU Lesser General Public License as published by
  // the Free Software Foundation; version 3.
  //
  // This program is distributed in the hope that it will be useful,
  // but WITHOUT ANY WARRANTY; without even the implied warranty of
  // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  // GNU Lesser General Public License for more details.
  //
  // You should have received a copy of the GNU Lesser General Public License
  // along with this program.  If not, see .
  //
  // Author: Loïc Molinari 

  // Static flow control (branching on a uniform value) is fast on most GPUs 
(including ultra-low
  // power ones) because it allows to use the same shader execution path for an 
entire draw call. We
  // rely on that technique here (also known as "uber-shader" solution) to 
avoid the complexity of
  // dealing with a multiple shaders solution.
  // FIXME(loicm) Validate GPU behavior with regards to static flow control.

  uniform sampler2D shapeTexture;
  uniform sampler2D sourceTexture;
  uniform lowp vec2 dfdtFactors;
  uniform lowp vec2 opacityFactors;
  uniform lowp float sourceOpacity;
  uniform lowp float distanceAA;
  uniform bool textured;
  uniform mediump int aspect;

  varying mediump vec2 shapeCoord;
  varying mediump vec4 sourceCoord;
  varying lowp vec4 backgroundColor;

  const mediump int FLAT  = 0x08;  // 1 << 3
  const mediump int INSET = 0x10;  // 1 << 4

  void main(void)
  {
  lowp vec4 shapeData = texture2D(shapeTexture, shap

[Touch-packages] [Bug 1487111] Re: camera app unresponsive if trusted prompt left for some time

[kevin gunn]

is there a power reason for making a choice for the user ?

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

Title:
  camera app unresponsive if trusted prompt left for some time

Status in camera-app package in Ubuntu:
  New

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select "accept"
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

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

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

[Touch-packages] [Bug 1487589] Re: package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in dbus package in Ubuntu:
  New

Bug description:
  No more info.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: dbus 1.9.20-1ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Thu Aug 13 16:08:47 2015
  DuplicateSignature: package:dbus:1.9.20-1ubuntu2:dependency problems - 
leaving triggers unprocessed
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2014-05-26 (452 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu6
  SourcePackage: dbus
  Title: package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to wily on 2015-08-08 (13 days ago)

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

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

[Touch-packages] [Bug 1487589] [NEW] package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Yotam Benshalom]

Public bug reported:

No more info.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: dbus 1.9.20-1ubuntu2
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
Date: Thu Aug 13 16:08:47 2015
DuplicateSignature: package:dbus:1.9.20-1ubuntu2:dependency problems - leaving 
triggers unprocessed
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2014-05-26 (452 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu1
 apt  1.0.9.10ubuntu6
SourcePackage: dbus
Title: package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to wily on 2015-08-08 (13 days ago)

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


** Tags: amd64 apport-package wily

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

Title:
  package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in dbus package in Ubuntu:
  New

Bug description:
  No more info.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: dbus 1.9.20-1ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Thu Aug 13 16:08:47 2015
  DuplicateSignature: package:dbus:1.9.20-1ubuntu2:dependency problems - 
leaving triggers unprocessed
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2014-05-26 (452 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu6
  SourcePackage: dbus
  Title: package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to wily on 2015-08-08 (13 days ago)

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

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

[Touch-packages] [Bug 1487588] [NEW] Xorg freeze

[eezacque]

Public bug reported:

Every month or so, accessing the System Settings->Network panel, or
clicking my network in the wifi menu, freezes Ubuntu. The only way out
is a hard reset

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
Uname: Linux 4.2.0-040200rc6-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Aug 21 21:42:49 2015
DistUpgraded: 2015-05-05 01:44:42,463 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 3.19.0-26-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.1.0-040100-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.2.0-040200rc6-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Very infrequently
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
InstallationDate: Installed on 2014-10-24 (300 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-040200rc6-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to vivid on 2015-05-04 (108 days ago)
dmi.bios.date: 06/24/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-PRO(Wi-Fi ac)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd06/24/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Fri Aug 21 18:52:54 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4121 
 vendor WAC
xserver.version: 2:1.17.1-0ubuntu3

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


** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu vivid

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Every month or so, accessing the System Settings->Network panel, or
  clicking my network in the wifi menu, freezes Ubuntu. The only way out
  is a hard reset

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  Uname: Linux 4.2.0-040200rc6-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Aug 21 21:42:49 2015
  DistUpgraded: 2015-05-05 01:44:42,463 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-26-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.1.0-040100-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.2.0-040200rc6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
  InstallationDate: Inst

[Touch-packages] [Bug 1483558] Re: Content-Hub crash with an invalid app-id after transfer and doesn't clean up temp files

[Ken VanDine]

Is it the content-hub-service that crashes?  Or the app?  If the service
doesn't crash, the cached file should still get cleaned up with the
service exits.

The problem with APP_ID=fake is we need the APP_ID to be parse-able by
libubuntu-app-launch, plus it needs to be unique.  I wish setting
applicationName in the MainView would be enough to set the runtime
APP_ID, but it isn't.

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

Title:
  Content-Hub crash with an invalid app-id after transfer and doesn't
  clean up temp files

Status in content-hub package in Ubuntu:
  New

Bug description:
  The idea would to have at least a fake APP_ID for developping and
  testing/iterating on desktop. The import functionality itself works,
  but the crash doesn't give a good developer experience.

  Maybe we can decide on having an APP_ID=fake in the developer default
  template, and then, content-hub let that ID pass even if not
  installed?

  Note that one of the side effect of this crash after transfer is that
  the tmeporary files under HubIncoming aren't cleaned up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1483558/+subscriptions

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

[Touch-packages] [Bug 1487111] Re: camera app unresponsive if trusted prompt left for some time

[Bill Filler]

The desired behavior should be

1) pulse should not timeout after 30 seconds

or
2) if we keep the 30 second timeout, the trust-prompt should be removed after 
that period with the DENY choice selected

Currently, the trust-prompt stays on the screen even though silently
access has been denied.

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

Title:
  camera app unresponsive if trusted prompt left for some time

Status in camera-app package in Ubuntu:
  New

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select "accept"
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

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

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

[Touch-packages] [Bug 1487111] Re: camera app unresponsive if trusted prompt left for some time

[Florian Boucault]

Not being a Pulseaudio expert I am not sure it is relevant but I see the
following define in its code:

 #define DEFAULT_TIMEOUT (30)

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

Title:
  camera app unresponsive if trusted prompt left for some time

Status in camera-app package in Ubuntu:
  New

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select "accept"
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

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

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

[Touch-packages] [Bug 1467473] Re: Nexus 7 with shellRotation sometimes ends up with broken lockscreen

[Josh Arenson]

** Branch linked: lp:~dandrader/unity8/fixOrientedShellTests

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Nexus 7 with shellRotation sometimes ends up with broken lockscreen

Status in unity8 package in Ubuntu:
  Fix Committed

Bug description:
  Since shellRotation the Nexus7 sometimes ends up with a lockscreen
  state where it can't be unlocked because the PinLockScreen is squeezed
  into landscape format. To reproduce open some apps that allow rotating
  and play around with rotating and locking/unlocking.

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

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

[Touch-packages] [Bug 1360307] Re: Logging in to the desktop session brings up the lock screen

[Josh Arenson]

*** This bug is a duplicate of bug 1324602 ***
https://bugs.launchpad.net/bugs/1324602

** This bug has been marked a duplicate of bug 1324602
   [split] unity8-greeter doesn't run on desktop configurations

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

Title:
  Logging in to the desktop session brings up the lock screen

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  When logging in to the desktop session from LightDM, the lock screen
  is then brought up and requires typing the password again to unlock.
  The desired behavior should be to just go to the Dash as having to
  type another password is redundant.

  This occurs with version 8.00+14.10.20140822-0ubuntu1.

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

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

[Touch-packages] [Bug 1324602] Re: [split] unity8-greeter doesn't run on desktop configurations

[Josh Arenson]

Also have a ppa that will allow easily testing this on desktop, but its
not working quite right yet.

** Branch linked: lp:~josharenson/unity8/slim_greeter_real_lightdm

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

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

Title:
  [split] unity8-greeter doesn't run on desktop configurations

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Installing unity8-greeter, from the split greeter silo, on an
  unity8-mir desktop configuration leads to a non working lightdm

  * installing unity8-greeter leads to an empty screen with a cursor
  (looking like a Mir one), which runs for some seconds and do what
  looks like a respawn

  -> editing the unity8-greeter-wrapper to set the qpa to mirclient
  corrected the respawn issue but giving an empty screen still

  * install ubuntu-touch-session gives a working greeter but unlocking
  doesn't start the session

  * GreeterShell.qml has an issue and does unlock only in when autologin
  is enabled, editing that makes unlock dismiss the greeter

  but the session still doesn't start, unlocking the greeter gives a
  screen looking like the phone one ... that needs extra debugging

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Alberto Salvia Novella]

** Changed in: telephony-service (Ubuntu RTM)
   Status: Confirmed => Triaged

** Changed in: telephony-service (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: ofono (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Triaged

-- 
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:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in telephony-service package in Ubuntu:
  Triaged
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

[Touch-packages] [Bug 1478637] Re: X-Ubuntu-Supported-Orientations=landscape causes app to be upside down on devices with nativeOrientation=landscape

[Josh Arenson]

** Branch unlinked: lp:~josharenson/unity8/fix_upside_down_apps

** Branch linked: lp:~josharenson/unity8/new_fix_upsidedown

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

Title:
  X-Ubuntu-Supported-Orientations=landscape causes app to be upside down
  on devices with nativeOrientation=landscape

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  As the title says. There is probably a +/- issue with Landscape vs
  InvertedLandscape.

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

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

[Touch-packages] [Bug 1458694] Re: [vivid-overlay] unity8 fails to start on the emulator

[kevin gunn]

** Changed in: unity8 (Ubuntu)
   Status: New => Fix Committed

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

** Branch linked: lp:~mterry/unity8/fix-emulator-tutorial

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

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

Title:
  [vivid-overlay] unity8 fails to start on the emulator

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Committed

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 140
  device name: generic_x86
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-05-25 12:02:10
  version version: 140
  version ubuntu: 20150525
  version device: 20150210
  version custom: 20150525

  When starting unity8 (this started at image 136, probably when mir
  0.13 landed):

  phablet@ubuntu-phablet:~$ cat ./.cache/upstart/unity8.log
  ()
  [1432595001.896139] mirplatform: Found graphics driver: dummy
  [1432595001.898447] mirplatform: Found graphics driver: android
  qtmir.mir: MirServer created
  [1432595003.675225] Server: Starting
  [1432595003.679331] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/server-platform
  [1432595003.679501] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
  [1432595003.680673] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
  [1432595003.681107]  Loader: Failed to load module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error 
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined 
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
  [1432595003.684868] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
  [1432595003.685014] mirplatform: Found graphics driver: dummy
  [1432595003.685211] mirplatform: Found graphics driver: android
  [1432595003.685416] Platform Loader: Selected driver: android (version 0.13.0)
  qtmir.mir: PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0x9679764)
  qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x9676d24)
  qtmir.mir: MirShell::MirShell
  [1432595003.883766] DisplayServer: Mir version 0.13.0
  QtCompositor::setAllWindowsExposed true
  qtmir.clipboard: D-Bus registration successful.
  Mode argument was not provided or was set to an illegal value. Using default 
value of --mode= "full-greeter"
  Cannot create window: no screens available

  With version 135 it starts fine, but not fully functional, giving this
  error:

  QOpenGLShader::compile(Fragment): 0:2(12): warning: extension 
`GL_OES_standard_derivatives' unsupported in fragment shader
  0:2(1): error: #extension directive is not allowed in the middle of a shader

  *** Problematic Fragment shader source code ***
  #extension GL_OES_standard_derivatives : enable  // Enable dFdy() on OpenGL 
ES 2.
  #define lowp
  #define mediump
  #define highp

  // Copyright © 2015 Canonical Ltd.
  //
  // This program is free software; you can redistribute it and/or modify
  // it under the terms of the GNU Lesser General Public License as published by
  // the Free Software Foundation; version 3.
  //
  // This program is distributed in the hope that it will be useful,
  // but WITHOUT ANY WARRANTY; without even the implied warranty of
  // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  // GNU Lesser General Public License for more details.
  //
  // You should have received a copy of the GNU Lesser General Public License
  // along with this program.  If not, see .
  //
  // Author: Loïc Molinari 

  // Static flow control (branching on a uniform value) is fast on most GPUs 
(including ultra-low
  // power ones) because it allows to use the same shader execution path for an 
entire draw call. We
  // rely on that technique here (also known as "uber-shader" solution) to 
avoid the complexity of
  // dealing with a multiple shaders solution.
  // FIXME(loicm) Validate GPU behavior with regards to static flow control.

  uniform sampler2D shapeTexture;
  uniform sampler2D sourceTexture;
  uniform lowp vec2 dfdtFactors;
  uniform lowp vec2 opacityFactors;
  uniform lowp float sourceOpacity;
  uniform lowp float distanceAA;
  uniform bool textured;
  uniform mediump int aspect;

  varying mediump vec2 shapeCoord;
  varying mediump vec4 sourceCoord;
  varying lowp vec4 backgroundColor;

  const mediump int FLAT  = 0x08;  // 1 << 3
  const mediump int INSET = 0x10;  // 1 << 4

  void main(void)
  {
  lowp vec4 shapeData = texture2D(shapeTexture, shapeCoord);
  lowp vec4 color = backgroundColor;

  // FIXME(l

[Touch-packages] [Bug 1483752] Re: Trusted prompts make application inactive: Qt.application.active == false

[kevin gunn]

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

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

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

Title:
  Trusted prompts make application inactive: Qt.application.active ==
  false

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  When a trusted prompt shows up the application becomes "inactive",
  concretely QML applications receive a signal that
  Qt.application.active has changed to 'false'.

  This is will be an issue for example in the case of the camera-app
  trying to start recording a video, a pulseaudio trusted prompt will
  show up to ask for permission to record from the microphone but the
  camera-app believing that it's become inactive will immediately stop
  the recording.

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

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

[Touch-packages] [Bug 1486492] Re: Keyboard appears during call and does not disappear unless reboot

[kevin gunn]

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => High

** Changed in: dialer-app (Ubuntu)
   Importance: Undecided => High

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

Title:
  Keyboard appears during call and does not disappear unless reboot

Status in dialer-app package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  OS Ubutnu 15.04(r3) on MX4

  0.1+15.04.20150615-0ubuntu1

  Only occurs if the phone is locked. When answering the call via
  slider, once answered the Keyboard appears, and then does not
  disappear even when calls ended. Calls can also only end by remote end
  hanging up, due to keyboard obscuring the hang up button.

  Unfortunately keyboard is non responsive and phone has to be rebooted
  for any continued use. Sometimes keyboard half appears but effect is
  still the same.

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

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

[Touch-packages] [Bug 1487111] Re: camera app unresponsive if trusted prompt left for some time

[Florian Boucault]

In the case of the microphone trust prompt, it could be explained by the
fact that Pulseaudio times out and returns from pa_simple_new() after 30
seconds. Then the video recording starts with no access to the
microphone while the prompt is still shown.

In the logs of the camera app we can see:
Failed to open a PulseAudio channel to read the microphone:  Timeout
Failed to setup PulseAudio microphone recording stream

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

Title:
  camera app unresponsive if trusted prompt left for some time

Status in camera-app package in Ubuntu:
  New

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select "accept"
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

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

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

[Touch-packages] [Bug 1483127] Re: Proximity does not turn screen on during a call

[kevin gunn]

** Changed in: unity-system-compositor (Ubuntu)
 Assignee: (unassigned) => Alberto Aguirre (albaguirre)

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

Title:
  Proximity does not turn screen on during a call

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  This has regressed a week or two ago. It's not reliably reproducible,
  but bites me almost every time I want to end a call. It might be
  incoming calls only, or maybe only after a minute.

  Steps:
  * go on a call
  * cover the proximity sensor
  * uncover the proximity sensor

  Expected:
  * screen goes off/on as you cover/uncover the sensor

  Current:
  * screen goes off but not back on

  $ system-image-cli -i
  current build number: 90
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-08 21:08:55
  version version: 90
  version ubuntu: 20150807.1
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

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

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

[Touch-packages] [Bug 1485333] Re: [REGRESSION] cannot switch to a given window after showing desktop

[Alberto Salvia Novella]

** Changed in: unity (Ubuntu)
   Importance: Undecided => Low

** Changed in: unity (Ubuntu)
   Importance: Low => Medium

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

Title:
  [REGRESSION] cannot switch to a given window after showing desktop

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This is a regression which has appeared either in 14.10 or 15.04, as
  it didn't exist in 14.04.

  This is 100% systematically reproducible for me.

  1. have a few windows of the same program open, for example, three terminal 
windows
  2. make sure all of them are visible and one is focused
  3. hit Ctrl+Super+D so that all windows are hidden and the desktop is shown
  4. click on the terminal icon (or the icon of whatever example program we are 
testing the issue against) on the Launcher
  => one of the windows becomes visible, foreground and focused, as expected. 
But suppose you want to switch to one of the other ones
  5. click on the launcher icon again
  6. pick any window other than the one that was focused in the previous step

  Expected result: that window should be brought to front and given
  focus

  Observed result:
  the window does the animation as if it was going to be brought to front, but 
then vanishes, and is not visible at all
  the previous window is still on the foreground but no longer focused.
  No visible window is focused at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Aug 16 17:04:37 2015
  InstallationDate: Installed on 2013-10-11 (673 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-08-15 (0 days ago)

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

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

[Touch-packages] [Bug 1485333] Re: [REGRESSION] cannot switch to a given window after showing desktop

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity (Ubuntu)
   Status: New => Confirmed

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

Title:
  [REGRESSION] cannot switch to a given window after showing desktop

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This is a regression which has appeared either in 14.10 or 15.04, as
  it didn't exist in 14.04.

  This is 100% systematically reproducible for me.

  1. have a few windows of the same program open, for example, three terminal 
windows
  2. make sure all of them are visible and one is focused
  3. hit Ctrl+Super+D so that all windows are hidden and the desktop is shown
  4. click on the terminal icon (or the icon of whatever example program we are 
testing the issue against) on the Launcher
  => one of the windows becomes visible, foreground and focused, as expected. 
But suppose you want to switch to one of the other ones
  5. click on the launcher icon again
  6. pick any window other than the one that was focused in the previous step

  Expected result: that window should be brought to front and given
  focus

  Observed result:
  the window does the animation as if it was going to be brought to front, but 
then vanishes, and is not visible at all
  the previous window is still on the foreground but no longer focused.
  No visible window is focused at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Aug 16 17:04:37 2015
  InstallationDate: Installed on 2013-10-11 (673 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-08-15 (0 days ago)

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

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

[Touch-packages] [Bug 1447423] Re: package initramfs-tools 0.103ubuntu15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Alberto Salvia Novella]

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

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

Title:
  package initramfs-tools 0.103ubuntu15 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Happened during today's system update

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: initramfs-tools 0.103ubuntu15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu Apr 23 10:19:48 2015
  DuplicateSignature: package:initramfs-tools:0.103ubuntu15:subprocess 
installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2012-11-25 (878 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.103ubuntu15 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to vivid on 2015-03-14 (39 days ago)

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

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

[Touch-packages] [Bug 1448552] Re: package initramfs-tools 0.103ubuntu15 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio

[Alberto Salvia Novella]

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

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

Title:
  package initramfs-tools 0.103ubuntu15 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  I was selecting an additional graphics driver.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: initramfs-tools 0.103ubuntu15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Sat Apr 25 16:43:06 2015
  DuplicateSignature: package:initramfs-tools:0.103ubuntu15:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.103ubuntu15 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago)

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

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

[Touch-packages] [Bug 1400717] Re: package initramfs-tools 0.103ubuntu8 failed to install/upgrade: зацикливание триггеров, отмена работы

[Alberto Salvia Novella]

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

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

Title:
  package initramfs-tools 0.103ubuntu8 failed to install/upgrade:
  зацикливание триггеров, отмена работы

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
   lsb_release -rd   
  Description:Ubuntu Vivid Vervet (development branch)
  Release:15.04

  I have not noticed any problems; this is an automatic bug report after
  upgrading to the latest brunch.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: initramfs-tools 0.103ubuntu8
  ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Tue Dec  9 20:36:29 2014
  ErrorMessage: зацикливание триггеров, отмена работы
  InstallationDate: Installed on 2014-05-29 (193 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.103ubuntu8 failed to install/upgrade: 
зацикливание триггеров, отмена работы
  UpgradeStatus: Upgraded to vivid on 2014-12-01 (7 days ago)

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

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

[Touch-packages] [Bug 1483127] Re: Proximity does not turn screen on during a call

[Bill Filler]

Simple steps to reproduce:

1) make a phone call
2) put phone to ear and leave it there for 1 minute or longer
3) move phone away from ear

Expected results:
screen should turn on

Actual results:
screen does not turn on

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

Title:
  Proximity does not turn screen on during a call

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  This has regressed a week or two ago. It's not reliably reproducible,
  but bites me almost every time I want to end a call. It might be
  incoming calls only, or maybe only after a minute.

  Steps:
  * go on a call
  * cover the proximity sensor
  * uncover the proximity sensor

  Expected:
  * screen goes off/on as you cover/uncover the sensor

  Current:
  * screen goes off but not back on

  $ system-image-cli -i
  current build number: 90
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-08 21:08:55
  version version: 90
  version ubuntu: 20150807.1
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

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

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

[Touch-packages] [Bug 1485558] Re: NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10, nm-applet fills with irrelevant entries.

[Alberto Salvia Novella]

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

Title:
  NetworkManager breaks vboxnet* connections since 15.04, worked in
  14.04 and 14.10, nm-applet fills with irrelevant entries.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  On an Asus laptop running a freshly installed Ubuntu 15.04 64-bit, nm-
  applet shows that NetworkManager wants to manage vboxnet0 and
  vboxnet1. These are created by virtualbox which runs some guest OS
  inside a VM. On previous Ubuntu releases, network-manager did not try
  to manage them and there was no problem.

  # Observed behavior

  * nm-applet shows spinning animation for a long time, while it is not 
relevant. Clicking on "disconnect" in the menu unconfigures the interface which 
breaks it.
  * after suspend-resume of the host, vboxnet* lose their correct 
configurations. vboxnet0 (a host-only interface where virtualbox runs a private 
dhcp server) gets a different IP address. Looks like 
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1460750 but does not 
feel like a bug in virtualbox.

  # Expected behavior

  * Just like in 14.04 and 14.10, these interfaces are just ignored by
  network-manager and they just work.

  # Additional information

  * After reading http://superuser.com/questions/9720/disabling-
  networkmanager-for-a-specific-interface tried to add these lines to
  /etc/network/interfaces. Even after restarting network-manager, it has
  no effect.

  iface vboxnet0 inet manual
  iface vboxnet1 inet manual

  So, reverted the change.

  * Tried from https://blogs.gnome.org/dcbw/2015/02/16/networkmanager-
  for-administrators-part-1/ to add in /etc/NetworkManager/conf.d/ a
  file 50-virtualbox.conf containing the following lines. Even after
  restarting network-manager, it is ignored.

  [keyfile]
  unmanaged-devices=vboxnet0,vboxnet1

  * This is not eactly like https://www.virtualbox.org/ticket/13873, I'm not 
using Vagrant.
  * Booting to 14.04 or 14.10 (that have been kept intact on the same machine) 
things just work as expected.
  * /usr/share/doc/network-manager/NEWS.gz states that "'veth' interfaces are 
now unmanaged by default to cooperate better with external tools". Should 
vboxnet* be treated the same ?
  * This seems on the topic but unclear to me: 
https://bugzilla.gnome.org/show_bug.cgi?id=731014

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  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
  Date: Mon Aug 17 13:13:04 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-08-15 (1 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  IpRoute:
   default via 192.168.47.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev vboxnet0  scope link  metric 1000 
   192.168.47.0/24 dev wlan0  proto kernel  scope link  src 192.168.47.6 
   192.168.56.0/24 dev vboxnet0  proto kernel  scope link  src 192.168.56.102
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1487569] Re: a lot of packages need to be removed when execute apt-get dist-upgrade

[Khairul Aizat Kamarudzzaman]

$ uname -a; cat /etc/issue
Linux macbuntu 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:22:42 UTC 2015 i686 
i686 i686 GNU/Linux
Ubuntu Wily Werewolf (development branch) \n \l

** Summary changed:

-  a lot of files to be removed when execute apt-get dist-upgrade
+ a lot of packages need to be removed when execute apt-get dist-upgrade

** Summary changed:

- a lot of packages need to be removed when execute apt-get dist-upgrade
+ a lot of packages need to be remove when execute apt-get dist-upgrade

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

Title:
  a lot of packages need to be remove when execute apt-get dist-upgrade

Status in apt package in Ubuntu:
  New

Bug description:
  as spoken with cjwatson in #ubuntu-devel , please find the debug
  output as below:

  http://paste.ubuntu.com/12142592/
  http://paste.ubuntu.com/12142634/

  tarball for  /var/lib/apt/, /var/cache/apt/, and /var/lib/dpkg/ as
  attached.

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

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

[Touch-packages] [Bug 1483127] Re: Proximity does not turn screen on during a call

[Tiago Salem Herrmann]

I reverted unity-system-compositor to commit 236 and the bug is gone.
Not sure what commit actually introduced the issue though.

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

Title:
  Proximity does not turn screen on during a call

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  This has regressed a week or two ago. It's not reliably reproducible,
  but bites me almost every time I want to end a call. It might be
  incoming calls only, or maybe only after a minute.

  Steps:
  * go on a call
  * cover the proximity sensor
  * uncover the proximity sensor

  Expected:
  * screen goes off/on as you cover/uncover the sensor

  Current:
  * screen goes off but not back on

  $ system-image-cli -i
  current build number: 90
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-08 21:08:55
  version version: 90
  version ubuntu: 20150807.1
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

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

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

[Touch-packages] [Bug 1487131] Re: Camera/mic trust: mic denial in camera-app freezes camera

[Launchpad Bug Tracker]

** Branch linked: lp:~fboucault/qtubuntu-camera/trust_fixes

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

Title:
  Camera/mic trust: mic denial in camera-app freezes camera

Status in camera-app:
  In Progress
Status in Canonical System Image:
  New
Status in QtMir:
  Invalid
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  Similar, related to lp:1487126 , recording separately for the sake of
  thoroughness :) :

  TEST CASE
  1. Open camera, camera trust prompt appears
  2. Grant camera permission
  3. Switch to video
  4. Press record button, mic trust prompt appears from "qtubuntu-camera"
  5. *Deny* mic permission
  EXPECTED
  Returned to live preview
  ACTUAL
  Preview freezes

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

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

[Touch-packages] [Bug 1480122] Re: [systemd 223-1] dpkg: warning: --compare-versions used with obsolete relation operator '>'

[Alberto Salvia Novella]

** Changed in: dpkg (Ubuntu)
   Importance: Undecided => High

** Package changed: dpkg (Ubuntu) => systemd (Ubuntu)

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

** Changed in: hundredpapercuts
   Status: New => Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided => High

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

Title:
  [systemd 223-1] dpkg: warning: --compare-versions used with obsolete
  relation operator '>'

Status in One Hundred Papercuts:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is what i've seen while upgrading to systemd 223-1ubuntu1:

  Processing triggers for systemd (222-2ubuntu1) ...
  Processing triggers for initramfs-tools (0.103ubuntu16) ...
  dpkg: warning: --compare-versions used with obsolete relation operator '>'

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: dpkg 1.18.1ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu5
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Fri Jul 31 09:03:58 2015
  SourcePackage: dpkg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1483127] Re: Proximity does not turn screen on during a call

[Bill Filler]

** Changed in: canonical-devices-system-image
Milestone: None => ww34-2015

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Kevin Gunn (kgunn)

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

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

** Also affects: unity-system-compositor (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity-system-compositor (Ubuntu)
   Importance: Undecided => Critical

** Changed in: telephony-service (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Proximity does not turn screen on during a call

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  This has regressed a week or two ago. It's not reliably reproducible,
  but bites me almost every time I want to end a call. It might be
  incoming calls only, or maybe only after a minute.

  Steps:
  * go on a call
  * cover the proximity sensor
  * uncover the proximity sensor

  Expected:
  * screen goes off/on as you cover/uncover the sensor

  Current:
  * screen goes off but not back on

  $ system-image-cli -i
  current build number: 90
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-08 21:08:55
  version version: 90
  version ubuntu: 20150807.1
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

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

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

[Touch-packages] [Bug 1487126] Re: Camera/mic trust: initial video corrupt

[Launchpad Bug Tracker]

** Branch linked: lp:~fboucault/qtubuntu-camera/trust_fixes

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

Title:
  Camera/mic trust: initial video corrupt

Status in Canonical System Image:
  Confirmed
Status in QtMir:
  Incomplete
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  After granting camera and mic permission, able to record a video but
  the video is unplayable in media-player, media-player has to be
  killed.

  TEST CASE
  1. Open camera, camera trust prompt appears
  2. Grant camera permission
  3. Switch to video
  4. Press record button, mic trust prompt appears
  5. Grant mic permission
  6. Record video, press stop
  7. Swipe to photo roll, see video (preview being generated)
  8. Press play to watch video
  9. Media player opens
  EXPECTED
  Video plays
  ACTUAL
  Black screen

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

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

[Touch-packages] [Bug 1487159] Re: revoking mic permission in system-settings, camera appears to record but video is unplayable

[Launchpad Bug Tracker]

** Branch linked: lp:~fboucault/qtubuntu-camera/trust_fixes

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

Title:
  revoking mic permission in system-settings, camera appears to record
  but video is unplayable

Status in Canonical System Image:
  New
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  with silo 16 on arale

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

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

[Touch-packages] [Bug 1487569] Re: a lot of files to be removed when execute apt-get dist-upgrade

[Khairul Aizat Kamarudzzaman]

** Attachment added: "/var/lib/apt"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1487569/+attachment/4450423/+files/var-lib-apt.tar.gz

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

Title:
   a lot of files to be removed when execute apt-get dist-upgrade

Status in apt package in Ubuntu:
  New

Bug description:
  as spoken with cjwatson in #ubuntu-devel , please find the debug
  output as below:

  http://paste.ubuntu.com/12142592/
  http://paste.ubuntu.com/12142634/

  tarball for  /var/lib/apt/, /var/cache/apt/, and /var/lib/dpkg/ as
  attached.

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

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

[Touch-packages] [Bug 1487569] [NEW] a lot of files to be removed when execute apt-get dist-upgrade

[Khairul Aizat Kamarudzzaman]

Public bug reported:

as spoken with cjwatson in #ubuntu-devel , please find the debug output
as below:

http://paste.ubuntu.com/12142592/
http://paste.ubuntu.com/12142634/

tarball for  /var/lib/apt/, /var/cache/apt/, and /var/lib/dpkg/ as
attached.

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

** Attachment added: "/var/lib/dpkg"
   
https://bugs.launchpad.net/bugs/1487569/+attachment/4450422/+files/var-lib-dpkg.tar.gz

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

Title:
   a lot of files to be removed when execute apt-get dist-upgrade

Status in apt package in Ubuntu:
  New

Bug description:
  as spoken with cjwatson in #ubuntu-devel , please find the debug
  output as below:

  http://paste.ubuntu.com/12142592/
  http://paste.ubuntu.com/12142634/

  tarball for  /var/lib/apt/, /var/cache/apt/, and /var/lib/dpkg/ as
  attached.

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

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

[Touch-packages] [Bug 1480122] [NEW] [systemd 223-1] dpkg: warning: --compare-versions used with obsolete relation operator '>'

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This is what i've seen while upgrading to systemd 223-1ubuntu1:

Processing triggers for systemd (222-2ubuntu1) ...
Processing triggers for initramfs-tools (0.103ubuntu16) ...
dpkg: warning: --compare-versions used with obsolete relation operator '>'

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: dpkg 1.18.1ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.18-0ubuntu5
Architecture: i386
CurrentDesktop: GNOME
Date: Fri Jul 31 09:03:58 2015
SourcePackage: dpkg
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: systemd (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: apport-bug i386 wily
-- 
[systemd 223-1] dpkg: warning: --compare-versions used with obsolete relation 
operator '>'
https://bugs.launchpad.net/bugs/1480122
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1487159] Re: revoking mic permission in system-settings, camera appears to record but video is unplayable

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Status: New => In Progress

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

Title:
  revoking mic permission in system-settings, camera appears to record
  but video is unplayable

Status in Canonical System Image:
  New
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  with silo 16 on arale

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

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

[Touch-packages] [Bug 1487131] Re: Camera/mic trust: mic denial in camera-app freezes camera

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Status: New => In Progress

** Changed in: camera-app
 Assignee: (unassigned) => Florian Boucault (fboucault)

** Changed in: camera-app
   Status: New => In Progress

** Changed in: camera-app
   Importance: Undecided => Critical

** Changed in: qtmir
   Status: Incomplete => Invalid

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

Title:
  Camera/mic trust: mic denial in camera-app freezes camera

Status in camera-app:
  In Progress
Status in Canonical System Image:
  New
Status in QtMir:
  Invalid
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  Similar, related to lp:1487126 , recording separately for the sake of
  thoroughness :) :

  TEST CASE
  1. Open camera, camera trust prompt appears
  2. Grant camera permission
  3. Switch to video
  4. Press record button, mic trust prompt appears from "qtubuntu-camera"
  5. *Deny* mic permission
  EXPECTED
  Returned to live preview
  ACTUAL
  Preview freezes

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

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

[Touch-packages] [Bug 1430457] Re: upgrade from 14.10 to 15.04

[Alberto Salvia Novella]

** Changed in: rsyslog (Ubuntu)
   Importance: Undecided => High

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

Title:
  upgrade from 14.10 to 15.04

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  After my upgrade with "sudo do-release-upgrade -d" I got some errors
  about configurations and missing depends

  I tried  a dpkg --configure and got this:

  sudo dpkg --configure -a
  avahi-daemon (0.6.31-4ubuntu4) wird eingerichtet ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Job for avahi-daemon.service failed. See "systemctl status 
avahi-daemon.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript avahi-daemon, action "start" failed.
  dpkg: Fehler beim Bearbeiten des Paketes avahi-daemon (--configure):
   Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 
zurück
  dpkg: Abhängigkeitsprobleme verhindern Konfiguration von avahi-utils:
   avahi-utils hängt ab von avahi-daemon; aber:
Paket avahi-daemon ist noch nicht konfiguriert.

  dpkg: Fehler beim Bearbeiten des Paketes avahi-utils (--configure):
   Abhängigkeitsprobleme - verbleibt unkonfiguriert
  rsyslog (7.4.4-1ubuntu14) wird eingerichtet ...
  Der Benutzer »syslog« ist bereits ein Mitglied der Gruppe »adm«.
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  Job for rsyslog.service failed. See "systemctl status rsyslog.service" and 
"journalctl -xe" for details.
  invoke-rc.d: initscript rsyslog, action "restart" failed.
  dpkg: Fehler beim Bearbeiten des Paketes rsyslog (--configure):
   Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 
zurück
  dpkg: Abhängigkeitsprobleme verhindern Konfiguration von ubuntu-minimal:
   ubuntu-minimal hängt ab von rsyslog; aber:
Paket rsyslog ist noch nicht konfiguriert.

  dpkg: Fehler beim Bearbeiten des Paketes ubuntu-minimal (--configure):
   Abhängigkeitsprobleme - verbleibt unkonfiguriert
  Fehler traten auf beim Bearbeiten von:
   avahi-daemon
   avahi-utils
   rsyslog
   ubuntu-minimal

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: rsyslog 7.4.4-1ubuntu14
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  Date: Tue Mar 10 18:29:17 2015
  InstallationDate: Installed on 2013-05-31 (648 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: rsyslog
  UpgradeStatus: Upgraded to vivid on 2015-03-10 (0 days ago)

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

-- 
Mailing list: https://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 1410876] Re: Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a directory - Could not destroy snapshot %s - failed to allocate a pty; Insufficent privileges

[Jason Hobbs]

This bug is hit very rarely - we deploy thousands of containers a day and
see it a few times a week. I don't have a way to reproduce it reliably
other than waiting to hit it in OIL.

On Fri, Aug 21, 2015 at 12:22 PM, Serge Hallyn <1410...@bugs.launchpad.net>
wrote:

> @jason-hobbs or @lmic,
>
> can you provide a concise recipe for reproducing this in the
> Description?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1410876
>
> Title:
>   Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a
>   directory - Could not destroy  snapshot %s - failed to allocate a pty;
>   Insufficent privileges to control  juju-trusty-lxc-template
>
> Status in juju-core:
>   Invalid
> Status in lxc:
>   Fix Released
> Status in lxc package in Ubuntu:
>   Fix Released
> Status in lxc source package in Trusty:
>   Fix Committed
>
> Bug description:
>   This is for:
>
>   ++ export OPENSTACK_RELEASE=juno
>   ++ OPENSTACK_RELEASE=juno
>   ++ export COMPUTE=nova-lxc
>   ++ COMPUTE=nova-lxc
>   ++ export UBUNTU_RELEASE=trusty
>   ++ UBUNTU_RELEASE=trusty
>
>   Tool version is 1.20.14:
>   Launching instance
>   WARNING picked arbitrary tools &{1.20.14-precise-amd64
> https://streams.canonical.com/juju/tools/releases/juju-1.20.14-precise-amd64.tgz
> 932640702b5d9f08a312118a4afe330444308f92b7de350de9e547719f084bd9 8130412}
>- /MAAS/api/1.0/nodes/node-5f9c14e6-ae98-11e3-b194-00163efc5068/
>
>   and agent-version on node says 1.20.13.
>
>   Juju-status.yaml:
>
>   '5':
>   agent-state: started
>   agent-version: 1.20.13
>   containers:
> 5/lxc/0:
>   agent-state-info: 'error executing "lxc-clone": lxc_container:
> utils.c: mkdir_p:
> 220 Not a directory - failed to create directory
> ''/run/lock/lxc//var/lib/lxc/juju-trusty-lxc-template/snaps'';
> lxc_container: lxccontainer.c: do_snapshot_destroy: 3272 Could
> not destroy
> snapshot %s - failed to allocate a pty; Insufficent privileges
> to control
> juju-trusty-lxc-template'
>   instance-id: pending
>   series: trusty
> 5/lxc/1:
>   agent-state-info: cannot clone a running container
>   instance-id: pending
>   series: trusty
>   dns-name: apsaras.oil
>   hardware: arch=amd64 cpu-cores=4 mem=32768M
> tags=hw-ok,oil-slave-1,hardware-dell-poweredge-R210
>   instance-id:
> /MAAS/api/1.0/nodes/node-5f9c14e6-ae98-11e3-b194-00163efc5068/
>   series: trusty
>
>   and from log:
>
>   machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
> apiserver.go:150 <- [7C] unit-swift-storage-1
> {"RequestId":42,"Type":"Uniter","Request":"CharmURL","Params":{"Entities":[{"Tag":"service-swift-storage"}]}}
>   machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
> apiserver.go:157 -> [7C] unit-swift-storage-1 383.812us
> {"RequestId":42,"Response":{"Results":[{"Error":null,"Result":"local:trusty/swift-storage-90","Ok":false}]}}
> Uniter[""].CharmURL
>   machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
> apiserver.go:150 <- [7C] unit-swift-storage-1
> {"RequestId":43,"Type":"Uniter","Request":"CharmArchiveSha256","Params":{"URLs":[{"URL":"local:trusty/swift-storage-90"}]}}
>   machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
> apiserver.go:157 -> [7C] unit-swift-storage-1 777.029us
> {"RequestId":43,"Response":{"Results":[{"Error":null,"Result":"b8aac93898c3cc661c0804613e5cce79a402fbe596400e8e80e8a3a1bb16c577"}]}}
> Uniter[""].CharmArchiveSha256
>   machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
> apiserver.go:150 <- [61] machine-2
> {"RequestId":57,"Type":"Provisioner","Request":"SetStatus","Params":{"Entities":[{"Tag":"machine-2-lxc-0","Status":"error","Info":"error
> executing \"lxc-clone\": lxc_container: utils.c: mkdir_p: 220 Not a
> directory - failed to create directory
> '/run/lock/lxc//var/lib/lxc/juju-trusty-lxc-template/snaps'; lxc_container:
> lxccontainer.c: do_snapshot_destroy: 3272 Could not destroy snapshot %s -
> failed to allocate a pty; Insufficent privileges to control
> juju-trusty-lxc-template","Data":null}]}}
>   machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
> apiserver.go:150 <- [7C] unit-swift-storage-1
> {"RequestId":44,"Type":"Uniter","Request":"SetCharmURL","Params":{"Entities":[{"Tag":"unit-swift-storage-1","CharmURL":"local:trusty/swift-storage-90"}]}}
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1410876/+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/1410876

Title:
  Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a
  directory - Could not destroy  snapshot %s - failed to allocate a pty;
  Insufficent privileges to control  juju-trusty-lxc-template

Status in juju-core:
  Invalid
Status in 

[Touch-packages] [Bug 1477584] Re: package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Alberto Salvia Novella]

** Changed in: rsyslog (Ubuntu)
   Importance: Undecided => High

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

Title:
  package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  Identified the issue after upgrade to 15.04 from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: rsyslog 7.4.4-1ubuntu14
  ProcVersionSignature: Ubuntu 3.16.0-43.58-generic 3.16.7-ckt13
  Uname: Linux 3.16.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Thu Jul 23 14:34:45 2015
  DuplicateSignature: package:rsyslog:7.4.4-1ubuntu14:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-07-12 (11 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: rsyslog
  Title: package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess 
installed post-installation 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/1477584/+subscriptions

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

[Touch-packages] [Bug 1215957] Re: [greeter] needs a configuration interface for the authentification method to use

[Michael Terry]

I don't think there's a bug here anymore?

** Changed in: unity8 (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  [greeter] needs a configuration interface for the authentification
  method to use

Status in ubuntu-system-settings package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  That's part of the design in 
https://wiki.ubuntu.com/SecurityAndPrivacySettings#phone-locking:
  it should be possible to lock screen on suspend or not

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1215957/+subscriptions

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

[Touch-packages] [Bug 1410876] Re: Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a directory - Could not destroy snapshot %s - failed to allocate a pty; Insufficent privileges to

[Serge Hallyn]

@jason-hobbs or @lmic,

can you provide a concise recipe for reproducing this in the
Description?

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

Title:
  Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a
  directory - Could not destroy  snapshot %s - failed to allocate a pty;
  Insufficent privileges to control  juju-trusty-lxc-template

Status in juju-core:
  Invalid
Status in lxc:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Committed

Bug description:
  This is for:

  ++ export OPENSTACK_RELEASE=juno
  ++ OPENSTACK_RELEASE=juno
  ++ export COMPUTE=nova-lxc
  ++ COMPUTE=nova-lxc
  ++ export UBUNTU_RELEASE=trusty
  ++ UBUNTU_RELEASE=trusty

  Tool version is 1.20.14:
  Launching instance
  WARNING picked arbitrary tools &{1.20.14-precise-amd64 
https://streams.canonical.com/juju/tools/releases/juju-1.20.14-precise-amd64.tgz
 932640702b5d9f08a312118a4afe330444308f92b7de350de9e547719f084bd9 8130412}
   - /MAAS/api/1.0/nodes/node-5f9c14e6-ae98-11e3-b194-00163efc5068/

  and agent-version on node says 1.20.13.

  Juju-status.yaml:

  '5':
  agent-state: started
  agent-version: 1.20.13
  containers:
    5/lxc/0:
  agent-state-info: 'error executing "lxc-clone": lxc_container: 
utils.c: mkdir_p:
    220 Not a directory - failed to create directory 
''/run/lock/lxc//var/lib/lxc/juju-trusty-lxc-template/snaps'';
    lxc_container: lxccontainer.c: do_snapshot_destroy: 3272 Could not 
destroy
    snapshot %s - failed to allocate a pty; Insufficent privileges to 
control
    juju-trusty-lxc-template'
  instance-id: pending
  series: trusty
    5/lxc/1:
  agent-state-info: cannot clone a running container
  instance-id: pending
  series: trusty
  dns-name: apsaras.oil
  hardware: arch=amd64 cpu-cores=4 mem=32768M 
tags=hw-ok,oil-slave-1,hardware-dell-poweredge-R210
  instance-id: 
/MAAS/api/1.0/nodes/node-5f9c14e6-ae98-11e3-b194-00163efc5068/
  series: trusty

  and from log:

  machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver apiserver.go:150 <- 
[7C] unit-swift-storage-1 
{"RequestId":42,"Type":"Uniter","Request":"CharmURL","Params":{"Entities":[{"Tag":"service-swift-storage"}]}}
  machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver apiserver.go:157 -> 
[7C] unit-swift-storage-1 383.812us 
{"RequestId":42,"Response":{"Results":[{"Error":null,"Result":"local:trusty/swift-storage-90","Ok":false}]}}
 Uniter[""].CharmURL
  machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver apiserver.go:150 <- 
[7C] unit-swift-storage-1 
{"RequestId":43,"Type":"Uniter","Request":"CharmArchiveSha256","Params":{"URLs":[{"URL":"local:trusty/swift-storage-90"}]}}
  machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver apiserver.go:157 -> 
[7C] unit-swift-storage-1 777.029us 
{"RequestId":43,"Response":{"Results":[{"Error":null,"Result":"b8aac93898c3cc661c0804613e5cce79a402fbe596400e8e80e8a3a1bb16c577"}]}}
 Uniter[""].CharmArchiveSha256
  machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver apiserver.go:150 <- 
[61] machine-2 
{"RequestId":57,"Type":"Provisioner","Request":"SetStatus","Params":{"Entities":[{"Tag":"machine-2-lxc-0","Status":"error","Info":"error
 executing \"lxc-clone\": lxc_container: utils.c: mkdir_p: 220 Not a directory 
- failed to create directory 
'/run/lock/lxc//var/lib/lxc/juju-trusty-lxc-template/snaps'; lxc_container: 
lxccontainer.c: do_snapshot_destroy: 3272 Could not destroy snapshot %s - 
failed to allocate a pty; Insufficent privileges to control 
juju-trusty-lxc-template","Data":null}]}}
  machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver apiserver.go:150 <- 
[7C] unit-swift-storage-1 
{"RequestId":44,"Type":"Uniter","Request":"SetCharmURL","Params":{"Entities":[{"Tag":"unit-swift-storage-1","CharmURL":"local:trusty/swift-storage-90"}]}}

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1410876/+subscriptions

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

[Touch-packages] [Bug 1478257] Re: [MX4] phone does not ring and call can not be picked up

[Thomas Feldmann]

Yes indeed it appears to be the same one - sorry that I didn't find it
and created a duplicate bug report.

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

Title:
  [MX4] phone does not ring and call can not be picked up

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I noticed that sometimes I can not answer a call on the Meizu MX4 (OTA-5 
installed). Symptoms when someone tries to call:
  - no ringtone (even though the phone is not set to silent)
  - the display wakes, now on the first attempt the red and green buttons 
appear. I accept the call, but I can hear nothing and the person who is calling 
still gets the "ringtone" on his side - so the call actually was never picked 
up.
  - if immediately called again the screen wakes, but this time the red/green 
buttons to answer the call do not appear anymore at all
  - the call is registered as missed call in the notifications

  I observed this behavior already two times so far. So it keeps
  reappearing, although it is not exactly reproducible in the sense that
  it would happen always. I have accepted calls with the phone, which
  was not powered off between the time when it did work and now that it
  doesn't work.

  Please let me know, if you need further details and I will try to
  provide them.

  release: ubuntu 15.04 (r3)

  Thomas

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

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

[Touch-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic

[Alberto Salvia Novella]

** Changed in: bluez (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux-firmware (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Bluetooth mouse laggy and erratic

Status in bluez package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios
  A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves
  erratically (laggy, jumpy). The problem happens after a few (sometimes
  one) suspend and resume. I am attaching below some info on my system.
  Thank you.

  cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep 
-i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth
  Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac 
Wireless Network Adapter [14e4:43b1] (rev 03)
   Subsystem: Dell Device [1028:0019]
   Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0c45:670c Microdia
  Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
  Bus 001 Device 002: ID 0a5c:216f Broadcom Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [2.174367] Bluetooth: Core ver 2.20
  [2.174669] Bluetooth: HCI device and connection manager initialized
  [2.174792] Bluetooth: HCI socket layer initialized
  [2.174795] Bluetooth: L2CAP socket layer initialized
  [2.175449] Bluetooth: SCO socket layer initialized
  [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.542421] Bluetooth: BNEP filters: protocol multicast
  [3.542425] Bluetooth: BNEP socket layer initialized
  [3.551641] Bluetooth: RFCOMM TTY layer initialized
  [3.551649] Bluetooth: RFCOMM socket layer initialized
  [3.551654] Bluetooth: RFCOMM ver 1.11
  [   26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   26.569287] Bluetooth: HIDP socket layer initialized
  [   26.576971] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15
  [   26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [   72.448281] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16
  [   72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 2994.842547] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17
  [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 
lmp_ver=06 lmp_subver=220e
  [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [ 3811.777260] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20
  [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option 
usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr 
binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal 
dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel 
hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc 
glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd 
v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms 
intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic 
cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress 
snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit
  [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth]
  [ 5579.876261]  [] hci_dev_do_open+0xe1/0xa90 [bluetooth]
  [ 5579.876266]  [] hci_power_on+0x40/0x200 [bluetooth]
  [ 5579.876284] blue

[Touch-packages] [Bug 1467329] Re: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Alberto Salvia Novella]

** Changed in: lightdm (Ubuntu)
   Importance: Undecided => High

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

Title:
  package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Looks similar to bug #1433945 and bug #1424460, but those are
  different package versions.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  AptOrdering:
   lightdm: Install
   liblightdm-gobject-1-0: Install
   lightdm: Configure
   liblightdm-gobject-1-0: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun 21 17:59:16 2015
  DuplicateSignature: package:lightdm:1.14.2-0ubuntu1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user=oem
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: lightdm
  Title: package lightdm 1.14.2-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to vivid on 2015-06-14 (7 days ago)

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

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

[Touch-packages] [Bug 1485487] Re: package openssh-server 1:6.7p1-5ubuntu1.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Alberto Salvia Novella]

** Changed in: openssh (Ubuntu)
   Importance: Undecided => High

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

Title:
  package openssh-server 1:6.7p1-5ubuntu1.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  update-manager hanged on latest update

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: openssh-server 1:6.7p1-5ubuntu1.2
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  Date: Mon Aug 17 11:20:10 2015
  DuplicateSignature: package:openssh-server:1:6.7p1-5ubuntu1.2:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-04-06 (132 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: openssh
  Title: package openssh-server 1:6.7p1-5ubuntu1.2 failed to install/upgrade: 
subprocess installed post-installation 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/openssh/+bug/1485487/+subscriptions

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

[Touch-packages] [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Raymond]

https://www.virtualbox.org/changeset/55005/vbox/trunk/src/VBox/Devices/Audio/DevIchAc97.cpp

this patch intend to change rate from 48000Hz to 44100Hz

but the emuated ad1980 still using 48000Hz


Extended ID : codec=0 rev=2 DSA=0 VRM VRA
 Extended status : VRM VRA
 PCM front DAC : 48000Hz
 PCM ADC : 44100Hz
 PCM MIC ADC : 48000Hz

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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Volume Slider is only controlling PCM channel and is not controlling
  Master. In effect, Master is restricting the audio level to the
  default of approximately 45 Percent. In order to raise the Master
  Volume Level, alsamixer is capable of changing Master. Without
  manually raising Master to Max Volume, Volume Slider can only control
  volume from 0-45% which is the default level of Master.

  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1330 F pulseaudio
gene   1922 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Aug 20 13:00:57 2015
  InstallationDate: Installed on 2015-08-19 (1 days ago)
  InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_Type: Volume slider, or mixer problems
  Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1483127] Re: Proximity does not turn screen on during a call

[Bill Filler]

** Changed in: telephony-service (Ubuntu)
 Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh)

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

Title:
  Proximity does not turn screen on during a call

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

Bug description:
  This has regressed a week or two ago. It's not reliably reproducible,
  but bites me almost every time I want to end a call. It might be
  incoming calls only, or maybe only after a minute.

  Steps:
  * go on a call
  * cover the proximity sensor
  * uncover the proximity sensor

  Expected:
  * screen goes off/on as you cover/uncover the sensor

  Current:
  * screen goes off but not back on

  $ system-image-cli -i
  current build number: 90
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-08 21:08:55
  version version: 90
  version ubuntu: 20150807.1
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

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

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

[Touch-packages] [Bug 1486696] Re: lxc-create -B btrfs fails if lxc.lxcpath is not on the same filesystem as /var/cache/lxc (not a configurable option)

[Serge Hallyn]

** Changed in: lxc (Ubuntu)
   Status: New => Triaged

** Changed in: lxc (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  lxc-create -B btrfs fails if lxc.lxcpath is not on the same filesystem
  as /var/cache/lxc (not a configurable option)

Status in lxc package in Ubuntu:
  Triaged

Bug description:
  ## Version
  Description:Ubuntu 15.04
  Release:15.04
  lxc:
Installed: 1.1.2-0ubuntu3.1
Candidate: 1.1.2-0ubuntu3.1
Version table:
   *** 1.1.2-0ubuntu3.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.2-0ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

  ## Config changes from default
  >cat /etc/lxc/lxc.conf 
  lxc.lxcpath = /srv/vservers/lxc

  ## Mount details
  /var/cache/lxc in on root filesystem
  /srv/vservers/lxc is a btrfs mount point

  ## Command used (sample)
  > sudo lxc-create -B btrfs --name test-bt -t ubuntu -- -r trusty

  ## Error (sample)
  Copy /var/cache/lxc/trusty/rootfs-amd64 to /srv/vservers/lxc/test-bt/rootfs 
... 
  Copying rootfs to /srv/vservers/lxc/test-bt/rootfs ...
  Transaction commit: none (default)
  Delete subvolume '/srv/vservers/lxc/test-bt/rootfs'
  Create a snapshot of '/var/cache/lxc/trusty/rootfs-amd64' in 
'/srv/vservers/lxc/test-bt/rootfs'
  ERROR: cannot snapshot '/var/cache/lxc/trusty/rootfs-amd64' - Invalid 
cross-device link
  lxc_container: lxccontainer.c: create_run_template: 1108 container creation 
template for test-bt failed
  lxc_container: lxccontainer.c: container_destroy: 2056 Error destroying 
rootfs for test-bt
  lxc_container: lxc_create.c: main: 274 Error creating container test-bt

  ## Thoughts
  Maybe this is the expected behavior, if so a Documentation update stating 
something to the effect of "If you change the lxcpath to a different filesystem 
than the one where /var/cache/lxc livs you cannot create a btrfs backed 
container."
  -or-
  Let /var/cache/lxc be configured via lxc.conf and have the documentation note 
that they should reside on the same filesystem.

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

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

[Touch-packages] [Bug 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia

[Peter Würtz]

*sigh* late 2015, still not fixed in Ubuntu

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

Title:
  dlopen(libGL.so) resolves to mesa rather than nvidia

Status in NVIDIA Drivers Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in pyqt5 package in Ubuntu:
  Invalid
Status in python-qt4 package in Ubuntu:
  Invalid

Bug description:
  I'm having trouble with a combination of NVIDIA + Python + Qt +
  Opengl.

  I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and 
errors like this these:
  QGLShader: could not create shader
  Vertex shader for simpleShaderProg (MainVertexShader 
&PositionOnlyVertexShader) failed to compile

  This is an example application triggering the problem:
  http://pastebin.com/R0aa8ejs

  The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact 
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this 
error when trying the original demo application from python-qt4-doc. Also, 
calling
  QtGui.QApplication.setGraphicsSystem("opengl")
  produces the same errors.

  I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
  provided nvidia drivers (where 12.04 includes the most recent driver
  for now). After installing the driver using the original NVidia
  installer, the applications work as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+subscriptions

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

[Touch-packages] [Bug 1474940] Re: phone call ends after 2 hours

[Sebastien Bacher]

** Package changed: dialer-app (Ubuntu) => telephony-service (Ubuntu)

** Changed in: telephony-service (Ubuntu)
   Importance: Undecided => Low

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

Title:
  phone call ends after 2 hours

Status in telephony-service package in Ubuntu:
  New

Bug description:
  My calls will be finished after exactly 2:00:00 hours.

  Device: nexus 4 mako
  System: All up to date (stable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1474940/+subscriptions

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

[Touch-packages] [Bug 1409906] Re: landscape loses the addressee text box

[Sebastien Bacher]

** Changed in: messaging-app (Ubuntu RTM)
   Status: New => Won't Fix

** Changed in: messaging-app (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  landscape loses the addressee text box

Status in messaging-app package in Ubuntu:
  Fix Released
Status in messaging-app package in Ubuntu RTM:
  Won't Fix

Bug description:
  apologies if this is a specific subset of bug 1379421
  seeing this on ubuntu-rtm/krillin # 191
  also seeing on vivid/mako last week

  1. go to message app
  2. swipe up from bottom to begin writing a message
  3. rotate to landscape

  result - rotation occurs for message body with addressee "To:" block 
disappearing
  expected, the "to:" block to remain available for selecting/editing
  rotating back to portrait returns the "to:" text block

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

-- 
Mailing list: https://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 1486988] [NEW] /etc/cgconfig.conf ignored -> cgconfigd not working

[Serge Hallyn]

> # cgm create memory CH
> method return sender=(null sender) -> dest=(null destination) reply_serial=1
>int32 -1

This is not an error.  The -1 means that the cgroup did not already
exist.  Try

cgm listchildren freezer .

after the create, and you should see something like

method return sender=(null sender) -> dest=(null destination) reply_serial=1
   array [
  string "a1"
   ]

Note that cgmanager is not related to cgroup-lite, and that cgroup-lite
does not have a deamon - it simply mounts the cgroups so that they can
be used.


** Changed in: cgroup-lite (Ubuntu)
   Status: New => Invalid

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

Title:
  /etc/cgconfig.conf ignored -> cgconfigd not working

Status in cgroup-lite package in Ubuntu:
  Invalid

Bug description:
  cgroup-lite installed, but daemon missing from cgroup-lite:

  # dpkg -l | grep cgroup
  ii  cgmanager   0.24-0ubuntu7.3  amd64  Central cgroup manager daemon
  ii  cgmanager-utils 0.24-0ubuntu7.3  amd64  Central cgroup manager daemon 
(utilities)
  ii  cgroup-bin  0.38-1ubuntu2amd64  Tools to control and monitor 
control groups
  ii  cgroup-lite 1.9  allLight-weight package to set 
up cgroups at system boot
  ii  libcgmanager0:amd64 0.24-0ubuntu7.3  amd64  Central cgroup manager daemon 
(client library)
  ii  libcgmanager0:i386  0.24-0ubuntu7.3  i386   Central cgroup manager daemon 
(client library)
  ii  libcgroup1  0.38-1ubuntu2amd64  Library to control and 
monitor control groups

  # dpkg -L cgroup-lite
  /.
  /usr
  /usr/share
  /usr/share/doc
  /usr/share/doc/cgroup-lite
  /usr/share/doc/cgroup-lite/copyright
  /usr/share/doc/cgroup-lite/changelog.gz
  /usr/bin
  /etc
  /etc/init
  /etc/init/cgroup-lite.conf
  /bin
  /bin/cgroups-mount
  /bin/cgroups-umount
  /usr/bin/cgroups-mount
  /usr/bin/cgroups-umount

  cgroup-bin and cgmanage -packages just give errors trying to use them:

  # cgm create memory CH
  method return sender=(null sender) -> dest=(null destination) reply_serial=1
 int32 -1

  -> cgroups unusable with Ubuntu 14.04 LTS??

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cgroup-lite 1.9
  Uname: Linux 3.14.51+ x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  Date: Thu Aug 20 13:26:54 2015
  InstallationDate: Installed on 2011-10-19 (1400 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: cgroup-lite
  UpgradeStatus: Upgraded to trusty on 2014-02-24 (541 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1486988/+subscriptions

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

[Touch-packages] [Bug 1468695] Re: [messaging-app] Can't finish the message guide task when the phone is in the landscape mode

[Sebastien Bacher]

** Changed in: messaging-app (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [messaging-app] Can't finish the message guide task when the phone is
  in the landscape mode

Status in Ubuntu UX:
  Fix Released
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  $ system-image-cli -i
  current build number: 30
  device name: arale
  channel: ubuntu-touch/devel-proposed/meizu.en
  last update: 2015-06-23 02:58:10
  version version: 30
  version ubuntu: 20150622
  version device: 20150608-6e66f3c
  version custom: 20150602-731-5-32

  Reproduce steps:

  1,First use message app
  2,Got a message from another device
  3,Enter a message to view content
  4,Display guide for "how to delete the message"
  5,Rotation the device to landscape mode
  6,Check if the content of guide complete

  Expect Result:

  The "got it "button can display in the landscape mode normally

  Actual Result:

  The "got it "button can't display in the landscape mode

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

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

[Touch-packages] [Bug 1478723] Re: Predictive Dialing

[Sebastien Bacher]

*** This bug is a duplicate of bug 1474435 ***
https://bugs.launchpad.net/bugs/1474435

or rather bug #1474435

** This bug has been marked a duplicate of bug 1474435
   [dialler] "Smart dialing" is not supported

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

Title:
  Predictive Dialing

Status in dialer-app package in Ubuntu:
  New

Bug description:
  Hello everyone.

  I think it would be useful to introduce the predictive dialing
  keyboard, already equipped with alphabetic characters.

  In practice, by dialing the name of the person in your address book,
  using the letters on the keyboard, the phone should display the
  contacts that match the series of letters that you have typed.

  It might be added a button to change from "normal composition" to
  "predictive dialing".

  g

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

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

[Touch-packages] [Bug 1478723] Re: Predictive Dialing

[Sebastien Bacher]

*** This bug is a duplicate of bug 1474435 ***
https://bugs.launchpad.net/bugs/1474435

thanks, that's somewhat related to bug #1449691

** Changed in: dialer-app (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Predictive Dialing

Status in dialer-app package in Ubuntu:
  New

Bug description:
  Hello everyone.

  I think it would be useful to introduce the predictive dialing
  keyboard, already equipped with alphabetic characters.

  In practice, by dialing the name of the person in your address book,
  using the letters on the keyboard, the phone should display the
  contacts that match the series of letters that you have typed.

  It might be added a button to change from "normal composition" to
  "predictive dialing".

  g

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

-- 
Mailing list: https://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 1486696] [NEW] lxc-create -B btrfs fails if lxc.lxcpath is not on the same filesystem as /var/cache/lxc (not a configurable option)

[Serge Hallyn]

Indeed this is expected behavior.  Since there is no way to
create a btrfs subvolume in this instance, and you explicitly
asked for a btrfs subvolume, it should error.  A simple directory
copy must be used.

I think it might be reasonable to say that even if it has to
do a full directory copy, it could still create a new subvolume
so that clones can be done as snapshots.  Patches for either that
or for documentation improvement are welcome, so leaving this bug
open

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

Title:
  lxc-create -B btrfs fails if lxc.lxcpath is not on the same filesystem
  as /var/cache/lxc (not a configurable option)

Status in lxc package in Ubuntu:
  Triaged

Bug description:
  ## Version
  Description:Ubuntu 15.04
  Release:15.04
  lxc:
Installed: 1.1.2-0ubuntu3.1
Candidate: 1.1.2-0ubuntu3.1
Version table:
   *** 1.1.2-0ubuntu3.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.2-0ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

  ## Config changes from default
  >cat /etc/lxc/lxc.conf 
  lxc.lxcpath = /srv/vservers/lxc

  ## Mount details
  /var/cache/lxc in on root filesystem
  /srv/vservers/lxc is a btrfs mount point

  ## Command used (sample)
  > sudo lxc-create -B btrfs --name test-bt -t ubuntu -- -r trusty

  ## Error (sample)
  Copy /var/cache/lxc/trusty/rootfs-amd64 to /srv/vservers/lxc/test-bt/rootfs 
... 
  Copying rootfs to /srv/vservers/lxc/test-bt/rootfs ...
  Transaction commit: none (default)
  Delete subvolume '/srv/vservers/lxc/test-bt/rootfs'
  Create a snapshot of '/var/cache/lxc/trusty/rootfs-amd64' in 
'/srv/vservers/lxc/test-bt/rootfs'
  ERROR: cannot snapshot '/var/cache/lxc/trusty/rootfs-amd64' - Invalid 
cross-device link
  lxc_container: lxccontainer.c: create_run_template: 1108 container creation 
template for test-bt failed
  lxc_container: lxccontainer.c: container_destroy: 2056 Error destroying 
rootfs for test-bt
  lxc_container: lxc_create.c: main: 274 Error creating container test-bt

  ## Thoughts
  Maybe this is the expected behavior, if so a Documentation update stating 
something to the effect of "If you change the lxcpath to a different filesystem 
than the one where /var/cache/lxc livs you cannot create a btrfs backed 
container."
  -or-
  Let /var/cache/lxc be configured via lxc.conf and have the documentation note 
that they should reside on the same filesystem.

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

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

[Touch-packages] [Bug 1474435] Re: [dialler] "Smart dialing" is not supported

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: dialer-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  [dialler] "Smart dialing" is not supported

Status in Ubuntu UX:
  Triaged
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  In Android, Windows phone, and older platforms (meaning, everywhere
  but iOS and apparently Jolla) you can  use the T9 letters in the
  dialer app to type the beginning of names and get suggested phone
  numbers.

  For example, if "Mom" is a contact, then typing 66 will suggest
  contacts that start with / contain "mo", even if the number doesn't
  include 66.

  I swear that Mom being 666 in this context is purely a coincidence, my
  mom is a perfectly lovely person :-)

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

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

[Touch-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi

[Tony Espy]

@Michael

Can you please re-test when OTA6 is released ( or flash the latest rc-
proposed )?

@march

Please re-test when OTA6 is released ( should be out within the next
week or so ).   In general this should work much better when recent
fixes to NM land with OTA6.

That said, there may still be issues with re-connecting to a roaming
style network ( ie. an ESSID configuration where multiple access points
exist with the the same SSID ).

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

Title:
  [phone] Does not auto-switch to available, known WiFi

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  This might not be the place for this bug, please reassign as
  appropriate.

  I was only able to reproduce this on mako/rtm, krillin/vivid seems to
  behave better (but I do remember the same issue there).

  Steps:
  * connect to a password-protected WiFi network
  * go out of range
  * make sure a GSM connection is established
  * go back in the WiFi range

  Expected:
  * phone connects to the known WiFi automatically

  Current:
  * phone does not connect to WiFi

  Please find attached network-test-session logs from when I toggled
  WiFi and Plane mode to get some data on the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Tue Jan  6 12:01:55 2015
  InstallationDate: Installed on 2014-12-18 (18 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141218-163635)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)
  indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
  upstart.indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered

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

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

[Touch-packages] [Bug 1477146] Re: [inconsistency] Contacts list opened from the Dialer shows "+ Create New" on the first place

[Sebastien Bacher]

** Package changed: dialer-app (Ubuntu) => address-book-app (Ubuntu)

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
  [inconsistency] Contacts list opened from the Dialer shows "+ Create
  New" on the first place

Status in Ubuntu UX:
  New
Status in address-book-app package in Ubuntu:
  New

Bug description:
  When You open Contacts from the Dialer, a "+ Create New" item is shown
  as the first in the list. This takes too much space and is pretty
  obtrusive, especially in the "Favourites" tab, which is supposed to
  contain already existing contacts only. The solution could be to
  change this item to a draggable " + " in the bottom of the screen, the
  same way as it works in the stand-alone Contacts app already.

  Version: 0.1+15.04.20150415.2-0ubuntu1

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

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

[Touch-packages] [Bug 1478257] Re: [MX4] phone does not ring and call can not be picked up

[Sebastien Bacher]

could be a duplicate of bug #1471338 that should be fixed with the
coming ota update

** Changed in: dialer-app (Ubuntu)
   Importance: Undecided => High

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

Title:
  [MX4] phone does not ring and call can not be picked up

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I noticed that sometimes I can not answer a call on the Meizu MX4 (OTA-5 
installed). Symptoms when someone tries to call:
  - no ringtone (even though the phone is not set to silent)
  - the display wakes, now on the first attempt the red and green buttons 
appear. I accept the call, but I can hear nothing and the person who is calling 
still gets the "ringtone" on his side - so the call actually was never picked 
up.
  - if immediately called again the screen wakes, but this time the red/green 
buttons to answer the call do not appear anymore at all
  - the call is registered as missed call in the notifications

  I observed this behavior already two times so far. So it keeps
  reappearing, although it is not exactly reproducible in the sense that
  it would happen always. I have accepted calls with the phone, which
  was not powered off between the time when it did work and now that it
  doesn't work.

  Please let me know, if you need further details and I will try to
  provide them.

  release: ubuntu 15.04 (r3)

  Thomas

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

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

[Touch-packages] [Bug 1474319] Re: app spread only shows shadows of apps, no content

[Daniel d'Andrada]

So we got a fix for it in untiy8.
The terminal case from comment #3 is actually bug 1485608

** Branch linked: lp:~gerboland/unity8/fixGhostAppsWithRotatino

** Branch unlinked: lp:~dandrader/unity8/ghostApps2

** Changed in: unity8 (Ubuntu)
   Status: Invalid => Confirmed

** Changed in: qtmir (Ubuntu)
   Status: In Progress => Invalid

** Changed in: qtmir (Ubuntu)
 Assignee: Daniel d'Andrada (dandrader) => (unassigned)

** Changed in: qtmir
 Assignee: Daniel d'Andrada (dandrader) => (unassigned)

** Changed in: qtmir
   Status: In Progress => Invalid

** Description changed:

  on arale rc-proposed i'm hitting a bug in the spread since a while where
  apps do not have any content in the spread overview anymore but only
  show their shadow ...
  
  the image at http://i.imgur.com/r7tnyym.png shows the issue, as you can
  see the two front apps do not have any content but show only their
  shadow ... tapping on such an app to foreground it restarts it properly
  and the content is visible in the spread again.
  
  i do not see this behavior on krillin..
- 
- 
- 
- One way to reproduce:
- * open terminal
- * tap on Ctrl+D
- 
- Terminal's gone, but ghost remains.

** Changed in: unity8 (Ubuntu)
 Assignee: Daniel d'Andrada (dandrader) => Gerry Boland (gerboland)

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  app spread only shows shadows of apps, no content

Status in QtMir:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  on arale rc-proposed i'm hitting a bug in the spread since a while
  where apps do not have any content in the spread overview anymore but
  only show their shadow ...

  the image at http://i.imgur.com/r7tnyym.png shows the issue, as you
  can see the two front apps do not have any content but show only their
  shadow ... tapping on such an app to foreground it restarts it
  properly and the content is visible in the spread again.

  i do not see this behavior on krillin..

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

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

[Touch-packages] [Bug 1480088] Re: Improper message if dial without SIM card inserted

[Sebastien Bacher]

Thanks, a guess it's slightly confusing but it's not that common that
users try to use a phone without SIM to do calls

** Changed in: dialer-app (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Improper message if dial without SIM card inserted

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

Bug description:
  Test Environment:

  current build number: 72
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-09-28 04:55:39
  version version: 72
  version ubuntu: 20150729
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  Steps to reproduce:
  1.Get a phone without SIM card
  2.Open dial app
  3.Dial a valid number
  4.Observe the result

  Actual result:
  Improper message displays ¨No network: There is currently no network¨, see 
attached pic.

  Expected result:
  It should be ¨No SIM card¨

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

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

[Touch-packages] [Bug 1486889] Re: no message about"not an emergency number "popup, when call a non-emergency number with no SIM card

[Sebastien Bacher]

thanks, settings as low, it's a bit confusing but trying to call from a
phone without SIM is not the most frequent things users do

** Changed in: dialer-app (Ubuntu)
   Importance: Undecided => Low

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

Title:
  no message about"not an emergency number "popup,when call a non-
  emergency number  with no SIM card

Status in dialer-app package in Ubuntu:
  New

Bug description:
  system-image-cli -i
  current build number: 95
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-08-20 14:03:45
  version version: 95
  version ubuntu: 20150819
  version device: 20150818-0b38025
  version custom: 20150814-887-8-46

  reproduce steps:
  1.Setup:no SIM card inserted
  2. Lock device 
  3. Swipe away greeter and press Emergency call option 
  4. Enter a non-emergency number 
  5. Tap on the call button
  6.observe the result

  expect result:
  step 5, there will be a message display about "not an emergency number"
  actual result:
  no "not an emergency number" message display,while after a few seconds the 
call fail message display.

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

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

[Touch-packages] [Bug 1486492] Re: Keyboard appears during call and does not disappear unless reboot

[Sebastien Bacher]

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

** Also affects: ubuntu-keyboard (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Keyboard appears during call and does not disappear unless reboot

Status in dialer-app package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  OS Ubutnu 15.04(r3) on MX4

  0.1+15.04.20150615-0ubuntu1

  Only occurs if the phone is locked. When answering the call via
  slider, once answered the Keyboard appears, and then does not
  disappear even when calls ended. Calls can also only end by remote end
  hanging up, due to keyboard obscuring the hang up button.

  Unfortunately keyboard is non responsive and phone has to be rebooted
  for any continued use. Sometimes keyboard half appears but effect is
  still the same.

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

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

[Touch-packages] [Bug 1483127] Re: Proximity does not turn screen on during a call

[Jean-Baptiste Lallement]

** Changed in: telephony-service (Ubuntu)
   Importance: High => Critical

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

Title:
  Proximity does not turn screen on during a call

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

Bug description:
  This has regressed a week or two ago. It's not reliably reproducible,
  but bites me almost every time I want to end a call. It might be
  incoming calls only, or maybe only after a minute.

  Steps:
  * go on a call
  * cover the proximity sensor
  * uncover the proximity sensor

  Expected:
  * screen goes off/on as you cover/uncover the sensor

  Current:
  * screen goes off but not back on

  $ system-image-cli -i
  current build number: 90
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-08 21:08:55
  version version: 90
  version ubuntu: 20150807.1
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

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

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

[Touch-packages] [Bug 1483127] Re: Proximity does not turn screen on during a call

[Łukasz Zemczak]

** Tags added: lt-category-visible

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

Title:
  Proximity does not turn screen on during a call

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

Bug description:
  This has regressed a week or two ago. It's not reliably reproducible,
  but bites me almost every time I want to end a call. It might be
  incoming calls only, or maybe only after a minute.

  Steps:
  * go on a call
  * cover the proximity sensor
  * uncover the proximity sensor

  Expected:
  * screen goes off/on as you cover/uncover the sensor

  Current:
  * screen goes off but not back on

  $ system-image-cli -i
  current build number: 90
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-08 21:08:55
  version version: 90
  version ubuntu: 20150807.1
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

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

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

[Touch-packages] [Bug 1483127] Re: Proximity does not turn screen on during a call

[Sebastien Bacher]

confirmed, it doesn't turn the screen off when you remove the phone from
your ear to hang up, quite annoying

** Changed in: telephony-service (Ubuntu)
   Importance: Undecided => High

** Changed in: telephony-service (Ubuntu)
   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/1483127

Title:
  Proximity does not turn screen on during a call

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

Bug description:
  This has regressed a week or two ago. It's not reliably reproducible,
  but bites me almost every time I want to end a call. It might be
  incoming calls only, or maybe only after a minute.

  Steps:
  * go on a call
  * cover the proximity sensor
  * uncover the proximity sensor

  Expected:
  * screen goes off/on as you cover/uncover the sensor

  Current:
  * screen goes off but not back on

  $ system-image-cli -i
  current build number: 90
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-08 21:08:55
  version version: 90
  version ubuntu: 20150807.1
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

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

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

[Touch-packages] [Bug 1388201] Re: Toggling wifi on/off causes media playback to hiccup

[Tony Espy]

This bug is specific to arale, krillin, and most likely vegatta (
although as I don't have once, I haven't been able to test ).  It's
related to the fact that on devices using MTK's Wi-Fi driver, we're
forced to use hybris for power control of the Wi-Fi radios.  This
leverages the Android HAL functions wifi_load/unload_driver().  On
systems configured without kernel modules, this results in a driver
command to start/stop Wi-Fi ( this is accomplished by writing the string
"0" or "1" to the character device ( /dev/wmtWiFi ).

I just checked mako ( rc-proposed, #222 ) and no stuttering occurs when
Wi-Fi is enabled or disabled.

Also re-checked arale ( rc-proposed, #88 ) and krillin ( rc-proposed,
#104 ) and both still skip/stutter when Wi-Fi is toggled.

Bug #1487529 reported for arale.

** Summary changed:

- Toggling wifi on/off causes media playback to hiccup
+ [arale/krillin] Toggling wifi on/off causes media playback to hiccup

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

Title:
  [arale/krillin] Toggling wifi on/off causes media playback to hiccup

Status in Canonical System Image:
  Confirmed
Status in Network Menu:
  Invalid
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  1. Play a song with music-app
  2. Switch wifi off, notice that music-app playback pauses for a moment
  3. Switch wifi on, notice that music-app playback pauses for a moment
  4. Watch the CPU usage with top while toggling wifi and notice that the usage 
spikes to 100%

  Expected results:

  Music or video keeps playing without pausing while toggling wifi
  on/off

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

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

[Touch-packages] [Bug 1487534] [NEW] Unable to set Alt+Shift for switching keyboard layout

[anatoly techtonik]

Public bug reported:

I used to Alt+Shift combination for switching keyboard layouts. but I
can't find where to do this. Right clicking on language indicator and
choosing Preferences open IBus configuration window. But when I set
Alt+Shift, it just hangs.

** Affects: ubuntustudio
 Importance: Undecided
 Status: New

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

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

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

Title:
  Unable to set Alt+Shift for switching keyboard layout

Status in Ubuntu Studio:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  I used to Alt+Shift combination for switching keyboard layouts. but I
  can't find where to do this. Right clicking on language indicator and
  choosing Preferences open IBus configuration window. But when I set
  Alt+Shift, it just hangs.

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

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

[Touch-packages] [Bug 1487158] Re: Hot-spot should only be available when there is a modem to support it.

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-api-team/indicator-network/hotspot-cellular-
enabled-properties

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

Title:
  Hot-spot should only be available when there is a modem to support it.

Status in indicator-network package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install the latest rc-proposed image on flo

  EXPECTED:
  I expect to see no hotspot mode as there is only wifi available on flo

  ACTUAL:
  Hotspot is available and when enabled disabled the wifi.

  USER CASE:
  If at all possible it should be made that only when there is a 2/3/4g 
connection available that hotspot is available.  popey pointed out correctly 
that on flo there is no modem right now, but if it were docked or a 3g modem 
plugged in it then would have.

  POTENTIAL SOLUTION:
  The enable disable button in hotspot mode should only be pressable when the 
circumstances are true, this way there is no need to hid the option just make 
it so it can not be enabled if the circumstances are false.

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

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

[Touch-packages] [Bug 1487157] Re: mako and flo should have hotspot disabled

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-api-team/indicator-network/hotspot-cellular-
enabled-properties

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

Title:
  mako and flo should have hotspot disabled

Status in indicator-network package in Ubuntu:
  New

Bug description:
  METABUG FOR OTA6:

  Mako has an issue with wpa-supplicant that use 100% of the cpu and stops the 
phone from functioning as expected when hotspot is in use.
  Mako currently has hotspot installed, it can be enabled but devices can not 
connect to it.
  https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1429314

  Flo only has one modem wifi which is turn into the outgoing source for 
hotspot therefore disabling wifi.
  https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1487158

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

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

[Touch-packages] [Bug 1486996] Re: “Call” icon does not actually place a call

[Magdalena Mirowicz]

** Changed in: ubuntu-ux
   Importance: Undecided => Low

** Changed in: ubuntu-ux
   Status: New => Triaged

** Changed in: ubuntu-ux
 Assignee: (unassigned) => Olga Kemmet (olga-kemmet)

** Summary changed:

- “Call” icon does not actually place a call
+ [Dialer] [Address Book] “Call” icon does not actually place a call

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

Title:
  [Dialer] [Address Book] “Call” icon does not actually place a call

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Triaged
Status in address-book-app package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  New

Bug description:
  Reproduce:
  Open address-book-app, choose contact. Press the phone-off-the-hook icon to 
place a call

  What happens:
  The dialer-app opens with a number pre-filled.

  What I expected would happen:
  I expected the call to be placed.

  Rationale:
  The phone-off-the-hook icon in dialer-app represents placing a call, but not 
in address-book-app. Why the inconsistency?

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

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

[Touch-packages] [Bug 1423382] Re: unable to use apport to report a bug from point release Live CDs

[Brian Murray]

*** This bug is a duplicate of bug 1471903 ***
https://bugs.launchpad.net/bugs/1471903

** This bug has been marked a duplicate of bug 1471903
   -updates, -security missing from apt lists

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

Title:
  unable to use apport to report a bug from point release Live CDs

Status in apport package in Ubuntu:
  New

Bug description:
  Running apt-cache policy apport on an Ubuntu 14.04.2 Live CD returns
  the following:

  apport:
Installed: 2.14.1-0ubuntu3.7
Candidate: 2.14.1-0ubuntu3.7
Version table:
   *** 2.14.1-0ubuntu3.7 0
  100 /var/lib/dpkg/status
   2.14.1-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Because there is no record of where the package came from, the package
  is considered unofficial and its not possible to use "ubuntu-bug
  apport" to report a bug about apport or any other package.

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

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

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

[Sebastien Bacher]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

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

Title:
  Using ContentStore disables silently any StateSaver capability

Status in content-hub package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  1. Create the default template project
  2. Add on the page (with an id):
  TextField {
  id: foo
  StateSaver.properties: "text"
  }
  3. run the app, type something in the field, xkill it, restart
  -> the TextField content is restored by the StateSaver.
  4. import Ubuntu.Content 1.1
  -> StateSaver still works
  5. add anywhere on the page:
  ContentStore {
  id: appContentStore
  scope: ContentScope.App
  }
  -> The state is not restored anymore (note that it may be the first time, 
restoring when there was no ContentStore at kill time), then it constantly 
fails to restore.

  There is no warning or anything that reported an issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1485222/+subscriptions

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