Re: [Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

2016-10-28 Thread Steve Langasek
On Fri, Oct 28, 2016 at 06:46:07PM -, Ryan Harper wrote:
> > > we really want something like
> > >  After=networking|networkd-wait-online
> > > which handles determining if networkd was supposed to run or not

> > That already exists, it's network-online.target -- whatever "implements"
> > it (ifupdown, networkd, NM) will hook itself into this target. Nothing
> > more, nothing less, so if cloud-init just wants to wait until it's
> > online, then just make it Requires/After=network-online.target instead
> > of Before= it. (But again -- this is a very strong dependency which is
> > very inconvenient anywhere but cloud environments with essentially one
> > virtual ethernet card).

> It may be that network-online.target is the right place.  Scott had some
> reason for not using that explicitly before; I expect some details from
> him.

Because network-online.target is not guaranteed to be reached for the
reasons Martin mentions, so cloud-init depending on it will forever block
other services from starting up, /even if/ you had a valid local data
source.

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  New
Status in cloud-init package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in cloud-init source package in Xenial:
  New
Status in systemd source package in Xenial:
  Triaged

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  
  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
└─basic.target @11.403s
  └─sockets.target @11.401s
└─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
└─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
└─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
└─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
└─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
└─system.slice @783ms
  └─-.slice @721ms

  
  cloud-init would need networkd to run at or before 'networking.service' so it 
can raise networking to then find and use network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list 
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   

Re: [Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

2016-10-28 Thread Steve Langasek
On Fri, Oct 28, 2016 at 06:02:29PM -, Martin Pitt wrote:
> > However, if there isn't a local seed, then we must search again *once*
> networking is up.

> But this "if there isn't a local seed" isn't something you can express as
> a static condition, hence my thought that it might be better if c-i calls
> s-n-wait-online if and only if it's necessary.  But YMMV.

Yes, it's not a static condition; and even if it *were*, cloud-init should
apply sensible timeouts in the event that no network source is available.
So s-n-wait-online is still the better answer.

> > This works just fine with 'networking.service'

> This did/does not really work "fine" IMHO -- all of our cloud images
> hang for a long time at boot unless you give them a local data source or
> disable cloud-init.

That is the image working as designed, when booted in an environment it's
not designed for.

> It also imposes the restriction that you must be online during boot, which
> is fine for a cloud environment, but rather unfriendly for other
> scenarios.

cloud-init does not *require* you to be online.  It *requires* you to
provide a data source; as you've already pointed out, it can be a local disk
or it can be a network source.  Sometimes you have a disk source, sometimes
you have a network source; this is not a design decision of cloud-init, it's
a function of the *cloud environment* where you're booting the image, and
it's out of the scope of this bug to redesign cloud-init to be something
other than it is - a tool for provisioning generic images when booting
noninteractively in a cloud.

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  New
Status in cloud-init package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in cloud-init source package in Xenial:
  New
Status in systemd source package in Xenial:
  Triaged

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  
  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
└─basic.target @11.403s
  └─sockets.target @11.401s
└─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
└─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
└─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
└─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
└─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
└─system.slice @783ms
  └─-.slice @721ms

  
  cloud-init would need networkd to run at or before 'networking.service' so it 
can raise networking to then find and use network-based datasources.

  # grep 

Re: [Touch-packages] [Bug 1633828] Re: Mounting /boot/efi fails always after updating to 16.10

2016-10-28 Thread Prasanna Kumar
System does not boot as mount times out and drops to a emergency shell.

Did not try mounting manually. Will get back with result soon.

On 29-Oct-2016 12:20 am, "Phillip Susi"  wrote:

> So what happens when you don't comment it out?  What happens if you
> manually try to mount it?
>
>
> ** Changed in: util-linux (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633828
>
> Title:
>   Mounting /boot/efi fails always after updating to 16.10
>
> Status in util-linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   System does not boot properly as mounting /boot/efi fails. Commented
>   out /boot/efi entry in /etc/fstab to boot system normally. This
>   started happening after update to 16.10. Everything was working fine
>   in 15.10, 16.04.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: mount 2.28.2-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
>   Uname: Linux 4.8.0-22-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu8
>   Architecture: amd64
>   Date: Sun Oct 16 15:23:19 2016
>   InstallationDate: Installed on 2015-11-20 (330 days ago)
>   InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   SourcePackage: util-linux
>   UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/util-linux/+
> bug/1633828/+subscriptions
>

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

Title:
  Mounting /boot/efi fails always after updating to 16.10

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  System does not boot properly as mounting /boot/efi fails. Commented
  out /boot/efi entry in /etc/fstab to boot system normally. This
  started happening after update to 16.10. Everything was working fine
  in 15.10, 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: mount 2.28.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 16 15:23:19 2016
  InstallationDate: Installed on 2015-11-20 (330 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago)

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

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


[Touch-packages] [Bug 1637684] Re: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file on stdin at conffile prompt

2016-10-28 Thread Steve Langasek
** Also affects: dpkg (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file
  on stdin at conffile prompt

Status in base-files package in Ubuntu:
  Incomplete
Status in dpkg package in Ubuntu:
  Triaged

Bug description:
  I don'know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: base-files 9.4ubuntu4.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 29 02:11:08 2016
  Dependencies:
   
  Df:
   Filesystem 1K-blocks  Used Available Use% Mounted on
   udev 8036636 0   8036636   0% /dev
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-10-29 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: base-files
  Title: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file 
on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.10-help-text: 2016-09-05T02:11:11

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

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


[Touch-packages] [Bug 1561545] Re: Launcher leaves application name artifact on desktop

2016-10-28 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Launcher leaves application name artifact on desktop

Status in xorg package in Ubuntu:
  Expired

Bug description:
  See attached info and attached screenshot.

  When mouse-hovering over an application icon in the launcher, and then
  moving the mouse away, often times there is a artifact of said
  application name bubble left on the desktop.

  I have my launcher set to auto-hide.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  BootLog: /dev/sda1: clean, 330541/7815168 files, 10329618/31258368 blocks
  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 Mar 24 08:39:47 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1427]
  InstallationDate: Installed on 2016-03-17 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160316)
  MachineType: ASUSTeK Computer Inc. UX31E
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=77be5fdd-c844-4d59-af29-cc718cf6b41a ro intel_state=disable 
pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 "acpi_osi=Windows 2009" 
"acpi_os_name=Windows 2009" quiet splash intel_state=disable pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 "acpi_osi=Windows 2009" 
"acpi_os_name=Windows 2009" vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31E.210:bd12/26/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160318-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Mar 24 07:13:59 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id6107 
   vendor COR
  xserver.version: 2:1.18.1-1ubuntu4

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

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


[Touch-packages] [Bug 1594554] Re: Some letters are missing in thunderbird at least

2016-10-28 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Some letters are missing in thunderbird at least

Status in xorg package in Ubuntu:
  Expired

Bug description:
  It comes and goes. Some times the letter z is missing in a letter box

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-60.80~14.04.1-generic 3.16.7-ckt22
  Uname: Linux 3.16.0-60-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Mon Jun 20 20:39:05 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1362]
   NVIDIA Corporation GT218M [GeForce 310M] [10de:0a70] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1362]
  InstallationDate: Installed on 2015-06-06 (379 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK Computer Inc. U33Jc
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-60-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U33Jc.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U33Jc
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU33Jc.209:bd08/20/2010:svnASUSTeKComputerInc.:pnU33Jc:pvr1.0:rvnASUSTeKComputerInc.:rnU33Jc:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: U33Jc
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Jun 20 19:50:23 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4140 
   vendor AUO
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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


[Touch-packages] [Bug 1617962] Re: package libelf1:amd64 0.166-2ubuntu1 failed to install/upgrade: package libelf1:amd64 0.166-2ubuntu1 cannot be configured because libelf1:i386 is at a different vers

2016-10-28 Thread Launchpad Bug Tracker
[Expired for elfutils (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package libelf1:amd64 0.166-2ubuntu1 failed to install/upgrade:
  package libelf1:amd64 0.166-2ubuntu1 cannot be configured because
  libelf1:i386 is at a different version (0.165-3ubuntu1)

Status in elfutils package in Ubuntu:
  Expired

Bug description:
  "The following packages have been kept back:"

  12 packages

  so I ran:

  sudo apt install <12 packages>

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libelf1:amd64 0.166-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Mon Aug 29 11:52:32 2016
  Dependencies:
   gcc-6-base 6.2.0-1ubuntu12
   libc6 2.24-0ubuntu1
   libgcc1 1:6.2.0-1ubuntu12
   zlib1g 1:1.2.8.dfsg-2ubuntu5
  ErrorMessage: package libelf1:amd64 0.166-2ubuntu1 cannot be configured 
because libelf1:i386 is at a different version (0.165-3ubuntu1)
  InstallationDate: Installed on 2016-08-05 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu3
  SourcePackage: elfutils
  Title: package libelf1:amd64 0.166-2ubuntu1 failed to install/upgrade: 
package libelf1:amd64 0.166-2ubuntu1 cannot be configured because libelf1:i386 
is at a different version (0.165-3ubuntu1)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1605618] Re: Monitor on Lenovo dock not detected after Suspend

2016-10-28 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Monitor on Lenovo dock not detected after Suspend

Status in xorg package in Ubuntu:
  Expired

Bug description:
  What I do:
  Lenovo x250 is connected to Lenovo dock where an additional monitor is 
connected. I only use the external.
  Then I close the lid, take the laptop off the dock and use it a few minutes 
later just fine.
  Then I return back home, connect the laptop to the dock again with closed 
lid. I press the dock's power button to wake it up. External monitor does not 
react.
  When I open the lid, the internal monitor is on, I can not switch to the 
external monitor in system settings, it is not detected in "xrandr --query".

  Ubuntu 16.04.1
  xorg: 1:7.7+13ubuntu3

  Would be nice if you guys can help. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: [9.228976] rc.local[1043]:  * Starting crypto disk...
  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 Jul 22 14:23:04 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-28-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2016-05-24 (59 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20CLS41500
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=9f9a0e4b-b36a-456a-be5e-e5e00a4d1a0b ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET42W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CLS41500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET42W(1.21):bd02/26/2016:svnLENOVO:pn20CLS41500:pvrThinkPadX250:rvnLENOVO:rn20CLS41500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CLS41500
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jul 18 21:16:45 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.2

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

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


[Touch-packages] [Bug 1613001] Re: mouse cursor flashing after adding third monitor through usb 3.0 displaylink monitor

2016-10-28 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  mouse cursor flashing after adding third monitor through usb 3.0
  displaylink monitor

Status in xorg package in Ubuntu:
  Expired

Bug description:
  
  Ubuntu 16.04 LTS, i7-3630QM, Intel HD Graphics 4000

  LVDS1 primary is Samsung NP350 laptop monitor
  HDMI1 is HDMI monitor
  DVI-I-1 is through USB 3.0 displaylink to HDMI/DVI/Eth adapter, 
idVendor=17e9, idProduct=4307, monitor connected via HDMI

  Mouse cursor constantly flashing on HDMI1 (sometimes clicking at empty
  area stops flashing, but mouse/keyboard action in a field with
  editable cursor like a web form triggers flashing), occasionally on
  LVDS1 but never on DVI-I-1

  
  $ xrandr
  Screen 0: minimum 8 x 8, current 5440 x 1080, maximum 32767 x 32767
  LVDS1 connected primary 1600x900+3840+0 (normal left inverted right x axis y 
axis) 380mm x 210mm
 1600x900  60.06*+
 1440x900  59.89  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 800x450   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  HDMI1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 
600mm x 340mm
 1920x1080 60.00*+  50.0059.94  
 1920x1080i60.0050.0059.94  
 1680x1050 59.88  
 1280x1024 75.0260.02  
 1440x900  59.90  
 1280x960  60.00  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1440x576  50.00  
 1024x768  75.0870.0760.00  
 1440x480  60.0059.94  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0066.6760.0059.94  
 720x400   70.08  
  VGA1 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 connected 1920x1080+0+0 598mm x 336mm
 1920x1080 60.00*+  50.0059.94  
 1680x1050 59.88  
 1600x900  60.00  
 1280x1024 75.0260.02  
 1280x960  60.00  
 1280x800  59.91  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 1024x576  59.97  
 832x624   74.55  
 800x600   75.0060.3256.25  
 720x576   50.00  
 848x480   60.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
1920x1080 (0xf7) 148.500MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.50KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  60.00Hz
1920x1080 (0xf8) 148.500MHz +HSync +VSync
  h: width  1920 start 2448 end 2492 total 2640 skew0 clock  
56.25KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  50.00Hz
1920x1080 (0xf9) 148.352MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.43KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  59.94Hz
1680x1050 (0xfd) 119.000MHz +HSync -VSync
  h: width  1680 start 1728 end 1760 total 1840 skew0 clock  
64.67KHz
  v: height 1050 start 1053 end 1059 total 1080   clock  59.88Hz
1280x1024 (0xfe) 135.000MHz +HSync +VSync
  h: width  1280 start 1296 end 1440 total 1688 skew0 clock  
79.98KHz
  v: height 1024 start 1025 end 1028 total 1066   clock  75.02Hz
1280x1024 (0xff) 108.000MHz +HSync +VSync
  h: width  1280 start 1328 end 1440 total 1688 skew0 clock  
63.98KHz
  v: height 1024 start 1025 end 1028 total 1066   clock  60.02Hz
1280x960 (0x100) 108.000MHz +HSync +VSync
  h: width  1280 start 1376 end 1488 total 1800 skew0 clock  
60.00KHz
  v: height  960 start  961 end  964 total 1000   clock  60.00Hz
1152x864 (0x101) 108.000MHz +HSync +VSync
  h: width  1152 start 1216 end 1344 total 1600 skew0 clock  
67.50KHz
  v: height  864 start  865 end  868 total  900   clock  75.00Hz
1280x720 (0x102) 74.250MHz +HSync +VSync
  h: width  1280 start 1390 end 1430 total 1650 skew0 clock  
45.00KHz
  v: height  720 start  725 end  730 total  750   clock  60.00Hz
1280x720 (0x103) 

[Touch-packages] [Bug 1616113] Re: Occasionally mouse cursor get stucked, internally i915 driver seems to be culprit

2016-10-28 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Occasionally mouse cursor get stucked, internally i915 driver seems to
  be culprit

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I documented my problem here:
  
http://askubuntu.com/questions/795970/lubuntu-14-04-mouse-cursor-stucks-occasionally

  tl;tr
  Mouse cursor stucks on certain events (clicking on Back-button in 
Chromium-brouser triggers it every time), and then in logs are following lines:

  [drm] stuck on render ring
  [drm] GPU crash dump saved to /sys/class/drm/card0/error
  [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, 
including userspace.
  [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> 
DRM/Intel
  [drm] drm/i915 developers can then reassign to the right component if it's 
not a kernel issue.
  [drm] The gpu crash dump is required to analyze gpu hangs, so please always 
attach it.
  [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x77d7000 ctx 
0) at 0x77d94a4
  [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
  [drm:i915_reset] *ERROR* Failed to reset chip.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: LXDE
  Date: Tue Aug 23 18:05:06 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:100c]
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:4192): WARNING **: Failed to load user image: Failed 
to open file '/home/margo/.face': No such file or directory
   
   ** (lightdm-gtk-greeter:4192): WARNING **: Failed to load user image: Failed 
to open file '/home/wanradt/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1276): WARNING **: Failed to 
load user image: Failed to open file '/home/margo/.face': No such file or 
directory
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-93-generic 
root=UUID=e0593e21-dee3-49bd-bb82-e32995ff34c7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2JKT45AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr2JKT45AUS:bd07/01/2008:svnLENOVO:pn8795D1G:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct4:cvrNONE:
  dmi.product.name: 8795D1G
  dmi.product.version: ThinkCentre M55
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Aug 23 17:44:59 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: intel

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

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


[Touch-packages] [Bug 1618077] Re: [Lenovo ThinkPad T520] Regression: cannot set up 3 display configuration any more (Optimus)

2016-10-28 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [Lenovo ThinkPad T520] Regression: cannot set up 3 display
  configuration any more (Optimus)

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Shortly after trying to enable the 3rd monitor and the error showed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Aug 29 16:37:10 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-28-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21d1]
   NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d1]
  InstallationDate: Installed on 2016-02-07 (203 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  LightdmDisplayLog:
   Cannot do multiple crtcs without X server dirty tracking 2 interface
   randr: failed to set shadow slave pixmap
   Cannot do multiple crtcs without X server dirty tracking 2 interface
   randr: failed to set shadow slave pixmap
  MachineType: LENOVO 42435HG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=88e9500d-048c-4021-af00-6403ffc0c05e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42435HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn42435HG:pvrThinkPadT520:rvnLENOVO:rn42435HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42435HG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Aug 26 19:58:54 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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


[Touch-packages] [Bug 1637684] Re: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file on stdin at conffile prompt

2016-10-28 Thread Steve Langasek
The logs attached to your bug report show that:
 - You have an /etc/update-motd.d/10-help-text.txt file on your system which 
has been customized to contain Indonesian help text in a way that, if it was 
done by a package, would not be policy compliant
 - This customization generated a prompt on upgrade asking whether to keep your 
installed version of this conffile, or take the new version of the conffile 
from the package
 - Either from you, or from some software component, the prompt was sent an end 
of file (^D) instead of an answer.

Questions for you:
 - what tool did you use to apply software updates?
 - did you see this prompt about the conffile?  if so, what action did you take?
 - do you know why /etc/update-motd.d/10-help-text.txt is modified on your 
system?

I also see from the log that this was an error that happened when you
were applying updates in June.  I don't know why this apport bug report
is only being submitted now.  It's understandable if you don't remember
what you did as part of an upgrade back in June; however, if at all
possible, we would like to understand exactly what happened as part of
your upgrade in order to best fix this bug.

I am able to reproduce this problem just by running apt from a
commandline and hitting ^D at a conffile prompt.  This part is
definitely a dpkg bug, as dpkg should use the default option (default=N)
on EOF instead of aborting.

** Changed in: base-files (Ubuntu)
   Status: New => Incomplete

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

Title:
  package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file
  on stdin at conffile prompt

Status in base-files package in Ubuntu:
  Incomplete

Bug description:
  I don'know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: base-files 9.4ubuntu4.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 29 02:11:08 2016
  Dependencies:
   
  Df:
   Filesystem 1K-blocks  Used Available Use% Mounted on
   udev 8036636 0   8036636   0% /dev
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-10-29 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: base-files
  Title: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file 
on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.10-help-text: 2016-09-05T02:11:11

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

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


[Touch-packages] [Bug 1637684] [NEW] package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file on stdin at conffile prompt

2016-10-28 Thread pandri
Public bug reported:

I don'know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: base-files 9.4ubuntu4.2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Jun 29 02:11:08 2016
Dependencies:
 
Df:
 Filesystem 1K-blocks  Used Available Use% Mounted on
 udev 8036636 0   8036636   0% /dev
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2016-10-29 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: base-files
Title: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file 
on stdin at conffile prompt
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.update-motd.d.10-help-text: 2016-09-05T02:11:11

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file
  on stdin at conffile prompt

Status in base-files package in Ubuntu:
  New

Bug description:
  I don'know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: base-files 9.4ubuntu4.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 29 02:11:08 2016
  Dependencies:
   
  Df:
   Filesystem 1K-blocks  Used Available Use% Mounted on
   udev 8036636 0   8036636   0% /dev
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-10-29 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: base-files
  Title: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file 
on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.10-help-text: 2016-09-05T02:11:11

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

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


[Touch-packages] [Bug 1637683] [NEW] ubuntu 10.16 internal speakers don't work, but headphones do

2016-10-28 Thread Austin Clements
Public bug reported:

Under sound settings only headphone output is listed as an option, no
internal speakers are listed. Headphone playback does work. In
alsamixer, speaker output was at 0 and muted, but unmuting and
increasing volume does not produce playback in speakers.

ASUS X550LB laptop

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  austinclem1   1647 F pulseaudio
 /dev/snd/controlC0:  austinclem1   1647 F pulseaudio
CurrentDesktop: Unity
Date: Fri Oct 28 20:42:56 2016
InstallationDate: Installed on 2016-10-29 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  austinclem1   1647 F pulseaudio
 /dev/snd/controlC0:  austinclem1   1647 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [X550LB, Realtek ALC3236, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550LB.403
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550LB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LB.403:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X550LB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  ubuntu 10.16 internal speakers don't work, but headphones do

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Under sound settings only headphone output is listed as an option, no
  internal speakers are listed. Headphone playback does work. In
  alsamixer, speaker output was at 0 and muted, but unmuting and
  increasing volume does not produce playback in speakers.

  ASUS X550LB laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  austinclem1   1647 F pulseaudio
   /dev/snd/controlC0:  austinclem1   1647 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 28 20:42:56 2016
  InstallationDate: Installed on 2016-10-29 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  austinclem1   1647 F pulseaudio
   /dev/snd/controlC0:  austinclem1   1647 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [X550LB, Realtek ALC3236, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LB.403
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LB.403:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 280571] Re: NetworkManager does not auto-connect to VPNs marked "Connect Automatically"

2016-10-28 Thread Dean Robinson
** Package changed: network-manager (Ubuntu) => network-manager-openvpn
(Ubuntu)

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

Title:
  NetworkManager does not auto-connect to VPNs marked "Connect
  Automatically"

Status in NetworkManager:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager package in Debian:
  Fix Released

Bug description:
  VPN connections marked "Connect Automatically" are not activated when
  a wired or wireless network becomes available.

  Fixed upstream in commit:

  commit ece5e209cdc409a21e249dacbdbc953a1db4c6b7
  Author: Jiří Klimeš 
  Date:   Tue Aug 21 17:49:41 2012 +0200

  core: VPN autoconnect feature (bgo #560471) (rh #483120)

  We go through the SECONDARIES state where we check if there are some
  secondary
  (VPN or other) UUIDs that are to be activated before progressing to
  ACTIVATED.
  In case of an error with a secondary UUID or its activation, the base
  connection
  can't activate successfully.

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

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


[Touch-packages] [Bug 1578176] Re: Cannot place or recieve calls when using in-car bluetooth system

2016-10-28 Thread Stunts
This looks a lot like bug #1546310
But in that case, there seems to be a fix released (OTA10 I assume). Just 
thought it could be interesting to have it linked here for reference.

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

Title:
  Cannot place or recieve calls when using in-car bluetooth system

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  After working around bug
  https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158 I was
  able to pair the phone (BQ Aquaris E4.5) with the car hands-free
  system.

  However, thing don't quite work as expected.
  I can use the car's system to place a call using the phone, but The audio is 
not getting properly routed. After placing the call, I can't hear any sounds 
(not even the "ringing" noise), I don't get any feedback after the other person 
has answered the phone, and the other person can't hear me either.

  Furthermore, Long after the other person has hung up the call, the
  phone still looks like the call is ongoing (I have to manually
  disconnect it).

  I can also use the system to answer an incoming call, but the
  sympthoms are the same. No audio on either end.

  Would a debug log be helpful in this situation 
(https://wiki.ubuntu.com/DebuggingBluetooth)?
  Or is something else required?

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

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


[Touch-packages] [Bug 1595963] Re: vt1-6 getting stuck or blank

2016-10-28 Thread Michał Sawicz
Yes, when it was blank, it was blank until a reboot. Switching VTs
worked fine.

I've upgraded to yakkety now and have not been able to reproduce yet.

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

Title:
  vt1-6 getting stuck or blank

Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  It's happening from time to time that my vt1-6 are getting stuck
  (showing tty1 and no input) or blank (just black) completely.

  Restarting system-getty.slice or console-getty.slice doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 24 10:00:54 2016
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS 12-9Q33
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: systemd 229-4ubuntu6
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic.efi.signed 
root=ZFS=/root ro root=ZFS=username-laptop/root quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1637523] Re: App from side stage loses focus when switching to desktop mode

2016-10-28 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
   Status: New => Triaged

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

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

Title:
  App from side stage loses focus when switching to desktop mode

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  bq M10 rc-proposed r220

  Steps to reproduce:
  1. Open an app
  2. Move it to the side stage
  3. Switch to desktop mode

  Expected result:
  The app stays focused, on top of scopes

  What happens instead:
  The app is under scopes. Scopes are focused.

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

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


[Touch-packages] [Bug 1637502] Re: Keyboard stays on screen when doing spread

2016-10-28 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
   Status: New => Triaged

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

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

Title:
  Keyboard stays on screen when doing spread

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  bq M10 rc-proposed r220

  If the OSK is visible and I'm starting to do swipe from the right, I
  expect OSK to hide. Meanwhile the OSK hides only when the spread is
  complete and I take my finger off the screen.

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

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


[Touch-packages] [Bug 880881] Re: [ffe] Power indicator does not combine multiple battery status

2016-10-28 Thread Pedro Côrte-Real
Similar thing on a T460s. It seems the joining of the two batteries is
not really done. I currently have one battery with 0:07 left and another
with 1:37 and the total result is shown as 1:37. It seems the summing up
has regressed.

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

Title:
  [ffe] Power indicator does not combine multiple battery status

Status in indicator-power:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released

Bug description:
  I have an EliteBook 8540w with internal and external battery running Ubuntu 
11.10 (oneiric).
  Linux  3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 
x86_64 x86_64 GNU/Linux

  The power indicator (indicator-power, version 0.9-0ubuntu2) does not combine 
the status of both batteries.
  E.g. if one battery still has 1 hour left, and the other has 2 hours left, it 
will show 1:00 or 2:00, instead of 3:00.
  E.g. When the external battery is almost run out (but the internal one is 
still charged), the indicator becomes red, instead of staying white/grey. It 
should only be red when both batteries are almost drained.
  E.g. when the internal one is fully charged, and the external one is 
discharging, the estimated time show is the estimated time that the external 
one will be discharged, not taking into account the internal one. see attached 
screenshot (total time show should be around 4 hours)

  The original applet provided by gnome (I re-enabled the notification
  area) does (still) have the behavior as I expect. In other words, this
  is a regression compared to 10.10 (pre-unity).

  : "If a device has
  multiple batteries and uses only one of them at a time, they should be
  presented as separate items inside the battery menu, but everywhere
  else they should be aggregated. Their percentages should be averaged.
  If any are discharging, the aggregated time remaining should be the
  maximum of the times for all those that are discharging, plus the sum
  of the times for all those that are idle. Otherwise, the aggregated
  time remaining should be the the maximum of the times for all those
  that are charging."

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/880881/+subscriptions

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


[Touch-packages] [Bug 861642] Re: upowerd uses 100% cpu till killed

2016-10-28 Thread Mike Myers
I would like to use my Linux system to charge up my iOS devices, but I
don't want to "Trust this Computer" so maybe we can drill down further
on this bug.

As soon as I connect a locked iDevice (tested iOS 9 and iOS 10):

$ top

top - 12:22:28 up 24 days, 21:05,  2 users,  load average: 0.50, 0.56, 0.84
Tasks: 222 total,   2 running, 220 sleeping,   0 stopped,   0 zombie
%Cpu(s): 37.7 us,  2.8 sy,  0.0 ni, 59.1 id,  0.5 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem :  3917996 total,   228612 free,  2176052 used,  1513332 buff/cache
KiB Swap:  4063228 total,  3597580 free,   465648 used.  1188276 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
 2184 root  20   0  348112   5596   4800 R  70.4  0.1   3886:07 upowerd

upowerd itself doesn't tell me much:

$ upower --monitor
Monitoring activity from the power daemon. Press Ctrl+C to cancel.
[15:26:55.169]  device added: 
/org/freedesktop/UPower/devices/media_player_1_1

$ upower --monitor-detail
Monitoring activity from the power daemon. Press Ctrl+C to cancel.
[15:28:23.805]  device added: 
/org/freedesktop/UPower/devices/media_player_1_1
  native-path:  /sys/devices/pci:00/:00:14.0/usb1/1-1
  vendor:   Apple_Inc.
  model:iPod
  serial:   8b1d0ada9c849c62fd52263c3797034216608bf0
  power supply: no
  updated:  Wed 31 Dec 1969 07:00:00 PM EST (1477682903 seconds ago)
  has history:  yes
  has statistics:   no
  media-player
warning-level:   none
percentage:  0%
icon-name:  'battery-missing-symbolic'

perf top: it shows the top four items to be libgmp.so.10.3.0 in:
__gmpn_redc_1
__gmpn_sqr_basecase
__gmpn_mul_basecase
__gmpz_probab_prime_p

`perf top --sort=comm,dso` shows that the top item is upowerd, in
libgmp.so.10.3.0

This is a math library. I can only guess, but it may be doing math
operations to compute the UDID of the iOS device every time it tries to
communicate with it? Some SHA1 operations maybe.

To use strace on the upowerd process (PID 2184):

$ sudo strace -p 2184 -c
strace: Process 2184 attached
strace: [ Process PID=2184 runs in x32 mode. ]
strace: [ Process PID=2184 runs in 64 bit mode. ]
^Cstrace: Process 2184 detached
% time seconds  usecs/call callserrors syscall
-- --- --- - - 
 58.050.000101   196   sendto
 41.950.73   0 14494   getrusage
  0.000.00   024   close
  0.000.00   030 6 stat
  0.000.00   0 6   poll
  0.000.00   096   select
  0.000.00   024   socket
  0.000.00   024   connect
  0.000.00   096   recvfrom
-- --- --- - - 
100.000.000174 14890 6 total

$ sudo strace -p 2184 -e sendto -i
This shows that it is sending XML messages over and over again. For fuller 
output you can add `-s 999` ... these are XML formatted messages being sent to 
the iPod as part of some kind of iOS proprietary communications protocol.

You can verify using a USB capture via usbmon, that the host Linux
system is in an infinite loop asking the iPod for something. Wireshark
doesn't have a dissector for iOS vendor-specific interfaces and commands
but you can see the same XML messages traveling the USB bus that were
observed in strace.

Is this actually a bug in libimobiledevice ? This seems like a failure
to obey an iOS protocol. Supposedly I am already on the latest version:
my package is 1.2.0+dfsg-3~ubuntu0.2

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

Title:
  upowerd uses 100% cpu till killed

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  top - 12:57:54 up  2:56,  3 users,  load average: 1.06, 1.12, 1.35
  Tasks: 219 total,   2 running, 216 sleeping,   0 stopped,   1 zombie
  Cpu0  : 70.2%us, 29.8%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu1  :  2.3%us,  1.3%sy,  0.0%ni, 96.4%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu2  :  1.0%us,  0.3%sy,  0.0%ni, 98.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu3  :  0.7%us,  1.6%sy,  0.0%ni, 97.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu4  :  0.0%us,  0.3%sy,  0.0%ni, 99.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu5  :  0.0%us,  0.3%sy,  0.0%ni, 98.3%id,  1.4%wa,  0.0%hi,  0.0%si,  0.0%st
  Mem:   5994176k total,  4198260k used,  1795916k free,63308k buffers
  Swap:  8193144k total,   355188k used,  7837956k free,   334316k cached

PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND  
  
   2268 

[Touch-packages] [Bug 1506427] Re: /usr/lib/unity/unity-panel-service:11:g_type_check_instance_is_a:ido_calendar_menu_item_key_press:_gtk_marshal_BOOLEAN__BOXED:g_closure_invoke:signal_emit_unlocked_R

2016-10-28 Thread Launchpad Bug Tracker
** Branch linked: lp:~3v1n0/ido/parent-signals-disconnection

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

Title:
  /usr/lib/unity/unity-panel-
  
service:11:g_type_check_instance_is_a:ido_calendar_menu_item_key_press:_gtk_marshal_BOOLEAN__BOXED:g_closure_invoke:signal_emit_unlocked_R

Status in ido package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

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

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


[Touch-packages] [Bug 1637663] [NEW] package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-28 Thread Je
Public bug reported:

root@ntp-srv001:~# apt-get install ntp
Reading package lists... Done
Building dependency tree   
Reading state information... Done
ntp is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 86 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2.14.04.10) ...
dpkg: error processing package ntp (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 ntp
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@ntp-srv001:~#

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10
ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Oct 28 15:24:45 2016
DuplicateSignature: package:ntp:1:4.2.6.p5+dfsg-3ubuntu2.14.04.10:subprocess 
installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-10-28 (0 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
NtpStatus: ntpq: read: Connection refused
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: ntp
Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check trusty

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

Title:
  package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in ntp package in Ubuntu:
  New

Bug description:
  root@ntp-srv001:~# apt-get install ntp
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  ntp is already the newest version.
  0 upgraded, 0 newly installed, 0 to remove and 86 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2.14.04.10) ...
  dpkg: error processing package ntp (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   ntp
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  root@ntp-srv001:~#

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Oct 28 15:24:45 2016
  DuplicateSignature: package:ntp:1:4.2.6.p5+dfsg-3ubuntu2.14.04.10:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-28 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: ntp
  Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1636747] Re: Printer canon MF3010.

2016-10-28 Thread Tyler Hicks
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Printer canon MF3010.

Status in cups package in Ubuntu:
  New

Bug description:
  Iinstal drivers for printer, he see printer, but then i need to print,
  printer have no reaction on it.. i instal drivers from canon site,
  64bit, debian,

  
  lupul@Zotac:~$ $ lsmod | grep usb
  $: command not found
  lupul@Zotac:~$ lsmod | grep usb
  usblp  20480  0 
  rtsx_usb_ms20480  0 
  memstick   20480  1 rtsx_usb_ms
  btusb  45056  0 
  btrtl  16384  1 btusb
  btbcm  16384  1 btusb
  btintel16384  1 btusb
  bluetooth 516096  25 bnep,btbcm,btrtl,btusb,rfcomm,btintel
  rtsx_usb_sdmmc 28672  0 
  rtsx_usb   24576  2 rtsx_usb_sdmmc,rtsx_usb_ms
  usbhid 49152  0 
  hid   118784  2 hid_generic,usbhid
  lupul@Zotac:~$ tail -f /var/log/syslog
  Oct 26 11:41:03 Zotac colord: Device added: cups-MF3010
  Oct 26 11:41:29 Zotac kernel: [ 5999.346697] usblp1: removed
  Oct 26 11:41:42 Zotac kernel: [ 6012.583208] usblp 1-3:1.1: usblp1: USB 
Bidirectional printer dev 18 if 1 alt 0 proto 2 vid 0x04A9 pid 0x2759
  Oct 26 11:43:37 Zotac kernel: [ 6127.943687] usb 1-3: USB disconnect, device 
number 18
  Oct 26 11:43:37 Zotac kernel: [ 6127.944292] usblp1: removed
  Oct 26 11:43:37 Zotac udev-configure-printer: remove 
/devices/pci:00/:00:1d.7/usb1/1-3
  Oct 26 11:43:37 Zotac udev-configure-printer: URI of detected printer: 
usb://Canon/MF3010?serial=0167F3C3=1, normalized: canon mf3010 
serial 0167f3c3 interface 1
  Oct 26 11:43:37 Zotac udev-configure-printer: URI of print queue: 
usb://Canon/MF3010?serial=0167F3C3=1, normalized: canon mf3010 
serial 0167f3c3 interface 1
  Oct 26 11:43:37 Zotac udev-configure-printer: Queue 
ipp://localhost:631/printers/MF3010 has matching device URI
  Oct 26 11:43:37 Zotac udev-configure-printer: Disabled printer 
ipp://localhost:631/printers/MF3010 as the corresponding device was unplugged 
or turned off
  Oct 26 11:45:08 Zotac kernel: [ 6218.772381] usb 1-3: new high-speed USB 
device number 19 using ehci-pci
  Oct 26 11:45:08 Zotac kernel: [ 6218.928989] usb 1-3: New USB device found, 
idVendor=04a9, idProduct=2759
  Oct 26 11:45:08 Zotac kernel: [ 6218.928997] usb 1-3: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Oct 26 11:45:08 Zotac kernel: [ 6218.929002] usb 1-3: Product: MF3010
  Oct 26 11:45:08 Zotac kernel: [ 6218.929007] usb 1-3: Manufacturer: Canon Inc
  Oct 26 11:45:08 Zotac kernel: [ 6218.929011] usb 1-3: SerialNumber: 
0167F3C3
  Oct 26 11:45:08 Zotac kernel: [ 6218.940274] usblp 1-3:1.1: usblp1: USB 
Bidirectional printer dev 19 if 1 alt 0 proto 2 vid 0x04A9 pid 0x2759
  Oct 26 11:45:08 Zotac mtp-probe: checking bus 1, device 19: 
"/sys/devices/pci:00/:00:1d.7/usb1/1-3"
  Oct 26 11:45:08 Zotac mtp-probe: bus: 1, device: 19 was not an MTP device
  Oct 26 11:45:08 Zotac udev-configure-printer: add 
/devices/pci:00/:00:1d.7/usb1/1-3
  Oct 26 11:45:08 Zotac udev-configure-printer: device devpath is 
/devices/pci:00/:00:1d.7/usb1/1-3
  Oct 26 11:45:08 Zotac udev-configure-printer: MFG:Canon MDL:MF3010 SERN:- 
serial:0167F3C3
  Oct 26 11:45:09 Zotac kernel: [ 6220.039167] usblp1: removed
  Oct 26 11:45:09 Zotac kernel: [ 6220.045639] usblp 1-3:1.1: usblp1: USB 
Bidirectional printer dev 19 if 1 alt 0 proto 2 vid 0x04A9 pid 0x2759
  Oct 26 11:45:09 Zotac hp[9777]: io/hpmud/pp.c 627: unable to read device-id 
ret=-1
  Oct 26 11:45:10 Zotac python: io/hpmud/pp.c 627: unable to read device-id 
ret=-1
  Oct 26 11:45:10 Zotac udev-configure-printer: URI contains USB serial number
  Oct 26 11:45:10 Zotac udev-configure-printer: URI match: 
usb://Canon/MF3010?serial=0167F3C3=1
  Oct 26 11:45:10 Zotac udev-configure-printer: URI of detected printer: 
usb://Canon/MF3010?serial=0167F3C3=1, normalized: canon mf3010 
serial 0167f3c3 interface 1
  Oct 26 11:45:10 Zotac udev-configure-printer: URI of print queue: 
usb://Canon/MF3010?serial=0167F3C3=1, normalized: canon mf3010 
serial 0167f3c3 interface 1
  Oct 26 11:45:10 Zotac udev-configure-printer: Queue 
ipp://localhost:631/printers/MF3010 has matching device URI
  Oct 26 11:45:10 Zotac udev-configure-printer: Re-enabled printer 

[Touch-packages] [Bug 1637291] Re: package python-gi 3.22.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239

2016-10-28 Thread Tyler Hicks
** Information type changed from Private Security to Public

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

Title:
  package python-gi 3.22.0-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 239

Status in pygobject package in Ubuntu:
  New

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: python-gi 3.22.0-1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 28 02:45:39 2016
  DuplicateSignature:
   package:python-gi:3.22.0-1
   Setting up python3-idna (2.1-1) ...
   Segmentation fault (core dumped)
   dpkg: error processing package python3-idna (--configure):
subprocess installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 239
  InstallationDate: Installed on 2016-10-27 (0 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: pygobject
  Title: package python-gi 3.22.0-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 239
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1460794] Re: boot fails if /dev/cgroup fstab entry is present

2016-10-28 Thread delijati
I had the same problem, thanks for this ticket and the provided fix:

$ cat /etc/fstab
proc/proc   procnodev,noexec,nosuid 0   0
# / was on /dev/vda1 during installation
UUID=8b76c1d0-c6b8-46d7-9cf8-0c5af739bc60 /   ext4
errors=remount-ro 0   1
# swap was on /dev/vda5 during installation
UUID=85bb4129-a290-4854-aab6-8ffe14be3b84 noneswapsw
  0   0
# cgroup /cgroup cgroup

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

Title:
  boot fails if /dev/cgroup fstab entry is present

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I recently upgraded a server from 14.10 to 15.04. The upgrade claim to
  have worked but the system could not boot afterwards.

  Basically when you attempt to reboot you end up at an emergency maintenance 
prompt early in the boot process.
  After a lot of digging one of the messages in the logs gives:
  systemd[1]: /usr appears to be on its own filesystem and is not already 
mounted. This is not a supported setup. Some things will probably break 
(sometimes even silently) in mysterious ways. Consult 
http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken

  Basically systemd cannot deal with /usr being on a separate partition.
  That needs to be fixed or systemd should not be used for upgrades with
  a separate /usr partition.

  This is related to bug 1460790 but asking for systemd to actually be fixed.
  Please see bug 1460790 if you are looking for a work around on this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Mon Jun  1 15:29:32 2015
  InstallationDate: Installed on 2010-05-23 (1835 days ago)
  InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 
(20100427)
  MachineType: Supermicro X8STi
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/tcsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=676235cd-93b1-426e-8336-fa0078d96145 ro quiet acpi=off pci=noacpi
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-06-01 (0 days ago)
  dmi.bios.date: 09/17/10
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X8STi
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd09/17/10:svnSupermicro:pnX8STi:pvr1234567890:rvnSupermicro:rnX8STi:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X8STi
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro

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

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


[Touch-packages] [Bug 1577049] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04

2016-10-28 Thread experimancer
** Tags removed: xenial

** Tags removed: verification-done yakkety
** Tags added: verification-failed xenial

** Tags added: verification-done yakkety

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

Title:
  Switch user feature has disappeared from GNOME Shell since upgrade
  from 15.10 to 16.04

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Released
Status in accountsservice package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  Ubuntu 16.04's accountsservice was built without systemd support because 
systemd dropped libsystemd-login because that functionality was merged into 
libsystemd.

  At a minimum, this broke GNOME Shell's "Switch User" feature.

  Test Case
  =
  1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages.
  2. Add a user if necessary to ensure you have at least 2 user accounts 
configured.
  3. Reload gnome-shell. You can do this with Alt+F2 and entering the lower 
case letter r. Or you can log out of all user accounts and log back in.
  4. Click the system status area in the top right of GNOME Shell.
  5. Click your user name. "Switch User" should appear in the list.

  Regression Potential
  
  None.
  The one-line change to accountsservice's configure check was made in Debian's 
accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was 
included in accountsservice 0.6.42 released in June.

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

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


[Touch-packages] [Bug 1637624] Re: having some abnormal working

2016-10-28 Thread Tyler Hicks
** Information type changed from Private Security to Public

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

Title:
  having some abnormal working

Status in xorg package in Ubuntu:
  New

Bug description:
  refresh option not coming..
  welcome screen of ubuntu not showing
  vlc media player not working properly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.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
  Date: Sat Oct 29 01:01:01 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06c2]
  InstallationDate: Installed on 2016-10-25 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 8087:07dc Intel Corp. 
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:5683 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 3559
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=bdee4485-8459-4670-a646-3ec068ec8c78 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.6
  dmi.board.name: 047TR1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.6:bd01/12/2016:svnDellInc.:pnVostro3559:pvr:rvnDellInc.:rn047TR1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 3559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Oct 28 23:00:51 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1199 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.1

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

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


[Touch-packages] [Bug 1577049] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04

2016-10-28 Thread experimancer
FYI: This fix does not resolve the issue of missing "Switch User" line
in the Ubuntu/Xenial/16.04.1 desktop GUI.

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

Title:
  Switch user feature has disappeared from GNOME Shell since upgrade
  from 15.10 to 16.04

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Released
Status in accountsservice package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  Ubuntu 16.04's accountsservice was built without systemd support because 
systemd dropped libsystemd-login because that functionality was merged into 
libsystemd.

  At a minimum, this broke GNOME Shell's "Switch User" feature.

  Test Case
  =
  1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages.
  2. Add a user if necessary to ensure you have at least 2 user accounts 
configured.
  3. Reload gnome-shell. You can do this with Alt+F2 and entering the lower 
case letter r. Or you can log out of all user accounts and log back in.
  4. Click the system status area in the top right of GNOME Shell.
  5. Click your user name. "Switch User" should appear in the list.

  Regression Potential
  
  None.
  The one-line change to accountsservice's configure check was made in Debian's 
accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was 
included in accountsservice 0.6.42 released in June.

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

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


[Touch-packages] [Bug 1506427] Re: /usr/lib/unity/unity-panel-service:11:g_type_check_instance_is_a:ido_calendar_menu_item_key_press:_gtk_marshal_BOOLEAN__BOXED:g_closure_invoke:signal_emit_unlocked_R

2016-10-28 Thread Treviño
** No longer affects: unity (Ubuntu)

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

** No longer affects: unity

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

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

** Changed in: ido (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  /usr/lib/unity/unity-panel-
  
service:11:g_type_check_instance_is_a:ido_calendar_menu_item_key_press:_gtk_marshal_BOOLEAN__BOXED:g_closure_invoke:signal_emit_unlocked_R

Status in ido package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

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

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


[Touch-packages] [Bug 1577049] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04

2016-10-28 Thread experimancer
Still no "Swicth User" displayed in the top right corner list under the
user name in desktop UI.

This "fix" does not resolve the bug (missing Swicth User in the UI) in
Ubuntu/16.04.1/Xenial with accountsservice 0.6.40-2ubuntu11.2.

These bug report should be reopened.

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

Title:
  Switch user feature has disappeared from GNOME Shell since upgrade
  from 15.10 to 16.04

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Released
Status in accountsservice package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  Ubuntu 16.04's accountsservice was built without systemd support because 
systemd dropped libsystemd-login because that functionality was merged into 
libsystemd.

  At a minimum, this broke GNOME Shell's "Switch User" feature.

  Test Case
  =
  1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages.
  2. Add a user if necessary to ensure you have at least 2 user accounts 
configured.
  3. Reload gnome-shell. You can do this with Alt+F2 and entering the lower 
case letter r. Or you can log out of all user accounts and log back in.
  4. Click the system status area in the top right of GNOME Shell.
  5. Click your user name. "Switch User" should appear in the list.

  Regression Potential
  
  None.
  The one-line change to accountsservice's configure check was made in Debian's 
accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was 
included in accountsservice 0.6.42 released in June.

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

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


[Touch-packages] [Bug 1636473] Re: random cursor jumps when clicking on dell xps 13

2016-10-28 Thread s.illes79
Hi Chris,

1) Not sure, laptop came with dell version of ubuntu 14.04 LTS but i wiped it 
on the second day, however i did not notice for those 2 days - maybe dell has a 
patch ?
2) I'll try it later, right now it's not feasible - i'm on the move and 
internet connection is a joke here.
3) I tried synclient AreaBottomEdge=4000, which slightly improved the 
situation, but only if the click happens inside the bottom edge, if happens 
outside than itis still possible to get random jumps.

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

Title:
  random cursor jumps when clicking on dell xps 13

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  1 out of 20-40 clicks on the touch pad results in a pointer jump and a
  "random" click.

  Hard to reproduce, but mostly happens when I use my middle finger to
  move the cursor and click with index finger. Sometimes the double
  touch of middle/index finger is interpreted as mouse move, the jump is
  more or less the same distance as if i had moved the index to the
  middle finger position.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.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: Tue Oct 25 22:04:10 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0704]
  InstallationDate: Installed on 2016-09-08 (46 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=fe8099eb-a258-42d6-8f67-69496f1e0fcf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Oct 22 20:20:44 2016
  xserver.configfile: default
  xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193 
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.1

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

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


[Touch-packages] [Bug 1637652] [NEW] stucked in a login loop

2016-10-28 Thread Benet J. Darder
Public bug reported:

after 16.10 upgrade I cannot login into the graphical interface

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Oct 28 23:40:30 2016
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
 nvidia-340, 340.98, 4.8.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Point of View BV G86 [GeForce 8500 GT] [1acc:0857]
InstallationDate: Installed on 2012-03-13 (1690 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Gigabyte Technology Co., Ltd. Z68XP-UD3P
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=ca_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=401cb21e-ddab-46d5-a6dd-72a53a7f0ca3 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F7
dmi.board.name: Z68XP-UD3P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd02/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: Z68XP-UD3P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Oct 28 23:29:28 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech Gaming Keyboard G610 KEYBOARD, id 8
 inputLogitech Gaming Keyboard G610 KEYBOARD, id 9
 inputLogitech USB Optical Mouse MOUSE, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6

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


** Tags: amd64 apport-bug ubuntu yakkety

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

Title:
  stucked in a login loop

Status in xorg package in Ubuntu:
  New

Bug description:
  after 16.10 upgrade I cannot login into the graphical interface

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Oct 28 23:40:30 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
   nvidia-340, 340.98, 4.8.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Point of View BV G86 [GeForce 8500 GT] [1acc:0857]
  InstallationDate: Installed on 2012-03-13 (1690 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. Z68XP-UD3P
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=401cb21e-ddab-46d5-a6dd-72a53a7f0ca3 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: Z68XP-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
 

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-10-28 Thread Dave Chiluk
I spoke too soon still exists in Yakkety.

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

Title:
  cannot view wifi networks after re-enabling wifi

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

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Touch-packages] [Bug 1637633] [NEW] Can 't log in ubuntuone account with plugin

2016-10-28 Thread Мария
Public bug reported:

When i want to login in my ubuntuone account with a plugin it show me
"Incorrect password or email", but everything works when i login in web,
because my login(email) and password are correct.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: account-plugin-ubuntuone 15.11+16.10.20160920
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 28 23:33:50 2016
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
InstallationDate: Installed on 2016-10-22 (6 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
ProcEnviron:
 LANGUAGE=ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntuone-credentials
UpgradeStatus: Upgraded to yakkety on 2016-10-23 (5 days ago)

** Affects: ubuntuone-credentials (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  Can 't log in ubuntuone account with plugin

Status in ubuntuone-credentials package in Ubuntu:
  New

Bug description:
  When i want to login in my ubuntuone account with a plugin it show me
  "Incorrect password or email", but everything works when i login in
  web, because my login(email) and password are correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: account-plugin-ubuntuone 15.11+16.10.20160920
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 28 23:33:50 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2016-10-22 (6 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntuone-credentials
  UpgradeStatus: Upgraded to yakkety on 2016-10-23 (5 days ago)

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

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


[Touch-packages] [Bug 1635996] Re: Libreoffice temporarily hangs / freezes Ubuntu 16.10

2016-10-28 Thread Christopher M. Penalver
Giraffe, the information being attached isn't helpful unfortunately, and can be 
due to not following the provided instructions. Hence, could you please run the 
following command once from a terminal by ensuring you have the package 
xdiagnose installed, and that you click the Yes button for attaching additional 
debugging information:
apport-collect -p xorg 1635996

** Package changed: xserver-xorg-video-intel (Ubuntu) => xorg (Ubuntu)

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635996/+attachment/4768323/+files/JournalErrors.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635996/+attachment/4768321/+files/ProcEnviron.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635996/+attachment/4768319/+files/Dependencies.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635996/+attachment/4768318/+files/ProcEnviron.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635996/+attachment/4768322/+files/Dependencies.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635996/+attachment/4768315/+files/ProcEnviron.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635996/+attachment/4768316/+files/Dependencies.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635996/+attachment/4768313/+files/Dependencies.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635996/+attachment/4768324/+files/ProcEnviron.txt

** Description changed:

  Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD 
Graphics 530 (Skylake GT2) /  Mesa 12.0.3 ) causes LibreOffice and the Ubuntu 
Desktop interface to become unresponsive every few minutes. This freezing will 
last for about five seconds before everything works again.
  When i keep typing while everything freezes the text will appear after the 
system becomes responsive again.
  
  This only happens when i use the Intel HD Graphics 530 IGP.  When using
  the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics
  everything is fine.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice-writer 1:5.2.2-0ubuntu2
  Uname: Linux 4.8.4-040804-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 23 19:13:44 2016
  InstallationDate: Installed on 2016-03-17 (219 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago)
- --- 
- ApportVersion: 2.20.3-0ubuntu8
- Architecture: amd64
- CurrentDesktop: XFCE
- DistroRelease: Ubuntu 16.10
- InstallationDate: Installed on 2016-03-17 (224 days ago)
- InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
- Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1
- PackageArchitecture: amd64
- Tags:  yakkety
- Uname: Linux 4.8.4-040804-generic x86_64
- UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago)
- UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
- _MarkForUpload: True
- --- 
- ApportVersion: 2.20.3-0ubuntu8
- Architecture: amd64
- DistroRelease: Ubuntu 16.10
- InstallationDate: Installed on 2016-03-17 (224 days ago)
- InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
- Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: 
unknown]
- PackageArchitecture: amd64
- Tags: yakkety third-party-packages
- Uname: Linux 4.8.4-040804-generic x86_64
- UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
- UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago)
- UserGroups:
-  
- _MarkForUpload: True
- --- 
- ApportVersion: 2.20.3-0ubuntu8
- Architecture: amd64
- CurrentDesktop: XFCE
- DistroRelease: Ubuntu 16.10
- InstallationDate: Installed on 2016-03-17 (224 days ago)
- InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
- Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: 
unknown]
- PackageArchitecture: amd64
- Tags: yakkety third-party-packages
- Uname: Linux 4.8.4-040804-generic x86_64
- UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
- UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago)
- UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
- _MarkForUpload: True
- --- 
- ApportVersion: 2.20.3-0ubuntu8
- Architecture: amd64
- DistroRelease: Ubuntu 16.10
- InstallationDate: Installed on 2016-03-17 (224 days ago)
- InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 

