[Touch-packages] [Bug 1423817] Re: Ubuntu Phone: No sound notifications

[costales]

@Sebastien, thanks for the info, but it's in all the applications
(native with notifications I only have Telegram) :O Even webapps.

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

Title:
  Ubuntu Phone: No sound notifications

Status in indicator-sound package in Ubuntu:
  Invalid

Bug description:
  Hi!

  In the BQ Ubuntu Edition, when I receive a notification by Telegram or
  webapp, I don't get a sound notification, just a vibration.

  In the system settings is set all for a play sound.

  Thanks in advance!

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

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

[Touch-packages] [Bug 1423817] Re: Ubuntu Phone: No sound notifications

[Sebastien Bacher]

Thanks for that's not an indicator or settings bug, but due to those
applications. Bug #1421332 for example

** Changed in: indicator-sound (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Ubuntu Phone: No sound notifications

Status in indicator-sound package in Ubuntu:
  Invalid

Bug description:
  Hi!

  In the BQ Ubuntu Edition, when I receive a notification by Telegram or
  webapp, I don't get a sound notification, just a vibration.

  In the system settings is set all for a play sound.

  Thanks in advance!

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

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

[Touch-packages] [Bug 1423810] Re: [krillin] apparmor fd_inheritance regression test causes kernel to crash

[Steve Beattie]

And the unix_fd_server test as well:

phablet@ubuntu-phablet:~/src/apparmor-2.9.1/tests/regression/apparmor$ sudo sh 
-c 'VERBOSE=1 bash unix_fd_server.sh'
[sudo] password for phablet:
ok: fd passing; unconfined -> unconfined
ok: fd passing; confined -> unconfined
ok: fd passing; confined (bad perm) -> unconfined
ok: fd passing; confined (no perm) -> unconfined
ok: fd passing; unconfined -> confined
ok: fd passing; unconfined -> confined (no perm)
ok: fd passing; confined -> confined
ok: fd passing; confined (bad perm) -> confined
ok: fd passing; confined (no perm) -> confined
ok: fd passing; confined -> confined (bad perm)

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

Title:
  [krillin] apparmor fd_inheritance regression test causes kernel to
  crash

Status in apparmor package in Ubuntu:
  New

Bug description:
  On krillin with vivid-proposed, running the fd_inheritance test from
  the apparmor regression tests causes the kernel to crash and
  spontaneously reboot the device:

  phablet@ubuntu-phablet:~/src/apparmor-2.9.1/tests/regression/apparmor$ logger 
"running fd_inheritance tests now"
  phablet@ubuntu-phablet:~/src/apparmor-2.9.1/tests/regression/apparmor$ sudo 
sh -c 'VERBOSE=1 bash fd_inheritance.sh'
  ok: fd inheritance; unconfined -> unconfined
  ok: fd inheritance; confined -> unconfined
  ok: fd inheritance; confined (bad perm) -> unconfined
  ok: fd inheritance; confined (no perm) -> unconfined
  ok: fd inheritance; unconfined -> confined
  ok: fd inheritance; unconfined -> confined (no perm)
  ok: fd inheritance; confined -> confined
  ok: fd inheritance; confined (bad perm) -> confined
  ok: fd inheritance; confined (no perm) -> confined
  ok: fd inheritance; confined -> confined (bad perm)
  [device reboots here]

  This is what syslog sees before it falls over, though nothing after the 
logger invocation makes it to the disk:
  Feb 20 03:51:47 ubuntu-phablet phablet: running fd_inheritance tests now
  Feb 20 03:52:05 ubuntu-phablet kernel: [  489.942611]type=1400 
audit(1424404325.798:141): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7449 comm="apparmor_parser"
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.272023]type=1400 
audit(1424404326.128:142): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7477 comm="apparmor_parser"
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.305028]type=1400 
audit(1424404326.158:143): apparmor="DENIED" operation="open" 
profile="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 name="/tmp/sdtest.7416-27080-LFDs8z/file" pid=7483 comm="fd_inheritance" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.573275]type=1400 
audit(1424404326.428:144): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7505 comm="apparmor_parser"
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.606454]type=1400 
audit(1424404326.468:145): apparmor="DENIED" operation="open" 
profile="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 name="/tmp/sdtest.7416-27080-LFDs8z/file" pid=7510 comm="fd_inheritance" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.886149]type=1400 
audit(1424404326.748:146): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7536 comm="apparmor_parser"
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.916538]type=1400 
audit(1424404326.778:147): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor" 
pid=7537 comm="apparmor_parser"
  Feb 20 03:52:07 ubuntu-phablet kernel: [  491.226336]type=1400 
audit(1424404327.088:148): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor" 
pid=7568 comm="apparmor_parser"
  Feb 20 03:52:07 ubuntu-phablet kernel: [  491.734888]type=1400 
audit(1424404327.588:149): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor" 
pid=7612 comm="apparmor_parser"
  Feb 20 03:52:07 ubuntu-phablet kernel: [  491.786710]type=1400 
audit(1424404327.648:150): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7613 comm="apparmor_parser"
  Feb 20 03:52:07 ubuntu-phablet kernel: [ 

[Touch-packages] [Bug 1378883] Re: [system-settings] missing SIM unlock

[Jonas G. Drange]

** Changed in: indicator-network (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: indicator-network
   Status: Triaged => Fix Released

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

Title:
  [system-settings] missing SIM unlock

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Network Menu:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu RTM:
  Fix Released

Bug description:
  Build r91

  1. set up a SIM PIN or make sure the inserted SIM has already a set up SIM 
PIN (reboot device if needed)
  2. after reboot, don't unlock
  3. navigate to System Settings > Security & Privacy > SIM PIN

  What you see: A green tick on the toggle next to the SIM PIN and
  beneath that a "Change PIN..." button

  What you should see: Some way to unlock the SIM without turning off
  the SIM PIN.

  There are three relevant states for a SIM:
  (A) no SIM PIN set
  (B) SIM PIN set, SIM locked
  (C) SIM PIN set, SIM unlocked.

  If a SIM PIN is set, when you start up the phone you have the choice
  to unlock it (switch from B to C) or not (stay on B).

  If you don't unlock it, you can't make or receive calls, send or
  receive SMS, or use cellular data in any app. And you probably can't
  predict ahead of time whether you'll want to do any of those things.

  Currently System Settings only lets you turn the SIM PIN on (A to C)
  or off (C to A), not to unlock it. System Settings should let you do
  this too.

  :
  "Whenever it is locked, at the trailing end should be an 'Unlock…'
  button..."

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

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

[Touch-packages] [Bug 1423817] [NEW] Ubuntu Phone: No sound notifications

[costales]

Public bug reported:

Hi!

In the BQ Ubuntu Edition, when I receive a notification by Telegram or
webapp, I don't get a sound notification, just a vibration.

In the system settings is set all for a play sound.

Thanks in advance!

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Ubuntu Phone: No sound notifications

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Hi!

  In the BQ Ubuntu Edition, when I receive a notification by Telegram or
  webapp, I don't get a sound notification, just a vibration.

  In the system settings is set all for a play sound.

  Thanks in advance!

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

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

[Touch-packages] [Bug 1423810] Re: [krillin] apparmor fd_inheritance regression test causes kernel to crash

[Steve Beattie]

Looks like the socketpair tests cause a similar issue:

phablet@ubuntu-phablet:~/src/apparmor-2.9.1/tests/regression/apparmor$ sudo sh 
-c 'VERBOSE=1 bash socketpair.sh'
[sudo] password for phablet:
ok: SOCKETPAIR (unconfined)
ok: SOCKETPAIR (unconfined bad con)
ok: SOCKETPAIR (unconfined bad mode)
ok: SOCKETPAIR (confined)
ok: SOCKETPAIR (confined bad con)
ok: SOCKETPAIR (confined bad mode)
ok: SOCKETPAIR (complain)
ok: SOCKETPAIR (complain bad mode)
ok: SOCKETPAIR (complain)
ok: SOCKETPAIR (confined exec transition)
ok: SOCKETPAIR (confined exec transition, crosscheck rejection)
ok: SOCKETPAIR (confined exec no transition)
ok: SOCKETPAIR (confined exec transition from complain)
ok: SOCKETPAIR (confined exec transition to complain)
[phone spontaneously reboots here]

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

Title:
  [krillin] apparmor fd_inheritance regression test causes kernel to
  crash

Status in apparmor package in Ubuntu:
  New

Bug description:
  On krillin with vivid-proposed, running the fd_inheritance test from
  the apparmor regression tests causes the kernel to crash and
  spontaneously reboot the device:

  phablet@ubuntu-phablet:~/src/apparmor-2.9.1/tests/regression/apparmor$ logger 
"running fd_inheritance tests now"
  phablet@ubuntu-phablet:~/src/apparmor-2.9.1/tests/regression/apparmor$ sudo 
sh -c 'VERBOSE=1 bash fd_inheritance.sh'
  ok: fd inheritance; unconfined -> unconfined
  ok: fd inheritance; confined -> unconfined
  ok: fd inheritance; confined (bad perm) -> unconfined
  ok: fd inheritance; confined (no perm) -> unconfined
  ok: fd inheritance; unconfined -> confined
  ok: fd inheritance; unconfined -> confined (no perm)
  ok: fd inheritance; confined -> confined
  ok: fd inheritance; confined (bad perm) -> confined
  ok: fd inheritance; confined (no perm) -> confined
  ok: fd inheritance; confined -> confined (bad perm)
  [device reboots here]

  This is what syslog sees before it falls over, though nothing after the 
logger invocation makes it to the disk:
  Feb 20 03:51:47 ubuntu-phablet phablet: running fd_inheritance tests now
  Feb 20 03:52:05 ubuntu-phablet kernel: [  489.942611]type=1400 
audit(1424404325.798:141): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7449 comm="apparmor_parser"
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.272023]type=1400 
audit(1424404326.128:142): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7477 comm="apparmor_parser"
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.305028]type=1400 
audit(1424404326.158:143): apparmor="DENIED" operation="open" 
profile="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 name="/tmp/sdtest.7416-27080-LFDs8z/file" pid=7483 comm="fd_inheritance" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.573275]type=1400 
audit(1424404326.428:144): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7505 comm="apparmor_parser"
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.606454]type=1400 
audit(1424404326.468:145): apparmor="DENIED" operation="open" 
profile="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 name="/tmp/sdtest.7416-27080-LFDs8z/file" pid=7510 comm="fd_inheritance" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.886149]type=1400 
audit(1424404326.748:146): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7536 comm="apparmor_parser"
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.916538]type=1400 
audit(1424404326.778:147): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor" 
pid=7537 comm="apparmor_parser"
  Feb 20 03:52:07 ubuntu-phablet kernel: [  491.226336]type=1400 
audit(1424404327.088:148): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor" 
pid=7568 comm="apparmor_parser"
  Feb 20 03:52:07 ubuntu-phablet kernel: [  491.734888]type=1400 
audit(1424404327.588:149): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor" 
pid=7612 comm="apparmor_parser"
  Feb 20 03:52:07 ubuntu-phablet kernel: [  491.786710]type=1400 
audit(1424404327.648:150): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="/home

[Touch-packages] [Bug 1423811] Re: 219-1ubuntu1 regression: boot hangs, logind fails

[Martin Pitt]

** Description changed:

  Since yesterday, systemd does not boot properly any more. It takes very
  long, ends up in an X failsafe session, and eventually you just get a
  getty on VT1.
  
+ Downgrading libpam-systemd libsystemd0 systemd systemd-sysv to
+ https://launchpad.net/ubuntu/+source/systemd/218-10ubuntu2 fixes the
+ boot again.
+ 
  $ sudo systemctl list-jobs
-  JOB UNITTYPESTATE  
+  JOB UNITTYPESTATE
  1634 sound.targetstopwaiting
  1176 NetworkManager.service  start   running
  1598 cgproxy.service start   waiting
  1632 failsafe-graphical.target   stopwaiting
  1563 alsa-restore.servicestart   waiting
  1594 plymouth-quit-wait.service  start   waiting
  1588 getty-static.servicestart   waiting
  1562 alsa-state.service  start   waiting
-  121 systemd-update-utmp-runlevel.servicestart   waiting
+  121 systemd-update-utmp-runlevel.servicestart   waiting
  1640 ifup@wlan0.service  stopwaiting
  1544 systemd-ask-password-plymouth.path  start   waiting
  1507 friendly-recovery.service   start   waiting
  1607 anacron.service start   waiting
  1489 systemd-binfmt.service  start   waiting
  1637 system-systemd\x2drfkill.slice  stopwaiting
  1636 systemd-rfkill@rfkill1.service  stopwaiting
  1631 failsafe-x.service  stopwaiting
  1638 systemd-backlight@backlight:intel_backlight.service stopwaiting
  1610 pppd-dns.servicestart   waiting
  1483 systemd-machine-id-commit.service   start   waiting
  1635 system-systemd\x2dbacklight.slice   stopwaiting
  1557 systemd-hwdb-update.service start   waiting
  1630 systemd-backlight@backlight:acpi_video0.service stopwaiting
  1500 sys-kernel-config.mount start   waiting
-   92 multi-user.target   start   waiting
+   92 multi-user.target   start   waiting
  1509 debian-fixup.servicestart   waiting
  1641 systemd-rfkill@rfkill0.service  stopwaiting
  1613 plymouth-quit.service   start   waiting
  1639 system-ifup.slice   stopwaiting
  1642 ifup@lxcbr0.service stopwaiting
  1633 acpid.service   stopwaiting
  1643 systemd-logind.service  restart waiting
  1543 plymouth-start.service  start   waiting
  1499 plymouth-read-write.service start   waiting
  
  Attaching debug journal.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-1ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 20 07:39:03 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-20 (91 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141119)
  MachineType: LENOVO 2324CTO
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-13-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ quiet 
splash vt.handoff=7 init=/sbin/upstart
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

** Description changed:

  Since yesterday, systemd does not boot properly any more. It takes very
  long, ends up in an X failsafe session, and eventually you just get a
  getty on VT1.
  
  Downgrading libpam-systemd libsystemd0 systemd systemd-sysv to
  https://launchpad.net/ubuntu/+source/systemd/218-10ubuntu2 fixes the
  boot again.
+ 
+ This happens both with the standard "qu

[Touch-packages] [Bug 1423811] [NEW] 219-1ubuntu1 regression: boot hangs, logind fails

[Martin Pitt]

Public bug reported:

Since yesterday, systemd does not boot properly any more. It takes very
long, ends up in an X failsafe session, and eventually you just get a
getty on VT1.

$ sudo systemctl list-jobs
 JOB UNITTYPESTATE  
1634 sound.targetstopwaiting
1176 NetworkManager.service  start   running
1598 cgproxy.service start   waiting
1632 failsafe-graphical.target   stopwaiting
1563 alsa-restore.servicestart   waiting
1594 plymouth-quit-wait.service  start   waiting
1588 getty-static.servicestart   waiting
1562 alsa-state.service  start   waiting
 121 systemd-update-utmp-runlevel.servicestart   waiting
1640 ifup@wlan0.service  stopwaiting
1544 systemd-ask-password-plymouth.path  start   waiting
1507 friendly-recovery.service   start   waiting
1607 anacron.service start   waiting
1489 systemd-binfmt.service  start   waiting
1637 system-systemd\x2drfkill.slice  stopwaiting
1636 systemd-rfkill@rfkill1.service  stopwaiting
1631 failsafe-x.service  stopwaiting
1638 systemd-backlight@backlight:intel_backlight.service stopwaiting
1610 pppd-dns.servicestart   waiting
1483 systemd-machine-id-commit.service   start   waiting
1635 system-systemd\x2dbacklight.slice   stopwaiting
1557 systemd-hwdb-update.service start   waiting
1630 systemd-backlight@backlight:acpi_video0.service stopwaiting
1500 sys-kernel-config.mount start   waiting
  92 multi-user.target   start   waiting
1509 debian-fixup.servicestart   waiting
1641 systemd-rfkill@rfkill0.service  stopwaiting
1613 plymouth-quit.service   start   waiting
1639 system-ifup.slice   stopwaiting
1642 ifup@lxcbr0.service stopwaiting
1633 acpid.service   stopwaiting
1643 systemd-logind.service  restart waiting
1543 plymouth-start.service  start   waiting
1499 plymouth-read-write.service start   waiting

