[Touch-packages] [Bug 1162781] Re: bluez package out of date, 5.23 is available in debian sid/jessie

[Gizmo Chicken]

Looks like BlueZ 5.33 is now in Wiley.  Great!  Thanks much!

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

Title:
  bluez package out of date, 5.23 is available in debian sid/jessie

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  Looks like there have been a lot of improvements to bluez since the
  4.x series. Would be nice to get the latest release pulled in.

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

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

[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

[Niklas Keller]

I can confirm that updating to vivid-proposed fixes that behavior.

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  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
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

[Niklas Keller]

** Changed in: systemd (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  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
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1403792] Re: brightness of one of two screens no longer adjustable with hotkeys and menu

[Cesar Peralta]

Same happen with Ubuntu 14.04.3 64 bit, I had 14.04.2 x86 and worked
fine with graphic controller "Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)" but when updated to a 64 bit due to
notebook capabilities just did not worked...

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

Title:
  brightness of one of two screens no longer adjustable with hotkeys and
  menu

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  Without noticible cause the brightness of the screen of my laptop is
  no longer adjustable and stuck at the lowest level. Both the hotkey on
  my keyboard and the brightness submenu in the system settings no
  longer show any reaction to changes (i.e. key pressing and using the
  regulation bar in the menu).

  The issue persists accross reboots which makes the main screen of my
  laptop unusable and it necessary to plug in an extra monitor!

  I had this issue on an unknown version of Ubuntu < 14.10 and the
  installation of `indicator-brightness` (https://launchpad.net
  /~indicator-brightness/+archive/ubuntu/ppa) and setting the brightness
  in it once to the lowest and then to the highest level fixed the issue
  (persistently accross reboots), but now it doesn't show any reaction
  neither (I adjusted the package soucres to point to `trusty` after
  `sudo add-apt-repository ppa:indicator-brightness/ppa` in order to be
  able to install in 14.10). When the issue occured `indicator-
  brightness` was not installed.

  I could only fix the issue by rebooting and entering BIOS/EFI menu and
  using brightness hotkeys there.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  Uname: Linux 3.17.6-031706-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  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
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Dec 18 10:06:33 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3904]
  MachineType: LENOVO 20221
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.17.6-031706-generic 
root=UUID=27047ee0-b60c-4dc6-8c14-f416b264f331 ro
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141201.f99522e6-0ubuntu0ricotz
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20141210.47aaabda-0ubuntu0ricotz~utopic
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20141210.47aaabda-0ubuntu0ricotz~utopic
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1~utopic1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.916+git20141215.99537089-0ubuntu0sarvatt~utopic
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt
  xserver.bootTime: Thu Dec 18 10:05:52 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5557
   vendor CMN
  xserver.version: 2:1.16.1.901-1ubuntu1~utopic1

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

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

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

[David Gerstmann]

Hello Alan Burgess, my name is David. The easiest way that I have found to
deal with this problem is to go into your Terminal and type in the
following in this order (I'll try to be as specific as possible).
sudo apt-get autoclean  (that's exactly how it should look, then press
enter), next...
sudo apt-get autoremove (then enter), again...
sudo apt-get clean  (enter)

Do this every time before you attempt to update your computer. It may be a
bit of a pain, but it'll get you to where you need to be until someone
comes up with a permanent fix or another long term supported version comes
out again. Try this and let me know how it works for you. Good luck.
P.S., if you don't know what the terminal is, go into your dash and
simply type in the search window... "terminal", and that should come up
with what's known as the terminal emulator. Click on it and follow the
above instructions.

On Wed, Aug 12, 2015 at 1:35 PM, Alan Burgess 
wrote:

> Hello Casaba,
>
> Could you provide detailed instructions on how to resolve this issue
> please.
>
> Also when will this bug be resolved?
>
> Thanks
>
> Alan
>
>
>
> On 12/08/15 12:10, Csaba wrote:
> > ** Project changed: null-and-void => ubuntu
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/798414
>
> Title:
>   update-initramfs should produce a more helpful error when there isn't
>   enough  free space
>
> Status in initramfs-tools:
>   Confirmed
> Status in Ubuntu:
>   Fix Released
> Status in initramfs-tools package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Binary package hint: initramfs-tools
>
>   When generating a new initramfs there is no check for available free
>   space, subsequently its possible for update-initramfs to fail due to a
>   lack of free space.  This is resulting in package installation
>   failures for initramfs-tools.  For example:
>
>   Setting up initramfs-tools (0.98.8ubuntu3) ...
>   update-initramfs: deferring update (trigger activated)
>   Processing triggers for initramfs-tools ...
>   update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic
>
>   gzip: stdout: No space left on device
>   E: mkinitramfs failure cpio 141 gzip 1
>   update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
>   dpkg: error processing initramfs-tools (--configure):
>subprocess installed post-installation script returned error exit
> status 1
>
>   WORKAROUND:
>
>   Remove unused kernels using computer janitor or manually free space on
>   your partition containing the /boot file system.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions
>

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

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

Status in initramfs-tools:
  Confirmed
Status in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: initramfs-tools

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

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

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

  WORKAROUND:

  Remove unused kernels using computer janitor or manually free space on
  your partition containing the /boot file system.

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

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

[Touch-packages] [Bug 1464970] Re: S

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  S

Status in xorg package in Ubuntu:
  Expired

Bug description:
  S

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-54-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jun 14 09:10:57 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2015-04-22 (52 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-54-generic.efi.signed 
root=UUID=cdf5c68b-d27c-48f1-8380-c961657ade75 ro noprompt persistent quiet 
splash foo=bar vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFH:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Jun 14 08:03:26 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputPIXART USB OPTICAL MOUSE MOUSE, id 9
   inputDELL DELL USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19322 
   vendor GSM
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1465105] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Headphone Out, Front] Playback problem the headphones and mic none of the jack's rae detected when i plug somethi

[Launchpad Bug Tracker]

[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Headphone Out,
  Front] Playback problem the headphones and mic none of the jack's rae
  detected when i plug something in i had to use usb mic n headphones
  now those broke...i need help

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  he headphones and mic none of the jack's rae detected when i plug
  something in i had to use usb mic n headphones now those broke...i
  need help

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  manny  3927 F pulseaudio
   /dev/snd/controlC1:  manny  3927 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jun 14 23:47:35 2015
  InstallationDate: Installed on 2015-05-20 (26 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: None of the above
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Headphone Out, 
Front] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: FM2A55M-VG3+
  dmi.board.vendor: ASRock
  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.:bvrP1.00:bd10/14/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A55M-VG3+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-06-14T23:37:34.232881

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

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

[Touch-packages] [Bug 1417726] Re: After resumnig from sleep, playing videos doesn't work

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  After resumnig from sleep, playing videos doesn't work

Status in xorg package in Ubuntu:
  Expired

Bug description:
  This started a few weeks ago, after some update I guess. When my
  machine resumes from sleep,  if I try to play video in any player I
  have installed (vlc, smplayer, totem), all I get for a picture is a
  black screen. Sound is going, just there is no picture. I can get very
  flickering and unwatchable picture if I choose some OpenGL-based
  renderer (in smplayer). Sometimes, if I turn on or off second monitor,
  playing works for a while. The only way to enable playback is to
  restart X (logout/login or computer restart), which is geting quite
  tiresome because I need to close all my programs and open them again.

  I'm not sure if this is xorg, Unity or driver bug, but it really bugs
  me.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Feb  3 19:51:32 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / 
R9 280] [1002:679a] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:0424]
  InstallationDate: Installed on 2014-08-02 (185 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9174): WARNING **: Failed to load background: Failed 
to open file '/usr/share/lubuntu/wallpapers/lubuntu-default-wallpaper.png': No 
such file or directory
   
   ** (lightdm-gtk-greeter:9174): WARNING **: Failed to load user image: Failed 
to open file '/home/zzarko/.face': No such file or directory
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1810): WARNING **: Failed to load background: Failed 
to open file '/usr/share/lubuntu/wallpapers/lubuntu-default-wallpaper.png': No 
such file or directory
   
   ** (lightdm-gtk-greeter:1810): WARNING **: Failed to load user image: Failed 
to open file '/home/zzarko/.face': No such file or directory
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic 
root=UUID=b677df99-e917-4360-b8b5-13b8db6712cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: Z68 Extreme4 Gen3
  dmi.board.vendor: ASRock
  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.:bvrP1.00:bd07/08/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68Extreme4Gen3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Feb  3 19:48:59 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /u

[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Expired

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  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
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

** Patch removed: "Proposed debdiff for trusty"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1410876/+attachment/4445026/+files/lxclock.debdiff

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

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 1296218] Re: aa-complain crashed with apparmor.common.AppArmorException in get_profile_flags(): '/etc/apparmor.d/usr.bin.chromium-browser contains no profile'

[Mathew Hodson]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-notes
   Status: New => Fix Released

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

Title:
  aa-complain crashed with apparmor.common.AppArmorException in
  get_profile_flags(): '/etc/apparmor.d/usr.bin.chromium-browser
  contains no profile'

Status in AppArmor:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Triaged
Status in apparmor source package in Utopic:
  Fix Released

Bug description:
  Here the profile exists
  ---
  $ sudo aa-autodep /usr/bin/chromium-browser
  Profile for /usr/bin/chromium-browser already exists - skipping.
  
  Here it doesn't exist
  
  $ sudo aa-genprof /usr/bin/chromium-browser
  Traceback (most recent call last):
File "/usr/sbin/aa-genprof", line 102, in 
  apparmor.helpers[program] = apparmor.get_profile_flags(profile_filename, 
program)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 600, in 
get_profile_flags
  raise AppArmorException(_('%s contains no profile') % filename)
  apparmor.common.AppArmorException: '/etc/apparmor.d/usr.bin.chromium-browser 
contains no profile'
  ---
  and finally this crashes again
  ---
  $ sudo aa-complain /usr/bin/chromium-browser
  Setting /usr/bin/chromium-browser to complain mode.
  Traceback (most recent call last):
File "/usr/sbin/aa-complain", line 30, in 
  tool.cmd_complain()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 178, in 
cmd_complain
  apparmor.set_complain(profile, program)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 264, in 
set_complain
  change_profile_flags(filename, program, 'complain', True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 603, in 
change_profile_flags
  old_flags = get_profile_flags(filename, program)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 600, in 
get_profile_flags
  raise AppArmorException(_('%s contains no profile') % filename)
  apparmor.common.AppArmorException: '/etc/apparmor.d/usr.bin.chromium-browser 
contains no profile'

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: apparmor-utils 2.8.95~2430-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-18.38-lowlatency 3.13.6
  Uname: Linux 3.13.0-18-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Sun Mar 23 08:47:30 2014
  ExecutablePath: /usr/sbin/aa-complain
  InstallationDate: Installed on 2014-03-08 (14 days ago)
  InstallationMedia: Ubuntu-Studio 14.04 "Trusty Tahr" - Alpha amd64 (20140224)
  InterpreterPath: /usr/bin/python3.4
  ProcCmdline: /usr/bin/python3 /usr/sbin/aa-complain /usr/bin/chromium-browser
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-lowlatency 
root=UUID=4333a8e9-30cd-431d-8682-8211c549f168 ro quiet splash vt.handoff=7
  PythonArgs: ['/usr/sbin/aa-complain', '/usr/bin/chromium-browser']
  SourcePackage: apparmor
  Title: aa-complain crashed with apparmor.common.AppArmorException in 
get_profile_flags(): '/etc/apparmor.d/usr.bin.chromium-browser contains no 
profile'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1484555] Re: When resized to narrow, history view becomes blank

[Launchpad Bug Tracker]

** Branch linked: lp:~artmello/webbrowser-app/webbrowser-app-fix_1484555

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

Title:
  When resized to narrow, history view becomes blank

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The responsive history view landed with webbrowser-app
  0.23+15.10.20150812.1-0ubuntu1, so that there are two different
  layouts depending on the width of the window.

  To reproduce the issue:
   1) launch the browser on desktop
   2) open the history view (with e.g. Ctrl+H)
   3) resize the window horizontally to narrow it

  Expected result: at some point the narrow layout replaces the wide layout.
  Current result: at the point where the narrow layout replaces the wide 