[Touch-packages] [Bug 1635996] [NEW] Libreoffice temporarily hangs / freezes Ubuntu 16.10

2016-10-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD 
Graphics 530 (Skylake GT2) /  Mesa 12.0.3 ) causes LibreOffice and the Ubuntu 
Desktop interface to become unresponsive every few minutes. This freezing will 
last for about five seconds before everything works again.
When i keep typing while everything freezes the text will appear after the 
system becomes responsive again.

This only happens when i use the Intel HD Graphics 530 IGP.  When using
the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics
everything is fine.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libreoffice-writer 1:5.2.2-0ubuntu2
Uname: Linux 4.8.4-040804-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Sun Oct 23 19:13:44 2016
InstallationDate: Installed on 2016-03-17 (219 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago)
--- 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2016-03-17 (224 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1
PackageArchitecture: amd64
Tags:  yakkety
Uname: Linux 4.8.4-040804-generic x86_64
UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
--- 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2016-03-17 (224 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: 
unknown]
PackageArchitecture: amd64
Tags: yakkety third-party-packages
Uname: Linux 4.8.4-040804-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago)
UserGroups:
 
_MarkForUpload: True
--- 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2016-03-17 (224 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: 
unknown]
PackageArchitecture: amd64
Tags: yakkety third-party-packages
Uname: Linux 4.8.4-040804-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
--- 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2016-03-17 (224 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: 
unknown]
PackageArchitecture: amd64
Tags: yakkety third-party-packages
Uname: Linux 4.8.4-040804-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago)
UserGroups:
 