Attaching debug journal.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-1ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 20 07:39:03 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-11-20 (91 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141119)
MachineType: LENOVO 2324CTO
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-13-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ quiet 
splash vt.handoff=7 init=/sbin/upstart
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET95WW (2.55 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2324CTO
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 Pro
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2324CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

** Affects: systemd (Ubuntu)
 Importance: Critical
 Assignee: Martin Pitt (pitti)
 Status: In Progress


** Tags: amd64 apport-bug vivid

** Attachment added: "journal with debugging"
   
https://bugs.launchpad.net/bugs/1423811/+attachment/4323096/+files/journal.txt

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

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-15.02

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

Title:
  219-1ubuntu1 regression: boot hangs, logind fails

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Since yesterday, systemd d

[Touch-packages] [Bug 1385331] Re: Notification LED stays on when no messages in notification center

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-messages -
13.10.1+15.04.20150219-0ubuntu1

---
indicator-messages (13.10.1+15.04.20150219-0ubuntu1) vivid; urgency=medium

  [ Ted Gould ]
  * Provide functions that allow for action names directly (LP:
#1385331)
 -- CI Train BotThu, 19 Feb 2015 15:55:54 +

** Changed in: indicator-messages (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 qmenumodel in Ubuntu.
https://bugs.launchpad.net/bugs/1385331

Title:
  Notification LED stays on when no messages in notification center

Status in the base for Ubuntu mobile products:
  In Progress
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in qmenumodel package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in qmenumodel package in Ubuntu RTM:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  Fix Released

Bug description:
  Observed the notification LED staying on even though there were no
  notifications in the indicators and the notification icon was greyed
  out.

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

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

[Touch-packages] [Bug 1423810] [NEW] [krillin] apparmor fd_inheritance regression test causes kernel to crash

[Steve Beattie]

Public bug reported:

On krillin with vivid-proposed, running the fd_inheritance test from the
apparmor regression tests causes the kernel to crash and spontaneously
reboot the device:

phablet@ubuntu-phablet:~/src/apparmor-2.9.1/tests/regression/apparmor$ logger 
"running fd_inheritance tests now"
phablet@ubuntu-phablet:~/src/apparmor-2.9.1/tests/regression/apparmor$ sudo sh 
-c 'VERBOSE=1 bash fd_inheritance.sh'
ok: fd inheritance; unconfined -> unconfined
ok: fd inheritance; confined -> unconfined
ok: fd inheritance; confined (bad perm) -> unconfined
ok: fd inheritance; confined (no perm) -> unconfined
ok: fd inheritance; unconfined -> confined
ok: fd inheritance; unconfined -> confined (no perm)
ok: fd inheritance; confined -> confined
ok: fd inheritance; confined (bad perm) -> confined
ok: fd inheritance; confined (no perm) -> confined
ok: fd inheritance; confined -> confined (bad perm)
[device reboots here]

This is what syslog sees before it falls over, though nothing after the logger 
invocation makes it to the disk:
Feb 20 03:51:47 ubuntu-phablet phablet: running fd_inheritance tests now
Feb 20 03:52:05 ubuntu-phablet kernel: [  489.942611]type=1400 
audit(1424404325.798:141): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7449 comm="apparmor_parser"
Feb 20 03:52:06 ubuntu-phablet kernel: [  490.272023]type=1400 
audit(1424404326.128:142): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7477 comm="apparmor_parser"
Feb 20 03:52:06 ubuntu-phablet kernel: [  490.305028]type=1400 
audit(1424404326.158:143): apparmor="DENIED" operation="open" 
profile="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 name="/tmp/sdtest.7416-27080-LFDs8z/file" pid=7483 comm="fd_inheritance" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Feb 20 03:52:06 ubuntu-phablet kernel: [  490.573275]type=1400 
audit(1424404326.428:144): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7505 comm="apparmor_parser"
Feb 20 03:52:06 ubuntu-phablet kernel: [  490.606454]type=1400 
audit(1424404326.468:145): apparmor="DENIED" operation="open" 
profile="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 name="/tmp/sdtest.7416-27080-LFDs8z/file" pid=7510 comm="fd_inheritance" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Feb 20 03:52:06 ubuntu-phablet kernel: [  490.886149]type=1400 
audit(1424404326.748:146): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7536 comm="apparmor_parser"
Feb 20 03:52:06 ubuntu-phablet kernel: [  490.916538]type=1400 
audit(1424404326.778:147): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor" 
pid=7537 comm="apparmor_parser"
Feb 20 03:52:07 ubuntu-phablet kernel: [  491.226336]type=1400 
audit(1424404327.088:148): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor" 
pid=7568 comm="apparmor_parser"
Feb 20 03:52:07 ubuntu-phablet kernel: [  491.734888]type=1400 
audit(1424404327.588:149): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor" 
pid=7612 comm="apparmor_parser"
Feb 20 03:52:07 ubuntu-phablet kernel: [  491.786710]type=1400 
audit(1424404327.648:150): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7613 comm="apparmor_parser"
Feb 20 03:52:07 ubuntu-phablet kernel: [  491.787186]type=1400 
audit(1424404327.648:151): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor" 
pid=7613 comm="apparmor_parser"
Feb 20 03:52:08 ubuntu-phablet kernel: [  492.354445]type=1400 
audit(1424404328.208:152): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 pid=7658 comm="apparmor_parser"
Feb 20 03:52:08 ubuntu-phablet kernel: [  492.354874]type=1400 
audit(1424404328.208:153): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor" 
pid=7658 comm="apparmor_parser"
Feb 20 03:52:08 ubuntu-phablet kernel: [  492.398480]type=1400 
audit(1424404328.258:154): apparmor="DENIED" operation="open" 
profile="/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance"
 name="/tmp/

[Touch-packages] [Bug 1301623] Re: unity freezes when moving windows among workspaces

[Ian]

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

I can confirm that disabeling window snapping in unity tweak tool fixes
this issue for me, I like my window snapping :(

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

Title:
  unity freezes when moving windows among workspaces

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Sometimes In Ubuntu 14.04, when I move windows from one workspace to
  another, Unity freezes, letting me with this 4 workspaces overview. I
  have to use terminal and restart Unity to resolve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr  2 23:26:06 2014
  DistUpgraded: 2014-03-18 07:46:56,695 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:365e]
  InstallationDate: Installed on 2014-02-10 (51 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: LENOVO 10104
  ProcEnviron:
   LANGUAGE=cs
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic 
root=UUID=3a918684-e656-4e86-9b7b-22e0fd6b2135 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-18 (15 days ago)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT31AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10104
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Mar 31 16:48:50 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8192
   vendor LEN
  xserver.version: 2:1.15.0-1ubuntu7

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

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

[Touch-packages] [Bug 1423031] Re: NSS incorrectly preferring a longer, weaker chain over a shorter, stronger chain

[Mathew Hodson]

** 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 nss in Ubuntu.
https://bugs.launchpad.net/bugs/1423031

Title:
  NSS incorrectly preferring a longer, weaker chain over a shorter,
  stronger chain

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Lucid:
  Fix Released
Status in nss source package in Precise:
  Fix Released
Status in nss source package in Trusty:
  Fix Released
Status in nss source package in Utopic:
  Fix Released
Status in nss source package in Vivid:
  Fix Released
Status in nss package in Debian:
  Confirmed

Bug description:
  See:

  https://code.google.com/p/chromium/issues/detail?id=437733

  and

  https://code.google.com/p/chromium/issues/detail?id=459131

  This issue is fixed in upstream libnss3 version >= 3.17.4

  This issue causes incorrect SHA1 sunset behaviour in Google Chrome.

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

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

[Touch-packages] [Bug 1423031] Re: NSS incorrectly preferring a longer, weaker chain over a shorter, stronger chain

[Mathew Hodson]

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-1569

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

Title:
  NSS incorrectly preferring a longer, weaker chain over a shorter,
  stronger chain

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Lucid:
  Fix Released
Status in nss source package in Precise:
  Fix Released
Status in nss source package in Trusty:
  Fix Released
Status in nss source package in Utopic:
  Fix Released
Status in nss source package in Vivid:
  Fix Released
Status in nss package in Debian:
  Confirmed

Bug description:
  See:

  https://code.google.com/p/chromium/issues/detail?id=437733

  and

  https://code.google.com/p/chromium/issues/detail?id=459131

  This issue is fixed in upstream libnss3 version >= 3.17.4

  This issue causes incorrect SHA1 sunset behaviour in Google Chrome.

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

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

[Touch-packages] [Bug 1423455] Re: [vivid] [systemd] 6.0-0ubuntu3 upgrade have broken sound output

[dino99]

Finally found the good settings to get back the sound output (after a
cold reboot)

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

Title:
  [vivid]  [systemd] 6.0-0ubuntu3 upgrade have broken sound output

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Previous 6.0-0ubuntu2 was working fine; but since that 3 upgrade the
  sound is broken: the settings looks normal (no mute or warnings) and
  there is no 'beep' when testing the speakers output.

  Sadly the 'proposed' packages can't be downgraded as it try to remove most of 
the DE packages too.
  Please bring back the previous packages (via an 0ubuntu4+is0ubuntu2 or so) 
until a real fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0
  Uname: Linux 3.19.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1765 F pulseaudio
   /dev/snd/pcmC0D1p:   oem1765 F...m pulseaudio
   /dev/snd/controlC0:  oem1765 F pulseaudio
  BootDmesg: (Nothing has been logged yet.)
  CurrentDesktop: GNOME
  Date: Thu Feb 19 07:06:08 2015
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1423455] Re: [vivid] [systemd] 6.0-0ubuntu3 upgrade have broken sound output

[dino99]

Thanks Luke, finally i've found the good settings to get back the sound
output

** Changed in: pulseaudio (Ubuntu)
   Status: New => Invalid

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

Title:
  [vivid]  [systemd] 6.0-0ubuntu3 upgrade have broken sound output

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Previous 6.0-0ubuntu2 was working fine; but since that 3 upgrade the
  sound is broken: the settings looks normal (no mute or warnings) and
  there is no 'beep' when testing the speakers output.

  Sadly the 'proposed' packages can't be downgraded as it try to remove most of 
the DE packages too.
  Please bring back the previous packages (via an 0ubuntu4+is0ubuntu2 or so) 
until a real fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0
  Uname: Linux 3.19.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1765 F pulseaudio
   /dev/snd/pcmC0D1p:   oem1765 F...m pulseaudio
   /dev/snd/controlC0:  oem1765 F pulseaudio
  BootDmesg: (Nothing has been logged yet.)
  CurrentDesktop: GNOME
  Date: Thu Feb 19 07:06:08 2015
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1423455] Re: [vivid] [systemd] 6.0-0ubuntu3 upgrade have broken sound output

[dino99]

** Summary changed:

- [vivid]  6.0-0ubuntu3 upgrade have broken sound output
+ [vivid]  [systemd] 6.0-0ubuntu3 upgrade have broken sound output

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

Title:
  [vivid]  [systemd] 6.0-0ubuntu3 upgrade have broken sound output

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Previous 6.0-0ubuntu2 was working fine; but since that 3 upgrade the
  sound is broken: the settings looks normal (no mute or warnings) and
  there is no 'beep' when testing the speakers output.

  Sadly the 'proposed' packages can't be downgraded as it try to remove most of 
the DE packages too.
  Please bring back the previous packages (via an 0ubuntu4+is0ubuntu2 or so) 
until a real fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0
  Uname: Linux 3.19.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1765 F pulseaudio
   /dev/snd/pcmC0D1p:   oem1765 F...m pulseaudio
   /dev/snd/controlC0:  oem1765 F pulseaudio
  BootDmesg: (Nothing has been logged yet.)
  CurrentDesktop: GNOME
  Date: Thu Feb 19 07:06:08 2015
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1066157] Re: dash +orca does not speak the names of application icons

[Launchpad Bug Tracker]

** Branch linked: lp:~themuso/unity/set-focus-to-false-on-window-
deactivation

** Branch linked: lp:~themuso/unity/explore-children-when-view-or-
layout-added

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

Title:
  dash +orca does not speak the names of application icons

Status in OEM Priority Project:
  New
Status in Unity:
  Triaged
Status in Unity 5.0 series:
  New
Status in Unity 6.0 series:
  Won't Fix
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  using orca and navigating around the dash with the keyboard I hear the
  names of videos, shopping results, files and folders, application
  suggestions from the software centre, but not the very most important
  thing in the dash - applications installed that I might want to run.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1066157/+subscriptions

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

[Touch-packages] [Bug 1423787] [NEW] music-app blocks system suspend even when not playing any song

[Ricardo Salveti]

Public bug reported:

current build number: 241
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-02-20 00:41:40
version version: 241
version ubuntu: 20150219
version device: 20150216-fe747ac
version custom: 20150216-561-29-186

I know we currently have an exception in the lifecycle for music-app,
and it seems that there is a quite critical bug with it at the current
image.

Opening up music-app is already enough for unity8 to hold a system state
request from powerd, blocking suspend until you close the app (having it
in the background doesn't really help here).

Ideally the system state request (wakelock) should just be enabled and
active when the music-app is also active, playing songs.

This bug can drastically affect the battery life for the user of the
phone.

You can check this by running 'powerd-cli list' after opening music-app.
phablet@ubuntu-phablet:~$ powerd-cli list
powerd-cli: Running as user is not fully supported.
System State Requests:
  Name: active, Owner: :1.77, State: 1

** Affects: qtmir (Ubuntu RTM)
 Importance: Undecided
 Status: New

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

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

** Package changed: unity8 (Ubuntu) => unity8 (Ubuntu RTM)

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

Title:
  music-app blocks system suspend even when not playing any song

Status in qtmir package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  current build number: 241
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-20 00:41:40
  version version: 241
  version ubuntu: 20150219
  version device: 20150216-fe747ac
  version custom: 20150216-561-29-186

  I know we currently have an exception in the lifecycle for music-app,
  and it seems that there is a quite critical bug with it at the current
  image.

  Opening up music-app is already enough for unity8 to hold a system
  state request from powerd, blocking suspend until you close the app
  (having it in the background doesn't really help here).

  Ideally the system state request (wakelock) should just be enabled and
  active when the music-app is also active, playing songs.

  This bug can drastically affect the battery life for the user of the
  phone.

  You can check this by running 'powerd-cli list' after opening music-app.
  phablet@ubuntu-phablet:~$ powerd-cli list
  powerd-cli: Running as user is not fully supported.
  System State Requests:
Name: active, Owner: :1.77, State: 1

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

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

[Touch-packages] [Bug 1423786] [NEW] idk

Public bug reported:

idk

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic i686
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Feb 19 22:29:29 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.13.0-44-generic, i686: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:029f]
   Subsystem: Dell Device [1028:029f]
InstallationDate: Installed on 2015-01-16 (34 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
MachineType: Dell Inc. Studio 1537
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=7308edf5-f8bd-4a0c-9cbd-15b658a95edc ro persistent quiet splash 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/02/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0P173H
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A02
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd09/02/2008:svnDellInc.:pnStudio1537:pvrA02:rvnDellInc.:rn0P173H:rvrA02:cvnDellInc.:ct8:cvrA02:
dmi.product.name: Studio 1537
dmi.product.version: A02
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
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.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.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Feb 19 17:41:01 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 397 
 vendor LGD
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/1423786

Title:
  idk

Status in xorg package in Ubuntu:
  New

Bug description:
  idk

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Feb 19 22:29:29 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.13.0-44-generic, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:029f]
 Subsystem: Dell Device [1028:029f]
  InstallationDate: Installed on 2015-01-16 (34 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: Dell Inc. Studio 1537
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=7308edf5-f8bd-4a0c-9cbd-15b658a95edc ro persistent quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0P173H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:b

[Touch-packages] [Bug 1367835] Re: Error downloading GPS Xtra data: [...] Timeout was reached: No space left on device

[Gorsh]

I get the same exact timeout error; mako with 15.04 (r1).

Is there a way we can hack it to work in the meantime?

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

Title:
  Error downloading GPS Xtra data: [...] Timeout was reached: No space
  left on device

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  To test location-service with latest utopic-proposed image on mako, I had to 
make some adjustments:
  1) change:
  export HERE_IMEI_FRAGMENT=$Serial
  to:
  export HERE_IMEI_FRAGMENT=35513605
  in /etc/init/ubuntu-location-provider-here-posclientd.conf to help the 
service come up on boot (see bug #1367244), not sure it helps though.

  2) change
  exec /usr/bin/ubuntu-location-serviced --bus system --provider $provider 
$poptions
  to:
  exec /usr/bin/ubuntu-location-serviced --bus system --provider $provider 
$poptions --provider remote::Provider 
--remote::Provider::name="com.ubuntu.espoo.Service.Provider" 
--remote::Provider::path="/com/ubuntu/espoo/Service/Provider"
  in /etc/init/ubuntu-location-service.override.

  I saw this in location-service log:
  E0910 16:42:09.632657  4078 android_hardware_abstraction_layer.cpp:157] Error 
downloading GPS Xtra data: 
/build/buildd/net-cpp-1.1.0+14.10.20140804/src/core/net/http/impl/curl/request.h@157
 - execute: Timeout was reached: No space left on device

  $ system-image-cli -i
  current build number: 235
  device name: mako
  channel: ubuntu-touch/utopic-proposed
  last update: 2014-09-10 15:19:31
  version version: 235
  version ubuntu: 20140910
  version device: 20140903.1
  version custom: mako-0.3a

  Seems this is due to GPS data file being saved to the wrong place:
  $ df -hl
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/loop0  2,0G  1,5G  423M  78% /
  udev916M  4,0K  916M   1% /dev
  tmpfs   184M  728K  183M   1% /run
  /dev/mmcblk0p23  13G  1,7G   11G  14% /home
  /dev/loop1  107M  105M  1,5M  99% /lib/modules
  none4,0K 0  4,0K   0% /android
  tmpfs   918M  4,0K  918M   1% /etc/fstab
  /dev/disk/by-partlabel/cache552M   55M  498M  10% /android/cache
  /dev/disk/by-partlabel/persist   16M  4,2M   12M  27% /android/persist
  /dev/disk/by-partlabel/modem 64M   54M   11M  83% /android/firmware
  none4,0K 0  4,0K   0% /sys/fs/cgroup
  tmpfs   918M   32K  918M   1% /tmp
  none5,0M 0  5,0M   0% /run/lock
  none918M   96K  918M   1% /run/shm
  none100M   24K  100M   1% /run/user
  tmpfs   918M 0  918M   0% /media
  tmpfs   918M  8,0K  918M   1% /var/lib/sudo

  Cheers,

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

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

[Touch-packages] [Bug 1423031] Re: NSS incorrectly preferring a longer, weaker chain over a shorter, stronger chain

[Cambell Prince]

Tested on Trusty and confirmed fixed.  Thanks.

- Google Chrome 40.0.2214.115-1
- libnss3 2:3.17.4-0ubuntu0.14.04.1

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

Title:
  NSS incorrectly preferring a longer, weaker chain over a shorter,
  stronger chain

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Lucid:
  Fix Released
Status in nss source package in Precise:
  Fix Released
Status in nss source package in Trusty:
  Fix Released
Status in nss source package in Utopic:
  Fix Released
Status in nss source package in Vivid:
  Fix Released
Status in nss package in Debian:
  Confirmed

Bug description:
  See:

  https://code.google.com/p/chromium/issues/detail?id=437733

  and

  https://code.google.com/p/chromium/issues/detail?id=459131

  This issue is fixed in upstream libnss3 version >= 3.17.4

  This issue causes incorrect SHA1 sunset behaviour in Google Chrome.

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

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

[Touch-packages] [Bug 1423359] Re: taking screenshots with mirscreencast fails

[Daniel van Vugt]

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

** Tags added: screencast

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

Title:
  taking screenshots with mirscreencast fails

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

Bug description:
  From autopilot we see this when there is a failed test.

  21:40:25.138 ERROR testcase:387 - Taking screenshot failed: Command
  '['mirscreencast', '-m', '/run/mir_socket', '-n', '1', '-f', '/tmp/ap-
  screenshot-data-1424295625.rgba']' returned non-zero exit status 1

  I tried setting the LC_ALL env var to C, and it works.

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

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

[Touch-packages] [Bug 1322494] Re: Xorg freeze

[Christopher M. Penalver]

Tom, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1322494/comments/4
regarding this being fixed with a reinstall. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yellow line and then choosing a new status in the revealed drop
down box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Full screen freeze appears at random, several times per day. I  am not
  sure, but it seems to happen more often after I start Skype

  - The screen completely freezes for about 30 seconds after I open a new 
window. It might be that window rendering even did not finish: window can be 
transparent in locked status or some fonts are rendered half-way
  - The notification bar is frozen, no drop downs, system monitor graph stops.
  -  I need to open Terminal, wait 30 seconds until screen comes alive again 
and then I can type reboot and system is ok again... 

  Side note:

  -  In 13.10 Skype status change symbols appeared instantly. Ever since 14.04, 
it takes about 2 seconds before new status appears
  - I lost the Sound Indicator from the notification bar for some unknow reason

  Dont know if cause of bug  is xorg or notify-osd or ... ?

  Ubuntu 14.04 LTS / i7-4770K / Intel graphics / Logitech wireless
  keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 23 09:40:22 2014
  DistUpgraded: 2014-04-28 19:58:18,374 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   i915-3.9-3.8, 0.02, 3.8.0-31-generic, x86_64: installed
   virtualbox, 4.3.10, 3.11.0-20-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
  InstallationDate: Installed on 2013-08-21 (274 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=640c9572-0cd1-4537-b058-a9e2df49680e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to trusty on 2014-04-28 (24 days ago)
  dmi.bios.date: 12/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1707
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z87
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ87:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
10.0.0-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri May 23 08:24:30 2014
  xserver.config

[Touch-packages] [Bug 1422345] Re: stop being nice does not work

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades - 0.83.5

---
unattended-upgrades (0.83.5) unstable; urgency=medium


  [ Brian Murray ]
  * properly restore niceness (LP: #1422345)

 -- Michael Vogt   Thu, 19 Feb 2015 15:06:58 +0100

** Changed in: unattended-upgrades (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1422345

Title:
  stop being nice does not work

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Fix Committed
Status in unattended-upgrades source package in Utopic:
  Fix Committed
Status in unattended-upgrades package in Debian:
  New

Bug description:
  Test Case
  -
  1) Install apache2 from the -release pocket
  2) Run unattended-upgrades
  3) Observe apache2 running with a niceness of 19
  4) Downgrade apache2 to the version from the -release pocket
  5) Install the version of unattended-upgrades from -proposed
  6) Run unattended-upgrades
  7) Observe apache2 running with a niceness of 0 i.e. no niceness


  Since version 0.81, unattended-upgrades does the upgrade calculation with 