layout, the view is empty.

  I’m suspecting that the model is not correctly set when switching
  view, due to implementation that delays setting the model by 1ms with
  a Timer (http://bazaar.launchpad.net/~phablet-team/webbrowser-
  app/trunk/view/head:/src/app/webbrowser/Browser.qml#L768).

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

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

[Touch-packages] [Bug 1320020] Re: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

[Nam La]

Same here.

Just installed Ubuntu 14.x LTS to avoid issues with my Broadcom 43142 (I
tried Fedora first.

This is a less-than-a-week old Asus X555LN that had W8.1 installed from
factory and completely removed from the Hard Drive.

* Secure Boot has been disabled.
* No dual boot here.
* Sound worked fine in Windows 8.1, Fedora 22 (unfortunately, WLAN did not and 
that's why I decided to try this Ubuntu LTS) and Windows 7 (I decided to try W7 
just to do a Dual Boot but then I desisted and installed Ubuntu).
* Sound works fine through headphones.
* Toggling between speakers and headphones does not resolve the issue.
* doing
 $ alsa force-reload 
does not resolve the issue.
* Disabling auto-mute via 
$ alsamixer
does not resolve the issue.


$ lspci | grep Audio 
shows 

00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller (rev 
04)

$ pulseaudio 
shows 

E: [pulseaudio] pid.c: Daemon already running.
E: [pulseaudio] main.c: pa_pid_file_create() failed.

Still looking for any additional information/entries at forums/tuts to
try. Please advise if this thread will be followed up on and if we can
expect any resolution. Thank you.

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

Title:
  [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I can get perfect sound through headphones, and the kernel recognizes
  the internal speaker, but nothing is ever played through it. I have
  personally tested a pair of earbuds to make sure that sound could play
  through the headphone port, and that isn't a problem. The sound driver
  just refuses to recognize the existence of the speaker, even though
  the kernel does.

  I wouldn't be surprised if the last upstream update had something to
  do with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isiah  7361 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu May 15 18:07:52 2014
  InstallationDate: Installed on 2014-01-29 (106 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isiah  7361 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (11 days ago)
  dmi.bios.date: 03/23/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0M7CYJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd03/23/2011:svnDellInc.:pnInspiron1470:pvrA05123:rvnDellInc.:rn0M7CYJ:rvrA05:cvnDellInc.:ct8:cvrA05:
  dmi.product.name: Inspiron 1470
  dmi.product.version: A05123
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1484555] Re: When resized to narrow, history view becomes blank

[Arthur Mello]

** Changed in: webbrowser-app (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  When resized to narrow, history view becomes blank

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The responsive history view landed with webbrowser-app
  0.23+15.10.20150812.1-0ubuntu1, so that there are two different
  layouts depending on the width of the window.

  To reproduce the issue:
   1) launch the browser on desktop
   2) open the history view (with e.g. Ctrl+H)
   3) resize the window horizontally to narrow it

  Expected result: at some point the narrow layout replaces the wide layout.
  Current result: at the point where the narrow layout replaces the wide 
layout, the view is empty.

  I’m suspecting that the model is not correctly set when switching
  view, due to implementation that delays setting the model by 1ms with
  a Timer (http://bazaar.launchpad.net/~phablet-team/webbrowser-
  app/trunk/view/head:/src/app/webbrowser/Browser.qml#L768).

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

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

[Touch-packages] [Bug 1388362] Re: Touchpad setting lost after suspend/resume

[David Cohen]

Possibly related to  https://bugs.launchpad.net/ubuntu/+source/unity-
settings-daemon/+bug/1283863

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

Title:
  Touchpad setting lost after suspend/resume

Status in powermgmt-base package in Ubuntu:
  New

Bug description:
  Have set up a Startup Application script to disable the touchpad on
  the referenced laptop.  After suspend/resume the touchpad is active
  again.

  xinput set-prop 15 "Device Enabled" 0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: powermgmt-base 1.31build1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Nov  1 07:26:49 2014
  InstallationDate: Installed on 2014-10-11 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: powermgmt-base
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1388362/+subscriptions

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

[Touch-packages] [Bug 1484175] Re: webbrowser_app.tests.test_bookmark_options.TestBookmarkOptions.test_save_bookmarked_url_in_existing_folder is flaky

[Arthur Mello]

** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  
webbrowser_app.tests.test_bookmark_options.TestBookmarkOptions.test_save_bookmarked_url_in_existing_folder
  is flaky

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  
webbrowser_app.tests.test_bookmark_options.TestBookmarkOptions.test_save_bookmarked_url_in_existing_folder
  is flaky. When running it on my desktop, I get approximately a 25%
  failure rate. The issue is with clicking the OK button of the bookmark
  options popover after changing the folder, which resizes the popover
  and makes the button move:

  test-log: {{{
  17:40:43.241 INFO _launcher:373 - Attempting to launch application 
'../../src/app/webbrowser/webbrowser-app' with arguments '--new-session 
http://test/test1' as a normal process
  17:40:43.253 INFO _launcher:431 - Launching process: 
['../../src/app/webbrowser/webbrowser-app', '-testability', '--new-session', 
'http://test/test1']
  17:40:44.195 INFO http_server:162 - "GET /test1 HTTP/1.1" 200 -
  17:40:44.835 INFO logging:45 - TabsBar: click_new_tab_button. Arguments (). 
Keyword arguments: {}.
  17:40:46.968 INFO logging:45 - AddressBar: go_to_url. Arguments 
('http://test/test2',). Keyword arguments: {}.
  17:40:46.968 INFO logging:45 - TextField: Write into the text field. 
Arguments ('http://test/test2', True). Keyword arguments: {}.
  17:40:47.454 INFO logging:45 - TextField: Clear the text field. Arguments (). 
Keyword arguments: {}.
  17:40:50.916 INFO http_server:162 - "GET /test2 HTTP/1.1" 200 -
  17:40:52.661 INFO logging:45 - BookmarkOptions: click_dismiss_button. 
Arguments (). Keyword arguments: {}.
  17:41:03.219 INFO _launcher:544 - waiting for process to exit.
  17:41:03.219 INFO _launcher:567 - Killing process 27424
  }}}

  Traceback (most recent call last):
File 
"/home/osomon/dev/phablet/browser/webbrowser-app/tests/autopilot/webbrowser_app/tests/test_bookmark_options.py",
 line 157, in test_save_bookmarked_url_in_existing_folder
  bookmark_options.wait_until_destroyed()
File "/usr/lib/python3/dist-packages/autopilot/introspection/dbus.py", line 
451, in wait_until_destroyed
  "Object was not destroyed after %d seconds" % timeout
  RuntimeError: Object was not destroyed after 10 seconds

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

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

[Touch-packages] [Bug 1484175] Re: webbrowser_app.tests.test_bookmark_options.TestBookmarkOptions.test_save_bookmarked_url_in_existing_folder is flaky

[Launchpad Bug Tracker]

** Branch linked: lp:~artmello/webbrowser-app/webbrowser-app-fix_1484175

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

Title:
  
webbrowser_app.tests.test_bookmark_options.TestBookmarkOptions.test_save_bookmarked_url_in_existing_folder
  is flaky

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  
webbrowser_app.tests.test_bookmark_options.TestBookmarkOptions.test_save_bookmarked_url_in_existing_folder
  is flaky. When running it on my desktop, I get approximately a 25%
  failure rate. The issue is with clicking the OK button of the bookmark
  options popover after changing the folder, which resizes the popover
  and makes the button move:

  test-log: {{{
  17:40:43.241 INFO _launcher:373 - Attempting to launch application 
'../../src/app/webbrowser/webbrowser-app' with arguments '--new-session 
http://test/test1' as a normal process
  17:40:43.253 INFO _launcher:431 - Launching process: 
['../../src/app/webbrowser/webbrowser-app', '-testability', '--new-session', 
'http://test/test1']
  17:40:44.195 INFO http_server:162 - "GET /test1 HTTP/1.1" 200 -
  17:40:44.835 INFO logging:45 - TabsBar: click_new_tab_button. Arguments (). 
Keyword arguments: {}.
  17:40:46.968 INFO logging:45 - AddressBar: go_to_url. Arguments 
('http://test/test2',). Keyword arguments: {}.
  17:40:46.968 INFO logging:45 - TextField: Write into the text field. 
Arguments ('http://test/test2', True). Keyword arguments: {}.
  17:40:47.454 INFO logging:45 - TextField: Clear the text field. Arguments (). 
Keyword arguments: {}.
  17:40:50.916 INFO http_server:162 - "GET /test2 HTTP/1.1" 200 -
  17:40:52.661 INFO logging:45 - BookmarkOptions: click_dismiss_button. 
Arguments (). Keyword arguments: {}.
  17:41:03.219 INFO _launcher:544 - waiting for process to exit.
  17:41:03.219 INFO _launcher:567 - Killing process 27424
  }}}

  Traceback (most recent call last):
File 
"/home/osomon/dev/phablet/browser/webbrowser-app/tests/autopilot/webbrowser_app/tests/test_bookmark_options.py",
 line 157, in test_save_bookmarked_url_in_existing_folder
  bookmark_options.wait_until_destroyed()
File "/usr/lib/python3/dist-packages/autopilot/introspection/dbus.py", line 
451, in wait_until_destroyed
  "Object was not destroyed after %d seconds" % timeout
  RuntimeError: Object was not destroyed after 10 seconds

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

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

[Touch-packages] [Bug 1485147] [NEW] /usr/bin/messaging-app:11:QByteArray::isNull:pattern:QtVersit::LineReader::tryReadLine:QtVersit::LineReader::readOneLine:QtVersit::LineReader::readLine

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: rtm-14.09 vivid

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

Title:
  /usr/bin/messaging-
  
app:11:QByteArray::isNull:pattern:QtVersit::LineReader::tryReadLine:QtVersit::LineReader::readOneLine:QtVersit::LineReader::readLine

Status in messaging-app package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1485146] [NEW] /usr/bin/messaging-app:11:node_copy:QList:QList:QtVersit::VersitUtils::changeCodec:QtVersit::VersitUtils::newlineList

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: rtm-14.09 vivid

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

Title:
  /usr/bin/messaging-
  
app:11:node_copy:QList:QList:QtVersit::VersitUtils::changeCodec:QtVersit::VersitUtils::newlineList

Status in messaging-app package in Ubuntu:
  New

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

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

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

** Patch added: "Proposed debdiff for trusty"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1410876/+attachment/4445026/+files/lxclock.debdiff

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

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 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]

Hi,

thanks for pointing that out.  The trusty package appears to be subtly
different - its src/lxc/lxclock.c creates
"/run/lxc/lock/$lxcpath/$lxcname".  Upstream it creates
"/run/lxc/lock/$lxcpath/.$lxcname", keeping
"/run/lxc/lock/$lxcpath/$lxcname" available to be a directory.


** Changed in: lxc
   Status: New => Fix Released

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

** Also affects: lxc (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

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

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

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

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 h

[Touch-packages] [Bug 1468680] Re: The warning dialog is doesn't presented

[Charles Kerr]

** Changed in: indicator-sound (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  The warning dialog is doesn't presented

Status in indicator-sound 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: 2015062
  version device: 20150608-6e66f3c
  version custom: 20150602-731-5-32

  Reproduce steps:

  1,Play a music file
  2,Press the volume up key until maximum reached
  3,Check that a volume warning dialog is presented

  Expect Result:

  The volume warning dialog is present

  Actual Result:

  The volume warning dialog is not present

  : "...whenever volume is at a
  high level, any headphones volume bubble instead of saying
  “Headphones” should say “High volume”, and the bar should be colored."

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

-- 
Mailing list: https://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 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

[Mark J Galea]

Hi Simon

I have just received my Meizu phone and it's working seamlessly with my
Mazda Car entertainment system :)

Regards

mj

On 7 August 2015 at 19:21, Simon Fels  wrote:

> @Mark: You can. Follow https://wiki.ubuntu.com/DebuggingBluetooth to
> generate logs with debugging statements and then please attach them
> here. But please check those for any private data before or send them to
> me by private mail.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1466839).
> https://bugs.launchpad.net/bugs/1435040
>
> Title:
>   Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
>
> Status in Canonical System Image:
>   Confirmed
> Status in bluez package in Ubuntu:
>   Confirmed
> Status in ubuntu-system-settings package in Ubuntu:
>   Incomplete
>
> Bug description:
>   With my FORD Focus Car, pairing does not work. The bluetooth system in
>   the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
>   and then prompts me to connect with a 4-digit pin code, but the Ubuntu
>   phone doesn't react at all and after a while the car system says that
>   it failed to connect.
>
>   image: 20150310-3201c0a
>   KRILIN01A-S15A_BQ_L100EN_2020_150312
>   OS Build 20
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions
>

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

Title:
  Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

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

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

[Touch-packages] [Bug 1481832] Re: VA-API implementation for gallium missing

[Robert Hooker]

The gallium va driver uses shaders for decoding and the VDPAU one uses
native hardware decoding.. It's much worse.

** Changed in: mesa (Ubuntu)
   Importance: High => Wishlist

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

Title:
  VA-API implementation for gallium missing

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [needs-packaging] mesa
  Please include "gallium_drv_video.so" which is a native va-api state tracker 
for mesa(gallium).

  URL: http://mesa3d.sourceforge.net/
  URL: http://freedesktop.org/wiki/Software/vaapi/ #intel/vdpau
  License: http://www.mesa3d.org/license.html

  Notes:
  Currently (as of today) in ubuntu 15.10 nightly amd64, va-api(vaapi) on 
AMD/Ati radeon opensource display hardware is using a vdpau backend  0.7.4 by 
Splitted-Desktop Systems (wrapper) on gallium r600. Although its possible and 
probably preferred (better performance less copying) to use a native 
implementation which mesa(gallium) 10.4 and higher delivers in a form of a 
va-api state tracker.

  vainfo #current default setup vdpau backend
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
  libva info: Found init function __vaDriverInit_0_37
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 
0.7.4
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD

  The preferred setup needs that "gallium_drv_video.so" binary which is
  currently unavailable in ubuntu and debian. As an example I added a
  package/binary from archlinux. Copying the gallium_drv_video.so to
  /usr/lib/x86_64-linux-gnu/dri/ and symlinking(correcting) the
  libLLVM-3.6.so to arch-linux default /usr/lib/ location and exporting
  a variable was enough to make it work!
  https://www.archlinux.org/packages/extra/x86_64/libva-mesa-driver/
  #example by archlinux

  export LIBVA_DRIVER_NAME=gallium
  vainfo #preferred setup using gallium va-api from arch-linux (symlinked 
libLLVM-3.6.so to /usr/lib)
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: User requested driver 'gallium'
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: Found init function __vaDriverInit_0_38
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: mesa gallium vaapi
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD

  I guess this binary "gallium_drv_video.so" might be available as a
  compile flag in the current mesa implementation... intel and vdpau has
  their own current implementation in a separate libva branch
  http://cgit.freedesktop.org/vaapi/libva/ ?

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

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

[Touch-packages] [Bug 1485101] Re: add FindValgrind.cmake to cmake-extras

[Antti Kaijanmäki]

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