_MarkForUpload: True

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: xorg (Ubuntu)
 Importance: Low
 Status: Incomplete


** Tags: amd64 apport-bug apport-collected third-party-packages yakkety
-- 
Libreoffice temporarily hangs / freezes Ubuntu 16.10
https://bugs.launchpad.net/bugs/1635996
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1633749] Re: Double login to switch back to my session after closing the guest session

2016-10-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Double login to switch back to my session after closing the guest
  session

Status in lightdm package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.10 x64

* I have my session open and want to temporarily switch to the guest 
session. I click on the appropriate item (top right menu of Unity).
* I am now on the guest session. After I'm done, I close the guest session.
* I am now in front of a screen where I can input my password to go back to 
my session. The wallpaper is the default Ubuntu wallpaper as when I am not 
logged in.
* After I validate my password, another screen is displayed that asks my 
again to enter my password. That time, the wallpaper is my personnal wallpaper 
I have in my session.
* I enter my password again and I am back to my session.

  I did not have to enter my password twice in previous versions of
  Ubuntu when switching of sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 15 18:26:17 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-14 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

2016-10-28 Thread Mihael
I have a Nokia J Bluetooth headset (BH-806) that connects to my Pro 5
Ubuntu phone but no sound is directed to the headset - instead it is
played still on the phone speaker. I tried with another headset and the
same result. I tried to record from my headset but it appears to be
still using the phone microphone. So the headset is connected but the
phone acts is if there would be no Bluetooth headset connected. When I
tried to connect a Bluetooth speaker only it worked perfect. So I have a
problem only with Bluetooth headsets (that have a microphone as well).
Is this the same bug (or a different bug) or does this have any solution
somewhere and then maybe somebody can help me?

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