os.nice(19). To finish the nice block in /usr/bin/unattended-upgrade, the 
following call is used:
  os.nice(0)

  Since the argument is interpreted as incremental, this should be:
  os.nice(-19)

  Without this fix, this problem is back:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701850
  "unattended-upgrades: nice 19/ionice idle inherited by restarted processes"

  Found in the trusty version (0.82.1ubuntu2), but probably in any
  version (including Debian) since 0.81.

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

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

[Touch-packages] [Bug 1423752] [NEW] Sound Settings not opening from indicator

[Elfy]

Public bug reported:

Saw an update for indicator-sound just now .

indicator-sound (12.10.2+15.04.20150205-0ubuntu1) vivid; urgency=medium

Double checked that indicator-sound worked correctly.

Updated and rebooted.

Sound Settings no longer starts from indicator.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Feb 19 23:39:35 2015
InstallationDate: Installed on 2015-01-09 (41 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150108)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug regression-proposed vivid

** Tags added: egression-proposed

** Tags removed: egression-proposed
** Tags added: regression-proposed

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

Title:
  Sound Settings not opening from indicator

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Saw an update for indicator-sound just now .

  indicator-sound (12.10.2+15.04.20150205-0ubuntu1) vivid;
  urgency=medium

  Double checked that indicator-sound worked correctly.

  Updated and rebooted.

  Sound Settings no longer starts from indicator.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Feb 19 23:39:35 2015
  InstallationDate: Installed on 2015-01-09 (41 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150108)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1362469] Re: AppArmor unrequested reply protection generates unallowable denials

[Tyler Hicks]

The AppArmor D-Bus mediation patches have been merged in upstream D-Bus.
The final patch set that was merged includes a fix for this bug, among
others that do not have Launchpad bugs but were discovered during the
upstream patch review process.

This is a debdiff to refresh the patches in our Vivid dbus package with
the versions that landed upstream.

I've tested it in an amd64 Vivid VM, using the test-dbus.py script from
lp:qa-regression-testing as well as the D-Bus regression tests in
lp:apparmor. I manually verified that the
org.freedesktop.DBus.GetConnectionCredentials method was working
correctly, as well as the legacy
org.freedesktop.DBus.GetAppArmorSecurityContext method. I also ran the
test case in comment #5 of this bug in addition to confining pasaffe and
verifying that this bug was fixed. Finally, I did manual exploratory
testing in the VM.

I also tested it on a Mako device using a vivid-proposed image (build
105). The testing was manual but I verified that I could use the
browser, use a webapp, install and use a new app, adjust system
settings, etc.

A PPA build of this package exists in ppa:ubuntu-security-proposed/ppa

** Patch added: "dbus_1.8.12-1ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1362469/+attachment/4322934/+files/dbus_1.8.12-1ubuntu2.debdiff

** Changed in: dbus (Ubuntu)
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

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

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

Title:
  AppArmor unrequested reply protection generates unallowable denials

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Starting with utopic's dbus 1.8.6-1ubuntu1 package, the new AppArmor
  unrequested reply protections can generate some denials that can't
  easily be allowed in policy. For example, when running a confined
  pasaffe, you see these denials when starting and closing pasaffe:

  apparmor="DENIED" operation="dbus_error"  bus="session"
  error_name="org.freedesktop.DBus.Error.UnknownMethod" mask="send"
  name=":1.22" pid=4993 profile="/usr/bin/pasaffe" peer_pid=3624
  peer_profile="unconfined"

  It isn't obvious how to construct an AppArmor D-Bus rule to allow that
  operation. A bare "dbus," rule allows it but that's not acceptable for
  profiles implementing tight D-Bus confinement.

  The code that implements unrequested reply protections should be
  reviewed for issues and, if everything looks good there,
  investigations into how to allow the operation that triggers the above
  denial should occur.

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

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

[Touch-packages] [Bug 1313289] Re: Low Graphics Mode with AMD R9 270X

[David Maza]

Working in the latest version of Ubuntu. It looks like an upstream
update of fglrx fixed it.

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

** Changed in: xorg (Ubuntu)
   Status: Fix Released => Invalid

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

Title:
  Low Graphics Mode with AMD R9 270X

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I have an AMD R9 270X graphics card and Ubuntu will occasionally go
  into "low-graphics mode" when starting up. At that point I cannot do
  anything apart from drop into the terminal.

  It happens sporadically, about 3/4 of the time. Often a reboot will
  fix it however because it happens so often, it's very annoying.

  I've tried installing fglrx and fglrx-updates along with the latest
  proprietary AMD drivers including 14.4 stable and 14.3 beta. However
  it still occurs.

  I've also tried using failsafeX settings among other things without
  success.

  Attached are the Xorg and Xorg.failsafe log files.

  There's a segmentation fault at the bottom of the failsafe log files
  which may have something to do with it?

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

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

[Touch-packages] [Bug 1421396] Re: Volume notification does not show if phone is muted

[Ted Gould]

** Changed in: indicator-sound (Ubuntu)
   Status: New => 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/1421396

Title:
  Volume notification does not show if phone is muted

Status in indicator-sound package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce

  1. Turn the volume all the way down (to mute)
  2. Wait for the volume notification to disappear
  3. Press volume decrease key again

  Expected behavior: volume notification appears, and gives user feedback that 
phone is muted
  Actual behavior: volume notification does not appear

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

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

[Touch-packages] [Bug 1416520] Re: vivid: Sound indicator pops up on initial boot after a flash

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-sound -
12.10.2+15.04.20150219.1-0ubuntu1

---
indicator-sound (12.10.2+15.04.20150219.1-0ubuntu1) vivid; urgency=medium

  [ Ted Gould ]
  * Add eventually functions to indicator fixture
  * Add notifications mock and tests
  * Track the reason a volume was set to filter volume changes more
accurately (LP: #1416520)
 -- CI Train BotThu, 19 Feb 2015 16:27:48 +

** Branch linked: lp:ubuntu/vivid-proposed/indicator-sound

** Changed in: indicator-sound (Ubuntu)
   Status: New => 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/1416520

Title:
  vivid: Sound indicator pops up on initial boot after a flash

Status in indicator-sound package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Flash vivid 84+ onto you mako/manta/flo
  2. When the welcome wizard start run though it
  3. At some point in the wizard or just after the volume osd with popup

  EXPECTED:
  I don't expect to the the indicator popup randomly

  ACTUAL:
  At some point in the boot process post flash the sound indicator osd pops up.

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

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

[Touch-packages] [Bug 1422401] Re: dialer app doesn't work correctly on multiple calls on a wired headset

[Launchpad Bug Tracker]

This bug was fixed in the package telepathy-ofono -
0.2+15.04.20150217-0ubuntu1

---
telepathy-ofono (0.2+15.04.20150217-0ubuntu1) vivid; urgency=medium

  [ Tiago Salem Herrmann ]
  * Retry when hangup() or answer() fail. (LP: #1422401)
 -- CI Train BotTue, 17 Feb 2015 17:23:42 +

** Changed in: telepathy-ofono (Ubuntu)
   Status: New => Fix Released

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

Title:
  dialer app doesn't work correctly on multiple calls on a wired headset

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Telepathy Ofono:
  New
Status in ofono package in Ubuntu:
  Confirmed
Status in telepathy-ofono package in Ubuntu:
  Fix Released
Status in ofono package in Ubuntu RTM:
  Confirmed
Status in telepathy-ofono package in Ubuntu RTM:
  Fix Released

Bug description:
  STEPS:
  REQUIREMENTS: 1 wired headset with call accept/hangup button

  1. Flash the latest rtm-proposed image
  2. Call the phone
  3. Tap the headset call accept button
  4. Tap the button again
  5. Recall the phone
  repeat steps 3-5 eventually the dialer app will not work as expected.

  EXPECTED:
  I always expect the call to go through and be accepted and hung up on.

  ACTUAL:
  At some point the call will not go through when accepted instead it will 
display the dialpad page of the dialer app.  The phone ringing the device will 
keep ringing, once you hang up that phone the phone under test beeps 3 times 
and displays a missed call notification.

  See attached video

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

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

[Touch-packages] [Bug 1421396] Re: Volume notification does not show if phone is muted

[Ted Gould]

** Branch linked: lp:~ted/indicator-sound/volume-reason

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

Title:
  Volume notification does not show if phone is muted

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Steps to reproduce

  1. Turn the volume all the way down (to mute)
  2. Wait for the volume notification to disappear
  3. Press volume decrease key again

  Expected behavior: volume notification appears, and gives user feedback that 
phone is muted
  Actual behavior: volume notification does not appear

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

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

[Touch-packages] [Bug 1422401] Re: dialer app doesn't work correctly on multiple calls on a wired headset

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/telepathy-ofono

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

Title:
  dialer app doesn't work correctly on multiple calls on a wired headset

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Telepathy Ofono:
  New
Status in ofono package in Ubuntu:
  Confirmed
Status in telepathy-ofono package in Ubuntu:
  Fix Released
Status in ofono package in Ubuntu RTM:
  Confirmed
Status in telepathy-ofono package in Ubuntu RTM:
  Fix Released

Bug description:
  STEPS:
  REQUIREMENTS: 1 wired headset with call accept/hangup button

  1. Flash the latest rtm-proposed image
  2. Call the phone
  3. Tap the headset call accept button
  4. Tap the button again
  5. Recall the phone
  repeat steps 3-5 eventually the dialer app will not work as expected.

  EXPECTED:
  I always expect the call to go through and be accepted and hung up on.

  ACTUAL:
  At some point the call will not go through when accepted instead it will 
display the dialpad page of the dialer app.  The phone ringing the device will 
keep ringing, once you hang up that phone the phone under test beeps 3 times 
and displays a missed call notification.

  See attached video

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

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

[Touch-packages] [Bug 1188569] Re: Some keyboard shortcuts randomly stop working

[Erik M]

I got the same. I made a different post, bug 1405214, and list  some 
observations here:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1405214

Whenever shortcuts stop working, and 
unity-settings-daemon 
crashes then also. (and it seems notify-osd, too, but I'm not sure)

It seemed first that
unity-tweak-tool --reset

fixed the issue -- but the problem returned (careful, many of your unity
custom settings will be lost and you need to reconfigure if you do
this!)

I still get the impression that this crash may be related to docking my
laptop -- at least I need to suspend and wake several times, otherwise
it doesn't happen. Anyone else seeing this behavior?

--> This is super annoying and debilitates my work flow enormously, as I
favor shortcuts vs. mouse usage!

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

Title:
  Some keyboard shortcuts randomly stop working

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  Certain shortcuts randomly stops working in my computer. They are Super+s 
(workspace switcher), Super+Up (switch to workspace above) and Super+Down 
(switch to workspace below). Other shortcuts work fine.

  A few notes that might help:
  1- Reassigning shortcuts make them work again except for Super+s.
  2- Rebooting make shortcuts work.
  3- I have been using these shortcuts with many previous ubuntu versions and 
my preferences are old.
  4- I am not sure of certain steps that produces the problem. The shortcuts 
sometimes stop working but once they stop, they do not work unless I reassign 
them or reboot.

  I am using Ubuntu 13.04.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,grid,mousepoll,place,wall,snap,resize,vpswitch,session,animation,gnomecompat,imgpng,commands,move,workarounds,fade,unitymtgrabhandles,expo,scale,ezoom,unityshell]
  Date: Fri Jun  7 13:40:06 2013
  InstallationDate: Installed on 2013-05-27 (11 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1404779] Re: Hp Designjet 130 prints part of page then freezes

[Rod Boudreaux]

Ok Seems like we got off track. Where should I go to get help?

When I connect my HP DesignJet 130 to Ubuntu 14.10 it installs a driver 
that says it is for my printer.

attached is a picture of the printer properties that shows the details.

Also attached is the HP-DesignJet_130_cdnj500.ppd which appears to be 
the driver scrip.

The driver prints part of a page then freezes. However it printed one 
test page complete When I set it to 11x17".

Please direct me to the proper place to get help. If you need more 
information let me know.

On 02/19/2015 02:07 AM, Sanjay Kumar wrote:
> Hello Rod,
>
> "HP Designjet 130 printer" is not supported in HP Linux driver (HPLIP).
> List of Designjet printers Supported/Not_Supported can be found at
> http://hplipopensource.com/hplip-web/supported_devices/designjet.html .
> Sorry for the inconvenience caused.
>
> Thanks,
> Sanjay
>


** Attachment added: "HP-DesignJet_130-cdnj500.ppd"
   
https://bugs.launchpad.net/bugs/1404779/+attachment/4322824/+files/HP-DesignJet_130-cdnj500.ppd

** Attachment added: "printerProperties.png"
   
https://bugs.launchpad.net/bugs/1404779/+attachment/4322825/+files/printerProperties.png

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

Title:
  Hp Designjet 130 prints part of page then freezes

Status in HP Linux Imaging and Printing:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  Cups

  Printer works under msdos. Have not been able to get full page printed under 
ubuntu. Prints A few lines to 1/3 page then freezes. must remove power to reset 
and remove paper. All controls freeze.
  Tried on several computers and ver of O/s. Currently 14.04. See attached 
Printer cmd report. Per lunchpad direction.

  
  rod@rod-HP-Compaq-dc7900-Convertible-Minitower:~$ lsmod | grep usb
  usblp  18277  0 
  usbhid 47070  0 
  hid87604  2 hid_generic,usbhid
  rod@rod-HP-Compaq-dc7900-Convertible-Minitower:~$ tail -f /var/log/syslog
  Dec 21 21:45:39 rod-HP-Compaq-dc7900-Convertible-Minitower python: 
io/hpmud/musb.c 2105: ignoring hp:/usb/hp_designjet_130?serial=MY6AID80CM 
support=0
  Dec 21 21:45:39 rod-HP-Compaq-dc7900-Convertible-Minitower python: 
io/hpmud/pp.c 627: unable to read device-id ret=-1
  Dec 21 21:45:54 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
1975.816339] type=1400 audit(1419216354.023:68): apparmor="DENIED" 
operation="signal" profile="/usr/sbin/cupsd" pid=2520 comm="cups-deviced" 
requested_mask="send" denied_mask="send" signal=term peer="unconfined"
  Dec 21 21:45:54 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
1975.818276] type=1400 audit(1419216354.023:69): apparmor="DENIED" 
operation="signal" profile="/usr/sbin/cupsd" pid=2150 comm="cupsd" 
requested_mask="send" denied_mask="send" signal=term peer="unconfined"
  Dec 21 21:45:54 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