** Changed in: cmake-extras (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

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

Title:
  add FindValgrind.cmake to cmake-extras

Status in cmake-extras package in Ubuntu:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  in source tree cmake/FindValgrind.cmake is not part of cmake-extras.

  This module is universally usable and thus should be added to cmake-
  extras.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cmake-extras/+bug/1485101/+subscriptions

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

[Touch-packages] [Bug 1481798] Re: package:modemmanager:1.4.10-1:subprocess installed post-installation script returned error exit status 100

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1481798

** Tags added: iso-testing

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

Title:
  package:modemmanager:1.4.10-1:subprocess installed post-installation
  script returned error exit status 100

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding modemmanager.  This problem was most recently seen with
  version 1.4.10-1, the problem page at
  https://errors.ubuntu.com/problem/abc807de9d9c87d965fea31c865192edb30b6738
  contains more details.

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

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

[Touch-packages] [Bug 458116] Re: cups printer instances not usable from gtk applications

[Bug Watch Updater]

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

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

Title:
  cups printer instances not usable from gtk applications

Status in Common Print Dialog:
  New
Status in GTK+:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  This (http://lists.opensuse.org/opensuse-bugs/2009-02/msg05856.html)
  bug on suse summarizes the problem.

  I have once filed a bug upstream
  (http://bugzilla.gnome.org/show_bug.cgi?id=582747) which never got any
  attention.

  My suggested workaround in the upstream bug would at least prevent one
  bad effect the bug is having if you define cups "instances" in your
  /etc/cups/lpoptions or ~/.cups/lpoptions - either using old kde 3.5
  print configuration dialog or "lpoptions" command line.

  Read the loptions man page to learn about cups "instances". They are
  really useful. If anybody knows an alternative I'd be happy to learn
  about it as well. Multiple "queues" (printers) for the same "device
  URL" are not an alternative, as at least /usr/share/system-config-
  printer/system-config-printer.py (System->Administration->Printing)
  doesn't seem to allow setting up multiple printers with the same
  device file due to a cups error (client-error-not-possible) occurring
  if you try (at least for the cnij_usb: backend I'm using).

  If the cups instances are here to stay and somebody gave me some tips
  on how to get my code accepted by upstream I'd maybe take some effort
  to implement instances in the gtk libprintbackend-cups library.

  But there is some other printing dialog efforts going on. E.g. "Common
  Printing Dialog" (https://wiki.edubuntu.org/CommonPrintingDialog) On
  this
  
(https://www.linuxfoundation.org/en/OpenPrinting/OpenPrinting_Summit_San_Francisco_2009)
  page you find some nice slides
  (https://www.linuxfoundation.org/images/4/4d/CommonPrintingDialogLF09.pdf)
  about it. Does anybody know if there are any useable results from this
  project yet ?

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Oct 22 13:57:49 2009
  DistroRelease: Ubuntu 9.10
  Package: libgtk2.0-0 2.18.3-1
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=C
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: gtk+2.0
  Uname: Linux 2.6.31-14-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/common-print-dialog-gtk/+bug/458116/+subscriptions

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

[Touch-packages] [Bug 1481798] Re: package:modemmanager:1.4.10-1:subprocess installed post-installation script returned error exit status 100

[Brian Murray]

This generally seems to be happening during distribution upgrades from
vivid to wily.

** Tags added: rls-w-incoming

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

Title:
  package:modemmanager:1.4.10-1:subprocess installed post-installation
  script returned error exit status 100

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding modemmanager.  This problem was most recently seen with
  version 1.4.10-1, the problem page at
  https://errors.ubuntu.com/problem/abc807de9d9c87d965fea31c865192edb30b6738
  contains more details.

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

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

[Touch-packages] [Bug 1385292] Re: can't rename files in nautilus

[Adriano Varoli Piazza]

I still experience this bug in Ubuntu 15.04.

Also, changing the importance from Critical to Low? Renaming files? What
the EFF?

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

Title:
  can't rename files in nautilus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Triaged

Bug description:
  sometimes can't rename files with F2 button. It is higlight changing,
  but nothing gonna happen, it is not responding

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 24 17:48:33 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-10-24 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1436912] Re: Unlocalized notification option ("Message")

[Lukáš Tinkl]

** Changed in: ubuntu-settings-components (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Unlocalized notification option ("Message")

Status in Canonical System Image:
  New
Status in ubuntu-settings-components package in Ubuntu:
  Fix Committed

Bug description:
  Test case.
  - Switch the device to Spanish.
  - From another device, make a phone call, don't accept it.
  - Open message indicator.

  Expected result.
  - Notification options are localized. 

  Actual result.
  - "Message" is not localized.

  "Call back" is localized, but "Message" is not. Actually, I don't find
  "Message" in telephone-service source code, but "Send".

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

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

[Touch-packages] [Bug 1484126] Re: [Indicators] Volume notification unnecessary when adjusting volume slider

[Lukáš Tinkl]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Lukáš Tinkl (lukas-kde)

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

Title:
  [Indicators] Volume notification unnecessary when adjusting volume
  slider

Status in Ubuntu UX:
  Fix Committed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Current situation:

  Go to Sound section of indicators, drag volume slider. The volume
  notification pops up, essentially replicating the slider below

  
  Desired solution:

  Let's remove the volume notification when sliding the the volume
  slider

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

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

[Touch-packages] [Bug 1485118] [NEW] please help me

[madhu]

Public bug reported:

display ligting

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
Uname: Linux 3.13.0-62-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.12
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Aug 15 02:48:46 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.13.0-61-generic, i686: installed
 bbswitch, 0.7, 3.13.0-62-generic, i686: installed
 nvidia-340, 340.76, 3.13.0-61-generic, i686: installed
 nvidia-340, 340.76, 3.13.0-62-generic, i686: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0506]
InstallationDate: Installed on 2015-08-03 (11 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
MachineType: Acer Aspire 4750
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=d8ae8d9b-5a3a-402a-8aa7-7c6d347ec4e9 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/24/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.01
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire 4750
dmi.board.vendor: Acer
dmi.board.version: V2.01
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.01
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.01:bd05/24/2011:svnAcer:pnAspire4750:pvrV2.01:rvnAcer:rnAspire4750:rvrV2.01:cvnAcer:ct9:cvrV2.01:
dmi.product.name: Aspire 4750
dmi.product.version: V2.01
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Aug 14 22:30:48 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id  22 
 vendor INL
xserver.version: 2:1.15.1-0ubuntu2.7

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


** Tags: apport-bug compiz-0.9 i386 trusty ubuntu

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

Title:
  please help me

Status in xorg package in Ubuntu:
  New

Bug description:
  display ligting

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Aug 15 02:48:46 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-61-generic, i686: installed
   bbswitch, 0.7, 3.13.0-62-generic, i686: installed
   nvidia-340, 340.76, 3.13.0-61-generic, i686: installed
   nvidia-340, 340.76, 3.13.0-62-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0506]
  InstallationDate: Installed on 2015-08-03 (11 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: Acer Aspire 4750
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=d8ae8d9b-5a3a-402a-8aa7-7c6d347ec4e9 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2011
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.01
  dmi.board.asset.tag: No Asset

[Touch-packages] [Bug 1460249] Re: package modemmanager 1.4.8-1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 100

[Brian Murray]

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

** This bug is no longer a duplicate of bug 1453339
   package modemmanager 1.4.8-1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 100
** This bug has been marked a duplicate of bug 1481798
   package:modemmanager:1.4.10-1:subprocess installed post-installation script 
returned error exit status 100

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

Title:
  package modemmanager 1.4.8-1 failed to install/upgrade: el subproceso
  instalado el script post-installation devolvió el código de salida de
  error 100

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  I was attempting to upgrade to Wily, and this package stalled the
  upgrade. Everything else appears to have installed/upgraded fine.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: modemmanager 1.4.8-1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.3-0ubuntu3
  Architecture: amd64
  Date: Fri May 29 22:14:52 2015
  DuplicateSignature: package:modemmanager:1.4.8-1:el subproceso instalado el 
script post-installation devolvió el código de salida de error 100
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 100
  InstallationDate: Installed on 2015-05-10 (19 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: modemmanager
  Title: package modemmanager 1.4.8-1 failed to install/upgrade: el subproceso 
instalado el script post-installation devolvió el código de salida de error 100
  UpgradeStatus: Upgraded to wily on 2015-05-30 (0 days ago)

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

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

[Touch-packages] [Bug 1463621] Re: package modemmanager 1.4.8-1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 100

[Brian Murray]

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

** This bug is no longer a duplicate of bug 1453339
   package modemmanager 1.4.8-1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 100
** This bug has been marked a duplicate of bug 1481798
   package:modemmanager:1.4.10-1:subprocess installed post-installation script 
returned error exit status 100

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

Title:
  package modemmanager 1.4.8-1 failed to install/upgrade: sub-processo
  script post-installation instalado retornou estado de saída de erro
  100

Status in modemmanager package in Ubuntu:
  New

Bug description:
  I dont know.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: modemmanager 1.4.8-1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic i686
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  Date: Tue Jun  9 20:27:58 2015
  DuplicateSignature: package:modemmanager:1.4.8-1:sub-processo script 
post-installation instalado retornou estado de saída de erro 100
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 100
  InstallationDate: Installed on 2014-07-08 (336 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: modemmanager
  Title: package modemmanager 1.4.8-1 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 100
  UpgradeStatus: Upgraded to wily on 2015-06-09 (0 days ago)

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

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

[Touch-packages] [Bug 1481798] Re: package:modemmanager:1.4.10-1:subprocess installed post-installation script returned error exit status 100

[Brian Murray]

>From a duplicate here is the failure when installing the package:

Setting up modemmanager (1.4.10-1) ...^M
initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused^M
invoke-rc.d: unknown initscript, /etc/init.d/modemmanager not found.^M
dpkg: error processing package modemmanager (--configure):^M
 subprocess installed post-installation script returned error exit status 100^M


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

** Changed in: modemmanager (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

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

Title:
  package:modemmanager:1.4.10-1:subprocess installed post-installation
  script returned error exit status 100

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding modemmanager.  This problem was most recently seen with
  version 1.4.10-1, the problem page at
  https://errors.ubuntu.com/problem/abc807de9d9c87d965fea31c865192edb30b6738
  contains more details.

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

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

[Touch-packages] [Bug 1478151] Re: package modemmanager 1.4.8-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 100

[Brian Murray]

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

** This bug is no longer a duplicate of bug 1453339
   package modemmanager 1.4.8-1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 100
** This bug has been marked a duplicate of bug 1481798
   package:modemmanager:1.4.10-1:subprocess installed post-installation script 
returned error exit status 100

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

Title:
  package modemmanager 1.4.8-1 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 100

Status in modemmanager package in Ubuntu:
  New

Bug description:
  While upgrading to unstable

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: modemmanager 1.4.8-1
  ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-23-generic x86_64
  ApportVersion: 2.18-0ubuntu2
  Architecture: amd64
  Date: Fri Jul 24 23:57:23 2015
  DuplicateSignature: package:modemmanager:1.4.8-1:le sous-processus script 
post-installation installé a retourné une erreur de sortie d'état 100
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 100
  InstallationDate: Installed on 2014-12-09 (227 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: modemmanager
  Title: package modemmanager 1.4.8-1 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 100
  UpgradeStatus: Upgraded to wily on 2015-07-24 (0 days ago)

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

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

[Touch-packages] [Bug 1453339] Re: package modemmanager 1.4.8-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1481798
   package:modemmanager:1.4.10-1:subprocess installed post-installation script 
returned error exit status 100

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

Title:
  package modemmanager 1.4.8-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in modemmanager package in Ubuntu:
  Triaged

Bug description:
  root@ubuntu-14101504a2:~# lsb_release -rd
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  root@ubuntu-14101504a2:~# apt-cache policy modemmanager
  modemmanager:
Installed: 1.4.8-1
Candidate: 1.4.8-1
Version table:
   *** 1.4.8-1 0
  500 http://mirrors.us.kernel.org/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  root@ubuntu-14101504a2:~#

  I expected to upgrade:
  root@ubuntu-14101504a2:~# sudo do-release-upgrade -d

  but I got error message at the end.

  fixed it with:
  root@ubuntu-14101504a2:~# sudo dpkg -a --configure
  and 
  root@ubuntu-14101504a2:~# apt-get -f install

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: modemmanager 1.4.8-1
  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: Fri May  8 18:55:52 2015
  DuplicateSignature: package:modemmanager:1.4.8-1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: modemmanager
  Title: package modemmanager 1.4.8-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-05-09 (0 days ago)

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

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

[Touch-packages] [Bug 1453844] Re: package modemmanager 1.4.8-1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 100 zurück

[Brian Murray]

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

** This bug is no longer a duplicate of bug 1453339
   package modemmanager 1.4.8-1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 100
** This bug has been marked a duplicate of bug 1481798
   package:modemmanager:1.4.10-1:subprocess installed post-installation script 
returned error exit status 100

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

Title:
  package modemmanager 1.4.8-1 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript gab den Fehlerwert 100 zurück

Status in modemmanager package in Ubuntu:
  New

Bug description:
  do-release-upgrade -d failed

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: modemmanager 1.4.8-1
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Mon May 11 16:31:10 2015
  DuplicateSignature: package:modemmanager:1.4.8-1:Unterprozess installiertes 
post-installation-Skript gab den Fehlerwert 100 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 100 zurück
  InstallationDate: Installed on 2015-03-19 (53 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.9ubuntu1
  SourcePackage: modemmanager
  Title: package modemmanager 1.4.8-1 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 100 zurück
  UpgradeStatus: Upgraded to wily on 2015-05-11 (0 days ago)

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

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

[Touch-packages] [Bug 1471605] Re: package modemmanager 1.4.8-1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 100

[Brian Murray]

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

** This bug is no longer a duplicate of bug 1453339
   package modemmanager 1.4.8-1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 100
** This bug has been marked a duplicate of bug 1481798
   package:modemmanager:1.4.10-1:subprocess installed post-installation script 
returned error exit status 100

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

Title:
  package modemmanager 1.4.8-1 failed to install/upgrade: il
  sottoprocesso installato script di post-installation ha restituito lo
  stato di errore 100

Status in modemmanager package in Ubuntu:
  New

Bug description:
  I just upgraded ubuntu to version 15.10 and I found this problem.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: modemmanager 1.4.8-1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  Date: Sun Jul  5 16:27:37 2015
  DuplicateSignature: package:modemmanager:1.4.8-1:il sottoprocesso installato 
script di post-installation ha restituito lo stato di errore 100
  ErrorMessage: il sottoprocesso installato script di post-installation ha 
restituito lo stato di errore 100
  InstallationDate: Installed on 2015-02-02 (153 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: modemmanager
  Title: package modemmanager 1.4.8-1 failed to install/upgrade: il 
sottoprocesso installato script di post-installation ha restituito lo stato di 
errore 100
  UpgradeStatus: Upgraded to wily on 2015-07-05 (0 days ago)

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

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

[Touch-packages] [Bug 1478074] Re: package modemmanager 1.4.8-1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 100

[Brian Murray]

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

** This bug is no longer a duplicate of bug 1453339
   package modemmanager 1.4.8-1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 100
** This bug has been marked a duplicate of bug 1481798
   package:modemmanager:1.4.10-1:subprocess installed post-installation script 
returned error exit status 100

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

Title:
  package modemmanager 1.4.8-1 failed to install/upgrade: подпроцесс
  установлен сценарий post-installation возвратил код ошибки 100

Status in modemmanager package in Ubuntu:
  New

Bug description:
  The package was not installed when upgrading from 15.04 to 15.10.
  Ustanvovilsya manually after the upgrade procedure and reboot the
  system.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: modemmanager 1.4.8-1
  ProcVersionSignature: Ubuntu 4.1.0-1.1-generic 4.1.0
  Uname: Linux 4.1.0-1-generic x86_64
  ApportVersion: 2.18-0ubuntu2
  Architecture: amd64
  Date: Thu Jul 23 19:52:09 2015
  DuplicateSignature: package:modemmanager:1.4.8-1:подпроцесс установлен 
сценарий post-installation возвратил код ошибки 100
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 100
  InstallationDate: Installed on 2015-07-23 (1 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: modemmanager
  Title: package modemmanager 1.4.8-1 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 100
  UpgradeStatus: Upgraded to wily on 2015-07-24 (0 days ago)

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

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

[Touch-packages] [Bug 1479085] Re: package modemmanager 1.4.10-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1481798
   package:modemmanager:1.4.10-1:subprocess installed post-installation script 
returned error exit status 100

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

Title:
  package modemmanager 1.4.10-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  I had Ubuntu 15.04 and I updated my system through terminal. Right
  after finishing the upgrade I got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: modemmanager 1.4.10-1
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  Date: Tue Jul 28 22:05:11 2015
  DuplicateSignature: package:modemmanager:1.4.10-1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-05-20 (69 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.1ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: modemmanager
  Title: package modemmanager 1.4.10-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-07-28 (0 days ago)

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

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

[Touch-packages] [Bug 1468125] Re: package modemmanager 1.4.8-1 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 100

[Brian Murray]

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

** This bug is no longer a duplicate of bug 1453339
   package modemmanager 1.4.8-1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 100
** This bug has been marked a duplicate of bug 1481798
   package:modemmanager:1.4.10-1:subprocess installed post-installation script 
returned error exit status 100

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

Title:
  package modemmanager 1.4.8-1 failed to install/upgrade: podproces
  zainstalowany skrypt post-installation zwrócił kod błędu 100

Status in modemmanager package in Ubuntu:
  New

Bug description:
  upgrading 15.04 to 15.10

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: modemmanager 1.4.8-1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  Date: Tue Jun 23 23:45:09 2015
  DuplicateSignature: package:modemmanager:1.4.8-1:podproces zainstalowany 
skrypt post-installation zwrócił kod błędu 100
  ErrorMessage: podproces zainstalowany skrypt post-installation zwrócił kod 
błędu 100
  InstallationDate: Installed on 2014-05-29 (390 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130609)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: modemmanager
  Title: package modemmanager 1.4.8-1 failed to install/upgrade: podproces 
zainstalowany skrypt post-installation zwrócił kod błędu 100
  UpgradeStatus: Upgraded to wily on 2015-06-23 (0 days ago)

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

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

[Touch-packages] [Bug 1457204] Re: package modemmanager 1.4.8-1 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 100 terug

[Brian Murray]

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

** This bug is no longer a duplicate of bug 1453339
   package modemmanager 1.4.8-1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 100
** This bug has been marked a duplicate of bug 1481798
   package:modemmanager:1.4.10-1:subprocess installed post-installation script 
returned error exit status 100

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

Title:
  package modemmanager 1.4.8-1 failed to install/upgrade: subproces
  post-installation script geïnstalleerd  gaf een foutwaarde 100 terug

Status in modemmanager package in Ubuntu:
  New

Bug description:
  No details

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: modemmanager 1.4.8-1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu2
  Architecture: amd64
  Date: Wed May 20 21:22:59 2015
  DuplicateSignature: package:modemmanager:1.4.8-1:subproces post-installation 
script geïnstalleerd  gaf een foutwaarde 100 terug
  ErrorMessage: subproces post-installation script geïnstalleerd  gaf een 
foutwaarde 100 terug
  InstallationDate: Installed on 2015-05-09 (11 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.9ubuntu1
  SourcePackage: modemmanager
  Title: package modemmanager 1.4.8-1 failed to install/upgrade: subproces 
post-installation script geïnstalleerd  gaf een foutwaarde 100 terug
  UpgradeStatus: Upgraded to wily on 2015-05-20 (0 days ago)

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

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

[Touch-packages] [Bug 1483913] Re: modemmanager crashes during wily upgrade and stops everything

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1481798
   package:modemmanager:1.4.10-1:subprocess installed post-installation script 
returned error exit status 100

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

Title:
  modemmanager crashes during wily upgrade and stops everything

Status in modemmanager package in Ubuntu:
  New

Bug description:
  During an upgrade from 15.04 to 15.10, modemmanager fails with:

  Error in function:
  Setting up modemmanager (1.4.10-1) ...
  invoke-rc.d: unknown initscript, /etc/init.d/modemmanager not found.
  dpkg: error processing package modemmanager (--configure):
   subprocess installed post-installation script returned error exit status 100

  
  and then the upgrade process stops dead.

  old version: modemmanager 1.4.0-1
  new version: modemmanager 1.4.10-1

  Ubuntu Wily Werewolf (development branch)
  Ubuntu 15.10
  linux 3.19.0-25 i686

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: modemmanager 1.4.10-1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic i686
  ApportVersion: 2.18-0ubuntu6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Tue Aug 11 18:13:09 2015
  InstallationDate: Installed on 2015-06-27 (45 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release i386 
(20150422.1)
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to wily on 2015-08-11 (0 days ago)

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

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

[Touch-packages] [Bug 1481798] Re: package:modemmanager:1.4.10-1:subprocess installed post-installation script returned error exit status 100

[Launchpad Bug Tracker]

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

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

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

Title:
  package:modemmanager:1.4.10-1:subprocess installed post-installation
  script returned error exit status 100

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding modemmanager.  This problem was most recently seen with
  version 1.4.10-1, the problem page at
  https://errors.ubuntu.com/problem/abc807de9d9c87d965fea31c865192edb30b6738
  contains more details.

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

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

[Touch-packages] [Bug 1470572] Re: native-origins.d information causes apport to strip origin information from Package

[Brian Murray]

And it also looks good on Trusty.

(trusty-amd64)root@impulse:/home/bdmurray# grep Package 
/tmp/apport.thunderbird.vimk8rjs.apport
Package: thunderbird 1:40.0~b1+build3-0ubuntu0.14.04.1 [origin: 
LP-PPA-mozillateam-thunderbird-next]
PackageArchitecture: amd64
SourcePackage: thunderbird
(trusty-amd64)root@impulse:/home/bdmurray# apt-cache policy apport
apport:
  Installed: 2.14.1-0ubuntu3.12
  Candidate: 2.14.1-0ubuntu3.12
  Version table:
 *** 2.14.1-0ubuntu3.12 0
500 http://192.168.10.7/ubuntu/ trusty-proposed/main amd64 Packages
100 /var/lib/dpkg/status


** Tags removed: verification-needed
** Tags added: verificaiton-done-vivid verification-done-trusty

** Tags removed: verificaiton-done-vivid
** Tags added: verification-done-vivid

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

Title:
  native-origins.d information causes apport to strip origin information
  from Package

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Committed
Status in apport source package in Vivid:
  Fix Committed

Bug description:
  I've discovered that if you have a file in /etc/apport/native-
  origins.d/ for a PPA then that origin information is stripped from the
  Package field of the report.

  Test Case
  1) Ensure that /etc/apport/native-origins.d/thunderbird contains 
LP-PPA-mozillateam-thunderbird-next
  2) sudo add-apt-repository ppa:mozillateam/thunderbird-next
  3) sudo apt-get update
  4) sudo apt-get install thunderbird
  5) ubuntu-bug thunderbird (apport-cli thunderbird)
  6) view package field in the report

  Package: thunderbird 1:38.0~b6+build2-0ubuntu1

  Instead I would expect the Package field to contain a "[origin: LP-
  PPA-mozillateam-thunderbird-next]" after the Package name.
  Additionally, my branch to retrace packages from PPAs depends on the
  origin information being there.

  Discussing this with pitti he said that "this needs fixing".

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

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

[Touch-packages] [Bug 1470572] Re: native-origins.d information causes apport to strip origin information from Package

[Brian Murray]

This looks good on vivid.

(vivid-amd64)root@impulse:/home/bdmurray# grep "Package" 
/tmp/apport.thunderbird.li0mhy1d.apport
Package: thunderbird 1:40.0~b1+build3-0ubuntu0.15.04.1 [origin: 
LP-PPA-mozillateam-thunderbird-next]
PackageArchitecture: amd64
SourcePackage: thunderbird
(vivid-amd64)root@impulse:/home/bdmurray# apt-cache policy apport
apport:
  Installed: 2.17.2-0ubuntu1.3
  Candidate: 2.17.2-0ubuntu1.3
  Version table:
 *** 2.17.2-0ubuntu1.3 0
500 http://192.168.10.7/ubuntu/ vivid-proposed/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  native-origins.d information causes apport to strip origin information
  from Package

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Committed
Status in apport source package in Vivid:
  Fix Committed

Bug description:
  I've discovered that if you have a file in /etc/apport/native-
  origins.d/ for a PPA then that origin information is stripped from the
  Package field of the report.

  Test Case
  1) Ensure that /etc/apport/native-origins.d/thunderbird contains 
LP-PPA-mozillateam-thunderbird-next
  2) sudo add-apt-repository ppa:mozillateam/thunderbird-next
  3) sudo apt-get update
  4) sudo apt-get install thunderbird
  5) ubuntu-bug thunderbird (apport-cli thunderbird)
  6) view package field in the report

  Package: thunderbird 1:38.0~b6+build2-0ubuntu1

  Instead I would expect the Package field to contain a "[origin: LP-
  PPA-mozillateam-thunderbird-next]" after the Package name.
  Additionally, my branch to retrace packages from PPAs depends on the
  origin information being there.

  Discussing this with pitti he said that "this needs fixing".

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

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

[Touch-packages] [Bug 1485115] [NEW] Event date on gallery displays AAA instead of year

[Dan González Rodríguez]

Public bug reported:

Device bq Aquaris 4.5 Ubuntu Edition (krillin r24)

When system language is configured as "Spanish (Spain)" every date square on 
event view displays the string "AAA" instead the year.
Photos and videos are correctly grouped.

This seems to be some translation problem (just guessing) since when
language is "Engligh (United States)" year displays as expected.

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

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

Title:
  Event date on gallery displays AAA instead of year

Status in gallery-app package in Ubuntu:
  New

Bug description:
  Device bq Aquaris 4.5 Ubuntu Edition (krillin r24)

  When system language is configured as "Spanish (Spain)" every date square on 
event view displays the string "AAA" instead the year.
  Photos and videos are correctly grouped.

  This seems to be some translation problem (just guessing) since when
  language is "Engligh (United States)" year displays as expected.

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

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

[Touch-packages] [Bug 1270257] Re: NetworkManager failed to function after suspend and resume

[Seth Arnold]

Andre, as I described in the previous comment, this bug is now useless
because it has been abused for too many tasks.

Please file a new bug, so that your logs and information can be
collected.

Thanks.

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

Title:
  NetworkManager failed to function after suspend and resume

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  NetworkManager failed to function after resuming from suspend. The
  indicator applet in the Mac OS style menu bar showed the empty
  quarter-circle, and clicking "Enable Networking" didn't change the
  menu options or the style of the applet. Running "sudo service
  network-manager restart" brought back functionality.

  $ dpkg -l systemd* logind*
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==
  un  logind (no description 
available)
  un  systemd(no description 
available)
  ii  systemd-services   204-0ubuntu19.1  amd64systemd runtime 
services
  ii  systemd-shim   6-0ubuntu0.13.10 amd64shim for systemd

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu22
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Fri Jan 17 10:08:48 2014
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-10-18 (456 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.14  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-11-06 (72 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-05T17:49:23
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1479445] Re: IN CAR: Signal Strength not shown in car display

[Michał Sawicz]

I found this working in my car with rc-proposed, so it must've landed in
the overlay?

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

Title:
  IN CAR: Signal Strength not shown in car display

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu RTM:
  New

Bug description:
  STEPS:
  Requirement: DUT with active sim and car that supports Bluetooth phones 
(Skoda Superb 2013 in my case)

  1. Connect the DUT to the car
  2. Check the console display for the strength of signal

  EXPECTED:
  I expect the display to show a similar strength to that on the phone

  ACTUAL:
  The signal strength is always at 0% however the display does show the Network 
connected to so there is some sort of feedback via bluetooth that there is a 
connection.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

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

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

[Touch-packages] [Bug 1485107] [NEW] white flickering line when open nautilus app 14.04 and 15.04

[Stasia]

Public bug reported:

When minimize a window and open again a white flickering line shows up.
I've made a video that illustrates this bug perfectly - 
https://youtu.be/yMj0JYQ3zZs 
True for 14.04 32 bit and 15.04 64 bit.

** 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/1485107

Title:
  white flickering line when open nautilus app 14.04 and 15.04

Status in unity package in Ubuntu:
  New

Bug description:
  When minimize a window and open again a white flickering line shows up.
  I've made a video that illustrates this bug perfectly - 
https://youtu.be/yMj0JYQ3zZs 
  True for 14.04 32 bit and 15.04 64 bit.

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

-- 
Mailing list: https://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 1465826] Re: The phone freez totally

[Magyar Csaba]

Hi,

I can't send you the file because of the below error.

"sudo adb shell
error: device not found"

BR,

Csaba Magyar


2015-07-31 19:45 keltezéssel, Gerry Boland írta:
> Hey,
> If this happens again, please connect your phone to your computer with USB, 
> use "adb shell" from a terminal to get a shell on your phone. Then do
>
> kill -SEGV `pidof unity8`
>
> This will make unity8 crash in the hung state it is in, and apport will
> do its job of uploading the crash file to us.
>
> To point us to the uploaded crash file, on your phone, please
> 1. open System Settings and go to Security & Privacy -> Diagnostics -> 
> Previous error reports
> 2. the web browser will open on a page, this contains all the crashes that 
> were uploaded from your device
> Could you grab this URL and share it with us please. For information security 
> reasons, you're welcome to email me the URL directly at 
> gerry.bol...@canonical.com
>
> Thanks
> -Gerry
>

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

Title:
  The phone freez totally

Status in QtMir:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I want to change between 2 application( dekko to web browser) , but the phone 
complcompletely freez.
  After ~20 minutes I restarted the phone.(pushed the ON buttone until restart)

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

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

[Touch-packages] [Bug 1484178] Re: Policy cache file mtimes are not being set correctly

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.10-0ubuntu3

---
apparmor (2.10-0ubuntu3) wily; urgency=medium

  * debian/patches/parser-fix-cache-file-mtime-regression.patch: Fix a bug
that resulted in the mtime of generate policy cache files to be set
incorrectly. The mtime of cache files should be the newest mtime detected
on the profile and abstraction files used to generate the policy cache
file. However, the bug caused the mtime of the policy cache file to either
not be updated or to be updated to an incorrect time. (LP: #1484178)
  * debian/patches/parser-verify-cache-file-mtime.patch: Add tests to verify
that the policy cache file's mtime is being set correctly and that cache
handling is correct when the profile or abstraction files are newer than
the policy cache file.
  * debian/patches/parser-run-caching-tests-without-apparmorfs.patch,
debian/patches/parser-do-cleanup-when-test-was-skipped.patch: Enable the
caching tests to run on the buildds even though apparmorfs isn't mounted.

 -- Tyler Hicks   Wed, 12 Aug 2015 13:01:56 -0500

** Changed in: apparmor (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Policy cache file mtimes are not being set correctly

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  Oliver Grawert (ogra) reported that Ubuntu Touch image builds were
  failing due to incorrect timestamps on pre-compiled policy cache
  files.

  Starting in AppArmor 2.10, the policy cache file's mtime was meant to be 
updated to be equal to the newest mtime detected
  on the profile and abstraction files used to generate the policy cache file:

http://bazaar.launchpad.net/~apparmor-
  dev/apparmor/master/revision/3079

  That change was not correct and resulted in the mtime of the policy
  cache file to either not be updated (equal to the policy cache file
  creation time) or to be updated to an incorrect time.

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

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

[Touch-packages] [Bug 1485101] [NEW] add FindValgrind.cmake to cmake-extras

[Antti Kaijanmäki]

Public bug reported:

in source tree cmake/FindValgrind.cmake is not part of cmake-extras.

This module is universally usable and thus should be added to cmake-
extras.

** Affects: cmake-extras (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: indicator-network (Ubuntu)
 Importance: Low
 Status: Confirmed

** Also affects: cmake-extras (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cmake-extras (Ubuntu)
   Status: New => Confirmed

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

Title:
  add FindValgrind.cmake to cmake-extras

Status in cmake-extras package in Ubuntu:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  in source tree cmake/FindValgrind.cmake is not part of cmake-extras.

  This module is universally usable and thus should be added to cmake-
  extras.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cmake-extras/+bug/1485101/+subscriptions

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

[Touch-packages] [Bug 1485095] Re: package systemd 219-7ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1485095

Title:
  package systemd 219-7ubuntu6 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  Raspberry Pi 2 running Ubuntu-Mate 15.04

  sudo apt-get install nut-client
  [sudo] password for grussell: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
libupsclient3
  Suggested packages:
nut-monitor
  The following NEW packages will be installed:
libupsclient3 nut-client
  0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
  Need to get 138 kB of archives.
  After this operation, 638 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 http://ports.ubuntu.com/ vivid/main libupsclient3 armhf 2.7.1-1ubuntu4 
[56.5 kB]
  Get:2 http://ports.ubuntu.com/ vivid/main nut-client armhf 2.7.1-1ubuntu4 
[81.8 kB]
  Fetched 138 kB in 2s (58.6 kB/s) 
  Selecting previously unselected package libupsclient3:armhf.
  (Reading database ... 145663 files and directories currently installed.)
  Preparing to unpack .../libupsclient3_2.7.1-1ubuntu4_armhf.deb ...
  Unpacking libupsclient3:armhf (2.7.1-1ubuntu4) ...
  Selecting previously unselected package nut-client.
  Preparing to unpack .../nut-client_2.7.1-1ubuntu4_armhf.deb ...
  Unpacking nut-client (2.7.1-1ubuntu4) ...
  Processing triggers for systemd (219-7ubuntu6) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for man-db (2.7.0.2-5) ...
  Setting up libupsclient3:armhf (2.7.1-1ubuntu4) ...
  Setting up nut-client (2.7.1-1ubuntu4) ...
  Failed to execute operation: Connection timed out
  Failed to start nut-client.service: Connection timed out
  invoke-rc.d: initscript nut-client, action "start" failed.
  dpkg: error processing package nut-client (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for libc-bin (2.21-0ubuntu4) ...
  Processing triggers for systemd (219-7ubuntu6) ...
  Failed to execute operation: Connection timed out
  dpkg: error processing package systemd (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for ureadahead (0.100.0-19) ...
  Errors were encountered while processing:
   nut-client
   systemd
  Error: Timeout was reached

  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.18.0-25.26-rpi2 3.18.17
  Uname: Linux 3.18.0-25-rpi2 armv7l
  ApportVersion: 2.17.2-0ubuntu1.2
  AptOrdering:
   libupsclient3: Install
   nut-client: Install
   libupsclient3: Configure
   nut-client: Configure
   NULL: ConfigurePending
  Architecture: armhf
  Date: Fri Aug 14 15:22:38 2015
  DuplicateSignature: package:systemd:219-7ubuntu6:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  Lsusb:
   Bus 001 Device 004: ID 13ba:0018 PCPlay Barcode PCP-BCG4209
   Bus 001 Device 005: ID 3938:1032  
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1920 
bcm2708_fb.fbheight=1080 bcm2709.boardrev=0xa01041 bcm2709.serial=0x82cca91e 
smsc95xx.macaddr=B8:27:EB:CC:A9:1E bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 
vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00  dwc_otg.lpm_enable=0 
console=tty1 root=/dev/mmcblk0p2 elevator=deadline rootwait
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: systemd
  Title: package systemd 219-7ubuntu6 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1485095] [NEW] package systemd 219-7ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Gregory W. Russell]

Public bug reported:

Raspberry Pi 2 running Ubuntu-Mate 15.04

sudo apt-get install nut-client
[sudo] password for grussell: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following extra packages will be installed:
  libupsclient3
Suggested packages:
  nut-monitor
The following NEW packages will be installed:
  libupsclient3 nut-client
0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 138 kB of archives.
After this operation, 638 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ports.ubuntu.com/ vivid/main libupsclient3 armhf 2.7.1-1ubuntu4 
[56.5 kB]
Get:2 http://ports.ubuntu.com/ vivid/main nut-client armhf 2.7.1-1ubuntu4 [81.8 
kB]
Fetched 138 kB in 2s (58.6 kB/s) 
Selecting previously unselected package libupsclient3:armhf.
(Reading database ... 145663 files and directories currently installed.)
Preparing to unpack .../libupsclient3_2.7.1-1ubuntu4_armhf.deb ...
Unpacking libupsclient3:armhf (2.7.1-1ubuntu4) ...
Selecting previously unselected package nut-client.
Preparing to unpack .../nut-client_2.7.1-1ubuntu4_armhf.deb ...
Unpacking nut-client (2.7.1-1ubuntu4) ...
Processing triggers for systemd (219-7ubuntu6) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for man-db (2.7.0.2-5) ...
Setting up libupsclient3:armhf (2.7.1-1ubuntu4) ...
Setting up nut-client (2.7.1-1ubuntu4) ...
Failed to execute operation: Connection timed out
Failed to start nut-client.service: Connection timed out
invoke-rc.d: initscript nut-client, action "start" failed.
dpkg: error processing package nut-client (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.21-0ubuntu4) ...
Processing triggers for systemd (219-7ubuntu6) ...
Failed to execute operation: Connection timed out
dpkg: error processing package systemd (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for ureadahead (0.100.0-19) ...
Errors were encountered while processing:
 nut-client
 systemd
Error: Timeout was reached

E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: systemd 219-7ubuntu6
ProcVersionSignature: Ubuntu 3.18.0-25.26-rpi2 3.18.17
Uname: Linux 3.18.0-25-rpi2 armv7l
ApportVersion: 2.17.2-0ubuntu1.2
AptOrdering:
 libupsclient3: Install
 nut-client: Install
 libupsclient3: Configure
 nut-client: Configure
 NULL: ConfigurePending
Architecture: armhf
Date: Fri Aug 14 15:22:38 2015
DuplicateSignature: package:systemd:219-7ubuntu6:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
Lsusb:
 Bus 001 Device 004: ID 13ba:0018 PCPlay Barcode PCP-BCG4209
 Bus 001 Device 005: ID 3938:1032  
 Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
 Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1920 
bcm2708_fb.fbheight=1080 bcm2709.boardrev=0xa01041 bcm2709.serial=0x82cca91e 
smsc95xx.macaddr=B8:27:EB:CC:A9:1E bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 
vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00  dwc_otg.lpm_enable=0 
console=tty1 root=/dev/mmcblk0p2 elevator=deadline rootwait
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.1
SourcePackage: systemd
Title: package systemd 219-7ubuntu6 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package armhf vivid

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

Title:
  package systemd 219-7ubuntu6 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  Raspberry Pi 2 running Ubuntu-Mate 15.04

  sudo apt-get install nut-client
  [sudo] password for grussell: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
libupsclient3
  Suggested packages:
nut-monitor
  The following NEW packages will be installed:
libupsclient3 nut-client
  0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
  Need to get 138 kB of archives

[Touch-packages] [Bug 1477759] Re: pyqt5 misbuild with python3.5

[Launchpad Bug Tracker]

This bug was fixed in the package dh-python - 2.20150719ubuntu2

---
dh-python (2.20150719ubuntu2) wily; urgency=medium

  * debian/tests/dh-python: Python 2.6 is uninstallable and unsupported.

 -- Barry Warsaw   Fri, 14 Aug 2015 11:28:09 -0400

** Changed in: dh-python (Ubuntu Wily)
   Status: Fix Committed => Fix Released

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

Title:
  pyqt5 misbuild with python3.5

Status in comedilib package in Ubuntu:
  Fix Released
Status in dh-python package in Ubuntu:
  Fix Released
Status in newt package in Ubuntu:
  Fix Released
Status in pyqt5 package in Ubuntu:
  Fix Released
Status in python3.5 package in Ubuntu:
  Fix Released
Status in comedilib source package in Wily:
  Fix Released
Status in dh-python source package in Wily:
  Fix Released
Status in newt source package in Wily:
  Fix Released
Status in pyqt5 source package in Wily:
  Fix Released
Status in python3.5 source package in Wily:
  Fix Released

Bug description:
  pyqt5 fails its autopkgtests after rebuild with python3.5, with a
  failure to find the enginio module under python3.5:

  testing python3.5
  Traceback (most recent call last):
File "test_import.py", line 1, in 
  from PyQt5.Enginio import EnginioClient
  ImportError: No module named 'PyQt5.Enginio'

  

  This is because the filename is wrong inside the package; the
  architecture string is doubled:

  $ dpkg -L python3-pyqt5.enginio | grep '\.so'
  
/usr/lib/python3/dist-packages/PyQt5/Enginio.cpython-35m-x86_64-linux-gnu-x86_64-linux-gnu.so
  /usr/lib/python3/dist-packages/PyQt5/Enginio.cpython-34m-x86_64-linux-gnu.so
  $

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

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

[Touch-packages] [Bug 1485089] Re: package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100

[Mike McCracken]

see also https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1485090

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

Title:
  package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 100

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  install failure during do-release-upgrade from vivid to wily

  seems to be not a coincidence that maas-dhcp 1.7.6 failed immediately
  after.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: isc-dhcp-server 4.3.1-5ubuntu2.1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  Date: Fri Aug 14 12:10:01 2015
  DhServerLeases:
   
  DuplicateSignature: package:isc-dhcp-server:4.3.1-5ubuntu2.1:subprocess new 
pre-removal script returned error exit status 100
  ErrorMessage: subprocess new pre-removal script returned error exit status 100
  InstallationDate: Installed on 2014-04-15 (485 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta amd64 
(20140326)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=2855a735-f240-4e8a-a2ef-2361fafe8731 ro
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-14 (0 days ago)
  upstart.isc-dhcp-server.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1485089/+subscriptions

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

[Touch-packages] [Bug 1485089] Re: package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100

[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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1485089

Title:
  package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 100

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  install failure during do-release-upgrade from vivid to wily

  seems to be not a coincidence that maas-dhcp 1.7.6 failed immediately
  after.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: isc-dhcp-server 4.3.1-5ubuntu2.1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  Date: Fri Aug 14 12:10:01 2015
  DhServerLeases:
   
  DuplicateSignature: package:isc-dhcp-server:4.3.1-5ubuntu2.1:subprocess new 
pre-removal script returned error exit status 100
  ErrorMessage: subprocess new pre-removal script returned error exit status 100
  InstallationDate: Installed on 2014-04-15 (485 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta amd64 
(20140326)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=2855a735-f240-4e8a-a2ef-2361fafe8731 ro
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-14 (0 days ago)
  upstart.isc-dhcp-server.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1485089/+subscriptions

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

[Touch-packages] [Bug 1485089] [NEW] package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100

[Mike McCracken]

Public bug reported:

install failure during do-release-upgrade from vivid to wily

seems to be not a coincidence that maas-dhcp 1.7.6 failed immediately
after.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: isc-dhcp-server 4.3.1-5ubuntu2.1
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
ApportVersion: 2.18-0ubuntu6
Architecture: amd64
Date: Fri Aug 14 12:10:01 2015
DhServerLeases:
 
DuplicateSignature: package:isc-dhcp-server:4.3.1-5ubuntu2.1:subprocess new 
pre-removal script returned error exit status 100
ErrorMessage: subprocess new pre-removal script returned error exit status 100
InstallationDate: Installed on 2014-04-15 (485 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=2855a735-f240-4e8a-a2ef-2361fafe8731 ro
SourcePackage: isc-dhcp
Title: package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 100
UpgradeStatus: Upgraded to wily on 2015-08-14 (0 days ago)
upstart.isc-dhcp-server.override: manual

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


** Tags: amd64 apport-package dist-upgrade wily

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

Title:
  package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 100

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  install failure during do-release-upgrade from vivid to wily

  seems to be not a coincidence that maas-dhcp 1.7.6 failed immediately
  after.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: isc-dhcp-server 4.3.1-5ubuntu2.1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  Date: Fri Aug 14 12:10:01 2015
  DhServerLeases:
   
  DuplicateSignature: package:isc-dhcp-server:4.3.1-5ubuntu2.1:subprocess new 
pre-removal script returned error exit status 100
  ErrorMessage: subprocess new pre-removal script returned error exit status 100
  InstallationDate: Installed on 2014-04-15 (485 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta amd64 
(20140326)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=2855a735-f240-4e8a-a2ef-2361fafe8731 ro
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-14 (0 days ago)
  upstart.isc-dhcp-server.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1485089/+subscriptions

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

[Touch-packages] [Bug 1367137] Re: [Icons] In "Updates" list, Ubuntu icon is blurry

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
14.04+15.10.20150813-0ubuntu1

---
ubuntu-themes (14.04+15.10.20150813-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Matthieu James ]
  * This update include a few bug fixes that we chased during our design
team bug sprint in August 2015: essentially a bunch of new mono
icons and updated existing designs. (LP: #1367137, #1478025,
#1294251, #1424819, #1431876)

 -- CI Train Bot   Thu, 13 Aug 2015 15:06:02
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Fix Released

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

Title:
  [Icons] In "Updates" list, Ubuntu icon is blurry

Status in Ubuntu theme:
  Fix Committed
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 14.10 r22

  1. Wait for an Ubuntu update to become available.
  2. Navigate to System Settings > "Updates".
  3. Look at the Ubuntu icon.

  What you see: The icon is blurry.

  What you should see: The icon should be sharp.

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

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

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

[Touch-packages] [Bug 1478025] Re: Speaker icons differences too small

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
14.04+15.10.20150813-0ubuntu1

---
ubuntu-themes (14.04+15.10.20150813-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Matthieu James ]
  * This update include a few bug fixes that we chased during our design
team bug sprint in August 2015: essentially a bunch of new mono
icons and updated existing designs. (LP: #1367137, #1478025,
#1294251, #1424819, #1431876)

 -- CI Train Bot   Thu, 13 Aug 2015 15:06:02
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Speaker icons differences too small

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  The icon theme got a nice update that made them all much lighter (as
  in weight), but also resulted in some of them being less readable,
  especially in a bright environment (aka. very often when you use a
  phone outside).

  See the attached image that's a combination of high volume, low volume
  and muted. The stroke through the muted speaker is very light, almost
  a one-pixel stroke on the Aquaris E4.5 phone, where the icons are
  displayed at 26x26 pixels. The volume indication (the two arches on
  the right of the speaker) seems unnecessary when muted, too, and just
  add confusion.

  In the low-volume case the arches seem equally unnecessary, since
  apart from spotting the arches you need to compare their colour to see
  "how much" of the indication is active vs. not. Could we not lose the
  inactive arches altogether?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: suru-icon-theme 14.04+15.04.20150707-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: armhf
  Date: Fri Jul 24 15:38:03 2015
  Dependencies:
   hicolor-icon-theme 0.14-0ubuntu1 [origin: unknown]
   ubuntu-mobile-icons 14.04+15.04.20150707-0ubuntu1
  InstallationDate: Installed on 2015-07-23 (1 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20150723-020304)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1230391] Re: please provide visual cue during background recording

[Jamie Strandboge]

Please see
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1224756/comments/36

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

Title:
  please provide visual cue during background recording

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

Bug description:
  After bug #1224756 is fixed, we should provide a visual cue for when
  an app moves to the background and is recording audio. This will allow
  an app like Skype to work normally in the foreground, but if the user
  launches another app into the foreground, the user is able to see that
  he/she is still on the Skype call. In addition to the usability
  benefit, this provides a security benefit because it stops
  eavesdropping because the user will have a visual cue that the
  malicious/misbehaving app is recording audio.

  This needs design.

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

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

[Touch-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store

[Jamie Strandboge]

Both pulseaudio and the camera service processes are out-of-process from
the app and therefore not themselves governed by app lifecycle. If app
lifecycle made sure to stop recording of audio and/or video when the app
is backgrounded, then a visual cue is arguably not required (see my note
below). If recording is not stopping when the app is backgrounded, we
need to let the user know (eg, like what we do with the dialer now).
Either route is fine from a security perspective, however, allowing the
continuation of recording in the background with a visual cue might
provide more utility.

Note: I personally feel we should be giving a visual cue (even if its
temporary (consider full screen app)) when any recording is happening--
this is subject for debate and needs design input.

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

Title:
  Pulseaudio should integrate with trust-store

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

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user ("Foo wants to use
  the microphone. Is this ok? Yes|No"), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If the app is 
allowed to do networking (the default for apps), then it can ship that 
information off to a server somewhere.

  Note 1, the alert to indicator-sound must happen via the out of
  process pulseaudio server and not the confined app itself to be
  effective.

  Note 2, we should consider how to enforce this for foreground apps
  only. Application lifecycle should probably handle this for 13.10
  (apps are suspended if not in foreground or if the screensaver is on),
  but we don't want an app on the converged device to record in the
  background when the user isn't paying attention. Example eavesdropping
  attack: start recording only when the screensaver is on (perhaps
  inhibiting the screensaver during recording would be enough).

  : "On the phone, if
  an app tries to access your ... microphone ... or video recording,
  this should be subject to permission. “Video recording” should be
  separate from “Camera” so that an app does not need two permissions
  when recording video, one for the camera and one for the microphone.
  If an app has permission to record video, it should have access to the
  microphone whenever it is recording video..."

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

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

[Touch-packages] [Bug 1439757] Re: Calendar does not display birthdays from address book

[Launchpad Bug Tracker]

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

** Changed in: qtorganizer5-eds (Ubuntu)
   Status: New => Confirmed

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

Title:
  Calendar does not display birthdays from address book

Status in Ubuntu Calendar App:
  Confirmed
Status in qtorganizer5-eds package in Ubuntu:
  Confirmed

Bug description:
  The calendar app does not display birthdays from my address book. They
  are stored in the contacts, so I guess they should be in the virtual
  Birthdays and Anniversaries calendar, but the calendar app does not
  display any events from that calendar.

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

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

[Touch-packages] [Bug 1485021] Re: Can't review apps from inside the store

[Michael Terry]

The problem is submitting new reviews (haven't tried comparing attempts
to edit reviews in both yet).

It works from the Apps scope, but not the Store scope.

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

Title:
  Can't review apps from inside the store

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  I can rate installed apps in the dash just fine.  But when I try to
  review an installed app from the store itself, it appears to let me do
  it, but the review never shows up.

  
  current build number: 22
  device name: mako
  channel: ubuntu-touch/stable/ubuntu
  last update: 2015-07-28 09:09:39
  version version: 22
  version ubuntu: 20150727.1
  version device: 20150210
  version custom: 20150713

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

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

[Touch-packages] [Bug 1485028] Re: Aggregate rating number not updating

[Rodney Dawes]

** Package changed: unity-scope-click (Ubuntu) => software-center-agent

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

Title:
  Aggregate rating number not updating

Status in Software Center Agent:
  New

Bug description:
  If you look at the Games department, you'll see "blamepopey" is listed
  first, with an aggregate rating of 5.0.  But if you click on it,
  you'll see it has three reviews: one 5.0 and two 1.0s.  Surely that
  doesn't add up to 5.0 average?

  (As one of the 1.0 reviewers, please don't take this report as part of
  an anti-blamepopey campaign, I just noticed the oddity and worried
  there was a store-wide bug.  :))

  current build number: 22
  device name: mako
  channel: ubuntu-touch/stable/ubuntu
  last update: 2015-07-28 09:09:39
  version version: 22
  version ubuntu: 20150727.1
  version device: 20150210
  version custom: 20150713

To manage notifications about this bug go to:
https://bugs.launchpad.net/software-center-agent/+bug/1485028/+subscriptions

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

[Touch-packages] [Bug 1485021] Re: Can't review apps from inside the store

[Rodney Dawes]

The problem is with submitting new reviews? Or you have this problem
only with editing reviews?

Also, when you say "in the dash," do you mean from the Apps scope, as
opposed to the Store scope? Both of these scopes use the exact same code
to build the previews, so it would be quite odd to have it working fine
in one, but not the other.

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

Title:
  Can't review apps from inside the store

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  I can rate installed apps in the dash just fine.  But when I try to
  review an installed app from the store itself, it appears to let me do
  it, but the review never shows up.

  
  current build number: 22
  device name: mako
  channel: ubuntu-touch/stable/ubuntu
  last update: 2015-07-28 09:09:39
  version version: 22
  version ubuntu: 20150727.1
  version device: 20150210
  version custom: 20150713

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

-- 
Mailing list: https://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 1224756] Re: Pulseaudio should integrate with trust-store

[John McAleely]

certainly. is there actually any way to *do* background recording, in the
current app lifecycle?

On 14 August 2015 at 19:23, Jamie Strandboge  wrote:

> Should bug #1230391 be revisited now that this is landing (show a visual
> cue if background recording)?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1224756
>
> Title:
>   Pulseaudio should integrate with trust-store
>
> Status in Canonical System Image:
>   In Progress
> Status in pulseaudio package in Ubuntu:
>   In Progress
>
> Bug description:
>   Currently the 'audio' policy group allows access to pulseaudio which
>   allows apps to use the microphone and eavesdrop on the user.
>   Pulseaudio needs to be modified to use trust-store, like location-
>   service does. Integrating with trust-store means that when an app
>   tries use the microphone via pulseaudio, pulseaudio will contact
>   trust-store, the trust-store will prompt the user ("Foo wants to use
>   the microphone. Is this ok? Yes|No"), optionally cache the result and
>   return the result to pulseaudio. In this manner the user is given a
>   contextual prompt at the time of access by the app. Using caching this
>   decision can be remembered the next time. If caching is used, there
>   should be a method to change the decision in settings.
>
>   Targeting to T-Series for now, since the trust-store is not in a
>   reusable form yet.
>
>   Original description:
>   David and the security team (inspired by an observation from Rick)
> discussed that when recording, pulseaudio should somehow unobtrusively show
> the user that it is recording. The easiest thing to do would be for
> pulseaudio to alert indicator-sound which would then turn its icon red
> (similar to indicator-message turning blue with new messages). Marking
> 'high' because apps with access to pulseaudio can currently eavedrop on
> users. If the app is allowed to do networking (the default for apps), then
> it can ship that information off to a server somewhere.
>
>   Note 1, the alert to indicator-sound must happen via the out of
>   process pulseaudio server and not the confined app itself to be
>   effective.
>
>   Note 2, we should consider how to enforce this for foreground apps
>   only. Application lifecycle should probably handle this for 13.10
>   (apps are suspended if not in foreground or if the screensaver is on),
>   but we don't want an app on the converged device to record in the
>   background when the user isn't paying attention. Example eavesdropping
>   attack: start recording only when the screensaver is on (perhaps
>   inhibiting the screensaver during recording would be enough).
>
>   : "On the phone, if
>   an app tries to access your ... microphone ... or video recording,
>   this should be subject to permission. “Video recording” should be
>   separate from “Camera” so that an app does not need two permissions
>   when recording video, one for the camera and one for the microphone.
>   If an app has permission to record video, it should have access to the
>   microphone whenever it is recording video..."
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1224756/+subscriptions
>

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

Title:
  Pulseaudio should integrate with trust-store

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

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user ("Foo wants to use
  the microphone. Is this ok? Yes|No"), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If

[Touch-packages] [Bug 1230391] Re: please provide visual cue during background recording

[John McAleely]

I am currently aware of no way for an application to record 'in the
background' due to the app lifecycle.

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

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

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

Title:
  please provide visual cue during background recording

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

Bug description:
  After bug #1224756 is fixed, we should provide a visual cue for when
  an app moves to the background and is recording audio. This will allow
  an app like Skype to work normally in the foreground, but if the user
  launches another app into the foreground, the user is able to see that
  he/she is still on the Skype call. In addition to the usability
  benefit, this provides a security benefit because it stops
  eavesdropping because the user will have a visual cue that the
  malicious/misbehaving app is recording audio.

  This needs design.

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

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

[Touch-packages] [Bug 1471338] Re: sometimes phone never wakes up or rings on incoming call

[Launchpad Bug Tracker]

** Branch linked: lp:~boiko/telephony-service/fix_1471338

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

Title:
  sometimes phone never wakes up or rings on incoming call

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

Bug description:
  testing on krilin build 56 vivid+overlay latest
  dual sims installed

  The problem is sometimes during an incoming call the phone never wakes
  up or rings at all (and no snap decision). From the remote end the
  call just continues to ring and eventually goes to voicemail. When
  this occurs the signal strength appears to have at least 3 bars.

  It seems ofono is not notifying the upper layers that a call is incoming. 
This can be verifed by running the following command:
  dbus-monitor --system | grep CallAdded

  This never gets fired during error condition when the incoming call is
  ringing from remote end.

  Attached is the ofono log when I got it to happen once (not sure where
  in the log corresponds to the failure)

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

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

[Touch-packages] [Bug 1230366] Re: Please provide Ubuntu camera service that integrates with trust-store

[Jamie Strandboge]

Should bug #1230391 be revisited now that this is landing (show a visual
cue if background recording)?

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

Title:
  Please provide Ubuntu camera service that integrates with trust-store

Status in Canonical System Image:
  In Progress
Status in qtubuntu-camera package in Ubuntu:
  Triaged
Status in qtubuntu-camera package in Ubuntu RTM:
  Invalid

Bug description:
  Currently Ubuntu Touch is using the android camera-service and that is
  the plan for 13.10.

  Going forward in 14.04, the android camera-service will no longer be
  used and camera access is going to move to the Ubuntu side. There was
  discussion of either using HAL directly (direct access to devices) or
  using a camera-service type thing in Ubuntu.

  Using devices directly causes at least a few problems:
   * can't prevent more than one user from accessing the device at a time
   * enumerating camera devices for apparmor policy is extra maintenance for 
porters
   * can't provide a contextual runtime prompt for access (like we (will) do 
with online accounts, location, microphone). This is particularly important for 
application confinement.

  Instead of direct hardware access, an out of process helper (in
  relation to the app) can be used to address all of these problems,
  similar to what pulseaudio does for audio. This service can ensure
  only one user can access the device at a time and since the service
  accesses the the device files on the app's behalf, we don't need to
  enumerate devices in /dev in policy. Furthermore, when an app accesses
  the service (ideally over DBus), the service can contact trust-store,
  the trust-store will prompt the user ("Foo wants to access the camera.
  Is this ok? Yes|No"), then optionally cache the result and return the
  result to the service. In this manner the user is given a contextual
  prompt at the time of access by the app. By using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in system settings.

  If direct hardware access is needed for performance reasons, it is
  possible to use fd delegation in AppArmor and have the service open
  the device and pass the fd to the app without having to enumerate the
  /dev devices. Please talk to jjohansen if pursuing this option.

  Lastly, bug #1230391 discusses providing a visual cue during
  background recording for audio. We will need to do the same for video
  recording. Feel free to add a task to bug #1230391 if there is work to
  integrate this new service with that visual cuing.

  This should be implemented in time for shippable devices to address
  the application confinement concern.

  : "On the
  phone, if an app tries to access your ... camera ... or video
  recording, this should be subject to permission..."

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

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

[Touch-packages] [Bug 1230391] Re: please provide visual cue during background recording

[Jamie Strandboge]

FYI, pulseaudio (bug #1224756) and the camera-service (bug #1230366) are
in the process of landing with trust-store integration. Should this bug
be looked at again now?

** Also affects: qtubuntu-camera (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  please provide visual cue during background recording

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in qtubuntu-camera package in Ubuntu:
  New

Bug description:
  After bug #1224756 is fixed, we should provide a visual cue for when
  an app moves to the background and is recording audio. This will allow
  an app like Skype to work normally in the foreground, but if the user
  launches another app into the foreground, the user is able to see that
  he/she is still on the Skype call. In addition to the usability
  benefit, this provides a security benefit because it stops
  eavesdropping because the user will have a visual cue that the
  malicious/misbehaving app is recording audio.

  This needs design.

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

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

[Touch-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store

[Jamie Strandboge]

Should bug #1230391 be revisited now that this is landing (show a visual
cue if background recording)?

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

Title:
  Pulseaudio should integrate with trust-store

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

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user ("Foo wants to use
  the microphone. Is this ok? Yes|No"), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If the app is 
allowed to do networking (the default for apps), then it can ship that 
information off to a server somewhere.

  Note 1, the alert to indicator-sound must happen via the out of
  process pulseaudio server and not the confined app itself to be
  effective.

  Note 2, we should consider how to enforce this for foreground apps
  only. Application lifecycle should probably handle this for 13.10
  (apps are suspended if not in foreground or if the screensaver is on),
  but we don't want an app on the converged device to record in the
  background when the user isn't paying attention. Example eavesdropping
  attack: start recording only when the screensaver is on (perhaps
  inhibiting the screensaver during recording would be enough).

  : "On the phone, if
  an app tries to access your ... microphone ... or video recording,
  this should be subject to permission. “Video recording” should be
  separate from “Camera” so that an app does not need two permissions
  when recording video, one for the camera and one for the microphone.
  If an app has permission to record video, it should have access to the
  microphone whenever it is recording video..."

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

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

[Touch-packages] [Bug 1485073] Re: Windows in "Show Desktop" mode lose decorations

[Andrea Azzarone]

** Changed in: unity
Milestone: None => 6.16.0

** Changed in: unity
Milestone: 6.16.0 => 7.3.3

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

Title:
  Windows in "Show Desktop" mode lose decorations

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  In Progress

Bug description:
  1. Open two windows of a same application
  2. Click on "show desktop"
  3. Click on the application icon
  4. Click again on the application icon

  One windows has no decorations. This is also causes a glitch during
  the fade out effect.

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

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

[Touch-packages] [Bug 1468680] Re: The warning dialog is doesn't presented

[Charles Kerr]

This is fixed as a part of the fix for bug #1481913

** Changed in: indicator-sound (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

** Changed in: indicator-sound (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: indicator-sound (Ubuntu)
   Status: Fix Released => In Progress

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

Title:
  The warning dialog is doesn't presented

Status in indicator-sound package in Ubuntu:
  In Progress

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: 2015062
  version device: 20150608-6e66f3c
  version custom: 20150602-731-5-32

  Reproduce steps:

  1,Play a music file
  2,Press the volume up key until maximum reached
  3,Check that a volume warning dialog is presented

  Expect Result:

  The volume warning dialog is present

  Actual Result:

  The volume warning dialog is not present

  : "...whenever volume is at a
  high level, any headphones volume bubble instead of saying
  “Headphones” should say “High volume”, and the bar should be colored."

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

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

[Touch-packages] [Bug 427100] Re: JPEG2000 thumbnail causes browser to crash

[Markus Majer]

You can add the tag "vivid"..
The bug still exists in Ubuntu 15.04!

Please fix it, because it also can used for other bad things besides just 
crashing Nautilus:
http://www.ubuntu.com/usn/usn-1315-1/

Here my dmesg output:
[ 9415.337774] nautilus[11166]: segfault at 7f4d50c5c540 ip 7f4d28a3701c sp 
7f4d50c5c530 error 7 in libjasper.so.1.0.0[7f4d28a1+4c000]
[ 9666.642346] nautilus[11391]: segfault at 7f01295a4540 ip 7f00f39ca01c sp 
7f01295a4530 error 6 in libjasper.so.1.0.0[7f00f39a3000+4c000]
[ 9685.330281] nautilus[11438]: segfault at 7f778a096540 ip 7f7789c9301c sp 
7f778a096530 error 6 in libjasper.so.1.0.0[7f7789c6c000+4c000]
[11242.749456] nautilus[14785]: segfault at 7f7f29a9b540 ip 7f7f0064201c sp 
7f7f29a9b530 error 6 in libjasper.so.1.0.0[7f7f0061b000+4c000]
[11373.131440] nautilus[14976]: segfault at 7fca7d85f430 ip 7fca5c3c601c sp 
7fca7d85f420 error 6 in libjasper.so.1.0.0[7fca5c39f000+4c000]

I can also confirm that it affects JPEG2000 files with transparency.

I had a hard time to figure out the problem and extract the file that was the 
reason. 
I moved it to a seperate folder with the console and opened it again, and it 
crashed every time changing in that folder.
Opening the file with GIMP or EOG, started from the console, it was no problem 
to display it.

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

Title:
  JPEG2000 thumbnail causes browser to crash

Status in jasper package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  Attached file was generated by the Meerkat Second Life viewer.

  THe file is a "texture" file in JPEG2000 format.  The file reads
  properly with the Meerkat viewer (Linux and Windows) and with
  IrfanView (Windows). Nautilus correctly lists this file unless the
  thumbnail function is enabled.

  With thumbnail enabled Nautilus reads about 70% of the JPEG2000 files
  then crashes. No crash report is generated.

  However the SECOND time that the file is listed the thumbnail works!

  This is a problem since there are several hundred of these files in a
  directory.

  I have been unable to find a validation tool for JPEG2000 to rule out
  format errors in the file itself.

  I can supply many more examples of these files if it would help trace
  the problem!

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/nautilus
  NonfreeKernelModules: nvidia
  Package: nautilus 1:2.26.2-0ubuntu2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  Uname: Linux 2.6.28-14-generic i686

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

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

[Touch-packages] [Bug 1381620] Re: apparmor read denial on ~/.cache/QML/Apps/

[Jamie Strandboge]

This is simply a noisy denial and the priority should be reduced (plus
we have policy in place now to silence the denial).

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

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

Title:
  apparmor read denial on ~/.cache/QML/Apps/

Status in qtdeclarative-opensource-src package in Ubuntu:
  Triaged

Bug description:
  I observed the following denials:
  apparmor="DENIED" operation="open" 
profile="com.ubuntu.developer.webapps.googleplus_googleplus_0.3" 
name="/home/phablet/.cache/QML/Apps/" pid=NNN comm="webapp-containe" 
requested_mask="r" denied_mask="r" fsuid=32011 ouid=32011
  apparmor="DENIED" operation="open" 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
name="/home/phablet/.cache/QML/Apps/" pid=NNN comm="webapp-containe" 
requested_mask="r" denied_mask="r" fsuid=32011 ouid=32011

  Apps should not have read access to the .cache/QML/Apps/ because that
  would be a privacy leak. After talking to ricmm on IRC, this is a
  noisy denial (ie, the app otherwise functions fine and the cache is
  used), but it is something that should be fixed in qtdeclarative-
  opensource-src to not confuse users.

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

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

[Touch-packages] [Bug 1485073] Re: Windows in "Show Desktop" mode lose decorations

[Andrea Azzarone]

** Branch linked: lp:~azzar1/unity/lp-1485073

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

Title:
  Windows in "Show Desktop" mode lose decorations

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  In Progress

Bug description:
  1. Open two windows of a same application
  2. Click on "show desktop"
  3. Click on the application icon
  4. Click again on the application icon

  One windows has no decorations. This is also causes a glitch during
  the fade out effect.

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

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

[Touch-packages] [Bug 1392380] Re: OA gives out all tokens to any app

[Jamie Strandboge]

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

** Changed in: signon (Ubuntu Utopic)
   Importance: Critical => Undecided

** Changed in: signon (Ubuntu Utopic)
   Status: Confirmed => Won't Fix

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

Title:
  OA gives out all tokens to any app

Status in Canonical System Image:
  Fix Released
Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Utopic:
  Won't Fix
Status in signon source package in Vivid:
  Fix Released
Status in signon package in Ubuntu RTM:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu RTM:
  Fix Released

Bug description:
  The attached app will steal all your tokens. All it takes is the
  "accounts" permission in the apparmor file.

  Here's the code: https://pastebin.canonical.com/120398/

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

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

[Touch-packages] [Bug 1485073] [NEW] Windows in "Show Desktop" mode lose decorations

[Andrea Azzarone]

Public bug reported:

1. Open two windows of a same application
2. Click on "show desktop"
3. Click on the application icon
4. Click again on the application icon

One windows has no decorations. This is also causes a glitch during the
fade out effect.

** Affects: unity
 Importance: Low
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress

** Affects: unity (Ubuntu)
 Importance: Low
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress

** Changed in: unity
   Importance: Undecided => Low

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

** Changed in: unity
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

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

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

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

Title:
  Windows in "Show Desktop" mode lose decorations

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  In Progress

Bug description:
  1. Open two windows of a same application
  2. Click on "show desktop"
  3. Click on the application icon
  4. Click again on the application icon

  One windows has no decorations. This is also causes a glitch during
  the fade out effect.

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

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

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

[Jamie Strandboge]

Note, the app should not be allowed to record until the user says it is
ok to record (or that answer is cached elsewhere). I'm not sure what the
result of Qt.application.active staying true will have, but if it means
the app continues recording, that is not correct. Consider the user
opening the app then gets distracted by something else and doesn't
notice the prompt but the app is still recording and possibly sending it
over the network.

-- 
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:
  New
Status in unity8 package in Ubuntu:
  Confirmed

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 1485069] Re: New camera service trust daemon fails to start on vegetahd

[John McAleely]

phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 91
device name: vegetahd
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-08-14 11:00:07
version version: 91
version ubuntu: 20150814
version device: 20150804-7bba081
version custom: 20150717-820-30-25-vivid


the device tarball is the usual lie. My tarball included:

7d7771051b6c988786e7bf95e145d8e8aee5a9e4 Fix bugs and add traces for 
trust-store support
e03ffe430d5cb19aa2b7dbec2b30d5f0f1e62873 Adjust permissions of socket. Provides 
a connection to a per-user remote trust-store implementation via a unix domain 
socket.

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

Title:
  New camera service trust daemon fails to start on vegetahd

Status in Canonical System Image:
  New
Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  While testing silo 30, I found that the expected CameraService session
  did not start:

  phablet@ubuntu-phablet:~$ ps -ef | grep trust
  phablet   1985  1563  0 17:32 ?00:00:00 
/usr/bin/trust-stored-skeleton --remote-agent DBusRemoteAgent --bus=session 
--local-agent MirAgent 
--trusted-mir-socket=/var/run/user/32011/mir_socket_trusted --for-service 
PulseAudio --with-text-domain PulseAudio --store-bus session
  phablet   2857  1563  0 17:32 ?00:00:00 
/usr/bin/trust-stored-skeleton --remote-agent DBusRemoteAgent --bus=system 
--local-agent MirAgent 
--trusted-mir-socket=/var/run/user/32011/mir_socket_trusted --for-service 
UbuntuLocationService --with-text-domain ubuntu-location-service --store-bus 
session
  phablet   4997  2872  0 17:34 pts/47   00:00:00 grep --color=auto trust

  When opening the camera app, rather than the expected trust prompt, I
  get a blank viewfinder (but an otherwise functional app)

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

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

[Touch-packages] [Bug 1484126] Re: [Indicators] Volume notification unnecessary when adjusting volume slider

[Charles Kerr]

indicator-sound already has code to do this.

Unity needs to tell the sound indicator that the menu is visible by
setting the "indicator-shown" action state to true.

This is why it works in Unity 7 -- if you go to the Unity 7 desktop,
pull down the sound menu, and drag the slider, you don't get an
information notification.

** Package changed: indicator-network (Ubuntu) => indicator-sound
(Ubuntu)

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

** Changed in: indicator-sound (Ubuntu)
   Status: New => Invalid

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

Title:
  [Indicators] Volume notification unnecessary when adjusting volume
  slider

Status in Ubuntu UX:
  Fix Committed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Current situation:

  Go to Sound section of indicators, drag volume slider. The volume
  notification pops up, essentially replicating the slider below

  
  Desired solution:

  Let's remove the volume notification when sliding the the volume
  slider

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

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

[Touch-packages] [Bug 1485069] Re: New camera service trust daemon fails to start on vegetahd

[John McAleely]

Logs from this machine

** Attachment added: "logs.tar.xz"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1485069/+attachment/898/+files/logs.tar.xz

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

Title:
  New camera service trust daemon fails to start on vegetahd

Status in Canonical System Image:
  New
Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  While testing silo 30, I found that the expected CameraService session
  did not start:

  phablet@ubuntu-phablet:~$ ps -ef | grep trust
  phablet   1985  1563  0 17:32 ?00:00:00 
/usr/bin/trust-stored-skeleton --remote-agent DBusRemoteAgent --bus=session 
--local-agent MirAgent 
--trusted-mir-socket=/var/run/user/32011/mir_socket_trusted --for-service 
PulseAudio --with-text-domain PulseAudio --store-bus session
  phablet   2857  1563  0 17:32 ?00:00:00 
/usr/bin/trust-stored-skeleton --remote-agent DBusRemoteAgent --bus=system 
--local-agent MirAgent 
--trusted-mir-socket=/var/run/user/32011/mir_socket_trusted --for-service 
UbuntuLocationService --with-text-domain ubuntu-location-service --store-bus 
session
  phablet   4997  2872  0 17:34 pts/47   00:00:00 grep --color=auto trust

  When opening the camera app, rather than the expected trust prompt, I
  get a blank viewfinder (but an otherwise functional app)

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

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

[Touch-packages] [Bug 1485069] Re: New camera service trust daemon fails to start on vegetahd

[John McAleely]

Here's some details from my system:

phablet@ubuntu-phablet:~$ dpkg -l | grep pulse
ii  gstreamer0.10-pulseaudio:armhf   0.10.31-3+nmu1ubuntu7  
   armhfGStreamer plugin for PulseAudio
ii  gstreamer1.0-pulseaudio:armhf1.4.5-1ubuntu2 
   armhfGStreamer plugin for PulseAudio
ii  libpulse-mainloop-glib0:armhf1:6.0-0ubuntu9 
   armhfPulseAudio client libraries (glib 
support)
ii  libpulse0:armhf  1:6.0-0ubuntu9 
   armhfPulseAudio client libraries
ii  libpulsedsp:armhf1:6.0-0ubuntu9 
   armhfPulseAudio OSS pre-load library
ii  pulseaudio   1:6.0-0ubuntu9 
   armhfPulseAudio sound server
ii  pulseaudio-module-bluetooth  1:6.0-0ubuntu9 
   armhfBluetooth module for PulseAudio 
sound server
ii  pulseaudio-module-droid  1:6.0-0ubuntu9 
   armhfAndroid Audio HAL module for 
PulseAudio sound server
ii  pulseaudio-module-trust-store1:6.0-0ubuntu9 
   armhftrust-store module for PulseAudio 
sound server
ii  pulseaudio-utils 1:6.0-0ubuntu9 
   armhfCommand line tools for the 
PulseAudio sound server

phablet@ubuntu-phablet:~$ dpkg -l | grep trust
ii  libtrust-store1:armhf
1.1.0+15.04.20150814-0ubuntu1 armhfC++11 
library for persisting trust requests - runtime library
ii  pulseaudio-module-trust-store1:6.0-0ubuntu9 
   armhftrust-store module for PulseAudio 
sound server
ii  trust-store-bin  
1.1.0+15.04.20150814-0ubuntu1 armhfDaemon 
binaries to be used by services.

phablet@ubuntu-phablet:~$ dpkg -l | grep session
ii  session-migration0.2.2  
   armhfTool to migrate in user session 
settings
ii  ubuntu-touch-session 
0.108+15.04.20150814.1-0ubuntu1   all  Ubuntu 
Session Manager for Ubuntu Touch Devices
ii  upstart-watchdog 0.3
   all  watchdog jobs to reboot when system 
or session jobs fail


citrain didn't seem to want to install, so I had to download and install the 
.deb's manually. Are there any I missed above?

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

Title:
  New camera service trust daemon fails to start on vegetahd

Status in Canonical System Image:
  New
Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  While testing silo 30, I found that the expected CameraService session
  did not start:

  phablet@ubuntu-phablet:~$ ps -ef | grep trust
  phablet   1985  1563  0 17:32 ?00:00:00 
/usr/bin/trust-stored-skeleton --remote-agent DBusRemoteAgent --bus=session 
--local-agent MirAgent 
--trusted-mir-socket=/var/run/user/32011/mir_socket_trusted --for-service 
PulseAudio --with-text-domain PulseAudio --store-bus session
  phablet   2857  1563  0 17:32 ?00:00:00 
/usr/bin/trust-stored-skeleton --remote-agent DBusRemoteAgent --bus=system 
--local-agent MirAgent 
--trusted-mir-socket=/var/run/user/32011/mir_socket_trusted --for-service 
UbuntuLocationService --with-text-domain ubuntu-location-service --store-bus 
session
  phablet   4997  2872  0 17:34 pts/47   00:00:00 grep --color=auto trust

  When opening the camera app, rather than the expected trust prompt, I
  get a blank viewfinder (but an otherwise functional app)

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

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

[Touch-packages] [Bug 1485069] [NEW] New camera service trust daemon fails to start on vegetahd

[John McAleely]

Public bug reported:

While testing silo 30, I found that the expected CameraService session
did not start:

phablet@ubuntu-phablet:~$ ps -ef | grep trust
phablet   1985  1563  0 17:32 ?00:00:00 /usr/bin/trust-stored-skeleton 
--remote-agent DBusRemoteAgent --bus=session --local-agent MirAgent 
--trusted-mir-socket=/var/run/user/32011/mir_socket_trusted --for-service 
PulseAudio --with-text-domain PulseAudio --store-bus session
phablet   2857  1563  0 17:32 ?00:00:00 /usr/bin/trust-stored-skeleton 
--remote-agent DBusRemoteAgent --bus=system --local-agent MirAgent 
--trusted-mir-socket=/var/run/user/32011/mir_socket_trusted --for-service 
UbuntuLocationService --with-text-domain ubuntu-location-service --store-bus 
session
phablet   4997  2872  0 17:34 pts/47   00:00:00 grep --color=auto trust

When opening the camera app, rather than the expected trust prompt, I
get a blank viewfinder (but an otherwise functional app)

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: ubuntu-touch-session (Ubuntu)
 Importance: Undecided
 Status: New

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

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

Title:
  New camera service trust daemon fails to start on vegetahd

Status in Canonical System Image:
  New
Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  While testing silo 30, I found that the expected CameraService session
  did not start:

  phablet@ubuntu-phablet:~$ ps -ef | grep trust
  phablet   1985  1563  0 17:32 ?00:00:00 
/usr/bin/trust-stored-skeleton --remote-agent DBusRemoteAgent --bus=session 
--local-agent MirAgent 
--trusted-mir-socket=/var/run/user/32011/mir_socket_trusted --for-service 
PulseAudio --with-text-domain PulseAudio --store-bus session
  phablet   2857  1563  0 17:32 ?00:00:00 
/usr/bin/trust-stored-skeleton --remote-agent DBusRemoteAgent --bus=system 
--local-agent MirAgent 
--trusted-mir-socket=/var/run/user/32011/mir_socket_trusted --for-service 
UbuntuLocationService --with-text-domain ubuntu-location-service --store-bus 
session
  phablet   4997  2872  0 17:34 pts/47   00:00:00 grep --color=auto trust

  When opening the camera app, rather than the expected trust prompt, I
  get a blank viewfinder (but an otherwise functional app)

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

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

[Touch-packages] [Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root

[eric.desrochers]

Unfortunately, I can't reproduce the behaviour on my side.
I'm providing a hotfix[1] based on the upstream commit[2] that addressed the 
issue.

If you can reproduce the problem, please test the hotfix and provide
feedbacks.

[1] https://launchpad.net/~eric-desrochers-z/+archive/ubuntu/lp1481388/+packages
[2] d6df9d3 [Bug 2224] Use-after-free in routing socket code after dropping root

Thanks !

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

Title:
  NTP : Use-after-free in routing socket code after dropping root

Status in ntp package in Ubuntu:
  Confirmed
Status in ntp source package in Trusty:
  Confirmed
Status in ntp source package in Wily:
  Confirmed

Bug description:
  We have 1 server (among hundreds) that its ntp service is crashing.

  A few minute/seconds after a start attempts we can see the following in 
syslog:
  ntpd[2729]: peers refreshed
  ntpd[2729]: Listening on routing socket on fd #49 for interface updates
  ntpd[2729]: i/o error on routing socket No buffer space available - disabling
  kernel: [157516.495224] ntpd[2729]: segfault at 31 ip 0031 sp 
79f11788 error 14 in libpthread-2.15.so[7f967a5d9000+18000]

  OS: Ubuntu 12.04.4 LTS
  Kernel: 3.11.0-19-generic

  I tried to compare it to other servers, and the only thing I could find that 
is different is that while it's up (before it crashes) I can see the following 
when running "lsof | grep ntp":
  ntpd 2729 ntp 49u sock 0,7 0t0 2473952565 can't identify protocol.

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

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

[Touch-packages] [Bug 1372011] Re: ListItem.Subtitled subText color is too dark with SuruDark

[Jamie Strandboge]

Any status on this?

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

Title:
  ListItem.Subtitled subText color is too dark with SuruDark

Status in permy:
  New
Status in Ubuntu UX:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  It is hard to read ListItem.Subtitled subText when using the SuruDark
  theme (or other dark themes).

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

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

[Touch-packages] [Bug 1424263] Re: Broken dependencies

[Lucas Farchetto]

** Information type changed from Public to Public Security

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

Title:
  Broken dependencies

Status in mesa package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  I can not install Steam from Steam website because reported package
  has broken dependencies. This bug affect any user that will install
  Ubuntu 14.04.2. Please fix it fast, cause i can not play my games on
  Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri:i386 (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.35  Sat Jan 10 21:27:15 
PST 2015
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 21 21:40:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 346.35, 3.16.0-30-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ac]
  InstallationDate: Installed on 2015-02-20 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=ea315497-1076-4f76-a2da-dc65caca572f ro quiet splash loglevel=0 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H87 Pro4
  dmi.board.vendor: ASRock
  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.:bvrP2.10:bd07/09/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Feb 21 17:22:09 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Touch-packages] [Bug 1471338] Re: sometimes phone never wakes up or rings on incoming call

[Bill Filler]

Here is full stack trace with all debug symbols installed

(gdb) t a a bt

Thread 6 (Thread 0xb38683a0 (LWP 4339)):
#0  0xb64a14e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0x in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 5 (Thread 0xb2eff3a0 (LWP 4340)):
#0  0xb64a14e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0x in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 4 (Thread 0xb18d33a0 (LWP 4341)):
#0  0xb64a8132 in epoll_wait () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0xb268b28a in boost::asio::detail::epoll_reactor::run (this=0x1a2fdf0, 
block=block@entry=true, 
ops=...) at /usr/include/boost/asio/detail/impl/epoll_reactor.ipp:392
#2  0xb268d262 in do_run_one (ec=..., this_thread=..., lock=..., this=0x1a2fd20)
at /usr/include/boost/asio/detail/impl/task_io_service.ipp:368
#3  boost::asio::detail::task_io_service::run (this=0x1a2fd20, ec=...)
at /usr/include/boost/asio/detail/impl/task_io_service.ipp:153
#4  0xb268d7c2 in run (
this=0xb269a660 
 const&)::io>)
at /usr/include/boost/asio/impl/io_service.ipp:59
#5  core::dbus::asio::Executor::run (this=)
at 
/build/buildd/dbus-cpp-4.3.0+15.04.20150505/src/core/dbus/asio/executor.cpp:386
#6  0xb2676678 in core::dbus::Bus::run (this=)
at /build/buildd/dbus-cpp-4.3.0+15.04.20150505/src/core/dbus/bus.cpp:343
#7  0xb65b32a0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#8  0xb6405490 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
#9  0xb64a7c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0xb10563a0 (LWP 4345)):
#0  0xb64a14e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0x in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0xb06d53a0 (LWP 4346)):
#0  0xb640dd44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
#1  0xb640b980 in __lll_lock_wait () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
---Type  to continue, or q  to quit---
#2  0xb6407202 in pthread_mutex_lock () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
#3  0xb609c024 in check_for_reply_and_update_dispatch_unlocked (
connection=connection@entry=0x19c52c0, pending=pending@entry=0xafd02c98)
at ../../dbus/dbus-connection.c:2353
#4  0xb609c0f6 in _dbus_connection_block_pending_call 
(pending=pending@entry=0xafd02c98)
at ../../dbus/dbus-connection.c:2461
#5  0xb60a810e in dbus_pending_call_block (pending=pending@entry=0xafd02c98)
at ../../dbus/dbus-pending-call.c:741
#6  0xb609c4d4 in dbus_connection_send_with_reply_and_block 
(connection=0x19c52c0, 
message=0xb0739898, timeout_milliseconds=-1, error=0xb06d471c)
at ../../dbus/dbus-connection.c:3575
#7  0xb6ba2f3c in q_dbus_connection_send_with_reply_and_block 
(error=0xb06d471c, 
timeout_milliseconds=-1, message=0xb0739898, connection=0x19c52c0) at 
qdbus_symbols_p.h:135
#8  QDBusConnectionPrivate::sendWithReply (this=this@entry=0x19c4220, 
message=..., 
sendMode=sendMode@entry=1, timeout=timeout@entry=-1) at 
qdbusintegrator.cpp:2046
#9  0xb6ba3506 in QDBusConnectionPrivate::getNameOwnerNoCache 
(this=this@entry=0x19c4220, 
serviceName=...) at qdbusintegrator.cpp:2503
#10 0xb6ba3ec6 in QDBusConnectionPrivate::getNameOwner (this=0x19c4220, 
serviceName=...)
at qdbusintegrator.cpp:2493
#11 0xb6ba8c78 in QDBusAbstractInterfacePrivate::QDBusAbstractInterfacePrivate 
(this=0xafd02c20, 
serv=..., p=..., iface=..., con=..., isDynamic=true) at 
qdbusabstractinterface.cpp:93
#12 0xb6babb62 in QDBusInterfacePrivate::QDBusInterfacePrivate 
(this=this@entry=0xafd02c20, 
serv=..., p=..., iface=..., con=...) at qdbusinterface.cpp:146
#13 0xb6babc90 in QDBusInterface::QDBusInterface (this=0xb06d4950, service=..., 
path=..., 
interface=..., connection=..., parent=0x0) at qdbusinterface.cpp:212
#14 0x0004c30e in GreeterContacts::GreeterContacts (this=0xafd026e0, 
parent=)
at 
/build/telephony-service-gxwyZt/telephony-service-0.1+15.04.20150810.1/libtelephonyservice/greetercontacts.cpp:94
#15 0x0004cc1c in GreeterContacts::instance ()
at 
/build/telephony-service-gxwyZt/telephony-service-0.1+15.04.20150810.1/libtelephonyservice/greetercontacts.cpp:46
#16 0x0005427a in RingtoneWorker::playIncomingCallSound (this=0x1a61e28)
at 
/build/telephony-service-gxwyZt/telephony-service-0.1+15.04.20150810.1/libtelephonyservice/ringtone.cpp:39
#17 0xb6dd7764 in QObject::event (this=, e=)
at kernel/qobject.cpp:1245
#18 0xb6db6a78 in notify (event=0x1a679d0, receiver=0x1a61e28, this=0xbe80f4a0)
at kernel/qcoreapplication.cpp:997
#19 QCoreApplication::notifyInternal (this=0xbe80f4a0, 
receiver=receiver@entry=0x1a61e28, 
---Type  to continue, or q  to quit---
event=event@entry=0x1a679d0) at kernel/qcoreapplication.cpp:935
#20 0xb6db8294 in sen

[Touch-packages] [Bug 1484178] Re: Policy cache file mtimes are not being set correctly

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/wily-proposed/apparmor

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

Title:
  Policy cache file mtimes are not being set correctly

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Oliver Grawert (ogra) reported that Ubuntu Touch image builds were
  failing due to incorrect timestamps on pre-compiled policy cache
  files.

  Starting in AppArmor 2.10, the policy cache file's mtime was meant to be 
updated to be equal to the newest mtime detected
  on the profile and abstraction files used to generate the policy cache file:

http://bazaar.launchpad.net/~apparmor-
  dev/apparmor/master/revision/3079

  That change was not correct and resulted in the mtime of the policy
  cache file to either not be updated (equal to the policy cache file
  creation time) or to be updated to an incorrect time.

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

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

[Touch-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store

[John McAleely]

This is in silo 30 as I type, blocked by bug #1483752

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

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

Title:
  Pulseaudio should integrate with trust-store

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

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user ("Foo wants to use
  the microphone. Is this ok? Yes|No"), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If the app is 
allowed to do networking (the default for apps), then it can ship that 
information off to a server somewhere.

  Note 1, the alert to indicator-sound must happen via the out of
  process pulseaudio server and not the confined app itself to be
  effective.

  Note 2, we should consider how to enforce this for foreground apps
  only. Application lifecycle should probably handle this for 13.10
  (apps are suspended if not in foreground or if the screensaver is on),
  but we don't want an app on the converged device to record in the
  background when the user isn't paying attention. Example eavesdropping
  attack: start recording only when the screensaver is on (perhaps
  inhibiting the screensaver during recording would be enough).

  : "On the phone, if
  an app tries to access your ... microphone ... or video recording,
  this should be subject to permission. “Video recording” should be
  separate from “Camera” so that an app does not need two permissions
  when recording video, one for the camera and one for the microphone.
  If an app has permission to record video, it should have access to the
  microphone whenever it is recording video..."

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

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

[Touch-packages] [Bug 1230366] Re: Please provide Ubuntu camera service that integrates with trust-store

[John McAleely]

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

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

Title:
  Please provide Ubuntu camera service that integrates with trust-store

Status in Canonical System Image:
  In Progress
Status in qtubuntu-camera package in Ubuntu:
  Triaged
Status in qtubuntu-camera package in Ubuntu RTM:
  Invalid

Bug description:
  Currently Ubuntu Touch is using the android camera-service and that is
  the plan for 13.10.

  Going forward in 14.04, the android camera-service will no longer be
  used and camera access is going to move to the Ubuntu side. There was
  discussion of either using HAL directly (direct access to devices) or
  using a camera-service type thing in Ubuntu.

  Using devices directly causes at least a few problems:
   * can't prevent more than one user from accessing the device at a time
   * enumerating camera devices for apparmor policy is extra maintenance for 
porters
   * can't provide a contextual runtime prompt for access (like we (will) do 
with online accounts, location, microphone). This is particularly important for 
application confinement.

  Instead of direct hardware access, an out of process helper (in
  relation to the app) can be used to address all of these problems,
  similar to what pulseaudio does for audio. This service can ensure
  only one user can access the device at a time and since the service
  accesses the the device files on the app's behalf, we don't need to
  enumerate devices in /dev in policy. Furthermore, when an app accesses
  the service (ideally over DBus), the service can contact trust-store,
  the trust-store will prompt the user ("Foo wants to access the camera.
  Is this ok? Yes|No"), then optionally cache the result and return the
  result to the service. In this manner the user is given a contextual
  prompt at the time of access by the app. By using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in system settings.

  If direct hardware access is needed for performance reasons, it is
  possible to use fd delegation in AppArmor and have the service open
  the device and pass the fd to the app without having to enumerate the
  /dev devices. Please talk to jjohansen if pursuing this option.

  Lastly, bug #1230391 discusses providing a visual cue during
  background recording for audio. We will need to do the same for video
  recording. Feel free to add a task to bug #1230391 if there is work to
  integrate this new service with that visual cuing.

  This should be implemented in time for shippable devices to address
  the application confinement concern.

  : "On the
  phone, if an app tries to access your ... camera ... or video
  recording, this should be subject to permission..."

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

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

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

[John McAleely]

This is blocking silo 30 from landing, which has trust store integration
for audio & camera.

-- 
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:
  New
Status in unity8 package in Ubuntu:
  Confirmed

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 1471338] Re: sometimes phone never wakes up or rings on incoming call

[Bill Filler]

** Attachment added: "dbus-monitor output when phone call"
   
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1471338/+attachment/847/+files/monitor.log

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

Title:
  sometimes phone never wakes up or rings on incoming call

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

Bug description:
  testing on krilin build 56 vivid+overlay latest
  dual sims installed

  The problem is sometimes during an incoming call the phone never wakes
  up or rings at all (and no snap decision). From the remote end the
  call just continues to ring and eventually goes to voicemail. When
  this occurs the signal strength appears to have at least 3 bars.

  It seems ofono is not notifying the upper layers that a call is incoming. 
This can be verifed by running the following command:
  dbus-monitor --system | grep CallAdded

  This never gets fired during error condition when the incoming call is
  ringing from remote end.

  Attached is the ofono log when I got it to happen once (not sure where
  in the log corresponds to the failure)

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

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

[Touch-packages] [Bug 1445892] Re: There is no wifi after hybernate mode with systemd-boot

[Twente]

The bug still exists

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

Title:
  There is no wifi after hybernate mode with systemd-boot

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

Bug description:
  You close notebooke, then you open it- and there is no wifi. You have to 
restart network-manager for obtaining wi-fi again
  ! If you choose upstart-boot option there is no problem with wifi after 
hybernation. Bug occures unly with systemd-boot

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 19 13:09:18 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-18 (547 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 10.0.1.1 dev wlan0  proto static  metric 1024
   10.0.1.0/24 dev wlan0  proto kernel  scope link  src 10.0.1.18
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE TIMESTAMP   
TIMESTAMP-REAL AUTOCONNECT  READONLY  DBUS-PATH 
  ACTIVE  DEVICE  STATE  ACTIVE-PATH
   k3b   66a32a2c-3eac-46e3-a111-0c63e94bd135  802-11-wireless  1429438056  Вс. 
19 апр. 2015 13:07:36  yes  no
/org/freedesktop/NetworkManager/Settings/0  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/4
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  k3b  
   66a32a2c-3eac-46e3-a111-0c63e94bd135  
/org/freedesktop/NetworkManager/ActiveConnection/4
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1475205] Re: Random Chinese character missing with Ubuntu font

[Launchpad Bug Tracker]

This bug was fixed in the package qtbase-opensource-src - 5.4.2+dfsg-
2ubuntu3

---
qtbase-opensource-src (5.4.2+dfsg-2ubuntu3) trusty; urgency=medium

  [ Gary Wang ]
  * debian/patches/enable_fonts_always_smoothly.patch:
- Workaround a glyph rendering problem by forcing distance field
  rendering (LP: #1462982) (LP: #1475205)

 -- Timo Jyrinki   Wed, 05 Aug 2015 11:44:25 +0300

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Random Chinese character missing with Ubuntu font

Status in Canonical System Image:
  Fix Committed
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Invalid
Status in ubuntu-font-family-sources package in Ubuntu:
  Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  After applied 50 GU setting in image, we started seeing randomly
  missing Chinese characters across scopes and apps header, not clipped
  at the begin or end of string, sometimes in the middle.

  STEPS:

  1. Switch display language to zh_CN in system settings
  2. Reboot the phone

  EXPECTED:

  I should see all header strings displayed properly.

  ACTUAL:

  Randomly missing character.

  VERSIONS:

  current build number: 51
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.zh-proposed
  last update: 2015-07-16 04:59:10
  version version: 51
  version ubuntu: 20150716
  version device: 20150709-8965e37
  version custom: 20150716-819-9-6

  -- update --
  The problem of missing characters can be reproduced even on a desktop, 
outside of the header, without importing Ubuntu.Components:

  import QtQuick 2.0
  Item {
  width: 800
  height: 600

  Text {
  anchors.centerIn: parent
  text: "系统设置 one two"
  font.family: "Ubuntu"
  font.pixelSize: 69
  font.weight: Font.Light
  }
  }

  The problem only appears to occur with this specific combination of
  font family, pixelSize and weight. Tim Peeters reproduced the problem
  on vivid on a laptop without changing the default settings for the
  language (LANGUAGE="en_US").

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

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

[Touch-packages] [Bug 1055272] Re: valgrind

[Simon Quigley]

Is this bug still valid?

I am asking because this is dated 2013.

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

Title:
  valgrind

Status in mesa package in Ubuntu:
  New

Bug description:
  The following program produces 55 errors with valgrind:

  int
  main()
  {
Display* display = XOpenDisplay(0);
int major;
int minor;
glXQueryVersion(display, &major, &minor);
XCloseDisplay(display);
  }

  51 instances in drm_intel_bufmgr_gem_init: Conditional jump or move depends 
on uninitialised value(s)
  2 instances in drm_intel_bufmgr_gem_init: Syscall param ioctl(generic) points 
to uninitialised byte(s)
  2 instances in fun:drmCommandWriteRead: Syscall param ioctl(generic) points 
to uninitialised byte(s)

  The corresponding suppression entries are:

  {
OpenGL-bad-ioctl
Memcheck:Param
ioctl(generic)
fun:ioctl
fun:drmIoctl
fun:drm_intel_bufmgr_gem_init
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2
obj:/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2
  }

  {
OpenGL-bad-ioctl-2
Memcheck:Param
ioctl(generic)
fun:ioctl
fun:drmIoctl
fun:drmCommandWriteRead
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2
obj:/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2
  }

  {
OpenGL-uninitialized-jump
Memcheck:Cond
fun:drm_intel_bufmgr_gem_init
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2
obj:/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2
  }

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

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

[Touch-packages] [Bug 1440360] Re: Incomplete long-left swipe resets dash

[Magdalena Mirowicz]

** Changed in: ubuntu-ux
 Assignee: (unassigned) => Paty Davila (dizzypaty)

** Changed in: ubuntu-ux
   Status: New => Triaged

** Changed in: ubuntu-ux
   Importance: Undecided => Medium

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

Title:
  Incomplete long-left swipe resets dash

Status in Ubuntu UX:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce the issue:
  1 - open e.g. Ubuntu Store scope (from the app scope) or Youtube scope (from 
the video scope)
  2 - (shortly) swipe from the left to invoke launcher

  Expected outcome:
  The launcher can be used to open a pinned app (while the current scope is 
still kept in the background) or dismissed to return to the current scope.

  Actual outcome:
  The current scope will immediately be closed and the first (main) scope 
(typically the app scope on devel-images and the Today scope on RTM) will be 
shown.
  If I understand the current design guidelines correctly this is the expected 
behaviour for a full left-to-right swipe, but not for a short swipe from the 
left to invoke the launcher.

  This behaviour can be observed on both the current devel-proposed and
  RTM images.

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

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