Title:
  Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

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

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


[Touch-packages] [Bug 1637629] [NEW] monitors become unavailable after blanking

2016-10-28 Thread Kevin O'Gorman
Public bug reported:

My monitors become unavailable and hard to configure after blanking, or
switching to a different input, let alone unplugging.

I can boot into 14.04 and do not see this problem.  It is present in
16.04.  I did not use the releases in between on this system.

It is a core-i7 machine, so the graphics is Intel and is on the
motherboard.  I'm using all three of the outputs provided by my
Z97-Deluxe mobo.  I have had to disable blanking because otherwise I
will definitely have at least one monitor no longer active when I wake
up the system.  Getting it active again requires a number, at least 3,
of attempts to "use this monitor" in the Display widget. plus un-
mirroring and putting it back in its proper place.

This also happens if I switch the monitors to using another input, which
I wanted to do because I have two systems and I'd like to switch the
monitors between them.  I'm having to use a workspace of ssh+tmux
instances instead, which has some drawbacks of its own, but is at least
workable.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: wl
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 28 12:50:37 2016
InstallationDate: Installed on 2016-08-08 (80 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  monitors become unavailable after blanking

Status in apport package in Ubuntu:
  New

Bug description:
  My monitors become unavailable and hard to configure after blanking,
  or switching to a different input, let alone unplugging.

  I can boot into 14.04 and do not see this problem.  It is present in
  16.04.  I did not use the releases in between on this system.

  It is a core-i7 machine, so the graphics is Intel and is on the
  motherboard.  I'm using all three of the outputs provided by my
  Z97-Deluxe mobo.  I have had to disable blanking because otherwise I
  will definitely have at least one monitor no longer active when I wake
  up the system.  Getting it active again requires a number, at least 3,
  of attempts to "use this monitor" in the Display widget. plus un-
  mirroring and putting it back in its proper place.

  This also happens if I switch the monitors to using another input,
  which I wanted to do because I have two systems and I'd like to switch
  the monitors between them.  I'm having to use a workspace of ssh+tmux
  instances instead, which has some drawbacks of its own, but is at
  least workable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Oct 28 12:50:37 2016
  InstallationDate: Installed on 2016-08-08 (80 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1637219] Re: ubuntu-bug begins with a warning message

2016-10-28 Thread Kevin O'Gorman
*** This bug is a duplicate of bug 1637213 ***
https://bugs.launchpad.net/bugs/1637213

** This bug has been marked a duplicate of bug 1637213
   ubuntu-bug begins with a warning message

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

Title:
  ubuntu-bug begins with a warning message

Status in apport package in Ubuntu:
  New

Bug description:
  ubuntu-bug begins immediately with the following warning message,
  which I'm pretty sure just confuses most of us.  If this gets posted,
  then the message does not indicate a failure.

  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 27 07:01:16 2016
  InstallationDate: Installed on 2016-08-08 (79 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-10-28 Thread Alexander Chepurko
@peter-sevemark Yep, same exact problems with WICD means it's the
wireless driver/kernel. Probably why no one is looking at this bug
seriously.

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

Title:
  cannot view wifi networks after re-enabling wifi

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

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Touch-packages] [Bug 1544754] Re: implement the HTML5 pointer lock API

2016-10-28 Thread Chris Coulson
** Changed in: oxide
Milestone: branch-1.19 => branch-1.20

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

Title:
  implement the HTML5 pointer lock API

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The internet archive just released a collection of Win 3.1 games, using the 
DosBox emulator to run them on the website. On Chrome this triggers a 
"Allow/Deny archive.org to disable your mouse cursor" popup. Games are only 
playable using mouse or touch after accepting this.
  In the browser app/ Oxide there's no such popup and mouse input doesn't work.

  https://archive.org/details/win3_Mono3Dlx

  Another (more lightweight) example page: https://mdn.github.io
  /pointer-lock-demo/

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

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


[Touch-packages] [Bug 1636124] Re: openssl lacks support for TLSv1 and TLSv1.1

2016-10-28 Thread Jan Henke
I am already using the recommended settings from Mozilla (Intermediate
Compatibility), I am just trying to get it running with those, but with
those settings as posted above, no TLSv1 and TLSv1.1 are offered to
clients.

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

Title:
  openssl lacks support for TLSv1 and TLSv1.1

Status in openssl package in Ubuntu:
  New

Bug description:
  OpenSSL in xenial (16.04) apparently lacks ciphers for both TLSv1 and
  TLSv1.1. This is causing problems, as my wife's mobile phone with an
  older version of Android does not support TLSv1.2 and thus cannot
  connect to my server running on 16.04 (Apache with mod_ssl).

  Can you please rebuild OpenSSL with the secure ciphers from TLSv1 and
  TLSv1.1 enabled?

  For reference, this list should also include TLSv1 and TLSv1.1: 
  openssl ciphers -v | awk '{print $2}' | sort | uniq
  SSLv3
  TLSv1.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.5
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 24 10:27:58 2016
  InstallationDate: Installed on 2014-04-18 (919 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssl
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (86 days ago)
  modified.conffile..etc.ssl.openssl.cnf: [modified]
  mtime.conffile..etc.ssl.openssl.cnf: 2015-06-05T16:54:36.431443

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

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


[Touch-packages] [Bug 1610929] Re: Implement Screen::GetShellMode()

2016-10-28 Thread Chris Coulson
** Changed in: oxide
   Status: Triaged => Fix Released

** Changed in: oxide
Milestone: None => branch-1.20

** Changed in: oxide
 Assignee: (unassigned) => Santosh (santoshbit2007)

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

Title:
  Implement Screen::GetShellMode()

Status in Mir:
  New
Status in Oxide:
  Fix Released
Status in unity8 package in Ubuntu:
  New

Bug description:
  This is currently just a stub that returns NonWindowed on mobile
  devices and Windowed everywhere else. It needs to be more intelligent
  than that (eg, Windowed on a tablet device) and needs to be dynamic,
  but I don't think there's a way for us to do that yet.

  Basically, we need to know whether the shell is in windowed or staged
  mode. The display's form factor isn't particularly relevant.

  This is needed to complete bug 1545088 and others.

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

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


[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-10-28 Thread Peter S
I'm starting to doubt that network-manager is the root of all this mess.
Have any of you tried using WICD instead (an alternative network
manager)? I seem to have the same connectivity issues there. And just as
with network-manager, they appear at random.

Here's an instruction:
https://help.ubuntu.com/community/WICD

I still consider this a bug though, since all my other devices on the
same wifi network are working flawlessly. Couldn't it be some bad
implementation of the Intel Wifi driver within the kernel?

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

Title:
  cannot view wifi networks after re-enabling wifi

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

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Touch-packages] [Bug 1598584] Re: wifi slows to a crawl when bluetooth is enabled

2016-10-28 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

** Changed in: frieza
 Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)

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

Title:
  wifi slows to a crawl when bluetooth is enabled

Status in arale:
  New
Status in Canonical System Image:
  In Progress
Status in frieza:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  I am having serious wifi performance issues on my Aquaris M10 (running
  rc-proposed r133). When measuring the wifi speed, I get download
  speeds of less than 1/20 compared to my Pro 5 at the same distance
  from the wifi router. This seems to be consistent through reboots. I
  had similar wifi performance also before recently upgrading to rc-
  proposed, which I thought would have fixed the issue.

  I am in the same place testing 3 different ubuntu devices and these are the 
readings of the wifi download speed:
  Laptop: 4 MB/s
  Pro 5: 3.5 MB/s
  Aquaris M10: 0.16 MB/s

  However, upload speed is about the same on all three devices.

  Turning bluetooth off gets Aquaris M10 wifi speed back to sort of
  normal, 2.5-3.4 MB/s. Bluetooth on, again 0.1-0.2 MB/s. Seems the two
  wireless technologies interfere with each other on the M10, while the
  Pro 5 doesn't have that problem.

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

-- 
Mailing list: https://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 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

2016-10-28 Thread Ryan Harper
On Fri, Oct 28, 2016 at 1:02 PM, Martin Pitt 
wrote:

> > However, if there isn't a local seed, then we must search again *once*
> networking is up.
>
> Fair enough, but you can then of course not use that unit to configure
> the network.


Of course we can.  We need to cycle the network though.


> But this "if there isn't a local seed" isn't something you
> can express as a static condition, hence my thought that it might be
> better if c-i calls s-n-wait-online if and only if it's necessary. But
> YMMV.
>

Right, though it's not clear to me that we can express this in unit terms.
It may have to be done internally;  That is, it's possible that in
cloud-init "net"
mode we need to block ourselves, until networking is-up.


>
>
> > This works just fine with 'networking.service'
>
> This did/does not really work "fine" IMHO -- all of our cloud images
> hang for a long time at boot unless you give them a local data source or
> disable cloud-init.


This is by-design.  cloud-init is *interposing* itself on purpose.


> It also imposes the restriction that you must be
>
online during boot, which is fine for a cloud environment, but rather
> unfriendly for other scenarios.
>

No, you need provide a datasource, or indicate (via boot params) that
you're not
interested in cloud-init running.

It's certainly true that if someone just qemu-system-x86 -hda cloud.img
that it's going
to hang.  But folks are explicitly booting a *cloud* image without a cloud.

We handle this fine with uvt-kvm which provides a nocloud-net seed when
booting.


> > due to the "atomic" nature of ifup where once the oneshot service
> runs, we can assume that networking is up. However, networkd runs and
> asynchronously brings up networking; which is fine but we now no longer
> have a clear checkpoint at which cloud-init can run with networking up
> but before.
>
> Again -- s-n-wait-online.service is exactly the networkd counterpart of
> networking.service for ifupdown, that gives you the "network is fully
> configured" synchronization point. The issue is not that it doesn't
> exist, but that I think that it's not a good thing to depend on either
> one.
>

It is, but it's a separate unit "networking" == "networkd" +
"networkd-wait-online"
However, netplan generator only emits the "systemd-networkd" target wants,
so
if we use After=systemd-networkd-wait-online; that's never run since
nothing wants it.
If we add it explicitly, then it runs even when networkd doesn't


>
> > we really want something like
> >  After=networking|networkd-wait-online
> > which handles determining if networkd was supposed to run or not
>
> That already exists, it's network-online.target -- whatever "implements"
> it (ifupdown, networkd, NM) will hook itself into this target. Nothing
> more, nothing less, so if cloud-init just wants to wait until it's
> online, then just make it Requires/After=network-online.target instead
> of Before= it. (But again -- this is a very strong dependency which is
> very inconvenient anywhere but cloud environments with essentially one
> virtual ethernet card).
>

It may be that network-online.target is the right place.  Scott had some
reason
for not using that explicitly before;  I expect some details from him.

It's no more inconvenient than cloud-init has ever been for users not
providing
a data-source, or booting with cloud-init disabled.


>
> BTW, I'm not sure if it came across -- if you play around with this,
> please drop systemd-networkd.service's After=dbus.service; that will get
> rid of the worst dependency cycles, and it's something which we can do
> in Xenial rather easily (not so easy for devel, that's the part we need
> to discuss with upstream or decide if we care enough about this feature,
> but eventually I figure we want to get rid of it either way).
>

I did play with it, but the networkd in xenial blocks for some non-trivial
amount of time (10s of seconds)
if dbus.service is not up.


>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1636912
>
> Title:
>   systemd-networkd runs too late for cloud-init.service (net)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/systemd/+bug/1636912/+subscriptions
>

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  New
Status in cloud-init package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in cloud-init source package in Xenial:
  New
Status in systemd source package in Xenial:
  Triaged

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init 

[Touch-packages] [Bug 1633828] Re: Mounting /boot/efi fails always after updating to 16.10

2016-10-28 Thread Phillip Susi
So what happens when you don't comment it out?  What happens if you
manually try to mount it?


** Changed in: util-linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  Mounting /boot/efi fails always after updating to 16.10

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  System does not boot properly as mounting /boot/efi fails. Commented
  out /boot/efi entry in /etc/fstab to boot system normally. This
  started happening after update to 16.10. Everything was working fine
  in 15.10, 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: mount 2.28.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 16 15:23:19 2016
  InstallationDate: Installed on 2015-11-20 (330 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago)

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

-- 
Mailing list: https://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 1522316] Icons are too big

2016-10-28 Thread Mikemecanic
-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1522316

Title:
  Icons are too big

Status in Nautilus:
  Incomplete
Status in nautilus package in Ubuntu:
  Triaged
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  On xenial the icons in nautilus (also on the Desktop) are too big.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec  3 09:37:55 2015
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'type', 'date_modified']"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2015-04-30 (216 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nautilus
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