1975.820058] parport0: lp tried to release parport when not owner
  Dec 21 21:45:54 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
1975.820072] parport0: ppdev0 forgot to release port
  Dec 21 21:51:12 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2294.664108] usb 3-2: USB disconnect, device number 4
  Dec 21 21:51:12 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2294.664280] usblp0: removed
  Dec 21 21:51:12 rod-HP-Compaq-dc7900-Convertible-Minitower 
udev-configure-printer: remove /devices/pci:00/:00:1a.0/usb3/3-2
  Dec 21 21:51:12 rod-HP-Compaq-dc7900-Convertible-Minitower colord: device 
removed: sysfs-Hewlett-Packard-hp_designjet_130
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.104036] usb 3-2: new full-speed USB device number 5 using uhci_hcd
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303075] usb 3-2: New USB device found, idVendor=03f0, idProduct=0314
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303080] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303083] usb 3-2: Product: hp designjet 130
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303085] usb 3-2: Manufacturer: Hewlett-Packard
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303088] usb 3-2: SerialNumber: MY6AID80CM
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.334166] usblp 3-2:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 0 
proto 2 vid 0x03F0 pid 0x0314
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower logger: loading HP 
Device 003 005
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower colord: Device 
added: sysfs-Hewlett-Packard-hp_designjet_130
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower 
udev-configure-printer: a

Re: [Touch-packages] [Bug 1423455] Re: [vivid] 6.0-0ubuntu3 upgrade have broken sound output

[Luke Yelavich]

I have no experience with trying to use pulseaudio when booting with
systemd, I am still using upstart, which is what vivid will be using.

I'll have to defer to someone who knows more about systemd.

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

Title:
  [vivid]  6.0-0ubuntu3 upgrade have broken sound output

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Previous 6.0-0ubuntu2 was working fine; but since that 3 upgrade the
  sound is broken: the settings looks normal (no mute or warnings) and
  there is no 'beep' when testing the speakers output.

  Sadly the 'proposed' packages can't be downgraded as it try to remove most of 
the DE packages too.
  Please bring back the previous packages (via an 0ubuntu4+is0ubuntu2 or so) 
until a real fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0
  Uname: Linux 3.19.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1765 F pulseaudio
   /dev/snd/pcmC0D1p:   oem1765 F...m pulseaudio
   /dev/snd/controlC0:  oem1765 F pulseaudio
  BootDmesg: (Nothing has been logged yet.)
  CurrentDesktop: GNOME
  Date: Thu Feb 19 07:06:08 2015
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1422486] Re: latest edge tutorial gets stuck with n7 landscape mode

[Michael Terry]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

Title:
  latest edge tutorial gets stuck with n7 landscape mode

Status in unity8 package in Ubuntu:
  New

Bug description:
  If you try the vivid silo 0 on N7, it puts N7 in landscape mode
  unfortunately the new edge tutorial gets stuck on the second step (right edge 
swipe)

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

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

[Touch-packages] [Bug 1423565] Re: Missing SIM page not shown during the setup wizard

[Michael Terry]

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

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

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

Title:
  Missing SIM page not shown during the  setup wizard

Status in unity8 package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu RTM:
  In Progress

Bug description:
  RTM image 240.

  0. Clean flash phone
  1. Boot the phone without a sim
  2. Note during the wizard it does not say that "No SIM card detected"

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: ubuntu-system-settings-wizard 0.3+15.04.20150218~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Wed Jan  1 08:23:23 2014
  InstallationDate: Installed on 2015-02-18 (-413 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150218-184321)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.ubuntu-system-settings-wizard-cleanup.log:
   ubuntu-system-settings-wizard start/post-stop, process 3095
   ubuntu-system-settings-wizard start/post-stop, process 3081
   ubuntu-system-settings-wizard start/post-stop, process 3276

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

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

[Touch-packages] [Bug 1423687] Re: compiz crashed with SIGSEGV in unity::MultiActionList::Initiate()

[Stephen M. Webb]

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

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

** Information type changed from Private to Public

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

Title:
  compiz crashed with SIGSEGV in unity::MultiActionList::Initiate()

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

Bug description:
  Disable Animations and enable them after restart of PC affect this.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150205-0ubuntu1
  Uname: Linux 3.18.3-031803-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 19 21:31:22 2015
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-10-16 (125 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141016)
  ProcCmdline: compiz
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   unity::MultiActionList::Initiate(std::string const&, std::vector > const&, int) const () from 
/usr/lib/compiz/libunityshell.so
   unity::MultiActionList::InitiateAll(std::vector > const&, int) const () from 
/usr/lib/compiz/libunityshell.so
   unity::PluginAdapter::InitiateScale(std::string const&, int) () from 
/usr/lib/compiz/libunityshell.so
   unity::PluginAdapter::ScaleWindowGroup(std::vector > const&, int, bool) () from 
/usr/lib/compiz/libunityshell.so
   unity::launcher::ApplicationLauncherIcon::Spread(bool, int, bool) () from 
/usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in unity::MultiActionList::Initiate()
  UpgradeStatus: Upgraded to vivid on 2015-01-23 (27 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions

[Brian Murray]

Hello seshagiri, or anyone else affected,

Accepted systemd into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.11 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Fix udev rules to consider mmc rpmb partitions

Status in systemd package in Ubuntu:
  Fix Released
Status in udev package in Ubuntu:
  Invalid
Status in udisks package in Ubuntu:
  Triaged
Status in udev source package in Precise:
  Triaged
Status in udisks source package in Precise:
  Confirmed
Status in systemd source package in Trusty:
  Fix Committed
Status in udisks source package in Trusty:
  Confirmed

Bug description:
  As per JEDEC 4.5 spec for eMMC devices,
  There is a new partitions as part of eMMC storage devices it self. (Further 
details please refer eMMC spec)

  *In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
  with "mmcblkXrpmb" if device expresses it support of RPMB.

  Issues observed:

  issue 1:
  RPMB (Replay Protected Memory Block), A signed access to a Replay Protected 
Memory Block is provided. This function provides means for the system to store 
data to the specific memory area in an authenticated and replay protected 
manner.
  In that case, any read/write access to this partition device will report 
errors.

  issue 2:
  The by-path, line is wrongly mapping to platform-sdhci-tegra.1  -> 
mmcblk2rpmb were as
  it should be platform-sdhci-tegra.1  -> mmcblk2

  ls -l /dev/disk/by-path/
  total 0
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.1 -> 
../../mmcblk2rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.1-part1 -> 
../../mmcblk2p1
  lrwxrwxrwx 1 root root 13 Jan  3  2000 platform-sdhci-tegra.2 -> ../../mmcblk1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.2-part1 -> 
../../mmcblk1p1
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.3 -> 
../../mmcblk0rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part1 -> 
../../mmcblk0p1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part2 -> 
../../mmcblk0p2

  We have locally resolved in our platform in this file 60-persistent-
  storage.rules

  For issue 1: (with this rule)
  # skip block read for partitions of type rpmb
  KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end"

  For issue 2:
  ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb", 
SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb"
  ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb", 
SYMLINK+="disk/by-path/$env{ID_PATH}"

  Please consider this issues fix in next udev release .

  
  SRU INFO: This is mostly an issue with running backported kernels on 12.04 
and 14.04. There is no test case which would reproduce this on arbitrary 
hardware, but there are several reporters which are in a position to verify a 
proposed update.

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

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

[Touch-packages] [Bug 1420544] Re: [SRU] Ubuntu instances on GCE should use NOOP scheduler

[Brian Murray]

Hello Ben, or anyone else affected,

Accepted systemd into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.11 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  [SRU] Ubuntu instances on GCE should use NOOP scheduler

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  [IMPACT] By default, the Ubuntu kernel uses deadline. Google has
  identified that Cloud Workloads running on Ubuntu perform better using
  NOOP as the default scheduler. Google has requested that Google Cloud
  Compute (GCE) instances use NOOP as the default.

  [FIX] Add udev rule for GCE devices to use NOOP by default.

  [VALIDATION]
  1. Boot Ubuntu instance on Google GCE
  2. Confirm that the scheduler is deadline:
 $ cat /sys/block/sda/queue/scheduler
 noop [deadline] cfq
  3. Install proposed udev package
  4. Reboot
  5. Confirm that schedule is now noop
 $ cat /sys/block/sda/queue/scheduler
[noop] deadline cfq

  [RISK] This patch will affect currently running instances and on
  reboot they should see better performance. However, there is a risk
  that some users will experience a performance hit.

  [ORIGINAL REPORT]

  Per Google's request, Ubuntu instances should use NOOP as the default
  scheduler.

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

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

[Touch-packages] [Bug 854841] Re: add-apt-repository will write duplicate entries to /etc/apt/sources.list

[Brian Murray]

Disregarding my typo of partner this was my test:

(trusty-amd64)root@impulse:/home/bdmurray# add-apt-repository "deb 
http://archive.canonical.com/ubuntu trusty partnet"
(trusty-amd64)root@impulse:/home/bdmurray# cat /etc/apt/sources.list
deb http://ubuntu.osuosl.org/ubuntu trusty main restricted universe multiverse
deb-src http://ubuntu.osuosl.org/ubuntu trusty main restricted universe 
multiverse
deb http://ubuntu.osuosl.org/ubuntu trusty-updates main restricted universe 
multiverse
deb-src http://ubuntu.osuosl.org/ubuntu trusty-updates main restricted universe 
multiverse
deb http://ubuntu.osuosl.org/ubuntu trusty-security main restricted universe 
multiverse
deb http://archive.canonical.com/ubuntu trusty partnet
# deb-src http://archive.canonical.com/ubuntu trusty partnet
deb-src http://ubuntu.osuosl.org/ubuntu trusty-security main restricted 
universe multiverse
(trusty-amd64)root@impulse:/home/bdmurray# add-apt-repository "deb 
http://archive.canonical.com/ubuntu trusty partnet"
(trusty-amd64)root@impulse:/home/bdmurray# cat /etc/apt/sources.list
deb http://ubuntu.osuosl.org/ubuntu trusty main restricted universe multiverse
deb-src http://ubuntu.osuosl.org/ubuntu trusty main restricted universe 
multiverse
deb http://ubuntu.osuosl.org/ubuntu trusty-updates main restricted universe 
multiverse
deb-src http://ubuntu.osuosl.org/ubuntu trusty-updates main restricted universe 
multiverse
deb http://ubuntu.osuosl.org/ubuntu trusty-security main restricted universe 
multiverse
deb http://archive.canonical.com/ubuntu trusty partnet
# deb-src http://archive.canonical.com/ubuntu trusty partnet
# deb-src http://archive.canonical.com/ubuntu trusty partnet
deb-src http://ubuntu.osuosl.org/ubuntu trusty-security main restricted 
universe multiverse

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

Title:
  add-apt-repository will write duplicate entries to
  /etc/apt/sources.list

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Hello,
  Add-apt-repository command allows one to add duplicate entries to sources 
list. Would it be possible to improve this utility it so it adds only unique 
entries?

  Eg. This command, when run twice, adds duplicate entries.
  $ sudo add-apt-repository "deb http://archive.canonical.com/ubuntu oneiric 
partner

  $ grep -Ri partner /etc/apt/sources.list

  ProblemType: BugDistroRelease: Ubuntu 11.10
  Package: python-software-properties 0.81.9
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Tue Sep 20 18:38:17 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110919)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1420544] Re: [SRU] Ubuntu instances on GCE should use NOOP scheduler

[Ben Howard]

Sorry about missing the SRU info. Added.

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

Title:
  [SRU] Ubuntu instances on GCE should use NOOP scheduler

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Trusty:
  In Progress

Bug description:
  [IMPACT] By default, the Ubuntu kernel uses deadline. Google has
  identified that Cloud Workloads running on Ubuntu perform better using
  NOOP as the default scheduler. Google has requested that Google Cloud
  Compute (GCE) instances use NOOP as the default.

  [FIX] Add udev rule for GCE devices to use NOOP by default.

  [VALIDATION]
  1. Boot Ubuntu instance on Google GCE
  2. Confirm that the scheduler is deadline:
 $ cat /sys/block/sda/queue/scheduler
 noop [deadline] cfq
  3. Install proposed udev package
  4. Reboot
  5. Confirm that schedule is now noop
 $ cat /sys/block/sda/queue/scheduler
[noop] deadline cfq

  [RISK] This patch will affect currently running instances and on
  reboot they should see better performance. However, there is a risk
  that some users will experience a performance hit.

  [ORIGINAL REPORT]

  Per Google's request, Ubuntu instances should use NOOP as the default
  scheduler.

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

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

[Touch-packages] [Bug 854841] Re: add-apt-repository will write duplicate entries to /etc/apt/sources.list

[Brian Murray]

Could you add a test case for this? I only see a duplicated commented
out deb-src entry which doesn't seem terribly important.

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

Title:
  add-apt-repository will write duplicate entries to
  /etc/apt/sources.list

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Hello,
  Add-apt-repository command allows one to add duplicate entries to sources 
list. Would it be possible to improve this utility it so it adds only unique 
entries?

  Eg. This command, when run twice, adds duplicate entries.
  $ sudo add-apt-repository "deb http://archive.canonical.com/ubuntu oneiric 
partner

  $ grep -Ri partner /etc/apt/sources.list

  ProblemType: BugDistroRelease: Ubuntu 11.10
  Package: python-software-properties 0.81.9
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Tue Sep 20 18:38:17 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110919)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1420544] Re: [SRU] Ubuntu instances on GCE should use NOOP scheduler

[Ben Howard]

** Description changed:

+ [IMPACT] By default, the Ubuntu kernel uses deadline. Google has
+ identified that Cloud Workloads running on Ubuntu perform better using
+ NOOP as the default scheduler. Google has requested that Google Cloud
+ Compute (GCE) instances use NOOP as the default.
+ 
+ [FIX] Add udev rule for GCE devices to use NOOP by default.
+ 
+ [VALIDATION]
+ 1. Boot Ubuntu instance on Google GCE
+ 2. Confirm that the scheduler is deadline:
+$ cat /sys/block/sda/queue/scheduler
+noop [deadline] cfq
+ 3. Install proposed udev package
+ 4. Reboot
+ 5. Confirm that schedule is now noop
+$ cat /sys/block/sda/queue/scheduler
+   [noop] deadline cfq
+ 
+ [RISK] This patch will affect currently running instances and on reboot
+ they should see better performance. However, there is a risk that some
+ users will experience a performance hit.
+ 
+ [ORIGINAL REPORT]
+ 
  Per Google's request, Ubuntu instances should use NOOP as the default
  scheduler.

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

Title:
  [SRU] Ubuntu instances on GCE should use NOOP scheduler

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Trusty:
  In Progress

Bug description:
  [IMPACT] By default, the Ubuntu kernel uses deadline. Google has
  identified that Cloud Workloads running on Ubuntu perform better using
  NOOP as the default scheduler. Google has requested that Google Cloud
  Compute (GCE) instances use NOOP as the default.

  [FIX] Add udev rule for GCE devices to use NOOP by default.

  [VALIDATION]
  1. Boot Ubuntu instance on Google GCE
  2. Confirm that the scheduler is deadline:
 $ cat /sys/block/sda/queue/scheduler
 noop [deadline] cfq
  3. Install proposed udev package
  4. Reboot
  5. Confirm that schedule is now noop
 $ cat /sys/block/sda/queue/scheduler
[noop] deadline cfq

  [RISK] This patch will affect currently running instances and on
  reboot they should see better performance. However, there is a risk
  that some users will experience a performance hit.

  [ORIGINAL REPORT]

  Per Google's request, Ubuntu instances should use NOOP as the default
  scheduler.

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

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

[Touch-packages] [Bug 1423415] Re: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.04

[Mario Limonciello]

I reproduced this once, but it was while switching HDA and I2S modes, so
i'm suspecting that it might have been related to the default device
being selected.  Are you still able to reproduce this on demand?

When I did reproduce it, xev did pick up keycodes, but no indicator in
the popup when they were pressed.

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

Title:
  [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys
  stopped working in Ubuntu 15.04

Status in Dell Sputnik:
  New
Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Volume hotkeys were working and now they're not. A coworker has
  another 2015 XPS 13 (model 9343) with Ubuntu 15.04. He hasn't updated
  in a week, and the hotkeys function, so it seems like the bug came up
  sometime in the past week.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   jared  4299 F...m arecord
   /dev/snd/controlC1:  jared  2929 F pulseaudio
   /dev/snd/controlC0:  jared  2929 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Feb 18 19:49:30 2015
  InstallationDate: Installed on 2014-11-03 (107 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago)
  dmi.bios.date: 02/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1423415/+subscriptions

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

[Touch-packages] [Bug 1420544] Re: [SRU] Ubuntu instances on GCE should use NOOP scheduler

[Ben Howard]

** Summary changed:

- Ubuntu instances on GCE should use NOOP scheduler
+ [SRU] Ubuntu instances on GCE should use NOOP scheduler

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

Title:
  [SRU] Ubuntu instances on GCE should use NOOP scheduler

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Trusty:
  In Progress

Bug description:
  Per Google's request, Ubuntu instances should use NOOP as the default
  scheduler.

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

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

[Touch-packages] [Bug 854841] Re: add-apt-repository will write duplicate entries to /etc/apt/sources.list

[Eric]

Bump. This still exists.

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

Title:
  add-apt-repository will write duplicate entries to
  /etc/apt/sources.list

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Hello,
  Add-apt-repository command allows one to add duplicate entries to sources 
list. Would it be possible to improve this utility it so it adds only unique 
entries?

  Eg. This command, when run twice, adds duplicate entries.
  $ sudo add-apt-repository "deb http://archive.canonical.com/ubuntu oneiric 
partner

  $ grep -Ri partner /etc/apt/sources.list

  ProblemType: BugDistroRelease: Ubuntu 11.10
  Package: python-software-properties 0.81.9
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Tue Sep 20 18:38:17 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110919)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1423340] Re: [notifications] can we make the volume notification bubble less intrusive

[taiebot65]

Screenshot of tap to return notification


** Attachment added: "taptoreturn.png"
   
https://bugs.launchpad.net/ubuntu-ux/+bug/1423340/+attachment/4322750/+files/taptoreturn.png

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

Title:
  [notifications] can we make the volume notification bubble less
  intrusive

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  Opinion

Bug description:
  See this thread
  https://lists.launchpad.net/ubuntu-phone/msg11237.html

  has some valid points

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

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

[Touch-packages] [Bug 1423340] Re: [notifications] can we make the volume notification bubble less intrusive

[taiebot65]

Just for info when i modify the volume the notification bubble stay up for 4 
sec after manipulation.
I did suggest to put this kind of notification in the top header bar of the 
dash like the "tap to return to call" notification of the dialer app.




** Attachment added: "Proposal"
   
https://bugs.launchpad.net/ubuntu-ux/+bug/1423340/+attachment/4322749/+files/rough_proposal.png

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

Title:
  [notifications] can we make the volume notification bubble less
  intrusive

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  Opinion

Bug description:
  See this thread
  https://lists.launchpad.net/ubuntu-phone/msg11237.html

  has some valid points

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

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

[Touch-packages] [Bug 1423679] [NEW] no resume after suspend

[Avinash Prasad]

Public bug reported:

I had been using ubuntu 12.10, system resume after suspend worked fine. Now I 
have upgraded to 14.04 LTS and the system does not resume after a suspend.
Also I would like to know if there's any way in which I can create a hotspot in 
ubuntu using a WIFI connection. The inbuilt hotspot works like android, i.e. 
the wifi connection stops as soon as the hotspot is created, I wish to use the 
wifi connection to create a hotspot for my phone (just like connectify me 
software on windows). Help me.
Avinash Prasad

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
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Feb 20 01:30:57 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8450G] [1002:9995] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:1950]
InstallationDate: Installed on 2015-02-16 (3 days ago)
InstallationMedia: It
MachineType: Hewlett-Packard HP ProBook 445 G1
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic 
root=/dev/mapper/it--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/05/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CPE Ver. F.21
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1950
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 91.0B
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1:pvrA2018CD200:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 445 G1
dmi.product.version: A2018CD200
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
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.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.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Feb 19 20:05:45 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.7
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 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/1423679

Title:
  no resume after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  I had been using ubuntu 12.10, system resume after suspend worked fine. Now I 
have upgraded to 14.04 LTS and the system does not resume after a suspend.
  Also I would like to know if there's any way in which I can create a hotspot 
in ubuntu using a WIFI connection. The inbuilt hotspot works like android, i.e. 
the wifi connection stops as soon as the hotspot is created, I wish to use the 
wifi connection to create a hotspot for my phone (just like connectify me 
software on windows). Help me.
  Avinash Prasad

  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
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Feb 20 01:30:57 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8450G] 
[1002:9995] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 

[Touch-packages] [Bug 1293439] Re: Apparmor prevents icedtea-7-plugin from creating necessary files

[Seth Arnold]

Franck, you may wish to file a new bug as this one is marked 'Fix
released'. Be sure to include DENIED lines from your kernel logs or
audit logs.

Thanks

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

Title:
  Apparmor prevents icedtea-7-plugin from creating necessary files

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  Apparmor prevents icedtea-7-plugin from creating
  /run/user//icedteaplugin--/, needed to work:

  Mar 17 10:48:52 ad2 kernel: [2831863.964092] type=1400
  audit(1395046132.183:851): apparmor="DENIED" operation="mkdir"
  parent=6425 profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
  name="/run/user/1000/icedteaplugin-pseudo-7DURO0/" pid=30285 comm
  ="plugin-containe" requested_mask="c" denied_mask="c" fsuid=1000
  ouid=1000

  ~> lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  ~> apt-cache policy apparmor
  apparmor:
Installed: 2.8.0-0ubuntu31.1
Candidate: 2.8.0-0ubuntu31.1
Version table:
   *** 2.8.0-0ubuntu31.1 0
  500 http://archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.8.0-0ubuntu31 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apparmor 2.8.0-0ubuntu31.1
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Mar 17 10:59:53 2014
  MarkForUpload: True
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=16001ea5-4e94-44ae-9838-da89b0f3f88e ro
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to saucy on 2013-09-10 (187 days ago)

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

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

[Touch-packages] [Bug 1423342] Re: SDCard fake needed for filemanager autopilot tests

[Nicholas Skaggs]

It's unclear to me where this helper should lie; presumably it's above
both autopilot and the toolkit, but ?

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

** Tags added: autopilot-helper

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

Title:
  SDCard fake needed for filemanager autopilot tests

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

Bug description:
  Faking SDCard is needed for writing autopilot tests for filemanager
  app: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1406988.

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

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

[Touch-packages] [Bug 1420934] Re: [online-accounts] re-authenticating an account does not work

[Renato Araujo Oliveira Filho]

I can not test this anymore, I tried to revoke the account manually, and 
re-sync but now syncevolution is getting stuck on 0%. 
This is the log from syncevolution.

  invisiblefilter:
[2015-02-19 19:41:11.114] ContextSupport 
ReadNextItem:allfields
[2015-02-19 19:41:11.114] Executing Script 
'initscript'
[2015-02-19 19:41:11.114] Now reading local sync set: 
report changes since reference1 at , and since reference2 at 

[2015-02-19 19:41:11.114] slow sync or testing, do full 
item scan to detect changes
[2015-02-19 19:41:11.114] starting PROPFIND, 
credentials unverified, deadline in 300.0s
[2015-02-19 19:41:11.115] retrieving OAuth2 token, 
attempt 0
[2015-02-19 19:41:11.115] asking for OAuth2 token with 
method oauth2, mechanism web_server and parameters 
{'ForceClientAuthViaRequestBody': , 'Host': 
<'accounts.google.com'>, 'AllowedSchemes': <['https', 'http']>, 
'Scope': <['email', 'https://www.googleapis.com/auth/carddav']>, 
'UiPolicy': , 'ClientId': 
<''>, 'ResponseType': 
<'code'>, 'AuthPath': <'o/oauth2/auth?access_type=offline'>, 
'ClientSecret': '>, 'RedirectUri': 
<'https://wiki.ubuntu.com/'>, 'TokenPath': <'o/oauth2/token'>}
[2015-02-19 19:41:43.111] signon-identity.c:360: 
identity_remote_object_destroyed_cb 360

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

Title:
  [online-accounts] re-authenticating an account does not work

Status in the base for Ubuntu mobile products:
  Confirmed
Status in signon-plugin-oauth2 package in Ubuntu:
  Fix Committed
Status in sync-monitor package in Ubuntu:
  New
Status in signon-plugin-oauth2 package in Ubuntu RTM:
  Fix Committed

Bug description:
  After a online account token became invalid we should use the function
  "AccountService.authenticate" to re-validate the account. But is is
  not working for google accounts.

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

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

[Touch-packages] [Bug 1423415] Re: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.04

[Daniel Jared Dominguez]

** Summary changed:

- [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped 
working in Ubuntu 15.10
+ [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped 
working in Ubuntu 15.04

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

Title:
  [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys
  stopped working in Ubuntu 15.04

Status in Dell Sputnik:
  New
Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Volume hotkeys were working and now they're not. A coworker has
  another 2015 XPS 13 (model 9343) with Ubuntu 15.04. He hasn't updated
  in a week, and the hotkeys function, so it seems like the bug came up
  sometime in the past week.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   jared  4299 F...m arecord
   /dev/snd/controlC1:  jared  2929 F pulseaudio
   /dev/snd/controlC0:  jared  2929 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Feb 18 19:49:30 2015
  InstallationDate: Installed on 2014-11-03 (107 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago)
  dmi.bios.date: 02/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1423415/+subscriptions

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

[Touch-packages] [Bug 1420976] Re: Cpu usage near 30% when conversation view is open

[Launchpad Bug Tracker]

This bug was fixed in the package messaging-app -
0.1+15.04.20150218-0ubuntu1

---
messaging-app (0.1+15.04.20150218-0ubuntu1) vivid; urgency=medium

  [ CI Train Bot ]
  * Resync trunk

  [ Gustavo Pichorim Boiko ]
  * Test that new messages are scrolled into view.

  [ Tiago Salem Herrmann ]
  * Disable spinner for incoming messages. (LP: #1420976)
 -- CI Train BotWed, 18 Feb 2015 12:23:38 +

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

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

Title:
  Cpu usage near 30% when conversation view is open

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Messaging App:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in messaging-app package in Ubuntu RTM:
  Fix Released

Bug description:
  Steps to reproduce:

  1) Receive a message
  2) Open conversation view to see that message
  3) run top on a terminal

  Expected behavior:
  messaging-app should not consume any cpu after initial rendering

  Current behavior
  Constant cpu usage near 30% if there are received messages. Not reproducible 
if there are only sent messages.

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

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

[Touch-packages] [Bug 1420976] Re: Cpu usage near 30% when conversation view is open

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/messaging-app

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

Title:
  Cpu usage near 30% when conversation view is open

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Messaging App:
  New
Status in messaging-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu RTM:
  Fix Released

Bug description:
  Steps to reproduce:

  1) Receive a message
  2) Open conversation view to see that message
  3) run top on a terminal

  Expected behavior:
  messaging-app should not consume any cpu after initial rendering

  Current behavior
  Constant cpu usage near 30% if there are received messages. Not reproducible 
if there are only sent messages.

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

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

[Touch-packages] [Bug 1423565] Re: Missing SIM page not shown during the setup wizard

[Launchpad Bug Tracker]

** Branch linked: lp:~mterry/unity8/wait-for-qofono

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

Title:
  Missing SIM page not shown during the  setup wizard

Status in unity8 package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu RTM:
  In Progress

Bug description:
  RTM image 240.

  0. Clean flash phone
  1. Boot the phone without a sim
  2. Note during the wizard it does not say that "No SIM card detected"

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: ubuntu-system-settings-wizard 0.3+15.04.20150218~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Wed Jan  1 08:23:23 2014
  InstallationDate: Installed on 2015-02-18 (-413 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150218-184321)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.ubuntu-system-settings-wizard-cleanup.log:
   ubuntu-system-settings-wizard start/post-stop, process 3095
   ubuntu-system-settings-wizard start/post-stop, process 3081
   ubuntu-system-settings-wizard start/post-stop, process 3276

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

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

[Touch-packages] [Bug 1301998] Re: Xorg freeze

[Nathaniel W. Turner]

Unfortunately, running Unity on this system makes doing my day job more
or less impossible, so I've switched to using the Gnome fallback
session. It's unlikely I'll have time to test this anytime soon.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Backtrace:
  https://launchpadlibrarian.net/171690059/XorgLogOld.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
  Uname: Linux 3.13.0-21-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  Date: Thu Apr  3 10:46:59 2014
  DistUpgraded: 2014-01-22 19:30:50,196 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: BFG Tech Device [19f1:201f]
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-21-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to trusty on 2014-01-23 (70 days ago)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WBIBX10J.86A.0336.2012.0626.0141
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP55WB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE64798-207
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0336.2012.0626.0141:bd06/26/2012:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-207:cvn:ct2:cvr:
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Apr  3 10:38:37 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputSleep Button KEYBOARD, id 7
   inputLogitech Optical USB Mouse MOUSE, id 8
   inputBTC USB Multimedia Keyboard KEYBOARD, id 9
   inputBTC USB Multimedia Keyboard KEYBOARD, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu7
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1423653] [NEW] credentialsNotFound signal sent when token needs to be deleted

[Rodney Dawes]

Public bug reported:

When trying to get the token, it may happen that signond disallows
access if the token is old and does not have the correct ACL added to
it. When this happens, the library will delete the token, so that the
using application may request immediate login again. However, we end up
sending both the credentialsNotFound signal, and then the
credentialsDeleted signal later, once the account has been deleted. This
can cause some slightly odd behavior in apps that are showing different
UI whether an account doesn't exist, or was deleted.

** Affects: ubuntuone-credentials (Ubuntu)
 Importance: High
 Status: Triaged

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

Title:
  credentialsNotFound signal sent when token needs to be deleted

Status in ubuntuone-credentials package in Ubuntu:
  Triaged

Bug description:
  When trying to get the token, it may happen that signond disallows
  access if the token is old and does not have the correct ACL added to
  it. When this happens, the library will delete the token, so that the
  using application may request immediate login again. However, we end
  up sending both the credentialsNotFound signal, and then the
  credentialsDeleted signal later, once the account has been deleted.
  This can cause some slightly odd behavior in apps that are showing
  different UI whether an account doesn't exist, or was deleted.

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

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

[Touch-packages] [Bug 1418853] Re: [Ubuntu Store] The created account will dispeared when trying to purchase some stuff on Ubuntu Store

[Rodney Dawes]

** Changed in: ubuntuone-credentials (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [Ubuntu Store] The created account will dispeared when trying to
  purchase some stuff on Ubuntu Store

Status in ubuntuone-credentials package in Ubuntu:
  Invalid

Bug description:
  Environment

  Unit: Mako (Nexus4)
  Product: Vivid
  System version: r88

  Steps:
  1. go to "System setting" -> "Accounts"
  2. Add a Ubuntu one account
  3. go to "Ubuntu Store" and search for a paid app from store e.g. Riddling.
  4. Tap on price tag to initiate a purchase
  5. pop up "Loading" page
  6. switch to "System setting" -> "account", the added account disappeared

  Expected result:
  Could see 'View wallet' link to opent he payments detail page and add credit 
card info... etc.

  Actual:
  1. it pending Loading page could not complete the purchase process
  2. the added account does not existed anymore

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

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

[Touch-packages] [Bug 1420544] Re: Ubuntu instances on GCE should use NOOP scheduler

[Brian Murray]

** Tags added: hw-specific

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

Title:
  Ubuntu instances on GCE should use NOOP scheduler

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Trusty:
  In Progress

Bug description:
  Per Google's request, Ubuntu instances should use NOOP as the default
  scheduler.

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

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

[Touch-packages] [Bug 1423359] Re: taking screenshots with mirscreencast fails

[Martin Pitt]

Ah, this is our old friend https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=391964 again: It's a mis-feature that ssh (which
runs behind phablet-shell) is blindly transfering the host's locale to
the remote target even if the target doesn't support that locale.

We can work around that in adt-run by pruning the locale settings more
aggressively.

** Bug watch added: Debian Bug tracker #391964
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391964

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

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

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

Title:
  taking screenshots with mirscreencast fails

Status in autopkgtest package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  From autopilot we see this when there is a failed test.

  21:40:25.138 ERROR testcase:387 - Taking screenshot failed: Command
  '['mirscreencast', '-m', '/run/mir_socket', '-n', '1', '-f', '/tmp/ap-
  screenshot-data-1424295625.rgba']' returned non-zero exit status 1

  I tried setting the LC_ALL env var to C, and it works.

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

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

[Touch-packages] [Bug 1423359] Re: taking screenshots with mirscreencast fails

[Martin Pitt]

Adding Mir task, mirscreencast shouldn't completely fail on an invalid
locale.

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

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

** Changed in: autopkgtest (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  taking screenshots with mirscreencast fails

Status in autopkgtest package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  From autopilot we see this when there is a failed test.

  21:40:25.138 ERROR testcase:387 - Taking screenshot failed: Command
  '['mirscreencast', '-m', '/run/mir_socket', '-n', '1', '-f', '/tmp/ap-
  screenshot-data-1424295625.rgba']' returned non-zero exit status 1

  I tried setting the LC_ALL env var to C, and it works.

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

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

[Touch-packages] [Bug 1420544] Missing SRU information

[Brian Murray]

Thanks for uploading the fix for this bug report to -proposed.  However,
when reviewing the package in -proposed and the details of this bug
report I noticed that the bug description is missing information
required for the SRU process.  You can find full details at
http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially
this bug is missing some of the following: a statement of impact, a test
case and details regarding the regression potential.  Thanks in advance!

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

Title:
  Ubuntu instances on GCE should use NOOP scheduler

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Trusty:
  In Progress

Bug description:
  Per Google's request, Ubuntu instances should use NOOP as the default
  scheduler.

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

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

[Touch-packages] [Bug 1377370] Re: ubuntu-desktop should depend on ibus-gtk

[Aron Xu]

** Changed in: hundredpapercuts
   Status: Confirmed => Fix Committed

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

Title:
  ubuntu-desktop should depend on ibus-gtk

Status in One Hundred Papercuts:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Note that ubuntu-desktop depends on ibus-gtk3 already.

  Looking at /usr/share/im-config/data/21-ibus.rc
  GTK_IM_MODULE is only set to ibus if both gtk-2.0 and gtk-3.0 ibus modules 
are present.  Otherwise it's set to xim.

  If GTK_IM_MODULE=xim and ibus is running, then various bugs happen
  like LP: #1374721 and LP: #1375742.

  Installing ibus-gtk makes those problems go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-desktop 1.327
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct  4 13:49:55 2014
  InstallationDate: Installed on 2014-09-03 (30 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1417532] Re: Words containing apostrophes don't get placed back into preedit correctly

[Launchpad Bug Tracker]

** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/fix-apostrophe-
preedit

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

Title:
  Words containing apostrophes don't get placed back into preedit
  correctly

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu Keyboard:
  Triaged
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu RTM:
  New

Bug description:
  Steps to reproduce

  1) Type "That'll" and press space

  2) Press backspace

  Expected result:

  "That'll" should be underlined (in pre-edit)

  Actual result:

  Only "ll" is underlined.

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

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