2016-10-28 Thread Martin Pitt
> However, if there isn't a local seed, then we must search again *once*
networking is up.

Fair enough, but you can then of course not use that unit to configure
the network. But this "if there isn't a local seed" isn't something you
can express as a static condition, hence my thought that it might be
better if c-i calls s-n-wait-online if and only if it's necessary. But
YMMV.


> This works just fine with 'networking.service'

This did/does not really work "fine" IMHO -- all of our cloud images
hang for a long time at boot unless you give them a local data source or
disable cloud-init. It also imposes the restriction that you must be
online during boot, which is fine for a cloud environment, but rather
unfriendly for other scenarios.

> due to the "atomic" nature of ifup where once the oneshot service
runs, we can assume that networking is up. However, networkd runs and
asynchronously brings up networking; which is fine but we now no longer
have a clear checkpoint at which cloud-init can run with networking up
but before.

Again -- s-n-wait-online.service is exactly the networkd counterpart of
networking.service for ifupdown, that gives you the "network is fully
configured" synchronization point. The issue is not that it doesn't
exist, but that I think that it's not a good thing to depend on either
one.

> we really want something like
>  After=networking|networkd-wait-online
> which handles determining if networkd was supposed to run or not

That already exists, it's network-online.target -- whatever "implements"
it (ifupdown, networkd, NM) will hook itself into this target. Nothing
more, nothing less, so if cloud-init just wants to wait until it's
online, then just make it Requires/After=network-online.target instead
of Before= it. (But again -- this is a very strong dependency which is
very inconvenient anywhere but cloud environments with essentially one
virtual ethernet card).

BTW, I'm not sure if it came across -- if you play around with this,
please drop systemd-networkd.service's After=dbus.service; that will get
rid of the worst dependency cycles, and it's something which we can do
in Xenial rather easily (not so easy for devel, that's the part we need
to discuss with upstream or decide if we care enough about this feature,
but eventually I figure we want to get rid of it either way).

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  New
Status in cloud-init package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in cloud-init source package in Xenial:
  New
Status in systemd source package in Xenial:
  Triaged

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  
  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
└─basic.target @11.403s
  └─sockets.target @11.401s
└─dbus.socket @11.398s
  

[Touch-packages] [Bug 1637536] Re: support setting non-supported modes (resolution)

2016-10-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  support setting non-supported modes (resolution)

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Reproduce:
  run mirout

  What happens:
  I only see one resolution supported.

  What should happen:
  I should see more resolutions, like I do on unity7.

  I guess, if in doubt, “support” the same ones as xrandr.

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

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


[Touch-packages] [Bug 1637598] Re: Screen corruption on docking station after upgrade to 16.10

2016-10-28 Thread Scott Howard
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (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/1637598

Title:
  Screen corruption on docking station after upgrade to 16.10

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  bottom and right side of external monitor is corrupted when Lenovo
  T450s laptop is connected to docking station.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct 28 13:04:20 2016
  DistUpgraded: 2016-10-27 12:22:52,228 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.4.0-45-generic, x86_64: installed
   acpi-call, 1.1.0, 4.8.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2015-12-25 (308 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20BWS0UH00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=58cf21bc-9d8e-415f-94e7-30888a2e8844 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-27 (0 days ago)
  dmi.bios.date: 07/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET61WW (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS0UH00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET61WW(1.25):bd07/13/2016:svnLENOVO:pn20BWS0UH00:pvrThinkPadT450s:rvnLENOVO:rn20BWS0UH00:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BWS0UH00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Fri Oct 28 11:12:48 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1637598/+subscriptions

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


[Touch-packages] [Bug 1637598] [NEW] Screen corruption on docking station after upgrade to 16.10

2016-10-28 Thread Scott Howard
Public bug reported:

bottom and right side of external monitor is corrupted when Lenovo T450s
laptop is connected to docking station.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Oct 28 13:04:20 2016
DistUpgraded: 2016-10-27 12:22:52,228 DEBUG icon theme changed, re-reading
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 1.1.0, 4.4.0-45-generic, x86_64: installed
 acpi-call, 1.1.0, 4.8.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
InstallationDate: Installed on 2015-12-25 (308 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20BWS0UH00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=58cf21bc-9d8e-415f-94e7-30888a2e8844 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to yakkety on 2016-10-27 (0 days ago)
dmi.bios.date: 07/13/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET61WW (1.25 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BWS0UH00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET61WW(1.25):bd07/13/2016:svnLENOVO:pn20BWS0UH00:pvrThinkPadT450s:rvnLENOVO:rn20BWS0UH00:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BWS0UH00
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Fri Oct 28 11:12:48 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6
xserver.video_driver: modeset

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "screen - bottom and right side is corrupted"
   
https://bugs.launchpad.net/bugs/1637598/+attachment/4768932/+files/screen_res_shaking.png

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

Title:
  Screen corruption on docking station after upgrade to 16.10

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  bottom and right side of external monitor is corrupted when Lenovo
  T450s laptop is connected to docking station.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct 28 13:04:20 2016
  DistUpgraded: 2016-10-27 12:22:52,228 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.4.0-45-generic, x86_64: installed
   acpi-call, 1.1.0, 4.8.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2015-12-25 (308 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20BWS0UH00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=58cf21bc-9d8e-415f-94e7-30888a2e8844 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded 

[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2016-10-28 Thread Andrea Lazzarotto (Lazza)
Indeed! And on Yakkety the situation is even worse. With the new VPN
menu the first VPN connection leaks DNS, the following connections do
not work until one changes the resolv.conf file to some static IP.

Compare this to running openvpn from the terminal (which works
perfectly) and you will see the problem is huge.

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Incomplete
Status in openvpn package in Ubuntu:
  Incomplete

Bug description:
  [Triage Notes]

  This bug can no longer make progress. Please see comment 50 for
  details and further instructions.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

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

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


[Touch-packages] [Bug 1637107] Re: Wrong audio profile (on a Skylake system), causing volume problems.

2016-10-28 Thread Mary Sherman
Thanks, I will try that.

For reference, audio via analog port works fine (it uses the correct
profile, `Analog Stereo Output`, which is the same which is
inappropriately used when plugging the digital cable).

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

Title:
  Wrong audio profile (on a Skylake system), causing volume problems.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a Skylake system (ASRock Z170 Gaming-ITX/ac) with (x)Ubuntu
  16.04.

  My speakers are connected via the SPDIF port, but there is a problem.

  When I inspect the audio profile (in `pavucontrol`), I see that `Analog 
Stereo Output (unplugged)` is selected.
  The speakers play regularly, even if this profile is wrong, but the volume 
doesn't work correctly - anything above mute will cause the speakers to play at 
maximum volume.

  If I choose the `Digital Stereo (IEC958)`, the speakers won't receive
  any signal at all.

  Debug info:

  ~$ lspci -vv # extract
  00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
Subsystem: ASRock Incorporation Sunrise Point-H HD Audio
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  
  ~$ dmesg | grep 00:1f.3
  [0.181004] pci :00:1f.3: [8086:a170] type 00 class 0x040300
  [0.181034] pci :00:1f.3: reg 0x10: [mem 0xdf14-0xdf143fff 
64bit]
  [0.181062] pci :00:1f.3: reg 0x20: [mem 0xdf12-0xdf12 
64bit]
  [0.181091] pci :00:1f.3: PME# supported from D3hot D3cold
  [0.181176] pci :00:1f.3: System wakeup disabled by ACPI
  [0.579846] iommu: Adding device :00:1f.3 to group 8
  [3.126041] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915_bpo])
  [4.185983] input: HDA Intel PCH Front Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input11
  [4.186034] input: HDA Intel PCH Rear Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input12
  [4.186081] input: HDA Intel PCH Line as 
/devices/pci:00/:00:1f.3/sound/card0/input13
  [4.186135] input: HDA Intel PCH Line Out as 
/devices/pci:00/:00:1f.3/sound/card0/input14
  [4.186188] input: HDA Intel PCH Front Headphone as 
/devices/pci:00/:00:1f.3/sound/card0/input15
  [4.186228] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input16
  [4.186267] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input17
  [4.186304] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input18

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   saverio3012 F...m pulseaudio
   /dev/snd/controlC0:  saverio3012 F pulseaudio
   /dev/snd/controlC1:  saverio3012 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Oct 27 10:21:31 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-11 (108 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Microsoft® LifeCam VX-2000 - Microsoft® LifeCam VX-2000
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.10
  dmi.board.name: Z170 Gaming-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.10:bd09/30/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1637556] Re: package libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1 failed to install/upgrade: package libavcodec-extra-54:amd64 is already installed and configured

2016-10-28 Thread dino99
*** This bug is a duplicate of bug 1635280 ***
https://bugs.launchpad.net/bugs/1635280

** This bug has been marked a duplicate of bug 1635280
   [ BUG 541595 IS BACK ] package is already installed and configured

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

Title:
  package libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1 failed to
  install/upgrade: package libavcodec-extra-54:amd64 is already
  installed and configured

Status in libav package in Ubuntu:
  New

Bug description:
  Tried to install EasyTag and pyRenamer

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-42.62~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  Date: Fri Oct 28 18:24:13 2016
  DuplicateSignature: 
package:libavcodec-extra-54:amd64:6:9.18-0ubuntu0.14.04.1:package 
libavcodec-extra-54:amd64 is already installed and configured
  ErrorMessage: package libavcodec-extra-54:amd64 is already installed and 
configured
  InstallationDate: Installed on 2016-09-09 (49 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: libav
  Title: package libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1 failed to 
install/upgrade: package libavcodec-extra-54:amd64 is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1637574] [NEW] popt feature request: poptStringFromArgv

2016-10-28 Thread Daniel U. Thibault
Public bug reported:

Feature request: the addition of a poptStringFromArgv that does the
opposite of poptParseArgvString: that is, turn a supplied argv, argc
pair into a canonically-equivalent string.

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


** Tags: featurerequest

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

Title:
  popt feature request: poptStringFromArgv

Status in popt package in Ubuntu:
  New

Bug description:
  Feature request: the addition of a poptStringFromArgv that does the
  opposite of poptParseArgvString: that is, turn a supplied argv, argc
  pair into a canonically-equivalent string.

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

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


[Touch-packages] [Bug 1637573] [NEW] popt man pages are incomplete and erroneous

2016-10-28 Thread Daniel U. Thibault
Public bug reported:

Error in popt man pages: the e-address e...@redhat.com is invalid
(probably has been for quite some time)

Omissions in popt man pages:

1) poptParseArgvString has an undocumented return int value. What does
it return and what does it mean?

2) poptGetArg recovers “leftover arguments” but its documentation fails
to make it clear that it should not be called until poptGetNextOpt has
returned -1.  I ran into this with an app that used popt but knew that
it had no options to check for: after generating the context with
poptGetContext, it tried to jump directly to poptGetArg, with disastrous
results.

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


** Tags: manpage

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

Title:
  popt man pages are incomplete and erroneous

Status in popt package in Ubuntu:
  New

Bug description:
  Error in popt man pages: the e-address e...@redhat.com is invalid
  (probably has been for quite some time)

  Omissions in popt man pages:

  1) poptParseArgvString has an undocumented return int value. What does
  it return and what does it mean?

  2) poptGetArg recovers “leftover arguments” but its documentation
  fails to make it clear that it should not be called until
  poptGetNextOpt has returned -1.  I ran into this with an app that used
  popt but knew that it had no options to check for: after generating
  the context with poptGetContext, it tried to jump directly to
  poptGetArg, with disastrous results.

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

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


[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2016-10-28 Thread Vincent Gerris
@https://launchpad.net/~cyphermox Mathieu, why are you marking this as 
Incomplete?
Can you be specific in what kind of information you need to consider it 
complete, instead of pointing people to a DNS admin, who may not be interested 
in filing a bug?

Some people clearly described how the behaviour changed from 14.04 and I can 
confirm this.
The current setup is nowhere near a working solution that a normal user that 
gets VPN connection info can work with.
That hurts business users and pisses developers and users off that even want to 
make an attempt to make it work.

The net is flooded with issues regarding VPN and DNS, it would be great if you 
can point us to the right steps and information to supply to actually get this 
working like say the cisco AnyConnect secure mobility client.
With the exact same VPN server, I can use that tool on Mac OS X without ANY 
configuration and it "Just works".

I would say the goal is to have it working like that for everybody using 
network manager.
Let's talk defaults, settings and requirements and I'll try to get the server 
info or anything else that is needed.

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Incomplete
Status in openvpn package in Ubuntu:
  Incomplete

Bug description:
  [Triage Notes]

  This bug can no longer make progress. Please see comment 50 for
  details and further instructions.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

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

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


[Touch-packages] [Bug 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks

2016-10-28 Thread Alberto Salvia Novella
** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

Title:
  network-manager after suspend showing arrow icon instead of wifi icon
  and showing no wifi networks

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401
  I'm creating my own bug report.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy network-manager
  network-manager:
Installiert:   1.2.2-0ubuntu0.16.04.3
Installationskandidat: 1.2.2-0ubuntu0.16.04.3
Versionstabelle:
   *** 1.2.2-0ubuntu0.16.04.3 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) What you expected to happen
  I'm connected by WiFi only, not by a wired connection. I expect to see the 
WiFi icon anytime while being connected to my WiFi network. Also, I expect to 
see all the WiFi networks around me (at least one other network with good 
reception and about 3 with bad reception).

  4) What happened instead
  After waking up the laptop from suspend, there appears the ethernet icon 
(arrow symbols) instead of the WiFi icon.
  Also, in this state there are no other WiFi networks visible in the 
network-manager.
  However, the laptop is still connected with my WiFi and the connection works 
as usual.
  Using "service network-manager restart" in the console I can get the wireless 
icon back and all the other networks around me are visible again.
  This can be reproduced anytime and with 100% "success rate". The problem 
appeared with Ubuntu 16.10 and was persistent since.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 24 20:06:09 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-15 (161 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlo1  proto static  metric 600 
   169.254.0.0/16 dev wlo1  scope link  metric 1000 
   192.168.1.0/24 dev wlo1  proto kernel  scope link  src 192.168.1.244  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlo1wifi  connected/org/freedesktop/NetworkManager/Devices/2  
WiNet 2 162de978-4466-46b0-957b-5f9c141d702a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eno1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1629611] Re: dns server priority broken

2016-10-28 Thread Alberto Salvia Novella
** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

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

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


[Touch-packages] [Bug 1632275] Re: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()

2016-10-28 Thread Launchpad Bug Tracker
** Branch linked: lp:~pete-woods/indicator-network/testing-improvements

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

Title:
  indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()

Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Live session on i386 has an issue immediately which reports that
  network-manager indicator crashed

  On the installed version it is impossible to connect to the net via
  wifi

  Will check on amd64 but as far as I can tell it is fine there.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: indicator-network 0.8.0+16.10.20160930.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  CasperVersion: 1.379
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Oct 11 10:17:39 2016
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
  ExecutableTimestamp: 1475255305
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha i386 (20161008)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
  ProcCwd: /home/ubuntu
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb779ceba :   mov0x4(%eax),%ebx
   PC (0xb779ceba) ok
   source "0x4(%eax)" (0x03eb) not located in a known VMA region (needed 
readable region)!
   destination "%ebx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-network
  Stacktrace:
   #0  do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfacd72b, ref=0x0, 
result=0x644, scope=0x3e7, i=3807944636, version=0xb779d529 , 
flags=5, skip=0x1, type_class=-1226258504, undef_map=0xd62) at dl-lookup.c:361
   n = 
   list = 
   #1  0x in ?? ()
   No symbol table info available.
  StacktraceTop:
   do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfacd72b, ref=0x0, 