[Touch-packages] [Bug 1421396] Re: Volume notification does not show if phone is muted

[Launchpad Bug Tracker]

** Branch linked: lp:~josharenson/indicator-sound/fix_mute_notifications

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

Title:
  Volume notification does not show if phone is muted

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Steps to reproduce

  1. Turn the volume all the way down (to mute)
  2. Wait for the volume notification to disappear
  3. Press volume decrease key again

  Expected behavior: volume notification appears, and gives user feedback that 
phone is muted
  Actual behavior: volume notification does not appear

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

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

[Touch-packages] [Bug 1423031] Re: NSS incorrectly preferring a longer, weaker chain over a shorter, stronger chain

[Launchpad Bug Tracker]

This bug was fixed in the package nss - 3.17.4-0ubuntu0.12.04.1

---
nss (3.17.4-0ubuntu0.12.04.1) precise-security; urgency=medium

  * SECURITY UPDATE: update to upstream 3.17.4 to get new CA certificate
bundle, and to fix incorrect SHA-1 behaviour. (LP: #1423031)
  * Removed unneeded patches:
- debian/patches/CVE-2014-1569.patch: included upstream.
 -- Marc DeslauriersThu, 19 Feb 2015 07:45:59 
-0500

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

Title:
  NSS incorrectly preferring a longer, weaker chain over a shorter,
  stronger chain

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Lucid:
  Fix Released
Status in nss source package in Precise:
  Fix Released
Status in nss source package in Trusty:
  Fix Released
Status in nss source package in Utopic:
  Fix Released
Status in nss source package in Vivid:
  Fix Released
Status in nss package in Debian:
  Confirmed

Bug description:
  See:

  https://code.google.com/p/chromium/issues/detail?id=437733

  and

  https://code.google.com/p/chromium/issues/detail?id=459131

  This issue is fixed in upstream libnss3 version >= 3.17.4

  This issue causes incorrect SHA1 sunset behaviour in Google Chrome.

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

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

[Touch-packages] [Bug 1420934] Re: [online-accounts] re-authenticating an account does not work

[David Barth]

** Changed in: signon-plugin-oauth2 (Ubuntu RTM)
   Status: Confirmed => Fix Committed

** Changed in: signon-plugin-oauth2 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [online-accounts] re-authenticating an account does not work

Status in the base for Ubuntu mobile products:
  Confirmed
Status in signon-plugin-oauth2 package in Ubuntu:
  Fix Committed
Status in sync-monitor package in Ubuntu:
  New
Status in signon-plugin-oauth2 package in Ubuntu RTM:
  Fix Committed

Bug description:
  After a online account token became invalid we should use the function
  "AccountService.authenticate" to re-validate the account. But is is
  not working for google accounts.

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

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

[Touch-packages] [Bug 1423031] Re: NSS incorrectly preferring a longer, weaker chain over a shorter, stronger chain

[Launchpad Bug Tracker]

This bug was fixed in the package nss - 2:3.17.4-0ubuntu0.14.10.1

---
nss (2:3.17.4-0ubuntu0.14.10.1) utopic-security; urgency=medium

  * SECURITY UPDATE: update to upstream 3.17.4 to get new CA certificate
bundle, and to fix incorrect SHA-1 behaviour. (LP: #1423031)
  * Removed unneeded patches:
- debian/patches/CVE-2014-1569.patch: included upstream.
 -- Marc DeslauriersThu, 19 Feb 2015 07:41:50 
-0500

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

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

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

Title:
  NSS incorrectly preferring a longer, weaker chain over a shorter,
  stronger chain

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Lucid:
  Fix Released
Status in nss source package in Precise:
  Fix Released
Status in nss source package in Trusty:
  Fix Released
Status in nss source package in Utopic:
  Fix Released
Status in nss source package in Vivid:
  Fix Released
Status in nss package in Debian:
  Confirmed

Bug description:
  See:

  https://code.google.com/p/chromium/issues/detail?id=437733

  and

  https://code.google.com/p/chromium/issues/detail?id=459131

  This issue is fixed in upstream libnss3 version >= 3.17.4

  This issue causes incorrect SHA1 sunset behaviour in Google Chrome.

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

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

[Touch-packages] [Bug 1423031] Re: NSS incorrectly preferring a longer, weaker chain over a shorter, stronger chain

[Launchpad Bug Tracker]

This bug was fixed in the package nss - 2:3.17.4-0ubuntu0.14.04.1

---
nss (2:3.17.4-0ubuntu0.14.04.1) trusty-security; urgency=medium

  * SECURITY UPDATE: update to upstream 3.17.4 to get new CA certificate
bundle, and to fix incorrect SHA-1 behaviour. (LP: #1423031)
  * Removed unneeded patches:
- debian/patches/CVE-2014-1569.patch: included upstream.
 -- Marc DeslauriersThu, 19 Feb 2015 07:44:05 
-0500

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

Title:
  NSS incorrectly preferring a longer, weaker chain over a shorter,
  stronger chain

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Lucid:
  Fix Released
Status in nss source package in Precise:
  Fix Released
Status in nss source package in Trusty:
  Fix Released
Status in nss source package in Utopic:
  Fix Released
Status in nss source package in Vivid:
  Fix Released
Status in nss package in Debian:
  Confirmed

Bug description:
  See:

  https://code.google.com/p/chromium/issues/detail?id=437733

  and

  https://code.google.com/p/chromium/issues/detail?id=459131

  This issue is fixed in upstream libnss3 version >= 3.17.4

  This issue causes incorrect SHA1 sunset behaviour in Google Chrome.

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

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

[Touch-packages] [Bug 1423031] Re: NSS incorrectly preferring a longer, weaker chain over a shorter, stronger chain

[Launchpad Bug Tracker]

This bug was fixed in the package nss - 3.17.4-0ubuntu0.10.04.1

---
nss (3.17.4-0ubuntu0.10.04.1) lucid-security; urgency=medium

  * SECURITY UPDATE: update to upstream 3.17.4 to get new CA certificate
bundle, and to fix incorrect SHA-1 behaviour. (LP: #1423031)
  * Removed unneeded patches:
- debian/patches/CVE-2014-1569.patch: included upstream.
 -- Marc DeslauriersThu, 19 Feb 2015 07:48:44 
-0500

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

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

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

Title:
  NSS incorrectly preferring a longer, weaker chain over a shorter,
  stronger chain

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Lucid:
  Fix Released
Status in nss source package in Precise:
  Fix Released
Status in nss source package in Trusty:
  Fix Released
Status in nss source package in Utopic:
  Fix Released
Status in nss source package in Vivid:
  Fix Released
Status in nss package in Debian:
  Confirmed

Bug description:
  See:

  https://code.google.com/p/chromium/issues/detail?id=437733

  and

  https://code.google.com/p/chromium/issues/detail?id=459131

  This issue is fixed in upstream libnss3 version >= 3.17.4

  This issue causes incorrect SHA1 sunset behaviour in Google Chrome.

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

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

[Touch-packages] [Bug 1422679] Re: glitch viewing svg

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

Title:
  glitch viewing svg

Status in librsvg package in Ubuntu:
  New

Bug description:
  open any libreoffice icons in eog in 
/usr/share/icons/gnome/scalable/mimetypes/
  this shows phantom white rectangle rescaling at different zoom levels
  opening in browsers produces no glitch

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

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

[Touch-packages] [Bug 1421396] Re: Volume notification does not show if phone is muted

[Launchpad Bug Tracker]

** Branch linked: lp:~josharenson/indicator-sound/fix_mute_notification

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

Title:
  Volume notification does not show if phone is muted

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Steps to reproduce

  1. Turn the volume all the way down (to mute)
  2. Wait for the volume notification to disappear
  3. Press volume decrease key again

  Expected behavior: volume notification appears, and gives user feedback that 
phone is muted
  Actual behavior: volume notification does not appear

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

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

[Touch-packages] [Bug 1384952] Re: USB Soundcard no microphone (input) device

[Michael]

It might also be worth noting that initially, the Xonar U7 produces a
broken pipe error, which is surpressed in order to access the item in
alsamixer.

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

Title:
  USB Soundcard no microphone (input) device

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  My Asus Xonar U7 Echelon External sound device working without input/capture 
device.
  No input device , Nothing recording with my usb soundcard. 

  ~$ arecord -l
   List of CAPTURE Hardware Devices 
  card 1: Ed [Xonar U7 Echelon Ed.], device 1: USB Audio [USB Audio #1]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ~$ lsusb
  Bus 002 Device 002: ID 1043:85c1 iCreate Technologies Corp.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.17.1-031701-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alper  2249 F pulseaudio
   /dev/snd/pcmC1D0p:   alper  2249 F...m pulseaudio
   /dev/snd/controlC1:  alper  2249 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 24 00:46:11 2014
  InstallationDate: Installed on 2014-10-07 (16 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G46 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.2:bd02/04/2013:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7693
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-10-23T19:38:42.156766

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

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

[Touch-packages] [Bug 1084979] Re: Submitting error report asks confounding questions

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.14.7-0ubuntu8.2

---
apport (2.14.7-0ubuntu8.2) utopic-proposed; urgency=medium

  * apport/ui.py: Only provide a UI to hooks if the crash db will accept the
report. This avoids asking questions if the report is merely sent to
whoopsie for Ubuntu stable releases. (LP: #1084979)
 -- Brian MurrayThu, 05 Feb 2015 09:39:32 -0800

** Changed in: apport (Ubuntu Utopic)
   Status: Fix Committed => Fix Released

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

Title:
  Submitting error report asks confounding questions

Status in Apport crash detection/reporting:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Utopic:
  Fix Released

Bug description:
  Test Case
  -
  1) start totem in a terminal
  2) pkill -11 totem
  3) observe apport crash dialog
  4) make sure send an error report is checked
  5) click Leave Closed
  6) Observe an apport dialog about "How would you describe the issue?"

  With the version of apport from -proposed the apport dialog will not
  appear.

  
  Original report
  ---
  Ubuntu 12.04
  apport 2.6.1-0ubuntu10, Ubuntu 12.10
  apport 2.12.5-0ubuntu2.2, Ubuntu 13.10

  1. In a release version of Ubuntu, trigger an error in something that
  has Apport hooks.

  What happens: You are asked questions which are often false and
  usually not understandable. For example:

  "It seems you have modified the contents of '/etc/cups/cupsd.conf'.
  Would you like to add the contents of it to your bug report?"
  https://launchpadlibrarian.net/124496439/apport-question.png -- You
  haven't, and there is no bug report.

  "Thanks for reporting this bug on unity. Is the issue you are reporting 
purely graphical (will report more information about your graphic configuration 
and will report the bug against compiz)?"
  
https://launchpadlibrarian.net/117922627/apport%20%28ubuntu-bug%20unity%20%231%29.png
 -- "Purely grapical" is unexplained, and there is no bug report.

  "Did your system recently lock up or require a hard reboot?" -- What's
  a "hard reboot"?

  What should happen: You are not asked any questions.

  If all reporters of actual bugs are expected to use English, hiding
  these questions from non-reporters might also resolve bug 855337.

  [Originally reported by Katie Taylor.]

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

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

[Touch-packages] [Bug 1423394] Re: Unity Desktop Crashes when using Google Chrome Browser

[D. HIll]

apport information

** Tags added: apport-collected third-party-packages trusty

** Description changed:

  1.) Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  
  2.) google-chrome-stable:
Installed: 40.0.2214.111-1
Candidate: 40.0.2214.111-1
Version table:
   *** 40.0.2214.111-1 0
  500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages
  100 /var/lib/dpkg/status
  
  3.) Expect to see video play and no crashing.
  
- 4.) When using Google Chrome (current version 40.0.2214.111 (64-bit))
- and attempting to watch any Youtube video, the Unity Desktop experiences
- a crash and the Unity Desktop (unity start/search and task bar)
- disappear. I am unable to launch a terminal window. All Window menus
- disappear (i.e. Minimize, Maximize, Close) including those that are
- related to the top right shutdown/restart/logoff menu. Desktop
- background remains viewable and Desktop icons are also viewable.
- Keyboard input starts to malfunction in window sections.
+ 4.) When using Google Chrome (current version 40.0.2214.111 (64-bit)) and 
attempting to watch any Youtube video, the Unity Desktop experiences a crash 
and the Unity Desktop (unity start/search and task bar) disappear. I am unable 
to launch a terminal window. All Window menus disappear (i.e. Minimize, 
Maximize, Close) including those that are related to the top right 
shutdown/restart/logoff menu. Desktop background remains viewable and Desktop 
icons are also viewable. Keyboard input starts to malfunction in window 
sections.
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.7
+ Architecture: amd64
+ CompizPlugins: 
[core,composite,opengl,decor,snap,resize,move,imgpng,grid,regex,mousepoll,place,vpswitch,compiztoolbox,gnomecompat,animation,session,wall,fade,unitymtgrabhandles,expo,scale,workarounds,ezoom,unityshell]
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 14.04
+ InstallationDate: Installed on 2013-08-24 (544 days ago)
+ InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
+ Package: unity 7.2.3+14.04.20140826-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
+ Tags: trusty third-party-packages
+ Uname: Linux 3.13.0-45-generic x86_64
+ UpgradeStatus: Upgraded to trusty on 2014-05-18 (276 days ago)
+ UserGroups: adm lp lpadmin sambashare sudo wireshark
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1423394/+attachment/4322662/+files/Dependencies.txt

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

Title:
  Unity Desktop Crashes when using Google Chrome Browser

Status in unity package in Ubuntu:
  Incomplete

Bug description:
  1.) Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2.) google-chrome-stable:
Installed: 40.0.2214.111-1
Candidate: 40.0.2214.111-1
Version table:
   *** 40.0.2214.111-1 0
  500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages
  100 /var/lib/dpkg/status

  3.) Expect to see video play and no crashing.

  4.) When using Google Chrome (current version 40.0.2214.111 (64-bit)) and 
attempting to watch any Youtube video, the Unity Desktop experiences a crash 
and the Unity Desktop (unity start/search and task bar) disappear. I am unable 
to launch a terminal window. All Window menus disappear (i.e. Minimize, 
Maximize, Close) including those that are related to the top right 
shutdown/restart/logoff menu. Desktop background remains viewable and Desktop 
icons are also viewable. Keyboard input starts to malfunction in window 
sections.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,snap,resize,move,imgpng,grid,regex,mousepoll,place,vpswitch,compiztoolbox,gnomecompat,animation,session,wall,fade,unitymtgrabhandles,expo,scale,workarounds,ezoom,unityshell]
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-08-24 (544 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Tags: trusty third-party-packages
  Uname: Linux 3.13.0-45-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-18 (276 days ago)
  UserGroups: adm lp lpadmin sambashare sudo wireshark
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1423394] ProcEnviron.txt

[D. HIll]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1423394/+attachment/4322664/+files/ProcEnviron.txt

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

Title:
  Unity Desktop Crashes when using Google Chrome Browser

Status in unity package in Ubuntu:
  Incomplete

Bug description:
  1.) Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2.) google-chrome-stable:
Installed: 40.0.2214.111-1
Candidate: 40.0.2214.111-1
Version table:
   *** 40.0.2214.111-1 0
  500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages
  100 /var/lib/dpkg/status

  3.) Expect to see video play and no crashing.

  4.) When using Google Chrome (current version 40.0.2214.111 (64-bit)) and 
attempting to watch any Youtube video, the Unity Desktop experiences a crash 
and the Unity Desktop (unity start/search and task bar) disappear. I am unable 
to launch a terminal window. All Window menus disappear (i.e. Minimize, 
Maximize, Close) including those that are related to the top right 
shutdown/restart/logoff menu. Desktop background remains viewable and Desktop 
icons are also viewable. Keyboard input starts to malfunction in window 
sections.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,snap,resize,move,imgpng,grid,regex,mousepoll,place,vpswitch,compiztoolbox,gnomecompat,animation,session,wall,fade,unitymtgrabhandles,expo,scale,workarounds,ezoom,unityshell]
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-08-24 (544 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Tags: trusty third-party-packages
  Uname: Linux 3.13.0-45-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-18 (276 days ago)
  UserGroups: adm lp lpadmin sambashare sudo wireshark
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1352809] Update Released

[Brian Murray]

The verification of the Stable Release Update for cups has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  /usr/bin/lp on Trusty using -h option doesn't work as expected

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Trusty:
  Fix Committed
Status in cups source package in Utopic:
  Fix Released

Bug description:
  [SRU justification]
  The -h option should override the value stored in the CUPS_SERVER environment 
variable

  [Impact]
  Without this fix, user is unable to define the printserver to use with the -h 
option

  [Fix]
  Verify if the -h option has defined the printserver before using CUPS_SERVER 
to define it.

  [Test Case]
  $ export CUPS_SERVER="blah"
  $ lp -h {valid printserver} -d {printqueue} /etc/hosts

  Without the fix :
  lp: No such file or directory

  With the fix :
  request id is {printqueue}-37 (1 file(s))

  [Regression]
  None expected. New code path (from upstream patch) is only triggered if
  -h option is used.

  [Original description of the problem]

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  Codename: trusty

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  cups-client:
    Installed: 1.7.2-0ubuntu1.1

  3) What you expected to happen

  When using lp -h to send a print job to a printer, I expected to the
  job to be sent to the printer and to override any env variables set or
  conf file setting

  4) What happened instead

  To summarise the behaviour I'm seeing

  1) with CUPS_SERVER env variable unset and no ServerName set in 
/etc/cups/client.conf, we see that using lp -h with hostnames gives us error 
"lp: Error - add '/version=1.1' to server name."
  Using IPs sends the job to the printer as expected.

  2) with CUPS_SERVER env variable set using hostname with/without port
  and no ServerName set in /etc/cups/client.conf, we see that the only
  time it sends a job is when an IP and port are used. Otherwise it
  seems to error. I believe it's using the env variable, even though -h
  is being used.

  3) with CUPS_SERVER env variable set using IP address with/without
  port and no ServerName set in /etc/cups/client.conf we see that the
  job is always sent using lp -h but it is always sent to the value in
  env variable, thus ignoring the command line.

  ===

  with CUPS_SERVER env variable unset and no ServerName option set in
  /etc/cups/client.conf

  $ lp test2.txt
  lp: Error - scheduler not responding. (expected as no server is set or 
specified)

  Using hostname
  $ lp -h server1:631 test2.txt
  lp: Error - add '/version=1.1' to server name.

  $ lp -h server1 test2.txt
  lp: Error - add '/version=1.1' to server name.

  Using IP address
  $ lp -h 192.168.254.8 test2.txt
  request id is PDF-54 (1 file(s))

  $ lp -h 192.168.254.8:631 test2.txt
  request id is PDF-55 (1 file(s))

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=server1

  $ lp test2.txt
  lp: Error - add '/version=1.1' to server name.

  Using hostname
  $ lp -h server1 test2.txt
  lp: Error - add '/version=1.1' to server name.

  $ lp -h server1:631 test2.txt
  lp: Error - add '/version=1.1' to server name.

  Using IP address
  $ lp -h 192.168.254.8 test2.txt
  lp: Error - add '/version=1.1' to server name.

  $ lp -h 192.168.254.8:631 test2.txt
  request id is PDF-56 (1 file(s))

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=server:631

  Same results as above

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=192.168.254.8:631

  $ lp -h 555.555.555.555 test2.txt
  request id is PDF-66 (1 file(s))

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=192.168.254.8

  Same results as above

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

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

[Touch-packages] [Bug 1352809] Re: /usr/bin/lp on Trusty using -h option doesn't work as expected

[Launchpad Bug Tracker]

This bug was fixed in the package cups - 1.7.5-3ubuntu3

---
cups (1.7.5-3ubuntu3) utopic-proposed; urgency=medium

  * Fix -h option not honoured when CUPS_SERVER variable
is defined. (LP: #1352809)
 -- Louis BouchardMon, 09 Feb 2015 11:36:08 +0100

** Changed in: cups (Ubuntu Utopic)
   Status: Fix Committed => Fix Released

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

Title:
  /usr/bin/lp on Trusty using -h option doesn't work as expected

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Trusty:
  Fix Committed
Status in cups source package in Utopic:
  Fix Released

Bug description:
  [SRU justification]
  The -h option should override the value stored in the CUPS_SERVER environment 
variable

  [Impact]
  Without this fix, user is unable to define the printserver to use with the -h 
option

  [Fix]
  Verify if the -h option has defined the printserver before using CUPS_SERVER 
to define it.

  [Test Case]
  $ export CUPS_SERVER="blah"
  $ lp -h {valid printserver} -d {printqueue} /etc/hosts

  Without the fix :
  lp: No such file or directory

  With the fix :
  request id is {printqueue}-37 (1 file(s))

  [Regression]
  None expected. New code path (from upstream patch) is only triggered if
  -h option is used.

  [Original description of the problem]

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  Codename: trusty

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  cups-client:
    Installed: 1.7.2-0ubuntu1.1

  3) What you expected to happen

  When using lp -h to send a print job to a printer, I expected to the
  job to be sent to the printer and to override any env variables set or
  conf file setting

  4) What happened instead

  To summarise the behaviour I'm seeing

  1) with CUPS_SERVER env variable unset and no ServerName set in 
/etc/cups/client.conf, we see that using lp -h with hostnames gives us error 
"lp: Error - add '/version=1.1' to server name."
  Using IPs sends the job to the printer as expected.

  2) with CUPS_SERVER env variable set using hostname with/without port
  and no ServerName set in /etc/cups/client.conf, we see that the only
  time it sends a job is when an IP and port are used. Otherwise it
  seems to error. I believe it's using the env variable, even though -h
  is being used.

  3) with CUPS_SERVER env variable set using IP address with/without
  port and no ServerName set in /etc/cups/client.conf we see that the
  job is always sent using lp -h but it is always sent to the value in
  env variable, thus ignoring the command line.

  ===

  with CUPS_SERVER env variable unset and no ServerName option set in
  /etc/cups/client.conf

  $ lp test2.txt
  lp: Error - scheduler not responding. (expected as no server is set or 
specified)

  Using hostname
  $ lp -h server1:631 test2.txt
  lp: Error - add '/version=1.1' to server name.

  $ lp -h server1 test2.txt
  lp: Error - add '/version=1.1' to server name.

  Using IP address
  $ lp -h 192.168.254.8 test2.txt
  request id is PDF-54 (1 file(s))

  $ lp -h 192.168.254.8:631 test2.txt
  request id is PDF-55 (1 file(s))

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=server1

  $ lp test2.txt
  lp: Error - add '/version=1.1' to server name.

  Using hostname
  $ lp -h server1 test2.txt
  lp: Error - add '/version=1.1' to server name.

  $ lp -h server1:631 test2.txt
  lp: Error - add '/version=1.1' to server name.

  Using IP address
  $ lp -h 192.168.254.8 test2.txt
  lp: Error - add '/version=1.1' to server name.

  $ lp -h 192.168.254.8:631 test2.txt
  request id is PDF-56 (1 file(s))

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=server:631

  Same results as above

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=192.168.254.8:631

  $ lp -h 555.555.555.555 test2.txt
  request id is PDF-66 (1 file(s))

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=192.168.254.8

  Same results as above

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

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

[Touch-packages] [Bug 1423394] GconfCompiz.txt

[D. HIll]

apport information

** Attachment added: "GconfCompiz.txt"
   
https://bugs.launchpad.net/bugs/1423394/+attachment/4322663/+files/GconfCompiz.txt

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

Title:
  Unity Desktop Crashes when using Google Chrome Browser

Status in unity package in Ubuntu:
  Incomplete

Bug description:
  1.) Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2.) google-chrome-stable:
Installed: 40.0.2214.111-1
Candidate: 40.0.2214.111-1
Version table:
   *** 40.0.2214.111-1 0
  500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages
  100 /var/lib/dpkg/status

  3.) Expect to see video play and no crashing.

  4.) When using Google Chrome (current version 40.0.2214.111 (64-bit)) and 
attempting to watch any Youtube video, the Unity Desktop experiences a crash 
and the Unity Desktop (unity start/search and task bar) disappear. I am unable 
to launch a terminal window. All Window menus disappear (i.e. Minimize, 
Maximize, Close) including those that are related to the top right 
shutdown/restart/logoff menu. Desktop background remains viewable and Desktop 
icons are also viewable. Keyboard input starts to malfunction in window 
sections.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,snap,resize,move,imgpng,grid,regex,mousepoll,place,vpswitch,compiztoolbox,gnomecompat,animation,session,wall,fade,unitymtgrabhandles,expo,scale,workarounds,ezoom,unityshell]
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-08-24 (544 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Tags: trusty third-party-packages
  Uname: Linux 3.13.0-45-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-18 (276 days ago)
  UserGroups: adm lp lpadmin sambashare sudo wireshark
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1024540] Re: Apport won't send the crash report as it suggests

[Brian Murray]

Actually the same reason applies. 14.10 is not the development release
of Ubuntu, we are currently developing 15.04 and only that release of
Ubuntu sends crash reports to Launchpad.

** Changed in: apport (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Apport won't send the crash report as it suggests

Status in apport package in Ubuntu:
  Invalid

Bug description:
  After xorg or whatever crash apport suggests to send a bug report.
  Every time I press "send" it closes itself and doesn't proceed.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apport-gtk 2.0.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  CrashReports:
   640:1000:129:4388477:2012-07-09 13:33:24.37786 +0300:2012-07-09 
13:33:47.725139488 +0300:/var/crash/_usr_bin_indicator-weather.1000.crash
   664:1000:129:0:2012-07-09 13:33:46.672608290 +0300:2012-07-09 
13:33:46.672608290 +0300:/var/crash/_usr_bin_indicator-weather.1000.upload
   640:1000:129:225:2012-07-13 23:23:21.728192000 +0300:2012-07-13 
23:24:57.676808016 +0300:/var/crash/_usr_bin_nautilus.1000.crash
   600:117:129:0:2012-07-13 23:23:57.772365863 +0300:2012-06-03 
13:49:23.205949580 +0300:/var/crash/_usr_bin_indicator-weather.1000.uploaded
   600:0:129:1232008:2012-07-13 19:19:54.913043000 +0300:2012-07-13 
20:12:28.331323271 
+0300:/var/crash/xserver-xorg-video-intel.2012-07-13_19:19:55.442391.crash
  Date: Fri Jul 13 23:25:34 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to precise on 2012-04-27 (76 days ago)

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

-- 
Mailing list: https://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 1410925] Re: [HDA-Intel - HDA Intel, playback] Playback problem, no sound in mini hi-fi component

[Odair Reinaldo Marquez Diaz]

Si, bueno... Olvídenlo, era que el cable no estaba conectado al equipo de
sonido. Lo siento.

El Thu Jan 15 2015 at 0:40:53, Raymond <1410...@bugs.launchpad.net>
escribió:

> ** Changed in: alsa-driver (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1410925
>
> Title:
>   [HDA-Intel - HDA Intel, playback] Playback problem, no sound in mini
>   hi-fi component
>
> Status in alsa-driver package in Ubuntu:
>   Incomplete
>
> Bug description:
>   No hay sonido cuando el ordenador esta conectado a un equipo de sonido
>   estereo, pero si hay sonido al conectar auriculares o con los
>   parlantes propios del ordenador.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu4
>   ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
>   Uname: Linux 3.13.0-44-generic i686
>   ApportVersion: 2.14.1-0ubuntu3.6
>   Architecture: i386
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  odair  1835 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Wed Jan 14 12:52:31 2015
>   InstallationDate: Installed on 2015-01-14 (0 days ago)
>   InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386
> (20140722.2)
>   PackageArchitecture: all
>   ProcEnviron:
>LANGUAGE=es_HN:es
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=es_HN.UTF-8
>SHELL=/bin/bash
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
>   Symptom_Card: Audio Interno - HDA Intel
>   Symptom_Type: Only some of outputs are working
>   Title: [HDA-Intel - HDA Intel, playback] Playback problem
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/28/2011
>   dmi.bios.vendor: Hewlett-Packard
>   dmi.bios.version: F.23
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: 1584
>   dmi.board.vendor: Hewlett-Packard
>   dmi.board.version: 85.36
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.chassis.version: Chassis Version
>   dmi.modalias: dmi:bvnHewlett-Packard:bvrF.23:bd04/28/2011:svnHewlett-
> Packard:pnHPMini110-3700:pvr057E11A000202B0300100:
> rvnHewlett-Packard:rn1584:rvr85.36:cvnHewlett-Packard:
> ct10:cvrChassisVersion:
>   dmi.product.name: HP Mini 110-3700
>   dmi.product.version: 057E11A000202B0300100
>   dmi.sys.vendor: Hewlett-Packard
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+
> bug/1410925/+subscriptions
>

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

Title:
  [HDA-Intel - HDA Intel, playback] Playback problem, no sound in mini
  hi-fi component

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  No hay sonido cuando el ordenador esta conectado a un equipo de sonido
  estereo, pero si hay sonido al conectar auriculares o con los
  parlantes propios del ordenador.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  odair  1835 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 14 12:52:31 2015
  InstallationDate: Installed on 2015-01-14 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=es_HN:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_HN.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Audio Interno - HDA Intel
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/28/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1584
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 85.36
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.23:bd04/28/2011:svnHewlett-Packard:pnHPMini110-3700:pvr057E11A000202B0300100:rvnHewlett-Packard:rn1584:rvr85.36:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Mini 110-3700
  dmi.product.version: 057E11A000202B0300100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about th

[Touch-packages] [Bug 1417664]

[Ctice]

Author: ctice
Date: Thu Feb 19 00:43:33 2015
New Revision: 220805

URL: https://gcc.gnu.org/viewcvs?rev=220805&root=gcc&view=rev
Log:
Backport patch from Google 4.9 branch (r220431):

r220431 | wmi | 2015-02-04 16:27:54 -0800 (Wed, 04 Feb 2015) | 12 lines

Backport from gcc-4_9-branch.
2015-02-04  Matthias Klose  

PR target/64938
Backport from mainline
2015-01-15  Jan Hubicka  

PR ipa/64068
PR ipa/64559
* ipa.c (symbol_table::remove_unreachable_nodes):
Do not put abstract origins into boundary.


Added:
branches/google/gcc-4_9-mobile/gcc/testsuite/g++.dg/ipa/pr64068.C
branches/google/gcc-4_9-mobile/gcc/testsuite/gcc.dg/ipa/PR64559.c
Modified:
branches/google/gcc-4_9-mobile/gcc/ipa.c

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

Title:
  Unity8 build causes internal compiler error on armhf

Status in The GNU Compiler Collection:
  Fix Released
Status in gcc-4.9 package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  I've encountered this first today, thought this was a problem with
  some of my MPs, but have reduced them to no-op and the unity8 trunk
  does not build on armhf in the PPAs:

  In file included from 
/build/buildd/unity8-8.02+15.04.20150203.7/tests/mocks/Unity/fake_scopes.cpp:21:0:
  
/build/buildd/unity8-8.02+15.04.20150203.7/tests/mocks/Unity/fake_scopesoverview.h:
 At global scope:
  
/build/buildd/unity8-8.02+15.04.20150203.7/tests/mocks/Unity/fake_scopesoverview.h:27:7:
 internal compiler error: in symtab_remove_unreachable_nodes, at ipa.c:547
   class ScopesOverview : public Scope
 ^
  Please submit a full bug report,
  with preprocessed source if appropriate.
  See  for instructions.

  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-021/+sourcepub/4753156/+listing-
  archive-extra

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gcc-4.9 4.9.2-10ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb  3 17:59:59 2015
  SourcePackage: gcc-4.9
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1287222] Re: openssh-client 6.5 regression bug with certain servers

[Brian Candler]

The workaround is fine, but if you want more detailed description about the 
underlying issues (there are more than one) see  the Red Hat bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1026430

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

Title:
  openssh-client 6.5 regression bug with certain servers

Status in openssh package in Ubuntu:
  Confirmed
Status in openssh package in Debian:
  New
Status in openssh package in Fedora:
  Unknown

Bug description:
  Previous working versions of SSH (6.2p2) work fine on certain host
  machines as follows:

  penSSH_6.2p2 Ubuntu-6, OpenSSL 1.0.1f 6 Jan 2014
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to hostname [IPAddress] port 22.
  debug1: Connection established.
  debug1: identity file /home/nelsot08/.ssh/identity type -1
  debug1: identity file /home/nelsot08/.ssh/identity-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_rsa type 1
  debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
  debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
  debug1: identity file /home/nelsot08/.ssh/id_rsa-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_dsa type -1
  debug1: identity file /home/nelsot08/.ssh/id_dsa-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_ecdsa type -1
  debug1: identity file /home/nelsot08/.ssh/id_ecdsa-cert type -1
  debug1: Remote protocol version 2.0, remote software version Cisco-1.25
  debug1: no match: Cisco-1.25
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_6.2p2 Ubuntu-6
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: server->client aes128-cbc hmac-md5 none
  debug1: kex: client->server aes128-cbc hmac-md5 none
  debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
  debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
  debug1: Server host key: RSA 24:75:76:a1:80:0e:6c:4e:a8:c4:a6:a9:d3:34:98:18
  Warning: Permanently added 'hostname,IPAddress' (RSA) to the list of known 
hosts.
  debug1: ssh_rsa_verify: signature correct
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: Roaming not allowed by server
  debug1: SSH2_MSG_SERVICE_REQUEST sent
  debug1: SSH2_MSG_SERVICE_ACCEPT received

  
  But in 6.5p1 the following bug occurs:

  OpenSSH_6.5, OpenSSL 1.0.1f 6 Jan 2014
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to hostname [IPAddress] port 22.
  debug1: Connection established.
  debug1: identity file /home/nelsot08/.ssh/identity type -1
  debug1: identity file /home/nelsot08/.ssh/identity-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_rsa type 1
  debug1: identity file /home/nelsot08/.ssh/id_rsa-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_dsa type -1
  debug1: identity file /home/nelsot08/.ssh/id_dsa-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_ecdsa type -1
  debug1: identity file /home/nelsot08/.ssh/id_ecdsa-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_ed25519 type -1
  debug1: identity file /home/nelsot08/.ssh/id_ed25519-cert type -1
  debug1: Remote protocol version 2.0, remote software version Cisco-1.25
  debug1: no match: Cisco-1.25
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_6.5p1 Ubuntu-4
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: server->client aes128-cbc hmac-md5 none
  debug1: kex: client->server aes128-cbc hmac-md5 none
  debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<3072<8192) sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
  Connection closed by IPAddress

  
  This is a regression and there are multiple references to this bug occurring 
previously:

  http://www.held.org.il/blog/2011/05/the-myterious-case-of-broken-ssh-
  client-connection-reset-by-peer/

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

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

[Touch-packages] [Bug 1423565] Re: Missing SIM page not shown during the setup wizard

[Michael Terry]

** Branch linked: lp:~mterry/ubuntu-system-settings/wait-for-qofono

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

** Package changed: ubuntu-system-settings (Ubuntu) => ubuntu-system-
settings (Ubuntu RTM)