result=0x644, scope=0x3e7, i=3807944636, version=0xb779d529 , 
flags=5, skip=0x1, type_class=-1226258504, undef_map=0xd62) at dl-lookup.c:361
   ?? ()
  Title: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.indicator-network.log: indicator-network stop/pre-start, process 5765

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

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


[Touch-packages] [Bug 1637556] [NEW] package libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1 failed to install/upgrade: package libavcodec-extra-54:amd64 is already installed and configured

2016-10-28 Thread Pascal CHOUCHEN
Public bug reported:

Tried to install EasyTag and pyRenamer

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 4.4.0-42.62~14.04.1-generic 4.4.21
Uname: Linux 4.4.0-42-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
AptdaemonVersion: 1.1.1-1ubuntu5.2
Architecture: amd64
Date: Fri Oct 28 18:24:13 2016
DuplicateSignature: 
package:libavcodec-extra-54:amd64:6:9.18-0ubuntu0.14.04.1:package 
libavcodec-extra-54:amd64 is already installed and configured
ErrorMessage: package libavcodec-extra-54:amd64 is already installed and 
configured
InstallationDate: Installed on 2016-09-09 (49 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: libav
Title: package libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1 failed to 
install/upgrade: package libavcodec-extra-54:amd64 is already installed and 
configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package need-duplicate-check trusty

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

Title:
  package libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1 failed to
  install/upgrade: package libavcodec-extra-54:amd64 is already
  installed and configured

Status in libav package in Ubuntu:
  New

Bug description:
  Tried to install EasyTag and pyRenamer

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-42.62~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  Date: Fri Oct 28 18:24:13 2016
  DuplicateSignature: 
package:libavcodec-extra-54:amd64:6:9.18-0ubuntu0.14.04.1:package 
libavcodec-extra-54:amd64 is already installed and configured
  ErrorMessage: package libavcodec-extra-54:amd64 is already installed and 
configured
  InstallationDate: Installed on 2016-09-09 (49 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: libav
  Title: package libavcodec-extra-54:amd64 6:9.18-0ubuntu0.14.04.1 failed to 
install/upgrade: package libavcodec-extra-54:amd64 is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1636827] Re: wireless network list disappears

2016-10-28 Thread Christopher M. Penalver
Juraj, thank you for reporting this and helping make Ubuntu better. To
better understand:

1) Did this problem not occur in a Ubuntu release prior to 16.04?
2) When precisely does the wireless network list disappear (i.e. after doing 
what, is it consistently reproducible, etc.)?
3) Is this reproducible via http://cdimage.ubuntu.com/daily-live/current/ ?

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

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  wireless network list disappears

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  On Thinkpad W520, wireless network list disappears occasionally.
  Restarting the network manager service fixes the issue. Please see the
  following bug for more information:

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 26 13:57:59 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-12 (105 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp0s25  ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  
LARICS  3ad4f968-8fd1-4759-a3bc-746cb364628e  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   wlp3s0   wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
FERwlan 3f100dda-2c1b-46d6-83af-064c33b51c5a  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1489489] Re: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated

2016-10-28 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-system-settings-online-accounts
- 0.7+16.10.20161006.2-0ubuntu1

---
ubuntu-system-settings-online-accounts (0.7+16.10.20161006.2-0ubuntu1) yakkety; 
urgency=medium

  * Use GetConnectionCredentials() method instead of the deprecated
apparmor-specific method. (LP: #1489489)
  * Re-enable tests for powerpc, disable arm64

 -- Alberto Mardegan   Thu, 06 Oct 2016
09:59:28 +

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method
  is deprecated

Status in Ubuntu Online Accounts API:
  Confirmed
Status in apparmor package in Ubuntu:
  In Progress
Status in content-hub package in Ubuntu:
  Confirmed
Status in dbus package in Ubuntu:
  Triaged
Status in media-hub package in Ubuntu:
  Confirmed
Status in mediascanner2 package in Ubuntu:
  Fix Released
Status in signon-apparmor-extension package in Ubuntu:
  Fix Released
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  When upstream D-Bus merged the AppArmor mediation patches, they did
  not like the GetConnectionAppArmorSecurityContext() bus method.
  Instead, they decided to expose a peer's AppArmor context using the
  org.freedesktop.DBus.GetConnectionCredentials() bus method. All users
  of the GetConnectionAppArmorSecurityContext() method should switch to
  the GetConnectionCredentials() method as soon as possible so that
  Ubuntu can drop the patch that implements
  GetConnectionAppArmorSecurityContext() by the time 16.04 LTS is
  released.

  In order to switch to the new method, you'll need to depend on
  libapparmor 2.10 or newer.

  I'll be adding example code that illustrates how to switch from
  GetConnectionAppArmorSecurityContext() to GetConnectionCredentials().

  content-hub, media-hub, mediascanner2, signon-apparmor-extension,
  ubuntu-download-manager, and ubuntu-system-settings-online-accounts
  all need to transition to the new method of obtaining the AppArmor
  label.

  The apparmor package should be updated to drop the libapparmor-
  mention-dbus-method-in-getcon-man.patch patch and the dbus package
  should be updated to drop the aa-get-connection-apparmor-security-
  context.patch patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/online-accounts-api/+bug/1489489/+subscriptions

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


[Touch-packages] [Bug 1338180] Re: [Browser] iframe doesn't display anything when a load fails

2016-10-28 Thread Chris Coulson
So, the fix for this is that the error page will be implemented in HTML
and live in the new UbuntuWebView implementation inside Oxide.

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

Title:
  [Browser] iframe doesn't display anything when a load fails

Status in Oxide:
  Triaged
Status in Ubuntu UX:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Ex : http://jsfiddle.net/zHR89/

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

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


[Touch-packages] [Bug 1637536] Re: support setting non-supported modes (resolution)

2016-10-28 Thread kevin gunn
** Changed in: mir
   Importance: Undecided => High

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Chris Halse Rogers (raof)

** Changed in: mir
 Assignee: (unassigned) => Chris Halse Rogers (raof)

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Stephen M. Webb (bregma)

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

Title:
  support setting non-supported modes (resolution)

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  Reproduce:
  run mirout

  What happens:
  I only see one resolution supported.

  What should happen:
  I should see more resolutions, like I do on unity7.

  I guess, if in doubt, “support” the same ones as xrandr.

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

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


[Touch-packages] [Bug 1585723] Re: UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

2016-10-28 Thread Emanuele Antonio Faraone
And now is it landed?

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

Title:
  UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

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

Bug description:
  I'm digging into unity8 performance problems on older generation Intel
  GPUs - specifically i915 Atom GPUs.

  I've tested a simple QML file with a single empty UbuntuShape in it:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Rectangle {
  width: 400
  height: 300
  color: "blue"

  UbuntuShape {}
  }

  Running it with INTEL_DEBUG=perf env var set, I get this output:

  i915_program_error: Exceeded max ALU instructions (76 out of 64)
  ENTER FALLBACK 1: Program
  Mapping a busy BO, causing a stall on the GPU.

  which implies that MESA was unable to compile one of the UbuntuShape
  shaders as it created more ALU instructions than the GPU could deal
  with. MESA falls back to CPU rendering as a result.

  The GPU stall message I guess is related to that.

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

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


[Touch-packages] [Bug 1543467] Re: Unity8 can't correctly display multi-surface apps (i.e. menus and tooltips)

2016-10-28 Thread Emanuele Antonio Faraone
Any news?

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

Title:
  Unity8 can't correctly display multi-surface apps (i.e. menus and
  tooltips)

Status in Canonical System Image:
  Triaged
Status in QtMir:
  Triaged
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Unity8 can't display multi-surface apps (including menus and
  tooltips).

  Fixing bug 1497085 was a great start. However instead of crashing
  Unity8 now just shows the most recently created window by the app in
  the apps /single window/, and stretches it too. When such a secondary
  window like a menu or tooltip closes, you never get back to the
  original app window. So existing apps still aren't quite usable yet.

  Test case:
  sudo apt-get install mir-demos
  mir_demo_client_multiwin -- --desktop_file_hint=unity8

  Expected: Three windows (red, green, blue)
  Observed: Only the blue window

  You can also experience the same bug with lots of apps via:  Xmir
  -rootless under Unity8.

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

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


[Touch-packages] [Bug 1595963] Re: vt1-6 getting stuck or blank

2016-10-28 Thread Phillip Susi
When the tty goes blank though, can you still switch to the KDE desktop,
and back to the tty?  And is it still blank if and when you do?

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

Title:
  vt1-6 getting stuck or blank

Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  It's happening from time to time that my vt1-6 are getting stuck
  (showing tty1 and no input) or blank (just black) completely.

  Restarting system-getty.slice or console-getty.slice doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 24 10:00:54 2016
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS 12-9Q33
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: systemd 229-4ubuntu6
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic.efi.signed 
root=ZFS=/root ro root=ZFS=username-laptop/root quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1637536] Re: support setting non-supported modes (resolution)

2016-10-28 Thread Bill Filler
this is needed for system-settings, user expects to be able to change
resolutions as they did in unity7

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

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

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

Title:
  support setting non-supported modes (resolution)

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

Bug description:
  Reproduce:
  run mirout

  What happens:
  I only see one resolution supported.

  What should happen:
  I should see more resolutions, like I do on unity7.

  I guess, if in doubt, “support” the same ones as xrandr.

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

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


[Touch-packages] [Bug 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''

2016-10-28 Thread Phillip Susi
** Tags added: regression-release

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

Title:
  yakkety desktop - non-english installation crashes with
  /plugininstall.py: ValueError: invalid literal for int() with base 10:
  ''

Status in apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
  /daily-live/current/

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Preconditions: W10+Xenial xerus installed, internet connection, 3rd
  party sw and updates selected

  Steps to reproduce:

  1º Click something else on Installation type screen>select /dev/sdaX where 
Xenial is installed, use it to mount / and leave some space to create the /home 
partition(ext4)
  2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
  3º Installation starts

  Current result: After a little time installing it crashes and a window
  shows up to let the user know that some info is being gathered to send
  it to developers, and finally firefox opens on the bug report web on
  ubiquity package

  Expected result: No crashes during installation

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubiquity 16.10.5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Aug  8 15:50:56 2016
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
  ProcEnviron:
   LANGUAGE=es_ES.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1091783] Re: Confusing log message "init: failsafe main process (...) killed by TERM signal"

2016-10-28 Thread robotarmy
Yep, same as Erik

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

Title:
  Confusing log message "init: failsafe main process (...) killed by
  TERM signal"

Status in upstart package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 13.04 dev with upstart 1.6.1-1ubuntu1. On booting my
  system I'm seeing in /var/log/kern.log the line "Dec 18 18:17:46
  ubuntu kernel: <12>[   19.939989] init: failsafe main process (1033)
  killed by TERM signal".

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

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


[Touch-packages] [Bug 1562269] Re: On Ubuntu touch start bluetooth / stop bluetooth hangs

2016-10-28 Thread Jesse
+1 Anyone find a workaround?

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

Title:
  On Ubuntu touch start bluetooth / stop bluetooth hangs

Status in bluez package in Ubuntu:
  New

Bug description:
  When trying to start or stop the bluetooth subsystem, the start or
  stop command just hangs.

  A couple of upgrades back, we already *had* a similar situation, now
  it re-appeared.

  However, when Control-C'ing the start command, and then trying it
  again, it says "start: Job is already running: bluetooth"

  Likewise, when Control-C'ing the stop command and then trying it
  again, it says:  "stop: Job has already been stopped: bluetooth"

  
  root@alains-pocket-penguin:~# lsb_release -rd
  Description:Ubuntu 15.04
  Release:15.04
  root@alains-pocket-penguin:~# apt-cache policy bluez
  bluez:
Installed: 5.37-0ubuntu5~overlay1
Candidate: 5.37-0ubuntu5~overlay1
Version table:
   *** 5.37-0ubuntu5~overlay1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/emergency-snapshot/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   4.101-0ubuntu25 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

  What I expected to happen
   start bluetooth should start the bluetooth subsystem, and then return as 
quickly as possible
   stop bluetooth should stop the bluetooth subsystem, and then return as 
quickly as possible

  What happened instead
start bluetooth hangs... and after control-C'ing it, status bluetooth is 
"bluetooth start/starting"
stop bluetooth hangs... and after control-C'ing it, status bluetooth is 
"bluetooth stop/starting"

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

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


[Touch-packages] [Bug 1583795] Re: Indicator does not lead to setting when settings are docked in side stage

2016-10-28 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Triaged => Fix Committed

** Changed in: canonical-devices-system-image
Milestone: backlog => x1

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

Title:
  Indicator does not lead to setting when settings are docked in side
  stage

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

Bug description:
  If the M10 tablet is in tablet mode and the settings app is docked in side 
stage.
  The settings app is in background. So it is not active.
  I touch the buttery settings indicator.

  What i expect:
  1. The indicator section is closed
  2. The settings app opens in the side and shows the battery part of the 
settings app.

  What happens:
  1. The indicator section stays opened
  2. If i close the indicator section, the settings app stays in the background.
  3. If i take the settings app into the foreground( by swipping from the right 
edge to the left endge and touch onto the settings app, the empty side stage is 
shown for a short time and them the settings app appears in the side stage.

  Ubuntu version on the device: r109

  If you dismiss the indicator and touch the dash, the correct settings
  page immediately displays.

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

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


[Touch-packages] [Bug 1590801] Re: Selecting app icon does not show running app in side stage

2016-10-28 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Triaged => Fix Committed

** Changed in: canonical-devices-system-image
Milestone: backlog => x1

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

Title:
  Selecting app icon does not show running app in side stage

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

Bug description:
  Run an app like settings, put in side stage, hide the app

  There are two cases:

  Select the icon from the launcher
  Nothing happens

  Select the icon from the dash
  Firs time nothing happens
  Select it again
  The app appears in the side stage

  rc-proposed M10

  I expect bug #1583795 s related

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

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


[Touch-packages] [Bug 1637523] [NEW] App from side stage loses focus when switching to desktop mode

2016-10-28 Thread Michal Predotka
Public bug reported:

bq M10 rc-proposed r220

Steps to reproduce:
1. Open an app
2. Move it to the side stage
3. Switch to desktop mode

Expected result:
The app stays focused, on top of scopes

What happens instead:
The app is under scopes. Scopes are focused.

** Affects: unity8 (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/1637523

Title:
  App from side stage loses focus when switching to desktop mode

Status in unity8 package in Ubuntu:
  New

Bug description:
  bq M10 rc-proposed r220

  Steps to reproduce:
  1. Open an app
  2. Move it to the side stage
  3. Switch to desktop mode

  Expected result:
  The app stays focused, on top of scopes

  What happens instead:
  The app is under scopes. Scopes are focused.

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

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


[Touch-packages] [Bug 1363482] Re: ubuntu-keyring includes 1024D keys

2016-10-28 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-keyring - 2016.10.27

---
ubuntu-keyring (2016.10.27) zesty; urgency=medium

  * Drop 1024D key fragments. LP: #1363482
  * Remove 1024D keys from ubuntu-archive-keyring.
  * Add 1024D keys to ubuntu-archive-removed-keys.gpg.
  * Remove the md5sums.asc file, no longer valid.
  * Regenerate SHA512SUMS.txt.asc file.

 -- Dimitri John Ledkov   Thu, 27 Oct 2016 15:31:35
+0100

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

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

Title:
  ubuntu-keyring includes 1024D keys

Status in Ubuntu CD Images:
  Fix Released
Status in ubuntu-keyring package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-keyring as shipped in trusty contains old 1024D keys dating
  back to 2004 which are still being trusted for the main archive:

   % gpg /usr/share/keyrings/ubuntu-archive-keyring.gpg | grep 1024D
  pub  1024D/437D05B5 2004-09-12 Ubuntu Archive Automatic Signing Key 

  pub  1024D/FBB75451 2004-12-30 Ubuntu CD Image Automatic Signing Key 


  Given that newer 4096R keys are present and have been in precise
  (through -updates) and trusty, it seems to be about time to drop the
  older keys. (In the hope that apt does not chose on signatures it
  cannot verify, otherwise the publisher would need to stop signing with
  the old key as well.)

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

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


[Touch-packages] [Bug 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''

2016-10-28 Thread Phillip Susi
** Changed in: apt (Ubuntu Xenial)
   Importance: Undecided => Critical

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

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

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

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

Title:
  yakkety desktop - non-english installation crashes with
  /plugininstall.py: ValueError: invalid literal for int() with base 10:
  ''

Status in apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
  /daily-live/current/

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Preconditions: W10+Xenial xerus installed, internet connection, 3rd
  party sw and updates selected

  Steps to reproduce:

  1º Click something else on Installation type screen>select /dev/sdaX where 
Xenial is installed, use it to mount / and leave some space to create the /home 
partition(ext4)
  2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
  3º Installation starts

  Current result: After a little time installing it crashes and a window
  shows up to let the user know that some info is being gathered to send
  it to developers, and finally firefox opens on the bug report web on
  ubiquity package

  Expected result: No crashes during installation

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubiquity 16.10.5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Aug  8 15:50:56 2016
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
  ProcEnviron:
   LANGUAGE=es_ES.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1637518] [NEW] Phone doesn't ring (rings only for a second and stays silent)

2016-10-28 Thread GTriderXC
Public bug reported:

Since a few days, my phone doesn't ring on incoming call. A moment ago I
received a phone call: my phone rang for a second and the sound turned
off by itself. I could answer the call and it vibrated.

Reported for:

Bq E4.5 on OTA13

--
system-image-cli -i

current built number:35
krillin
channel: ubuntu-touch/stable/bq-aquaris.en
last update: 20.09.2016
version version 35
version ubuntu 20160913
tag:OTA-13
version device: 20160606-ab415b2
version custom: 20160831-991-38-18

Media hub log:

http://paste.ubuntu.com/23392737/

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

** Description changed:

  Since a few days, my phone doesn't ring on incoming call. A moment ago I
  received a phone call: my phone rang for a second and the sound turned
- off by itself. I could answer the call and it kept on ringing.
+ off by itself. I could answer the call and it vibrated.
  
  Reported for:
  
  Bq E4.5 on OTA13
  
  --
  system-image-cli -i
  
  current built number:35
  krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 20.09.2016
  version version 35
  version ubuntu 20160913
  tag:OTA-13
  version device: 20160606-ab415b2
  version custom: 20160831-991-38-18
  
  Media hub log:
  
  http://paste.ubuntu.com/23392737/

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

Title:
  Phone doesn't ring (rings only for a second and stays silent)

Status in dialer-app package in Ubuntu:
  New

Bug description:
  Since a few days, my phone doesn't ring on incoming call. A moment ago
  I received a phone call: my phone rang for a second and the sound
  turned off by itself. I could answer the call and it vibrated.

  Reported for:

  Bq E4.5 on OTA13

  --
  system-image-cli -i

  current built number:35
  krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 20.09.2016
  version version 35
  version ubuntu 20160913
  tag:OTA-13
  version device: 20160606-ab415b2
  version custom: 20160831-991-38-18

  Media hub log:

  http://paste.ubuntu.com/23392737/

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

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


[Touch-packages] [Bug 1637476] Re: gallery does not refresh

2016-10-28 Thread Pat McGowan
The app is monitoring the folders in the file system and no action
should be required from the user. For some reason a file saved in this
way is not detected although the log indicates the app detected some
activity. Try to reproduce on a desktop session.

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

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

Title:
  gallery does not refresh

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

Bug description:
  There seems to be no way to refresh the pictures in gallery.

  Reproduction:
  - open gallery
  - switch to Photos view
  => you see your pictures, say you have five
  - open gimp 
  - open one of the five pictures
  - edit it (or not)
  - export as -> save as sixth picture
  - switch back to gallery
  => you still see five pictures
  - swipe down
  => nothing happens, no refresh, you still see five pictures
  - look through the menu items 
  => no way to refresh
  - close gallery, by swiping from right, then swipe gallery down
  - open gallery again
  => you see six pictures

  Not very convenient or intuitive.

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

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


[Touch-packages] [Bug 1636473] Re: random cursor jumps when clicking on dell xps 13

2016-10-28 Thread Christopher M. Penalver
s.illes79, thank you for reporting this and helping make Ubuntu better.
To better understand:

1) Did this issue not occur in a Ubuntu release prior to 16.04?
2) Is this reproducible with the latest release of Ubuntu via 
http://cdimage.ubuntu.com/daily-live/current/ ?
3) Could you please clarify what you mean by 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1636473/comments/2 ? Did 
you try anything in that article and found improvement?

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

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

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

Title:
  random cursor jumps when clicking on dell xps 13

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  1 out of 20-40 clicks on the touch pad results in a pointer jump and a
  "random" click.

  Hard to reproduce, but mostly happens when I use my middle finger to
  move the cursor and click with index finger. Sometimes the double
  touch of middle/index finger is interpreted as mouse move, the jump is
  more or less the same distance as if i had moved the index to the
  middle finger position.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.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: Tue Oct 25 22:04:10 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0704]
  InstallationDate: Installed on 2016-09-08 (46 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=fe8099eb-a258-42d6-8f67-69496f1e0fcf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Oct 22 20:20:44 2016
  xserver.configfile: default
  xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193 
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.1

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

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


[Touch-packages] [Bug 1636473] Re: random cursor jumps when clicking on dell xps 13

2016-10-28 Thread Christopher M. Penalver
** Tags added: latest-bios-1.4.4 needs-upstream-testing

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

Title:
  random cursor jumps when clicking on dell xps 13

Status in xorg package in Ubuntu:
  New

Bug description:
  1 out of 20-40 clicks on the touch pad results in a pointer jump and a
  "random" click.

  Hard to reproduce, but mostly happens when I use my middle finger to
  move the cursor and click with index finger. Sometimes the double
  touch of middle/index finger is interpreted as mouse move, the jump is
  more or less the same distance as if i had moved the index to the
  middle finger position.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.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: Tue Oct 25 22:04:10 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0704]
  InstallationDate: Installed on 2016-09-08 (46 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=fe8099eb-a258-42d6-8f67-69496f1e0fcf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Oct 22 20:20:44 2016
  xserver.configfile: default
  xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193 
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.1

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

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


[Touch-packages] [Bug 1637502] [NEW] Keyboard stays on screen when doing spread

2016-10-28 Thread Michal Predotka
Public bug reported:

bq M10 rc-proposed r220

If the OSK is visible and I'm starting to do swipe from the right, I
expect OSK to hide. Meanwhile the OSK hides only when the spread is
complete and I take my finger off the screen.

** Affects: unity8 (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/1637502

Title:
  Keyboard stays on screen when doing spread

Status in unity8 package in Ubuntu:
  New

Bug description:
  bq M10 rc-proposed r220

  If the OSK is visible and I'm starting to do swipe from the right, I
  expect OSK to hide. Meanwhile the OSK hides only when the spread is
  complete and I take my finger off the screen.

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

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


[Touch-packages] [Bug 1590801] Re: Selecting app icon does not show running app in side stage

2016-10-28 Thread Michal Predotka
Looks like this is fixed in r219

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

Title:
  Selecting app icon does not show running app in side stage

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Run an app like settings, put in side stage, hide the app

  There are two cases:

  Select the icon from the launcher
  Nothing happens

  Select the icon from the dash
  Firs time nothing happens
  Select it again
  The app appears in the side stage

  rc-proposed M10

  I expect bug #1583795 s related

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

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


[Touch-packages] [Bug 1583795] Re: Indicator does not lead to setting when settings are docked in side stage

2016-10-28 Thread Michal Predotka
Looks like this is fixed in r219

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

Title:
  Indicator does not lead to setting when settings are docked in side
  stage

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  If the M10 tablet is in tablet mode and the settings app is docked in side 
stage.
  The settings app is in background. So it is not active.
  I touch the buttery settings indicator.

  What i expect:
  1. The indicator section is closed
  2. The settings app opens in the side and shows the battery part of the 
settings app.

  What happens:
  1. The indicator section stays opened
  2. If i close the indicator section, the settings app stays in the background.
  3. If i take the settings app into the foreground( by swipping from the right 
edge to the left endge and touch onto the settings app, the empty side stage is 
shown for a short time and them the settings app appears in the side stage.

  Ubuntu version on the device: r109

  If you dismiss the indicator and touch the dash, the correct settings
  page immediately displays.

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

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


[Touch-packages] [Bug 1587333] Re: When spread open, launched apps are in background

2016-10-28 Thread Michal Predotka
Looks like it's fixed in r219.

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

Title:
  When spread open, launched apps are in background

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  If you have the spread open and then launch a new application from the
  launcher, that new app is behind the most recently used app before
  this one. It should be in front as it was most recently launched.

  Steps to reproduce:-

  On a bq m10 running latest rc-proposed

  1. Open a few apps
  2. Swipe in from right to open the spread
  3. Short swipe in from left to open launcher
  4. Launch another app

  Expected behaviour:-

  App selected in step 4 is launched, spread closes, and that app comes
  to the front

  Actual behaviour:-

  App which was previously at the front is brought to front and newly
  launched app is behind it.

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

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


[Touch-packages] [Bug 1637476] Re: gallery does not refresh

2016-10-28 Thread dinamic
** Also affects: gallery-app (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
  gallery does not refresh

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in gallery-app package in Ubuntu:
  New

Bug description:
  There seems to be no way to refresh the pictures in gallery.

  Reproduction:
  - open gallery
  - switch to Photos view
  => you see your pictures, say you have five
  - open gimp 
  - open one of the five pictures
  - edit it (or not)
  - export as -> save as sixth picture
  - switch back to gallery
  => you still see five pictures
  - swipe down
  => nothing happens, no refresh, you still see five pictures
  - look through the menu items 
  => no way to refresh
  - close gallery, by swiping from right, then swipe gallery down
  - open gallery again
  => you see six pictures

  Not very convenient or intuitive.

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

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


[Touch-packages] [Bug 1637478] [NEW] Launcher: quicklists should not have a divider between each entry.

2016-10-28 Thread Andrea Azzarone
Public bug reported:

Do not show a divider between each ql entry but just between each
section, similar to what unity7 does.

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

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

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

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

** Branch linked: lp:~azzar1/unity-api/launcher-quicklist-add-
hasSeparator

** Branch linked: lp:~azzar1/unity8/fix-quicklist-separators

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

Title:
  Launcher: quicklists should not have a divider between each entry.

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Do not show a divider between each ql entry but just between each
  section, similar to what unity7 does.

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

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


[Touch-packages] [Bug 1637459] [NEW] Launching browser on external monitor causes mobile ua-overrides to be loaded

2016-10-28 Thread Andrew Hayzen
Public bug reported:

Setup:
I have a laptop that is plugged into an external monitor via HDMI

What happened:
1) Open a terminal, move it to the laptop screen and launch the webbrowser-app
2) Notice in the console that it loads the desktop UA overrides
3) Close the webbrowser-app and move the terminal to the external monitor
4) Launch the webbrowser-app in the terminal on the external monitor
5) Notice in the console that it loads the mobile UA overrides