** Changed in: ubuntu-system-settings (Ubuntu RTM)
   Status: Confirmed => In Progress

** Changed in: ubuntu-system-settings (Ubuntu RTM)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  Missing SIM page not shown during the  setup wizard

Status in unity8 package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu RTM:
  In Progress

Bug description:
  RTM image 240.

  0. Clean flash phone
  1. Boot the phone without a sim
  2. Note during the wizard it does not say that "No SIM card detected"

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: ubuntu-system-settings-wizard 0.3+15.04.20150218~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Wed Jan  1 08:23:23 2014
  InstallationDate: Installed on 2015-02-18 (-413 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150218-184321)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.ubuntu-system-settings-wizard-cleanup.log:
   ubuntu-system-settings-wizard start/post-stop, process 3095
   ubuntu-system-settings-wizard start/post-stop, process 3081
   ubuntu-system-settings-wizard start/post-stop, process 3276

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

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

[Touch-packages] [Bug 1423050] Re: App preview buttons appear before they can be clicked

[Albert Astals Cid]

It's actually not the images that we're waiting for, we are waiting for
the previewModel.loaded property (which is linked to the orange bar in
the bottom) to be true to enable the buttons, i'd agree that it seems
that the property changes to true a bit too late, maybe it's still
loading comments or something?

I'm readding unity-scope-click and unity-scopes-shell for comments

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

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

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

Title:
  App preview buttons appear before they can be clicked

Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  When I open the preview of an installed application, it shows the
  uninstall and close buttons. If I click them while the bottom loading
  bar is still moving, they will do nothing.

  To reproduce:
  Do a long touch in an app, for example, file manager
  As soon as the buttons appear, touch one of them.
  If you are fast and your connection is slow, then you will click the button 
before the images are fully loaded, so the progress bar will still be moving.
  And nothing will happen.

  Tested on krillin, vivid, r114

  I think there should be a clear indication that the buttons are
  disabled while the preview is being loaded. Or maybe it doesn't matter
  that the images are not loaded, the buttons should be clickable as
  soon as they appear.

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

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

[Touch-packages] [Bug 1422345] Re: stop being nice does not work

[Bug Watch Updater]

** Changed in: unattended-upgrades (Debian)
   Status: Unknown => New

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

Title:
  stop being nice does not work

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades source package in Trusty:
  Fix Committed
Status in unattended-upgrades source package in Utopic:
  Fix Committed
Status in unattended-upgrades package in Debian:
  New

Bug description:
  Test Case
  -
  1) Install apache2 from the -release pocket
  2) Run unattended-upgrades
  3) Observe apache2 running with a niceness of 19
  4) Downgrade apache2 to the version from the -release pocket
  5) Install the version of unattended-upgrades from -proposed
  6) Run unattended-upgrades
  7) Observe apache2 running with a niceness of 0 i.e. no niceness


  Since version 0.81, unattended-upgrades does the upgrade calculation with 
os.nice(19). To finish the nice block in /usr/bin/unattended-upgrade, the 
following call is used:
  os.nice(0)

  Since the argument is interpreted as incremental, this should be:
  os.nice(-19)

  Without this fix, this problem is back:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701850
  "unattended-upgrades: nice 19/ionice idle inherited by restarted processes"

  Found in the trusty version (0.82.1ubuntu2), but probably in any
  version (including Debian) since 0.81.

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

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

[Touch-packages] [Bug 1422345] Re: stop being nice does not work

[Brian Murray]

Given that the changelog entry has already been written and doesn't
include a debian bug reference I think it'd be best to close and maybe
include the changelog entry.

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

Title:
  stop being nice does not work

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades source package in Trusty:
  Fix Committed
Status in unattended-upgrades source package in Utopic:
  Fix Committed
Status in unattended-upgrades package in Debian:
  New

Bug description:
  Test Case
  -
  1) Install apache2 from the -release pocket
  2) Run unattended-upgrades
  3) Observe apache2 running with a niceness of 19
  4) Downgrade apache2 to the version from the -release pocket
  5) Install the version of unattended-upgrades from -proposed
  6) Run unattended-upgrades
  7) Observe apache2 running with a niceness of 0 i.e. no niceness


  Since version 0.81, unattended-upgrades does the upgrade calculation with 
os.nice(19). To finish the nice block in /usr/bin/unattended-upgrade, the 
following call is used:
  os.nice(0)

  Since the argument is interpreted as incremental, this should be:
  os.nice(-19)

  Without this fix, this problem is back:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701850
  "unattended-upgrades: nice 19/ionice idle inherited by restarted processes"

  Found in the trusty version (0.82.1ubuntu2), but probably in any
  version (including Debian) since 0.81.

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

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

[Touch-packages] [Bug 1422898] Re: Excessive CPU usage, even when the screen is turned off

[Albert Astals Cid]

we're leaking timers as crazy in unity8
start unity8 and it has 3 timers
now start unity8-dash and unity8 goes to 189 timers
now refresh the apps scope
and unity8 goes to 341 timers
which is very funny given unity8 doesn't really have anything to do with 
unity8-dash being refreshed
and it goes up with every dash refresh, eventually spending lots of cpu in just 
handling the timers

Need to verify where all those timers are coming from

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

Title:
  Excessive CPU usage, even when the screen is turned off

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Since mako image r102 (vivid-proposed), the CPU usage of Unity8 is very 
excessive and increasing over time.
  After boot, the phone runs smooth but after some time it lags heavily.

  As you can see from the attached output of the "top" command, Unity8
  consumes 23% of CPU power when the screen is TURNED OFF (command run
  via adb). When the screen is on, this figure is much higher and
  sometimes rises up to 60%.

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

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

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

[Alberto Aguirre]

Right Thread#1 and Thread#15 seem deadlock. There must be at least a
couple of different mutexes used by the Qt DBus abstraction that are
causing this but have not inspected the code fully yet.

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

Title:
  Unity8 completely frozen (unable to unlock, receive calls, etc)

Status in the base for Ubuntu mobile products:
  New
Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 224
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-01-29 18:53:09
  version version: 224
  version ubuntu: 20150129
  version device: 20150129-c75dcfb
  version custom: 20150129-528-26-182

  Was driving around with my car, and noticed once I got back home that
  my clock was stuck in a previous time (~20min before getting home),
  and after trying to use the phone I noticed unity8 was completely
  stuck, but the underling OS was still running fine.

  The worst here is that we're unable to notify the user about calls, as
  the interface is completely stuck. Another bad thing is that this
  could as well happen when the user is sleeping or something, without
  an easy way to know until he tries to use the phone.

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

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

[Touch-packages] [Bug 1365752] Re: ubuntu-desktop depends on iBus, which is totally broken

[Thiago Martins]

I would like to know why, WHY, for God's sake, that Ubuntu depends on
this totally broken iBus?

Sabotage? I'm starting to believe on this conspiracy theory...   :-/

What else can be?!

I'm glad that we still have a choice to remove iBus and use another
solution, like scim, for example...

Out of topic but, can you guys imagine when this systemd-thing starts to
break everything and we have no choice? Crazy times...   ;-(

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

Title:
  ubuntu-desktop depends on iBus, which is totally broken

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Baltix:
  New

Bug description:
  Upgrading from Ubuntu 12.04 to 14.04 the package iBus has been
  installed in the system and activated by default. This has caused an
  amount of pain because it has completely broken the input method
  (symptoms: no en-uk keyboard available composite not working, backtick
  to be pressed twice). The problems are reported in a number of places;
  I've read somewhere I can't remember that Unity has some form of
  workaround against ibus but I don't use Unity (using Awesome on some
  systems, lubuntu on another one) and other windows managers are
  affected.

  Even disabling ibus (which has to be done via gnome-language-selector,
  instead of the keyboard panel in gnome-control-center, which is an
  usability problem that deserves its own bug report) the ibus processes
  keep on running. Probably this has no consequence but still there is
  no reason to have unwanted running processes. I have no idea where do
  these processes start, but I clearly have the idea that they shouldn't
  be running where not necessary.

  Uninstalling ibus is not straightforward because the ubuntu-desktop
  package depends on it. The dependency the core package ubuntu-desktop
  on ibus is excessive for a package that is 1) unneeded by many users
  and 2) broken for many users.

  The best solution to date is to:

  ibus exit
  sudo mv /usr/lib/ibus{,.bak}
  sudo mv /usr/bin/ibus{,.bak}

  Please remove the dependency of ubuntu-desktop on ibus and avoid
  installing it for european languages.

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

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

[Touch-packages] [Bug 1423586] [NEW] Please backport memory leak fixes present up to 7.4.6

[Louis Bouchard]

Public bug reported:

Many memory leak situations were fixed in newer versions up to 7.4.6.
Please backport those fixes to Ubuntu

** Affects: rsyslog (Ubuntu)
 Importance: Medium
 Assignee: Louis Bouchard (louis-bouchard)
 Status: Confirmed

** Affects: rsyslog (Ubuntu Trusty)
 Importance: Medium
 Assignee: Louis Bouchard (louis-bouchard)
 Status: Confirmed


** Tags: cts

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

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

** Changed in: rsyslog (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

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

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

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

** Changed in: rsyslog (Ubuntu Trusty)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Tags added: cts

** Bug watch added: bugzilla.adiscon.com/ #486
   http://bugzilla.adiscon.com/show_bug.cgi?id=486

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

Title:
  Please backport memory leak fixes present up to 7.4.6

Status in rsyslog package in Ubuntu:
  Confirmed
Status in rsyslog source package in Trusty:
  Confirmed

Bug description:
  Many memory leak situations were fixed in newer versions up to 7.4.6.
  Please backport those fixes to Ubuntu

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

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

[Touch-packages] [Bug 1288801] Re: Invalid backend content for the bindings

[Alexandre Abreu]

** Changed in: unity-webapps-qml
   Status: In Progress => Fix Released

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

Title:
  Invalid backend content for the bindings

Status in Unity WebApps QML component:
  Fix Released
Status in unity-webapps-qml package in Ubuntu:
  Fix Released

Bug description:
  The backend qml/js file contents for the bindings is invalid and
  outdated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-webapps-qml/+bug/1288801/+subscriptions

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

[Touch-packages] [Bug 1376445] Re: Addition of signon-apparmor-extension causes token lookup problems

[Rodney Dawes]

** Changed in: pay-ui
   Importance: Critical => Undecided

** Changed in: pay-ui
   Status: Triaged => Invalid

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

Title:
  Addition of signon-apparmor-extension causes token lookup problems

Status in the base for Ubuntu mobile products:
  Fix Released
Status in go-onlineaccounts:
  Incomplete
Status in Pay UI:
  Invalid
Status in The Savilerow project:
  Invalid
Status in ACL for signond, AppArmor backend:
  Fix Released
Status in Online Accounts setup for Ubuntu Touch:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in ubuntuone-credentials package in Ubuntu:
  Fix Released
Status in signon-apparmor-extension package in Ubuntu RTM:
  Triaged
Status in ubuntu-system-settings-online-accounts package in Ubuntu RTM:
  New
Status in ubuntuone-credentials package in Ubuntu RTM:
  Fix Released

Bug description:
  As of image ~264 of ubuntu-touch, the signon-apparmor-extension
  package is included. As a result, apps like pay-ui cannot find the
  token any longer, and are not being notified that they are not allowed
  to access the token. The following error appears in the payui log
  file:

  2014-10-01 19:15:51,550 - DEBUG -
  ../../../../lib/SignOn/authsessionimpl.cpp 184 errorSlot
  QDBusError("com.google.code.AccountsSSO.SingleSignOn.Error.PermissionDenied",
  "Client has insuficient permissions to access the
  service.Method:getAuthSessionObjectPath")

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

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

[Touch-packages] [Bug 1422345] Re: stop being nice does not work

[Harald Staub]

Thank you (sorry, should have asked before). Do you think that it is
best for me to close the Debian bug report?

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

Title:
  stop being nice does not work

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades source package in Trusty:
  Fix Committed
Status in unattended-upgrades source package in Utopic:
  Fix Committed
Status in unattended-upgrades package in Debian:
  Unknown

Bug description:
  Test Case
  -
  1) Install apache2 from the -release pocket
  2) Run unattended-upgrades
  3) Observe apache2 running with a niceness of 19
  4) Downgrade apache2 to the version from the -release pocket
  5) Install the version of unattended-upgrades from -proposed
  6) Run unattended-upgrades
  7) Observe apache2 running with a niceness of 0 i.e. no niceness


  Since version 0.81, unattended-upgrades does the upgrade calculation with 
os.nice(19). To finish the nice block in /usr/bin/unattended-upgrade, the 
following call is used:
  os.nice(0)

  Since the argument is interpreted as incremental, this should be:
  os.nice(-19)

  Without this fix, this problem is back:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701850
  "unattended-upgrades: nice 19/ionice idle inherited by restarted processes"

  Found in the trusty version (0.82.1ubuntu2), but probably in any
  version (including Debian) since 0.81.

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

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

[Touch-packages] [Bug 1401141] Re: DHCP server does not work for IPoIB (Infiniband)

[Rafael David Tinoco]

** Summary changed:

- IPoIB does not work on Ubuntu due to DHCP
+ DHCP server does not work for IPoIB (Infiniband)

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

Title:
  DHCP server does not work for IPoIB (Infiniband)

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  Release:  Ubuntu 14.04.1 LTS
  Version:  4.2.4-7ubuntu12

  The current DHCP package in Ubuntu can't handle IPoIB clients.  For
  IB, Mellanox uses IPoIB, which is “Eth emulator” for the control path.
  DHCP is not working in this mode without a patch for DHCP server.

  =
  From IETF documentation:
  
http://git.openfabrics.org/pub/scm/~rupertd/docs/release_notes/ipoib_release_notes.txt
  ...
  "Note: Two patches for DHCP are required for supporting IPoIB. The patch files
  for DHCP v3.0.4 are available under the docs/dhcp/ directory.

  Standard DHCP fields holding MAC addresses are not large enough to contain an
  IPoIB hardware address. To overcome this problem, DHCP over InfiniBand 
messages
  convey a client identifier field used to identify the DHCP session. This 
client
  identifier field can be used to associate an IP address with a client 
identifier
  value, such that the DHCP server will grant the same IP address to any client
  that conveys this client identifier."
  ...
  "In order to use a DHCP client identifier, you need to first create a
  configuration file that defines the DHCP client identifier. Then run the DHCP
  client with this file using the following command:
  dhclient cf  
  Example of a configuration file for the ConnectX (PCI Device ID 26428), called
  dhclient.conf:Ubuntu 14.04.1 LTS
  # The value indicates a hexadecimal number
  interface "ib1" {
  send dhcp-client-identifier
  ff:00:00:00:00:00:02:00:00:02:c9:00:00:02:c9:03:00:00:10:39;
  }
  "

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

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

[Touch-packages] [Bug 1414762] Re: Password gets set instead of a passcode during welcome wizard

[Pat McGowan]

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

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

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

Title:
  Password gets set instead of a passcode during welcome wizard

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity8 package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu RTM:
  In Progress

Bug description:
  Whenever I quickly type the passcode during setup wizard, instead of
  passcode, password is set as security mechanism

  1. factory reset your phone
  2. on the startup wizard select 4-digit passcode as security mechanism
  3. when asked to confirm the passcode, quickly type it again.
  4. finish setup

  What happens:
  Instead of a passcode the password is set and I am greeted with OSK to unlock 
the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: ubuntu-system-settings 0.3+15.04.20150123.1~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Mon Jan 26 19:41:20 2015
  InstallationDate: Installed on 2015-01-26 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150126-162525)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1422345] Re: stop being nice does not work

[Brian Murray]

The fix was already merged upstream for what it is worth.

https://github.com/murraybd/unattended-upgrades/tree/lp-bug-1422345

** Also affects: unattended-upgrades (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778769
   Importance: Unknown
   Status: Unknown

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

Title:
  stop being nice does not work

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades source package in Trusty:
  Fix Committed
Status in unattended-upgrades source package in Utopic:
  Fix Committed
Status in unattended-upgrades package in Debian:
  Unknown

Bug description:
  Test Case
  -
  1) Install apache2 from the -release pocket
  2) Run unattended-upgrades
  3) Observe apache2 running with a niceness of 19
  4) Downgrade apache2 to the version from the -release pocket
  5) Install the version of unattended-upgrades from -proposed
  6) Run unattended-upgrades
  7) Observe apache2 running with a niceness of 0 i.e. no niceness


  Since version 0.81, unattended-upgrades does the upgrade calculation with 
os.nice(19). To finish the nice block in /usr/bin/unattended-upgrade, the 
following call is used:
  os.nice(0)

  Since the argument is interpreted as incremental, this should be:
  os.nice(-19)

  Without this fix, this problem is back:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701850
  "unattended-upgrades: nice 19/ionice idle inherited by restarted processes"

  Found in the trusty version (0.82.1ubuntu2), but probably in any
  version (including Debian) since 0.81.

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

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

[Touch-packages] [Bug 1414762] Re: Password gets set instead of a passcode during welcome wizard

[Michael Terry]

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

** No longer affects: unity8 (Ubuntu RTM)

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

Title:
  Password gets set instead of a passcode during welcome wizard

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity8 package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu RTM:
  In Progress

Bug description:
  Whenever I quickly type the passcode during setup wizard, instead of
  passcode, password is set as security mechanism

  1. factory reset your phone
  2. on the startup wizard select 4-digit passcode as security mechanism
  3. when asked to confirm the passcode, quickly type it again.
  4. finish setup

  What happens:
  Instead of a passcode the password is set and I am greeted with OSK to unlock 
the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: ubuntu-system-settings 0.3+15.04.20150123.1~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Mon Jan 26 19:41:20 2015
  InstallationDate: Installed on 2015-01-26 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150126-162525)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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