What I expected to happen:
For my screen size to be detected correctly, even if it is an external monitor, 
and then load the correct UA overrides (at step 5 I expected desktop UA 
overrides).

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

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

Title:
  Launching browser on external monitor causes mobile ua-overrides to be
  loaded

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Setup:
  I have a laptop that is plugged into an external monitor via HDMI

  What happened:
  1) Open a terminal, move it to the laptop screen and launch the webbrowser-app
  2) Notice in the console that it loads the desktop UA overrides
  3) Close the webbrowser-app and move the terminal to the external monitor
  4) Launch the webbrowser-app in the terminal on the external monitor
  5) Notice in the console that it loads the mobile UA overrides

  What I expected to happen:
  For my screen size to be detected correctly, even if it is an external 
monitor, and then load the correct UA overrides (at step 5 I expected desktop 
UA overrides).

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

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


[Touch-packages] [Bug 784500] Re: ALC269VB on Asus EeePC 1015PN, No sound from speakers, but sound from headphones

2016-10-28 Thread Mossroy
It's probably be the same problem I had on 1015PX : see the workaround I
posted on http://askubuntu.com/questions/649411/internal-speaker-not-
working-in-netbook/842760#842760

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

Title:
  ALC269VB on Asus EeePC 1015PN, No sound from speakers, but sound from
  headphones

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound from speakers has stopped working on Asus EeePC 1015PN , but
  sound from headphones still works. Sound worked fine during initial
  install, but has stopped working. It may be related to a BIOS update
  (possible BIOS mis-reporting pins or jacks or driver not getting
  information correctly?)  Unfortunately, BIOS cannot be downgraded to
  confirm -- all ASUS BIOS software refuses to flash to older BIOS (no
  force option).

  Currently using 11.04 with all updates installed, but problem appears to 
exist in 10.10 as well
  alsa-base version is 1.0.24+dfsg-0ubuntu1

  These are the troubleshooting steps I've tried with no effect:
  - check levels in alsamixer (all at 100% except mic boost, shows in 
alsa-info as 100% as well)
  - booting from LiveUSB, problem is there, too (did not used to be)
  - booting from 10.10 LiveUSB, problem is there, too (did not used to be)
  - installed linux-alsa-driver-modules-2.6.38-8-generic
  - sudo modprobe snd-hda-intel
  - adding "options snd-hda-intel model=asus" to alsa-base.conf
  Internal microphone works
  Speakers work in Windows

  lspci shows both audio cards correctly (the Intel one is what stopped 
working):
  00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition 
Audio Controller (rev 02)
  04:00.1 Audio device: nVidia Corporation High Definition Audio Controller 
(rev a1)

  alsa-info available here: http://www.alsa-
  project.org/db/?f=c4f073addd57b038a54f5c16e9dab24b3c551c5e

  Output of aplay -l:
   List of PLAYBACK Hardware Devices 
  card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: NVidia [HDA NVidia], device 7: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: NVidia [HDA NVidia], device 8: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: NVidia [HDA NVidia], device 9: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: alsa-base 1.0.24+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion:
   Advanced Linux Sound Architecture Driver Version 1.0.24.
   Compiled on May  5 2011 for kernel 2.6.38-8-generic (SMP).
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bsj1628 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf5efc000 irq 44'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,1043841c,00100100'
 Controls  : 12
 Simple ctrls  : 8
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfbffc000 irq 17'
 Mixer name : 'Nvidia GPU 0b HDMI/DP'
 Components : 'HDA:10de000b,10de0101,00100200'
 Controls  : 16
 Simple ctrls  : 4
  Date: Wed May 18 03:27:21 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0601
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1015PN
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0601:bd02/18/2011:svnASUSTeKComputerINC.:pn1015PN:pvrx.x:rvnASUSTeKComputerINC.:rn1015PN:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1015PN
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Touch-packages] [Bug 1626826] Re: KVM guest cannot use br0 created by brctl on Ubuntu16.04

2016-10-28 Thread ChristianEhrhardt
** Changed in: bridge-utils (Ubuntu)
   Status: New => Invalid

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

Title:
  KVM guest cannot use br0 created by brctl on Ubuntu16.04

Status in Ubuntu on IBM z Systems:
  Invalid
Status in bridge-utils package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - QI YE  - 2016-09-22 06:01:59 ==
  ---Problem Description---
  Ubuntu16.04. Created a bridge br0 on enc100 via brctl.  enc100 is the only 
external accessible nic. Defined a ubuntu guest to use br0 and assigned an IP 
to the guest in the same subnet as br0. After started the guest, couldn't 
access external servers or internet from the guest. 
   

  ---uname output---
  Linux ntc170 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 UTC 2016 
s390x s 390x s390x GNU/Linux
   
  Machine Type = 2827 (z Systems EC12) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. define br0 on enc100 via brctl command (IP on br0 is 192.168.1.170 for 
example)
  2. update /etc/network/interfaces
  3. create a guest on KVM and use br0 for it's nic
  4. Start guest via virsh command and assign an IP, e.g. 192.168.1.171.  After 
installation, cannot access external systems via KVM host.

  == Comment: #2 - QI YE  - 2016-09-22 09:53:58 ==
  attached sosreport file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1626826/+subscriptions

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


[Touch-packages] [Bug 1637026] Re: kill incorrectly parses negative PIDs

2016-10-28 Thread Martin Pitt
> systemd-sysctl.service failed

This is indeed a known wart in LXD containers, and it's conceptually
difficult to fix (see bug 1576341 or
https://github.com/lxc/lxcfs/issues/111 for some earlier discussion).

It would be wrong if sysctl would entirely ignore all failures, as this
would make actual (unintended) failures/typos/etc. much harder to detect
-- we don't want to hide these.

"apt-get install --reinstall procps" in lxd actually works fine in
zesty, but not in xenial -- in xenial the postinst has "invoke-rc.d
procps start" which is gone from zesty.

The current versions (also in Debian) do not start the init script on
install/upgrades:

  https://anonscm.debian.org/cgit/collab-
maint/procps.git/tree/debian/rules#n89

and I think that's the right thing -- this is usually something you want
done at boot, but not during runtime, and it potentially breaks package
upgrades too. So if you want to SRU this override_dh_install along, that
would be fine with me (with my SRU hat on).

** Bug watch added: LXCFS bug tracker #111
   https://github.com/lxc/lxcfs/issues/111

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

Title:
  kill incorrectly parses negative PIDs

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  When kill is called with a negative argument, incorrect parsing can lead it 
to call sys_kill(-1), thus sending a signal to all permitted processes on the 
system. A couple of users have hit this while deploying Hadoop, which seems to 
tickle this - basically killing everything on the system.

  [Test Case]
  Though I don't know what Hadoop is calling, here's a couple of ways to 
trigger this:

  One possibility is if kill were called w/ a numeric signal that
  happened to start with a '1' and while omitting the required 
  argument:

  kill -12

  Another would be to specify a numeric signal (that again happened to
  start with a 1) multiple times:
  kill -13 -13 12345

  [Regression Risk]
  This is a backport from upstream that is already available in 16.10, with no 
known regressions.

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

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


[Touch-packages] [Bug 1637026] Re: kill incorrectly parses negative PIDs

2016-10-28 Thread Martin Pitt
Ah, this is already tracked in bug 1637300, nevermind.

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

Title:
  kill incorrectly parses negative PIDs

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  When kill is called with a negative argument, incorrect parsing can lead it 
to call sys_kill(-1), thus sending a signal to all permitted processes on the 
system. A couple of users have hit this while deploying Hadoop, which seems to 
tickle this - basically killing everything on the system.

  [Test Case]
  Though I don't know what Hadoop is calling, here's a couple of ways to 
trigger this:

  One possibility is if kill were called w/ a numeric signal that
  happened to start with a '1' and while omitting the required 
  argument:

  kill -12

  Another would be to specify a numeric signal (that again happened to
  start with a 1) multiple times:
  kill -13 -13 12345

  [Regression Risk]
  This is a backport from upstream that is already available in 16.10, with no 
known regressions.

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

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


[Touch-packages] [Bug 1637300] Re: procps upgrades fail in a LXD container

2016-10-28 Thread Martin Pitt
This seems fine to me. I just replied to
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1637026/comments/4
before realizing that this issue is tracked here.

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

Title:
  procps upgrades fail in a LXD container

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  In Progress
Status in procps package in Debian:
  Fix Released

Bug description:
  [Impact]
  procps cannot be upgraded - or even reinstalled - in an LXD container. This 
means we cannot deliver updates (like the pending fix for LP: #1637026 in 
xenial-proposed) w/o putting container users in a bad state that requires a 
container restart to resolve.

  [Test Case]
  $ lxc launch ubuntu:xenial procpstest
  Creating procpstest
  Starting procpstest
  $ lxc exec procpstest -- /bin/bash
  root@procpstest:~# apt --reinstall install procps
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 209 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 procps arm64 
2:3.3.10-4ubuntu2 [209 kB]
  Fetched 209 kB in 1s (113 kB/s)  
  (Reading database ... 25398 files and directories currently installed.)
  Preparing to unpack .../procps_2%3a3.3.10-4ubuntu2_arm64.deb ...
  Unpacking procps (2:3.3.10-4ubuntu2) over (2:3.3.10-4ubuntu2) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Processing triggers for systemd (229-4ubuntu11) ...
  Setting up procps (2:3.3.10-4ubuntu2) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Job for systemd-sysctl.service failed because the control process exited with 
error code. See "systemctl status systemd-sysctl.service" and "journalctl -xe" 
for details.
  invoke-rc.d: initscript procps, action "start" failed.
  dpkg: error processing package procps (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   procps
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  root@procpstest:~#

  [Regression Risk]
  The proposed fix is to disable invoking the procps initscript on 
install/upgrade. This fix is already in yakkety, and I didn't find any bugs 
related to it in LP.

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

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


[Touch-packages] [Bug 1626826] Re: KVM guest cannot use br0 created by brctl on Ubuntu16.04

2016-10-28 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: New => Invalid

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

Title:
  KVM guest cannot use br0 created by brctl on Ubuntu16.04

Status in Ubuntu on IBM z Systems:
  Invalid
Status in bridge-utils package in Ubuntu:
  New

Bug description:
  == Comment: #0 - QI YE  - 2016-09-22 06:01:59 ==
  ---Problem Description---
  Ubuntu16.04. Created a bridge br0 on enc100 via brctl.  enc100 is the only 
external accessible nic. Defined a ubuntu guest to use br0 and assigned an IP 
to the guest in the same subnet as br0. After started the guest, couldn't 
access external servers or internet from the guest. 
   

  ---uname output---
  Linux ntc170 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 UTC 2016 
s390x s 390x s390x GNU/Linux
   
  Machine Type = 2827 (z Systems EC12) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. define br0 on enc100 via brctl command (IP on br0 is 192.168.1.170 for 
example)
  2. update /etc/network/interfaces
  3. create a guest on KVM and use br0 for it's nic
  4. Start guest via virsh command and assign an IP, e.g. 192.168.1.171.  After 
installation, cannot access external systems via KVM host.

  == Comment: #2 - QI YE  - 2016-09-22 09:53:58 ==
  attached sosreport file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1626826/+subscriptions

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


[Touch-packages] [Bug 1598584] Re: wifi slows to a crawl when bluetooth is enabled

2016-10-28 Thread Alfonso Sanchez-Beato
@Pat, would you mind giving a try to this new one? The older one was
engineering build, which maybe was affecting performance.

** Attachment added: "boot.img"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1598584/+attachment/4768768/+files/boot.img

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

Title:
  wifi slows to a crawl when bluetooth is enabled

Status in arale:
  New
Status in Canonical System Image:
  Confirmed
Status in frieza:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  I am having serious wifi performance issues on my Aquaris M10 (running
  rc-proposed r133). When measuring the wifi speed, I get download
  speeds of less than 1/20 compared to my Pro 5 at the same distance
  from the wifi router. This seems to be consistent through reboots. I
  had similar wifi performance also before recently upgrading to rc-
  proposed, which I thought would have fixed the issue.

  I am in the same place testing 3 different ubuntu devices and these are the 
readings of the wifi download speed:
  Laptop: 4 MB/s
  Pro 5: 3.5 MB/s
  Aquaris M10: 0.16 MB/s

  However, upload speed is about the same on all three devices.

  Turning bluetooth off gets Aquaris M10 wifi speed back to sort of
  normal, 2.5-3.4 MB/s. Bluetooth on, again 0.1-0.2 MB/s. Seems the two
  wireless technologies interfere with each other on the M10, while the
  Pro 5 doesn't have that problem.

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

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


[Touch-packages] [Bug 1626826] Comment bridged from LTC Bugzilla

2016-10-28 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2016-10-28 05:08 EDT---
Non-supported function -> Closed

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

Title:
  KVM guest cannot use br0 created by brctl on Ubuntu16.04

Status in Ubuntu on IBM z Systems:
  New
Status in bridge-utils package in Ubuntu:
  New

Bug description:
  == Comment: #0 - QI YE  - 2016-09-22 06:01:59 ==
  ---Problem Description---
  Ubuntu16.04. Created a bridge br0 on enc100 via brctl.  enc100 is the only 
external accessible nic. Defined a ubuntu guest to use br0 and assigned an IP 
to the guest in the same subnet as br0. After started the guest, couldn't 
access external servers or internet from the guest. 
   

  ---uname output---
  Linux ntc170 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 UTC 2016 
s390x s 390x s390x GNU/Linux
   
  Machine Type = 2827 (z Systems EC12) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. define br0 on enc100 via brctl command (IP on br0 is 192.168.1.170 for 
example)
  2. update /etc/network/interfaces
  3. create a guest on KVM and use br0 for it's nic
  4. Start guest via virsh command and assign an IP, e.g. 192.168.1.171.  After 
installation, cannot access external systems via KVM host.

  == Comment: #2 - QI YE  - 2016-09-22 09:53:58 ==
  attached sosreport file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1626826/+subscriptions

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


[Touch-packages] [Bug 1636381] Re: Details views in dialogs are too small

2016-10-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Details views in dialogs are too small

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Details views in dialogs are too small, the viewing height is approx. 15px.
  My machine has a screen resolution of 2880x1800 on 15". I have to adjust the 
scaling to 1,62 to be able to read text. This leads to just half a line 
displayed in the viewing slot.

  Initially I reported this issue with deja-dup
  (https://bugs.launchpad.net/bugs/1635197) but this issue also shows up
  on several other dialog boxes (e.g. system updates - download of
  repos, ...).

  Thus I presume it either to be related with Unity or xorg.

  If you need additional information to identity the source, let me
  know.

  This behaviour is new to 16.10 and can be reproduced on any machine
  that I have access to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 25 07:59:44 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.8.0-26-generic, x86_64: installed
   nvidia-367, 367.57, 4.8.0-26-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00f7]
   NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2]
  InstallationDate: Installed on 2016-10-22 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Apple Inc. MacBookPro10,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic.efi.signed 
root=UUID=9a60a19c-458f-4dca-8617-f7c6cacf9658 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Mon Oct 24 16:16:55 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-1ubuntu6

To manage notifications about this bug go to:

  1   2   >