date:20170612

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

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

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

Title:
  Bootup issues

Status in systemd package in Ubuntu:
  Expired

Bug description:
  2 min boot time on a ssd.

  Not sure if this is a bug or issues with grub.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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: Thu Apr 13 00:16:58 2017
  DistUpgraded: 2017-04-01 17:41:56,251 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.32, 4.4.0-71-generic, x86_64: installed
   virtualbox, 5.0.32, 4.4.0-72-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 
270X/370 OEM] [1002:6810] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Curacao XT [Radeon R7 
370 / R9 270X/370 OEM] [174b:e270]
  InstallationDate: Installed on 2017-04-01 (11 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=70e462eb-e84a-4333-9f94-c18d079a64e0 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-01 (11 days ago)
  dmi.bios.date: 01/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A78M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA:bd01/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 12 23:51:28 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1697287] Re: package isc-dhcp-client 4.3.3-5ubuntu12 [modified: usr/share/doc/isc-dhcp-client/changelog.Debian.gz] failed to install/upgrade: el paquete isc-dhcp-client no está l

2017-06-12 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package isc-dhcp-client 4.3.3-5ubuntu12 [modified: usr/share/doc/isc-
  dhcp-client/changelog.Debian.gz] failed to install/upgrade: el paquete
  isc-dhcp-client no está listo para configurarse  no se puede
  configurar (estado actual `half-installed')

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  rr

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12 [modified: 
usr/share/doc/isc-dhcp-client/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   linux-image-extra-4.4.0-77-generic: Remove
   linux-image-4.4.0-77-generic: Remove
   isc-dhcp-client: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun 11 09:10:44 2017
  DhclientLeases:
   
  ErrorMessage: el paquete isc-dhcp-client no está listo para configurarse  no 
se puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2016-09-23 (260 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic 
root=UUID=cee3f129-716d-46c7-9ab8-016c71f29972 ro quiet splash
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-client 4.3.3-5ubuntu12 [modified: 
usr/share/doc/isc-dhcp-client/changelog.Debian.gz] failed to install/upgrade: 
el paquete isc-dhcp-client no está listo para configurarse  no se puede 
configurar (estado actual `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1697287] Re: package isc-dhcp-client 4.3.3-5ubuntu12 [modified: usr/share/doc/isc-dhcp-client/changelog.Debian.gz] failed to install/upgrade: el paquete isc-dhcp-client no está l

2017-06-12 Thread Steve Beattie

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

Title:
  package isc-dhcp-client 4.3.3-5ubuntu12 [modified: usr/share/doc/isc-
  dhcp-client/changelog.Debian.gz] failed to install/upgrade: el paquete
  isc-dhcp-client no está listo para configurarse  no se puede
  configurar (estado actual `half-installed')

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  rr

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12 [modified: 
usr/share/doc/isc-dhcp-client/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   linux-image-extra-4.4.0-77-generic: Remove
   linux-image-4.4.0-77-generic: Remove
   isc-dhcp-client: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun 11 09:10:44 2017
  DhclientLeases:
   
  ErrorMessage: el paquete isc-dhcp-client no está listo para configurarse  no 
se puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2016-09-23 (260 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic 
root=UUID=cee3f129-716d-46c7-9ab8-016c71f29972 ro quiet splash
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-client 4.3.3-5ubuntu12 [modified: 
usr/share/doc/isc-dhcp-client/changelog.Debian.gz] failed to install/upgrade: 
el paquete isc-dhcp-client no está listo para configurarse  no se puede 
configurar (estado actual `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

2017-06-12 Thread Shaabi

Confirming on dell 9560! I cant get headphones to work even after
reboots. It worked fine and then stopped working recently.

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1697290] Re: package libssl-doc 1.0.2g-1ubuntu4.8 failed to install/upgrade: pacote libssl-doc não está pronto para configuração não posso configurar (estado atual 'half-install

2017-06-12 Thread Steve Beattie

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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1697290

Title:
  package libssl-doc 1.0.2g-1ubuntu4.8 failed to install/upgrade: pacote
  libssl-doc não está pronto para configuração  não posso configurar
  (estado atual 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  Tentei diversas vezes executar esta atualização. Mesmo com o uso de
  ferramentas como "dpkg --configure -a" ou o "apt-get -f install" não
  obtive sucesso.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl-doc 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl-doc: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun 11 12:40:04 2017
  Dependencies:
   
  DpkgTerminalLog:
   dpkg: erro ao processar o pacote libssl-doc (--configure):
pacote libssl-doc não está pronto para configuração
não posso configurar (estado atual 'half-installed')
  ErrorMessage: pacote libssl-doc não está pronto para configuração  não posso 
configurar (estado atual 'half-installed')
  InstallationDate: Installed on 2016-06-18 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl-doc 1.0.2g-1ubuntu4.8 failed to install/upgrade: pacote 
libssl-doc não está pronto para configuração  não posso configurar (estado 
atual 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution

2017-06-12 Thread Bug Watch Updater

** Changed in: apt
   Status: Unknown => New

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

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-
  daily.service execution

Status in APT:
  New
Status in cloud-init:
  Confirmed
Status in apt package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Confirmed

Bug description:
  apt-daily is now a systemd service rather than being invoked by
  cron.daily.  If one builds a custom AMI it is possible that the apt-
  daily.timer will fire during boot.  This can fire at the same time
  cloud-init is running and if cloud-init loses the race the invocation
  of apt (e.g. use of "packages:" in the config) will fail.

  There is a lot of discussion online about this change to apt-daily
  (e.g. unattended upgrades happening during business hours, delaying
  boot, etc.) and discussion of potential systemd changes regarding
  timers firing during boot (c.f.
  https://github.com/systemd/systemd/issues/5659).

  While it would be better to solve this in apt itself, I suggest that
  cloud-init be defensive when calling apt and implement some retry
  mechanism.

  Various instances of people running into this issue:

  https://github.com/chef/bento/issues/609
  https://clusterhq.atlassian.net/browse/FLOC-4486
  https://github.com/boxcutter/ubuntu/issues/73
  
https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image

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

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

[Touch-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

2017-06-12 Thread Kai-Heng Feng

Can you try if these kernel works?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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 Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  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.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

2017-06-12 Thread gali

@Kai-Heng, if that can help this is my configuration below:
-Dell Latitude E7450 on a Dell docking station with two screens (1 VGA , the 
other 
-Intel® Core™ i7-5600U CPU @ 2.60GHz × 4 
-GeForce 840M/PCIe/SSE2

ggalibert@ggalibert-Latitude-E7450:~$ lsmod | grep i915
i915 1208320  3
i2c_algo_bit   16384  1 i915
drm_kms_helper155648  2 i915,nvidia_drm
drm   364544  6 i915,drm_kms_helper,nvidia_drm
video  40960  3 i915,dell_wmi,dell_laptop

Last working kernel version is 4.4.0-72.

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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 Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  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.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

2017-06-12 Thread Alex Tu

freedesktop upstream[1] rejected the backport operation and suggest user to add 
another maintainer's ppa instead:
https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-xenial


[1] https://bugs.freedesktop.org/show_bug.cgi?id=101386

** Bug watch added: freedesktop.org Bugzilla #101386
   https://bugs.freedesktop.org/show_bug.cgi?id=101386

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in ModemManager:
  New
Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

  FCC authentication reference:
   * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
   * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

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

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

[Touch-packages] [Bug 1697535] Re: [Envy24 ICE1724] Audio doesn't work

** Summary changed:

- Envy24 ICE1724 doesn't work
+ [Envy24 ICE1724] Audio doesn't work

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

Title:
  [Envy24 ICE1724] Audio doesn't work

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 17.04
  PulseAudio Version: 1:10.0-1ubuntu2
  I expected the audio on my system to work without any additional action on my 
part. Instead, the audio does not work despite working on Windows.

  A few years ago, my onboard sound broke so I bought a pci sound card
  (ENCORE ENM232-8VIA 7.1) which seems to have the Envy24 ICE1724
  chipset. This sound card works on Windows but not Ubuntu or Debian.
  I've attempted to troubleshoot this myself over the past year or so
  and had no luck figuring out the problem (though ubuntu-bug seems to
  think there is a problem with pulseaudio).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 12 14:00:25 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-12-10 (184 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (55 days ago)
  dmi.bios.date: 09/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1104
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QL-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 2.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1104:bd09/11/2009:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5QL-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

OK. This bug is way oversubscribed and is getting confused by too many
people reporting problems that are not actually this bug.

It seems generally people using 17.04 either report this bug is fixed,
or are reporting different bugs.

So consider this one Fix Released for 17.04. I understand 16.04 is still
suffering though, so will nominate xenial for additional future fixes.

Everyone: If you continue to experience problems with the error
"TryAcquire() failed - Operation Not Authorized" then you can comment
here. We know it still happens in 16.04 but are interested to hear if it
can still happen in 17.04. If you experience any problems that are not
"TryAcquire() failed - Operation Not Authorized" then please log a
separate bug...

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

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

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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

[Touch-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

GreyBox: Please log a separate bug. You appear to have a different
problem...


** Changed in: pulseaudio (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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

[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution

2017-06-12 Thread Julian Andres Klode

We eventually want wait locking in apt, but I don't think it really
solves all issues, especially in scripts with multiple apt invocations.
Which is why apt-daily got an additional flock lock for the upcoming
SRUs. (see artful).

Feel free.to wait on the same.lock and probably add some ordering
against apt-daily and apt-daily-upgrade services.

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

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-
  daily.service execution

Status in APT:
  Unknown
Status in cloud-init:
  Confirmed
Status in apt package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Confirmed

Bug description:
  apt-daily is now a systemd service rather than being invoked by
  cron.daily.  If one builds a custom AMI it is possible that the apt-
  daily.timer will fire during boot.  This can fire at the same time
  cloud-init is running and if cloud-init loses the race the invocation
  of apt (e.g. use of "packages:" in the config) will fail.

  There is a lot of discussion online about this change to apt-daily
  (e.g. unattended upgrades happening during business hours, delaying
  boot, etc.) and discussion of potential systemd changes regarding
  timers firing during boot (c.f.
  https://github.com/systemd/systemd/issues/5659).

  While it would be better to solve this in apt itself, I suggest that
  cloud-init be defensive when calling apt and implement some retry
  mechanism.

  Various instances of people running into this issue:

  https://github.com/chef/bento/issues/609
  https://clusterhq.atlassian.net/browse/FLOC-4486
  https://github.com/boxcutter/ubuntu/issues/73
  
https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image

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

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

[Touch-packages] [Bug 1665289] Re: [unity8] Ubuntu Software can't launch installed apps from within its GUI

2017-06-12 Thread Robert Ancell

Unity 8 is discontinued.

** Changed in: gnome-software (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [unity8] Ubuntu Software can't launch installed apps from within its
  GUI

Status in Canonical System Image:
  New
Status in gnome-software package in Ubuntu:
  Won't Fix
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 unity8

  launch Ubuntu Software
  install some random app (deb or snap) and after it is installed click on the 
Launch button. 
  the app doesn't launch

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

-- 
Mailing list: https://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 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-06-12 Thread Daniel Axtens

Hi Mao,

OK, that sounds reasonable. I will follow up on this.

Regards,
Daniel

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

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

[Touch-packages] [Bug 1688208] Re: gnome-shell crashed with SIGSEGV in foreach_city() from foreach_city() from foreach_city() from foreach_city() from foreach_city()

2017-06-12 Thread Adam Conrad

Hello errors.ubuntu.com, or anyone else affected,

Accepted libgweather into zesty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libgweather/3.24.1-0ubuntu0.1 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: libgweather (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  gnome-shell crashed with SIGSEGV in foreach_city() from foreach_city()
  from foreach_city() from foreach_city() from foreach_city()

Status in libgweather:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  Fix Committed

Bug description:
  Impact
  ==
  Memory corruption in libgweather caused gnome-shell to crash. This is 
particularly bad for GNOME on Wayland as a gnome-shell crash will causes the 
user to lose their sessions.

  (GNOME Shell 3.24 introduced a new weather feature in the clock menu.)

  This particular error has been reported over 1000 times to
  errors.ubuntu.com from Ubuntu GNOME 17.04 and was also a Fedora 26
  blocker bug.

  Test Case
  =
  The number of crashes reported on errors.ubuntu.com for gnome-shell should be 
significantly lower once this new version of libgweather rolls out.

  Because e.u.com links this issue with gnome-shell, this is difficult
  to verify except that if you run gnome-shell, it shouldn't crash so
  often especially when first logging in.

  Regression Potential
  
  The main new commit here had already been cherry-picked by Fedora and in 
Ubuntu 17.10 Alpha. Considering the previous 

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.1-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/39b6625ed47999dab38b064b2d91bde1e11dec62 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1695567] Re: /usr/bin/gnome-shell:* Error in `/usr/bin/gnome-shell': double free or corruption (out): ADDR * in g_free() from gweather_location_unref()

2017-06-12 Thread Adam Conrad

Hello errors.ubuntu.com, or anyone else affected,

Accepted libgweather into zesty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libgweather/3.24.1-0ubuntu0.1 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: libgweather (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free
  or corruption (out): ADDR *** in g_free() from
  gweather_location_unref()

Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions

  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.

  This error has been reported over 700 times on errors.ubuntu.com for
  Ubuntu GNOME 17.04.

  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.

  [Other Info]
  This updates libgweather from 3.24.0 to 3.24.1
  https://git.gnome.org/browse/libgweather/log

  The guard_against_segfault commit was already present in Ubuntu 17.04.

   Original bug report 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.2-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/06422e05faafe183b4cb70daa7306dcb4c08c97e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1697552] [NEW] Can't login to Unity - get in a loop back to login screen

2017-06-12 Thread Joe Spurlock

Public bug reported:

"Could not acquire name on session bus" at Unity login screen and get in
a loop back to the login screen if (correctly) entering user password
(admin level account).

Can seem to log into the MATE desktop.However when Logged into MATE
desktop there is no Terminal avaialble.

Can navigate to the command line at the Unity login screen but do not
know what to do to correct the login issue with Unity.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Jun 12 17:01:41 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [103c:3398]
InstallationDate: Installed on 2017-06-09 (3 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Hewlett-Packard HP Compaq Elite 8300 USDT
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=ea35e559-442e-4ec2-b12a-6659b4317e63 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v03.04
dmi.board.asset.tag: MXL2481GVF
dmi.board.name: 3398
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: MXL2481GVF
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v03.04:bd10/05/2016:svnHewlett-Packard:pnHPCompaqElite8300USDT:pvr:rvnHewlett-Packard:rn3398:rvr:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: HP Compaq Elite 8300 USDT
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Mon Jun 12 16:54:09 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug ubuntu zesty

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

Title:
  Can't login to Unity - get in a loop back to login screen

Status in xorg package in Ubuntu:
  New

Bug description:
  "Could not acquire name on session bus" at Unity login screen and get
  in a loop back to the login screen if (correctly) entering user
  password (admin level account).

  Can seem to log into the MATE desktop.However when Logged into
  MATE desktop there is no Terminal avaialble.

  Can navigate to the command line at the Unity login screen but do not
  know what to do to correct the login issue with Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jun 12 17:01:41 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [103c:3398]
  InstallationDate: Installed on 2017-06-09 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP Compaq Elite 8300 USDT
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no

[Touch-packages] [Bug 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

2017-06-12 Thread FFab

Upstream kernel test - kernel 4.12-rc2 – rc5
Test results differ from rc1:
no "boot finished" sound, no remote login (ssh).
Reboot/shutdown by SysRQ keys after about 3 minutes possible.

Upstream kernels were installed on an updated Ubuntu installation.
For comparison I installed rc5 on an Ubuntu installation, which was updated 8 
weeks ago (2017-04-17) .
The test result was just like that of rc1 ("boot finished" sound after 45 sec.).

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When booting the screen is black – backlight on – off - on.
  When HDD is inactive
  - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or 
Strg + Alt + Del
  - remote access e.g. using ssh is possible

  Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

  My notebook is a HP Pavilion  17-g164ng with an AMD A10-8780P APU and
  2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

  It seems very similar to that described in #1597079.

  The bug report was generated from a remote PC. My HP notebook was started 
without any workaround parameters.
  This apport doesn't display the second graphic subsystem Topaz R7 as an 
apport generated with nomodeset xforcevesa.

  WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

  WORKAROUND: When booting in UEFI mode, use kernel parameters:
  nomodeset

  or:
  nomodeset xforcevesa

  Resolution without xforcevesa: 800x600
  Resolution with xforcevesa: 1600x900 – the optimal resolution

  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
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  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 Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.1
  xserver.video_driver: amdgpu

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

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

[Touch-packages] [Bug 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

2017-06-12 Thread FFab

Upstream kernel test - kernel 4.12-rc2 – rc5
Test results differ from rc1:
no  "boot finished" sound, no remote login (ssh).
Reboot/shutdown by SysRQ keys after about 3 minutes possible.

Upstream kernels were installed on an updated Ubuntu installation.
For comparison, I  installed rc5 on an Ubuntu installation, which was updated 8 
weeks ago (2017-04-17) .
The test result was just like that of rc1 ("boot finished" sound after 45 sec.).

** Tags removed: kernel-bug-exists-upstream-4.12-rc1
** Tags added: kernel-bug-exists-upstream-4.12-rc5

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When booting the screen is black – backlight on – off - on.
  When HDD is inactive
  - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or 
Strg + Alt + Del
  - remote access e.g. using ssh is possible

  Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

  My notebook is a HP Pavilion  17-g164ng with an AMD A10-8780P APU and
  2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

  It seems very similar to that described in #1597079.

  The bug report was generated from a remote PC. My HP notebook was started 
without any workaround parameters.
  This apport doesn't display the second graphic subsystem Topaz R7 as an 
apport generated with nomodeset xforcevesa.

  WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

  WORKAROUND: When booting in UEFI mode, use kernel parameters:
  nomodeset

  or:
  nomodeset xforcevesa

  Resolution without xforcevesa: 800x600
  Resolution with xforcevesa: 1600x900 – the optimal resolution

  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
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  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 Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.1
  xserver.video_driver: amdgpu

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

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

[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Hello Daniele, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu4
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Yakkety:
  Confirmed
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * Null-pointer dereference in resolved, results in resolved crash and
  reports on launchpad and errors.

  [Test Case]

   * Unknown steps to reproduce
   * Monitor the drop off in crashes on errors.ubuntu.com:
  https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465

  [Regression Potential]

   * The behavior is similar, instead of crashing resolved it returns an
  error in the relevant function. Whilst this may not result in correct
  dns resolution for the affected dns packets, it should not result in
  resolved crashes.

  [Original Bug Report]

  This is one of background errors that happens without any active app being 
involved.
  For the records, I had open: Firefox, Slack, Franz and the Terminal

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd. This problem was most recently seen with package version 233-6ubuntu2, 
the problem page at 
https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  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
  CrashCounter: 1
  Date: Thu Sep  8 09:33:55 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1189 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago)
  UserGroups:

  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1686784] Re: no predictable names for platform (non-PCI) NICs

Hello dann, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu4
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  no predictable names for platform (non-PCI) NICs

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Systems may have NICs attached to the "platform" bus. These are NICs that are 
onboard, but not attached to a PCI(-like) bus. Rather, they are described by 
firmware directly. None of the naming policies enabled by Ubuntu by default 
matches these NICs, so they end up having unpredictable names. In the case 
where other NICs are attached (e.g. PCIe cards), the ethN enumeration race 
occurs, making it impossible to have an interface name that is persistent 
across reboots. That is, if you do a network install over "eth0", on reboot 
that NIC now maybe "eth3", which causes it to fail to start the network on boot.

  The HiSilicon D05 boards are an example of this. It has 4 onboard NICs
  that are described by ACPI directly, and may also have other PCIe NICs
  plugged in.

  [Test Case]
  Boot a system with the characteristics described above, and check to see if 
any "ethN" interfaces exist.

  [Regression Risk]
  Unless one fixed the names locally with .netlink / .rules files the interface 
names will change for the ACPI/platform bus network interfaces, from random 
ethX names to stable names named like enaVENDORMODELiX. Thus we should check 
that this update doesn't negatively break certified ARM64 platforms with: ARM, 
NVIDIA, HISILICON platform bus ethernet devices.

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

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

[Touch-packages] [Bug 1672499] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf

Hello Seth, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu4
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on
  armhf

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * ADT test superfluously fails, resulting in SRU / proposed-migration
  delays

  [Test Case]

   * Check that systemd ADT tests pass

  [Regression Potential]

   * No change to the binary packages, this is a change in ADT test-
  suite only.

  [Original Bug Report]

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz

  root-unittests fails:

   -> Unit a.service:
    Description: a.service
    Instance: n/a
    Unit Load State: not-found
    Unit Active State: inactive
    State Change Timestamp: n/a
    Inactive Exit Timestamp: n/a
    Active Enter Timestamp: n/a
    Activeerror: org.freedesktop.systemd1.NoSuchUnit: Unit c.service not found.
  Assertion 'r == 0' failed at ../src/test/test-engine.c:62, function main(). 
Aborting.
   Exit Timestamp: n/a

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

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

[Touch-packages] [Bug 1686361] Re: systemd does not respect nofile ulimit when running in container

Hello Christian, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu4
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  systemd does not respect nofile ulimit when running in container

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Containers cannot use maximum RLIMIT_NOFILE, because systemd sets
  an arbitrary cap.

  [Test Case]

   * Start container with high RLIMIT_NOFILE (e.g. 100 000)
   * Check that RLIMIT_NOFILE on the container is more than 65536

  [Regression Potential]

   * This is a feature / change of behaviour. Some users may be relying
  on the lower RLIMIT_NOFILE cap, but it should not have a negative
  impact on the host (as in creating too many file descriptors/denial of
  service).

  [Original Bug Report]

  When systemd currently starts in a container that has RLIMIT_NOFILE set to 
e.g.
  10 systemd will lower it to 65536 since this value is hard-coded into 
systemd.
  I've pushed a patch to systemd upstream that will try to set
  the nofile limit to the allowed kernel maximum. If this fails, it will compute
  the minimum of the current set value (the limit that is set on the container)
  and the maximum value as soft limit and the currently set maximum value as the
  maximum value. This way it retains the limit set on the container.
  It would be great if we could backport this patch to have system adhere to
  nofile limits set for the container. This is especially important since user
  namespaces will allow you to lower the limit but not raise it back up 
afterwards.
  The upstream patch is appended.

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

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

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

It seems that the problem is that dnsmasq is forwarding DNS queries to
the systemd-resolved stub server, but they are incompatible in some
way:.  From /var/log/syslog:

Jun 12 17:05:34 sparkly dnsmasq[1177]: using nameserver 127.0.0.53#53
Jun 12 17:05:49 sparkly dnsmasq[1177]: Maximum number of concurrent DNS queries 
reached (max: 150)

As a workaround, I edited /etc/dnsmasq.conf and added these lines to
tell it to ignore resolve.conf and hardcoded my ISP's DNS servers
instead:

no-resolv
server=75.75.75.75
server=75.75.76.76

It seems to work: I'm running a hotspot on a USB wifi device and it's
working fine, and there's no sign of the CPU trouble.

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm

[Touch-packages] [Bug 1692136] Re: Backport "core/timer: downgrade message about random time addition (#5229)".

Hello Vinson, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu4
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  Backport "core/timer: downgrade message about random time addition
  (#5229)".

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Yakkety:
  Triaged
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * Systemd spams logs too much with pointless messages

  [Test Case]

   * Boot system and observe no pointless messages of scheduling random
  timers for things at a given offset

  [Regression Potential]

   * Low, this patch simply changes the priority of the message from
  info to debug.

  [Original bug report]

  Please backport upstream systemd v233 commit
  382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade
  message about random time addition (#5229)".
  
https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1

  This removes "random time" messages flooding dmesg.

  The spew was introduced with v229 commit "core: add new RandomSec=
  setting for time units".
  
https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07

  trusty based off v204 is not affected.

  xenial based off v229, yakkety based off v231, and zesty based off
  v232 need this fix.

  artful based off v233 has the fix.

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

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

[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"

2017-06-12 Thread Elvis Stansvik

Thank you! Been waiting for this fix for 11 months, and boy does it
taste sweet now that it's here :)

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

Title:
Please consider SRU of "xcb: Compress mouse motion and touch update
events"

Status in qtbase-opensource-src package in Ubuntu:
Fix Released
Status in qtbase-opensource-src source package in Xenial:
Fix Released

Bug description:
Mouse event compression stopped working in Qt 5, a regression from Qt
4:

https://bugreports.qt.io/browse/QTBUG-40889

The bug was fixed in Qt 5.6 https://codereview.qt-
project.org/#/c/126136/ where the fix has been thoroughly tested by
now.

Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a
backport of the 5.6 patch (only one trivial hunk failed, which was
easily fixed).

[Impact]

The bug affects any program that relies on the event compression Qt
normally performs. For example, VTK programs (ParaView, Tomviz, ...)
do their rendering in response to mouse events during camera
movements, and with event compression at the Qt level suddenly gone,
camera movements become very slow, since the application is now
flooded with mouse events and the rendering lags behind.

The problem is not limited to these programs however; it can be
observed by simply putting two regular, slightly slow-to-render,
widgets into a QSplitter and moving the splitter handle. The result is
a syrup-like experience as the widgets try to keep up with the
onslaught of resize events due to the lack of mouse event compression.

[Test Case]

The attached test application can be used to check if event
compression is functioning. It performs some artificial work on each
mouse move and prints a message. Click and drag the mouse a little.
After releasing the mouse, you'll notice that the printouts keeps
coming for quite a while, as the program is catching up with the flood
of events.

With the attached patch (and with Qt 4), the problem is gone - the
mouse event stream is compressed and the printouts are no longer
lagging behind.

[Regression Potential]

There's a small risk that some applications have made workarounds for
the faulty behavior, and that unwanted behavior is introduced if this
bug is fixed. But chances are high that such workarounds will keep
working, as the obvious workaround is to do timer based rendering
instead of event based. The workarounds will then simply become
unnecessary, but shouldn't cause problems.

I'm asking for someone to nominate this bug for an SRU of 16.04 LTS.

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

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

[Touch-packages] [Bug 1693032] Re: missing dependency on gnome-session-bin

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: software-properties (Ubuntu)
   Status: New => In Progress

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Changed in: software-properties (Ubuntu)
Milestone: None => ubuntu-17.07

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

Title:
  missing dependency on gnome-session-bin

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  When bug 1241210 was fixed SoftwarePropertiesGtk.py was changed to
  call gnome-session-quit which is provided by gnome-session-bin.
  However, a dependency on gnome-session-bin was never added to
  software-properties-gtk. This has led to the following possible
  Traceback:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1116, in on_driver_restart_clicked
  subprocess.call(['gnome-session-quit', '--reboot'])
    File "/usr/lib/python3.5/subprocess.py", line 247, in call
  with Popen(*popenargs, **kwargs) as p:
    File "/usr/lib/python3.5/subprocess.py", line 676, in __init__
  restore_signals, start_new_session)
    File "/usr/lib/python3.5/subprocess.py", line 1282, in _execute_child
  raise child_exception_type(errno_num, err_msg)
  FileNotFoundError: [Errno 2] Δεν υπάρχει τέτοιο αρχείο ή κατάλογος: 
'gnome-session-quit'

  There are a large collection of these crashes mixed in with this
  bucket:

  https://errors.ubuntu.com/problem/bc249affe50a221622d55a34ecfe5223704c012c

  I suspect that a lot of these crashes are from Lubuntu or Xubuntu
  systems, but its possible some are not and the missing dependency
  should be fixed anyway.

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

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

[Touch-packages] [Bug 1575779] Re: hostnamectl fails under lxd unpriv container

2017-06-12 Thread Christian Reis

I also see this trigger with juju-deployed jenkins and jenkins-slave
services against the lxd provider:

   apparmor="DENIED" operation="file_lock" profile="lxd-juju-
449b90-9_" pid=18662 comm="(ostnamed)" family="unix"
sock_type="dgram" protocol=0 addr=none

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

Title:
  hostnamectl fails under lxd unpriv container

Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  1.  % lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2.  % apt-cache policy apparmor
  apparmor:
Installed: 2.10.95-0ubuntu2
Candidate: 2.10.95-0ubuntu2
Version table:
   *** 2.10.95-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  % apt-cache policy lxd
  lxd:
Installed: 2.0.0-0ubuntu4
Candidate: 2.0.0-0ubuntu4
Version table:
   *** 2.0.0-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3. lxc launch ubuntu-daily:xenial x1
  lxc exec x1 /bin/bash

  root@x1:~# hostnamectl status 
 Static hostname: x1
   Icon name: computer-container
 Chassis: container
  Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d
 Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca
  Virtualization: lxc
Operating System: Ubuntu 16.04 LTS
  Kernel: Linux 4.4.0-18-generic
Architecture: x86-64

  
  4. hostnamectl status hangs indefinitely

  On the host, there are some audit messages for each invocation of
  hostnamectl

  [411617.032274] audit: type=1400 audit(1461695563.731:100):
  apparmor="DENIED" operation="file_lock" profile="lxd-
  x1_" pid=17100 comm="(ostnamed)" family="unix"
  sock_type="dgram" protocol=0 addr=none

  It's related to socket activation.  One can workaround this by running
  systemd-hostnamed in the background first

  root@x1:~# /lib/systemd/systemd-hostnamed & 
  [1] 2462
  root@x1:~# hostnamectl status 
 Static hostname: x1
   Icon name: computer-container
 Chassis: container
  Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d
 Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca
  Virtualization: lxc
Operating System: Ubuntu 16.04 LTS
  Kernel: Linux 4.4.0-18-generic
Architecture: x86-64

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed Apr 27 11:19:27 2016
  InstallationDate: Installed on 2016-01-01 (117 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e0b8b294-f364-4ef5-aa70-1916cdd37192 ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution

2017-06-12 Thread David Britton

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

** Also affects: apt via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864681
   Importance: Unknown
   Status: Unknown

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

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-
  daily.service execution

Status in APT:
  Unknown
Status in cloud-init:
  Confirmed
Status in apt package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Confirmed

Bug description:
  apt-daily is now a systemd service rather than being invoked by
  cron.daily.  If one builds a custom AMI it is possible that the apt-
  daily.timer will fire during boot.  This can fire at the same time
  cloud-init is running and if cloud-init loses the race the invocation
  of apt (e.g. use of "packages:" in the config) will fail.

  There is a lot of discussion online about this change to apt-daily
  (e.g. unattended upgrades happening during business hours, delaying
  boot, etc.) and discussion of potential systemd changes regarding
  timers firing during boot (c.f.
  https://github.com/systemd/systemd/issues/5659).

  While it would be better to solve this in apt itself, I suggest that
  cloud-init be defensive when calling apt and implement some retry
  mechanism.

  Various instances of people running into this issue:

  https://github.com/chef/bento/issues/609
  https://clusterhq.atlassian.net/browse/FLOC-4486
  https://github.com/boxcutter/ubuntu/issues/73
  
https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image

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

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

[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

2017-06-12 Thread RumtumTugger

I did as described by Tokyobadger
https://ubuntuforums.org/archive/index.php/t-2347827.html on 18may2017,
and the problem has vanished unti now (12jun2017).

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  
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
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
pr500k-9912ec-1  36301ded-0ac5-4a86-9621-87290ef159af  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
   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

[Touch-packages] [Bug 1696480] Re: python3-dbusmock / test_no_adapters test fails with bluez 5.45

This bug was fixed in the package python-dbusmock - 0.16.8-1

---
python-dbusmock (0.16.8-1) unstable; urgency=medium

  * New upstream release:
- bluez5 template tests: Fix failure of test_no_adapters with BlueZ 5.45.
  (LP: #1696480)

 -- Martin Pitt   Mon, 12 Jun 2017 13:57:49 +0200

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

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

Title:
  python3-dbusmock / test_no_adapters test fails with bluez 5.45

Status in python-dbusmock:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in python-dbusmock package in Ubuntu:
  Fix Released

Bug description:
  
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#bluez
  http://autopkgtest.ubuntu.com/packages/p/python-dbusmock/artful/amd64

  With bluez 5.45 python3-dbusmock tests fail with:

  ==
  FAIL: test_no_adapters (__main__.TestBlueZ5)
  --
  Traceback (most recent call last):
    File "./test_bluez5.py", line 107, in test_no_adapters
  self.assertEqual([l for l in out if 'Waiting to connect' not in l], [])
  AssertionError: Lists differ: ['org.freedesktop.DBus.Mock.MethodCalled', 
'registered', 'unregistered'] != []

  First list contains 3 additional elements.
  First extra element 0:
  'org.freedesktop.DBus.Mock.MethodCalled'

  - ['org.freedesktop.DBus.Mock.MethodCalled', 'registered', 'unregistered']
  + []

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.45-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun  7 18:01:13 2017
  InstallationDate: Installed on 2013-09-03 (1372 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InterestingModules: bnep bluetooth
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:

  rfkill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  upstart.bluetooth.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-dbusmock/+bug/1696480/+subscriptions

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

[Touch-packages] [Bug 1697153] Re: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal

Take a look at the link in my previous message; it essentially boils
down to:

sudo apt-get install -f --reinstall libnl-genl-3-200

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

Title:
  package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
  install/upgrade: Paket ist in einem sehr schlechten inkonsistenten
  Zustand - Sie sollten es  nochmal installieren, bevor Sie die
  Konfiguration versuchen.

Status in libnl3 package in Ubuntu:
  Incomplete

Bug description:
  linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ...
  Fehler traten auf beim Bearbeiten von:
   libnl-genl-3-200:amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libnl-3-200: Install
   libnl-3-200: Configure
   libnl-genl-3-200: Configure
   libnl-route-3-200: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jun 10 10:30:10 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   libnl-3-200 3.2.27-1ubuntu0.16.04.1
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  InstallationDate: Installed on 2016-04-03 (432 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libnl3
  Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - 
Sie sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago)

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

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

[Touch-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

2017-06-12 Thread GreyBox

Hi Daniel,

>> On that note, can anyone confirm if Ubuntu 17.04 (pulseaudio 10.0) has fixed 
>> this bug?
I can confirm that unfortunately fresh Ubuntu 17.04 has this bug on my laptop.

lsb_release -a
Release:17.04
(last updates using apt dist-upgrade)

lspci | grep Ath
04:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network 
Adapter (rev 32)
06:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet 
Controller (rev 10)

headphone:
Jabra Talk

grep blue /var/log/syslog
pulseaudio[1443]: [pulseaudio] module-bluez5-device.c: Refused to switch 
profile to a2dp_sink: Not connected

script (temporary) fixes this issue:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1577197/comments/34

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Incomplete
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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

[Touch-packages] [Bug 1697535] [NEW] Envy24 ICE1724 doesn't work

2017-06-12 Thread Ben Buehler

Public bug reported:

Release: Ubuntu 17.04
PulseAudio Version: 1:10.0-1ubuntu2
I expected the audio on my system to work without any additional action on my 
part. Instead, the audio does not work despite working on Windows.

A few years ago, my onboard sound broke so I bought a pci sound card
(ENCORE ENM232-8VIA 7.1) which seems to have the Envy24 ICE1724 chipset.
This sound card works on Windows but not Ubuntu or Debian. I've
attempted to troubleshoot this myself over the past year or so and had
no luck figuring out the problem (though ubuntu-bug seems to think there
is a problem with pulseaudio).

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CurrentDesktop: Unity:Unity7
Date: Mon Jun 12 14:00:25 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-12-10 (184 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to zesty on 2017-04-18 (55 days ago)
dmi.bios.date: 09/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1104
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5QL-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 2.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1104:bd09/11/2009:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5QL-E
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug zesty

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

Title:
  Envy24 ICE1724 doesn't work

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 17.04
  PulseAudio Version: 1:10.0-1ubuntu2
  I expected the audio on my system to work without any additional action on my 
part. Instead, the audio does not work despite working on Windows.

  A few years ago, my onboard sound broke so I bought a pci sound card
  (ENCORE ENM232-8VIA 7.1) which seems to have the Envy24 ICE1724
  chipset. This sound card works on Windows but not Ubuntu or Debian.
  I've attempted to troubleshoot this myself over the past year or so
  and had no luck figuring out the problem (though ubuntu-bug seems to
  think there is a problem with pulseaudio).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 12 14:00:25 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-12-10 (184 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (55 days ago)
  dmi.bios.date: 09/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1104
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QL-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 2.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1104:bd09/11/2009:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:

[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"

This bug was fixed in the package qtbase-opensource-src - 5.5.1+dfsg-
16ubuntu7.5

---
qtbase-opensource-src (5.5.1+dfsg-16ubuntu7.5) xenial; urgency=medium

* Backport upstream change to fix behavior of QMenuBar::isNativeMenuBar()
method (fix_isNativeMenuBar.diff). This should finally fix LP: #1380702.

-- Dmitry Shachnev Wed, 03 May 2017 22:22:47
+0300

** Changed in: qtbase-opensource-src (Ubuntu Xenial)
Status: Fix Committed => Fix Released

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

Title:
Please consider SRU of "xcb: Compress mouse motion and touch update
events"

Status in qtbase-opensource-src package in Ubuntu:
Fix Released
Status in qtbase-opensource-src source package in Xenial:
Fix Released

Bug description:
Mouse event compression stopped working in Qt 5, a regression from Qt
4:

https://bugreports.qt.io/browse/QTBUG-40889

The bug was fixed in Qt 5.6 https://codereview.qt-
project.org/#/c/126136/ where the fix has been thoroughly tested by
now.

Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a
backport of the 5.6 patch (only one trivial hunk failed, which was
easily fixed).

[Impact]

[Test Case]

With the attached patch (and with Qt 4), the problem is gone - the
mouse event stream is compressed and the printouts are no longer
lagging behind.

[Regression Potential]

I'm asking for someone to nominate this bug for an SRU of 16.04 LTS.

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

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

[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps

This bug was fixed in the package qtbase-opensource-src - 5.5.1+dfsg-
16ubuntu7.5

---
qtbase-opensource-src (5.5.1+dfsg-16ubuntu7.5) xenial; urgency=medium

  * Backport upstream change to fix behavior of QMenuBar::isNativeMenuBar()
method (fix_isNativeMenuBar.diff). This should finally fix LP: #1380702.

 -- Dmitry Shachnev   Wed, 03 May 2017 22:22:47
+0300

** Changed in: qtbase-opensource-src (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Released
Status in qtbase-opensource-src source package in Yakkety:
  Confirmed

Bug description:
  Impact
  ==

  This affects all Qt applications on Unity and other desktops which use
  global menu, either via appmenu-qt5 or via native implementation on
  Yakkety.

  Any shortcut is not working if the corresponding action is attached
  only to the menubar (i.e. and not also to the toolbar). It can be
  reproduced with almost any application by removing the toolbar (right-
  clicking on it and deselecting it).

  Test Case
  =

  * Open Qt Assistant;
  * Press Ctrl+T (this action is not on the toolbar).

  Expected: a new tab should be opened. Current result: nothing happens.

  In Yakkety the fix should work both with and without appmenu-qt5.

  Proposed Fix
  

  The proposed fix is a backport of the upstream fix at
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594.

  Actually just the qshortcut.cpp part would be sufficient, but the
  other parts make sure it plays fine together with https://cgit.kde.org
  /plasma-integration.git/commit/?id=aef74e97e2ed462a.

  Regression Potential
  

  The fix is in Zesty for 1½ months now (in upstream even longer), and
  so far nobody complained. People have verified that the fix works (see
  comment #63).

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

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

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

I just tried the workaround Kai-Heng mentioned in #9 above: I added
'DNSSEC=off' to /etc/systemd/resolved.conf, then rebooted.
Unfortunately I'm still seeing this CPU problem.

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C

[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution

2017-06-12 Thread David Britton

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

** No longer affects: apt (Ubuntu Zesty)

** No longer affects: apt (Ubuntu Yakkety)

** No longer affects: apt (Ubuntu Xenial)

** No longer affects: apt (Ubuntu Artful)

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

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-
  daily.service execution

Status in cloud-init:
  Confirmed
Status in apt package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Confirmed

Bug description:
  apt-daily is now a systemd service rather than being invoked by
  cron.daily.  If one builds a custom AMI it is possible that the apt-
  daily.timer will fire during boot.  This can fire at the same time
  cloud-init is running and if cloud-init loses the race the invocation
  of apt (e.g. use of "packages:" in the config) will fail.

  There is a lot of discussion online about this change to apt-daily
  (e.g. unattended upgrades happening during business hours, delaying
  boot, etc.) and discussion of potential systemd changes regarding
  timers firing during boot (c.f.
  https://github.com/systemd/systemd/issues/5659).

  While it would be better to solve this in apt itself, I suggest that
  cloud-init be defensive when calling apt and implement some retry
  mechanism.

  Various instances of people running into this issue:

  https://github.com/chef/bento/issues/609
  https://clusterhq.atlassian.net/browse/FLOC-4486
  https://github.com/boxcutter/ubuntu/issues/73
  
https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1693361/+subscriptions

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

[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2017-06-12 Thread Kai Holthaus

@nacc: The system was originally installed with Ubuntu Server 14.04. It
has been upgraded to 16.04.

apt policy open-iscsi:
open-iscsi:
  Installed: 2.0.873+git0.3b4b4500-14ubuntu3.3
  Candidate: 2.0.873+git0.3b4b4500-14ubuntu3.3
  Version table:
 *** 2.0.873+git0.3b4b4500-14ubuntu3.3 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2.0.873+git0.3b4b4500-14ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
 2.0.873-3ubuntu13 500
500 http://us.archive.ubuntu.com/ubuntu wily/main amd64 Packages

Modifying those two lines in /lib/systemd/system/open-iscsi.service does not 
have any effect - I'm still running into the timeout.
I have attached a new journal.txt (per instructions in #8). This time, the 
error message is
logout-all.sh[2206]: iscsiadm: No matching sessions found

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+attachment/4894804/+files/journal.txt

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Touch-packages] [Bug 1647638] Re: W: APT had planned for dpkg to do more than it reported back

I went looking through foundations team package bug reports with this
same error message and only found one:

[ 10:39AM 10167 ]  [ bdmurray@impulse:/misc/bug-attach ]
 $ for atlog in $(find . -name VarLogDistupgradeApttermlog.gz); do zgrep "APT 
had planned for dpkg to do more than it reported back" $atlog; done
[ 10:43AM 10168 ]  [ bdmurray@impulse:/misc/bug-attach ]
 $ grep -r "APT had planned for dpkg to do more than it reported back" *
apt/bug-1647638/Description.txt:W: APT had planned for dpkg to do more than it 
reported back (4 vs 6).
debconf/bug-1696989/Description.txt:W: APT had planned for dpkg to do more than 
it reported back (40 vs 44).

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

Title:
  W: APT had planned for dpkg to do more than it reported back

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I noticed that base-files was not completely installed and meant to
  fix it with "sudo apt-get install --reinstall base-files". This
  resulted in the following output.

  $ LANG=C sudo apt-get install --reinstall base-files
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-4.9.0-4 linux-headers-4.9.0-4-generic 
linux-image-4.9.0-4-generic linux-image-extra-4.9.0-4-generic
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 13 not upgraded.
  Need to get 0 B/56,9 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 598721 files and directories currently installed.)
  Preparing to unpack .../base-files_9.6ubuntu8_amd64.deb ...
  Unpacking base-files (9.6ubuntu8) over (9.6ubuntu8) ...
  Setting up base-files (9.6ubuntu8) ...
  Processing triggers for install-info (6.3.0.dfsg.1-1) ...
  Processing triggers for cracklib-runtime (2.9.2-3) ...
  Processing triggers for plymouth-theme-ubuntu-gnome-text (16.10.5) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for man-db (2.7.5-2) ...
  Processing triggers for initramfs-tools (0.125ubuntu8) ...
  update-initramfs: Generating /boot/initrd.img-4.9.0-8-generic
  W: APT had planned for dpkg to do more than it reported back (4 vs 6).
 Affected packages: base-files:amd64

  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty

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

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

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

I've also run into this CPU problem on 17.04.  Like tlk, I had to
install dnsmasq because I'm running a hotspot on a USB wifi device, and
the system log indicated that it wouldn't work unless dnsmasq is
installed.

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

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version:

[Touch-packages] [Bug 1681513] Re: Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi adapters from working (mac address randomization)

The solution in comment #1 fixed this for me as well.  I'm running 17.04
and am hosting a hotspot on a  ThinkPenguin Wireless N USB Adapter.  It
didn't work until I applied this workaround.

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

Title:
  Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi
  adapters from working (mac address randomization)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

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

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

[Touch-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

2017-06-12 Thread Giacomo Orlandi

@Kai-Heng I use a Dell E-Port Plus.

This is my ouput of lsmod | grep i915:
i915_bpo 1302528  5
intel_ips  20480  1 i915_bpo
i2c_algo_bit   16384  1 i915_bpo
drm_kms_helper155648  1 i915_bpo
drm   364544  6 i915_bpo,drm_kms_helper
video  40960  3 i915_bpo,dell_wmi,dell_laptop

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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 Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  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.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://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 1697153] Re: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es noch

2017-06-12 Thread Manfred

What Commands do I need to enter? 
Later the day it seems that I could install a new kernel. May try it the next 
two days again, before heading it vacation till end of June ;-) 

MANFRED

Am 12.06.2017 um 18:47 schrieb Joshua Powers
:

>> From terminal log (translated):
> 
> Dpkg: Error processing package libnl-genl-3-200: amd64 (--configure):
> Package is in a very bad inconsistent condition - you should get it
> Again before attempting the configuration.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1697153
> 
> Title:
>  package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
>  install/upgrade: Paket ist in einem sehr schlechten inkonsistenten
>  Zustand - Sie sollten es  nochmal installieren, bevor Sie die
>  Konfiguration versuchen.
> 
> Status in libnl3 package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ...
>  Fehler traten auf beim Bearbeiten von:
>   libnl-genl-3-200:amd64
>  E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
>  ProblemType: Package
>  DistroRelease: Ubuntu 16.04
>  Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1
>  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
>  Uname: Linux 4.4.0-78-generic x86_64
>  ApportVersion: 2.20.1-0ubuntu2.6
>  AptOrdering:
>   libnl-3-200: Install
>   libnl-3-200: Configure
>   libnl-genl-3-200: Configure
>   libnl-route-3-200: Configure
>   NULL: ConfigurePending
>  Architecture: amd64
>  Date: Sat Jun 10 10:30:10 2017
>  Dependencies:
>   gcc-6-base 6.0.1-0ubuntu1
>   libc6 2.23-0ubuntu7
>   libgcc1 1:6.0.1-0ubuntu1
>   libnl-3-200 3.2.27-1ubuntu0.16.04.1
>  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - 
> Sie sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
>  InstallationDate: Installed on 2016-04-03 (432 days ago)
>  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
>  RelatedPackageVersions:
>   dpkg 1.18.4ubuntu1.2
>   apt  1.2.20
>  SourcePackage: libnl3
>  Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
> install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - 
> Sie sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
>  UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1697153/+subscriptions

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

Title:
  package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
  install/upgrade: Paket ist in einem sehr schlechten inkonsistenten
  Zustand - Sie sollten es  nochmal installieren, bevor Sie die
  Konfiguration versuchen.

Status in libnl3 package in Ubuntu:
  Incomplete

Bug description:
  linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ...
  Fehler traten auf beim Bearbeiten von:
   libnl-genl-3-200:amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libnl-3-200: Install
   libnl-3-200: Configure
   libnl-genl-3-200: Configure
   libnl-route-3-200: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jun 10 10:30:10 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   libnl-3-200 3.2.27-1ubuntu0.16.04.1
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  InstallationDate: Installed on 2016-04-03 (432 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libnl3
  Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - 
Sie sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago)

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

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

[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2017-06-12 Thread Nish Aravamudan

@Kai: Hrm, that is odd -- was your 16.04 system the fresh install or an
upgraded one?

The lines I pasted in #49 are supposed to be present in 16.04 (afaict).

If they don't, can you provide `apt policy open-iscsi` in a pastebin?
And can you test if changing those lines to match fixes the issue there?

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser

2017-06-12 Thread Adam Conrad

** Also affects: click (Ubuntu Artful)
   Importance: Undecided
 Assignee: Sergio Schvezov (sergiusens)
   Status: Fix Released

** Also affects: click (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Break the conflicts with click the optparser

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Xenial:
  New
Status in click source package in Yakkety:
  New
Status in click source package in Zesty:
  New
Status in click source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * python-click and python-click-package conflict as they use the same
 python package for its implementation.

   * Since python-click-package is an implementation detail for the click 
 package and python3-click is a package meant to be used in other
 implementations it makes sense to break the conflict by moving the
 package name for python-click-package to a different name

   * snapcraft has moved from docopt to python3-click, users that have click
 installed don't have an upgrade path.his bug.

  [Test Case]

   * Where snapcraft 2.30 is present:
 
 - apt install click
 - Install snapcraft << 2.30
 - update to snapcraft >= 2.30
 - the upgrade should not be held on any package.
 - click and snapcraft commands should work.

  * Install python3-click and click should be possible. The click command
should keep working and python3 -c 'from click import group' shall work.

  
  [Regression Potential] 

   * Users depending on click from python-click-package will be importing an
 unexpected click in any scripts they may have.

  [Other Info]
   
   * While unfortunate, click as a technology is deprecated and not used
 anymore. This resolution path was discussed with slangasek and apw prior
 to any work.

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

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

[Touch-packages] [Bug 1278780] Re: apport takes too long to write crash report, appears to lock up phone

2017-06-12 Thread Steve Langasek

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

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

Title:
  apport takes too long to write crash report, appears to lock up phone

Status in Apport:
  Confirmed
Status in Canonical System Image:
  Invalid
Status in apport package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Invalid

Bug description:
  I can trigger a crash easily on my phone via bug 1262711. Other bugs
  are available.

  When that happens my phone appears to freeze. I am unable to do
  anything for approximately 1 to 1.5 minutes. As a user my initial gut
  reaction is to reboot the phone, thus losing the crash report, and
  wasting my time.

  Having the phone lock up for 1.5 minutes is a terrible user
  experience. Can we fix/mitigate/workaround that?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.13.2-0ubuntu2
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: armhf
  CrashReports:
   664:32011:110:10083:2014-02-10 15:41:18.152893384 +:2014-02-10 
15:11:09.169231740 
+:/var/crash/_usr_lib_arm-linux-gnueabihf_upstart-app-launch_desktop-hook.32011.crash
   640:0:110:1681527:2014-02-10 15:12:10.985193887 +:2014-02-10 
15:12:05.639489630 +:/var/crash/_usr_bin_powerd.0.crash
   640:0:110:21384:2014-02-11 07:58:44.876281991 +:2014-02-11 
07:58:44.876281991 +:/var/crash/_usr_sbin_system-image-dbus.0.crash
   640:32011:110:17122318:2014-02-11 09:19:49.915478726 +:2014-02-11 
09:18:20.850439824 +:/var/crash/_usr_bin_unity8.32011.crash
  Date: Tue Feb 11 09:20:15 2014
  InstallationDate: Installed on 2014-02-11 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140211)
  PackageArchitecture: all
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1593907] Re: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCRIPTION], just

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

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

Title:
  ntpdate startup routine prevents ntp service from launching up on
  Ubuntu 16.04 server on system boot; manually starting ntp service
  works: [FIX in DESCRIPTION], just need to apply it and release a new
  version

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  I've installed ntp service on the clean ubuntu 16.04 server system. 
Configured it. Checked that it works, but, after reboot, it doesn't start 
automatically.
  When I check: 'systemctl is-enabled ntp', it shows enabled.
  If I manually start it 'systemctl start ntp' it starts just fine and woks 
correctly,
  but until I manually start it, 'systemctl status ntp' shows:

  Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
  Active: inactive (deadi)

  Installed 1.29ubuntu2 version of init-systems-helper, but it didn't
  fix the problem.

  Found a bugreport on ntpd package:

  https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596

  led to solution that involves a change to be made in file:

  /etc/network/if-up.d/ntpdate

  of ntpdate package

  After changing from:
  __CODE_START__

  invoke-rc.d --quiet $service stop >/dev/null 2>&1 || true

   # Avoid running more than one at a time
   flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null 
|| :

  invoke-rc.d --quiet $service start >/dev/null 2>&1 || true

  __CODE_END__

  to:
  __CODE_START__

  systemctl --quiet stop $service.service >/dev/null 2>&1 || true

   # Avoid running more than one at a time
   flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null 
|| :

  systemctl --quiet start $service.service >/dev/null 2>&1 || true

  __CODE_END__

  ntpd service started launching on boot.

  System Information:

    lsb_release -rd:

  Description:Ubuntu 16.04 LTS
  Release:16.04

    apt-cache policy ntpdate:

  ntpdate:
    Установлен: 1:4.2.8p4+dfsg-3ubuntu5
    Кандидат:   1:4.2.8p4+dfsg-3ubuntu5
    Таблица версий:
   *** 1:4.2.8p4+dfsg-3ubuntu5 500
  500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1697153] Re: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal

>From terminal log (translated):

Dpkg: Error processing package libnl-genl-3-200: amd64 (--configure):
 Package is in a very bad inconsistent condition - you should get it
 Again before attempting the configuration.

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

Title:
  package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
  install/upgrade: Paket ist in einem sehr schlechten inkonsistenten
  Zustand - Sie sollten es  nochmal installieren, bevor Sie die
  Konfiguration versuchen.

Status in libnl3 package in Ubuntu:
  Incomplete

Bug description:
  linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ...
  Fehler traten auf beim Bearbeiten von:
   libnl-genl-3-200:amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libnl-3-200: Install
   libnl-3-200: Configure
   libnl-genl-3-200: Configure
   libnl-route-3-200: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jun 10 10:30:10 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   libnl-3-200 3.2.27-1ubuntu0.16.04.1
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  InstallationDate: Installed on 2016-04-03 (432 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libnl3
  Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - 
Sie sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago)

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

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

[Touch-packages] [Bug 1697375] Re: crash reports are not uploaded automatically

** Changed in: whoopsie (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: whoopsie (Ubuntu)
Milestone: None => ubuntu-17.06

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

Title:
  crash reports are not uploaded automatically

Status in whoopsie package in Ubuntu:
  New

Bug description:
  On artful crash reports are not uploaded automatically (several .crash
  files in /var/crash and no corresponding upload or .uploaded files)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: whoopsie 0.2.56
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 12 09:39:29 2017
  InstallationDate: Installed on 2013-09-03 (1377 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1697153] Re: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal

Thank you for taking the time to file a bug report.

One of your packages is reporting that it is in an inconsistent state. This
needs to be solved before you continue further operations. To help you get
started please see this question and response:
https://askubuntu.com/questions/148715/how-to-fix-package-is-in-a-very-bad-inconsistent-state-error

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

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

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

Title:
  package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
  install/upgrade: Paket ist in einem sehr schlechten inkonsistenten
  Zustand - Sie sollten es  nochmal installieren, bevor Sie die
  Konfiguration versuchen.

Status in libnl3 package in Ubuntu:
  Incomplete

Bug description:
  linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ...
  Fehler traten auf beim Bearbeiten von:
   libnl-genl-3-200:amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libnl-3-200: Install
   libnl-3-200: Configure
   libnl-genl-3-200: Configure
   libnl-route-3-200: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jun 10 10:30:10 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   libnl-3-200 3.2.27-1ubuntu0.16.04.1
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  InstallationDate: Installed on 2016-04-03 (432 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libnl3
  Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - 
Sie sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago)

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

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

[Touch-packages] [Bug 1584575] Re: /lib/systemd/system/lightdm.service file has no [Install] clause

2017-06-12 Thread Craig

I too needed to re-enable graphical login after having disabled it.

I can confirm adding:

[Install]
Alias=display-manager.service

to my /lib/systemd/system/lightdm.service file.

Allowed me to re-enable lightdm to start on boot (by running "sudo
systemctl enable lightdm"), previous to this I would end up booting to a
black screen with a flashing cursor in the top left.  Ctrl+Alt+F1 (for
VT1) etc... would lead me to the login prompts, Ctrl+Alt+F7 leads me
back to the screen with the flashing cursor (VT7).

So for me Ubuntu was expecting a graphical interface to be running and
had me on VT7 at boot.  Logging in from one of the other terminals
showed lightdm to be stopped ("systemctl status lightdm").  Prior to the
fix above I would have to manually start lightdm by logging in and
running "sudo systemctl start lightdm"

I hope the above helps anyone googling the issue as it took me a couple
of hours to track down why it wasn't starting when I thought it was re-
enabled.

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

Title:
  /lib/systemd/system/lightdm.service file has no [Install] clause

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  This concerns lightdm 1.18.1-0ubuntu1 in Xenial.

  The /lib/systemd/system/lightdm.service file lacks an [Install]
  clause. Meaning, that if you do

  # systemctl disable display-manager

  to prevent LightDM from starting, running

  # systemctl enable lightdm

  does not restore the /etc/systemd/system/display-manager.service
  symlink, and thus does not re-enable LightDM to run at the next boot
  as intended.

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

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

[Touch-packages] [Bug 1697502] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-06-12 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1688721, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  Was trying to install slack

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon Jun 12 12:30:10 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-12 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1697502] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-06-12 Thread ursa

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

Public bug reported:

Was trying to install slack

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Mon Jun 12 12:30:10 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-12 (0 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  Was trying to install slack

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon Jun 12 12:30:10 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-12 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1697335] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: el paquete libssl1.0.0:amd64 no está listo para configurarse no se puede configurar (estado a

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

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

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  el paquete libssl1.0.0:amd64 no está listo para configurarse  no se
  puede configurar (estado actual `half-installed')

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  Desconozco lo que sucede.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   linux-libc-dev: Install
   libssl1.0.0: Configure
   linux-libc-dev: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun 11 20:22:48 2017
  ErrorMessage: el paquete libssl1.0.0:amd64 no está listo para configurarse  
no se puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2016-11-20 (203 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
el paquete libssl1.0.0:amd64 no está listo para configurarse  no se puede 
configurar (estado actual `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1697481] Re: totem-video-thumbnailer crashed with signal 5 in g_malloc()

2017-06-12 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1697234, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1697481/+attachment/4894670/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1697481/+attachment/4894672/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1697481/+attachment/4894677/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1697481/+attachment/4894678/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1697481/+attachment/4894679/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1697481/+attachment/4894680/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1697481/+attachment/4894681/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1697234

** Tags removed: need-amd64-retrace

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

Title:
  totem-video-thumbnailer crashed with signal 5 in g_malloc()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Every time I open a folder with MTS video files the video thumbnailer
  crashes. It would be ok, if it just failed gracefully.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Jun 12 16:58:17 2017
  ExecutablePath: /usr/bin/totem-video-thumbnailer
  InstallationDate: Installed on 2016-09-09 (275 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 
file:///media/username/0123-4567/PRIVATE/AVCHD/BDMV/STREAM/00139.MTS 
/tmp/.gnome_desktop_thumbnail.59DG1Y
  Signal: 5
  SourcePackage: gstreamer1.0
  StacktraceTop:
   g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   gst_buffer_new_allocate () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
  Title: totem-video-thumbnailer crashed with signal 5 in g_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: lxd sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1697481/+subscriptions

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

[Touch-packages] [Bug 1696981] Re: fixrtc is ineffective when there is no battery for the RTC

** Tags added: rls-aa-incoming

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

Title:
  fixrtc is ineffective when there is no battery for the RTC

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  When there is no battery for the RTC, fixrtc is not able to find a
  good enough date. To fix the clock, this script is using the last time
  the root filesystem was mounted, but as that is done before there is
  any network, and as after a reboot/poweroff the RTC time is always
  reset (because time is not kept due to lack of battery), the mount
  time will never be good.

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

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

[Touch-packages] [Bug 1697481] [NEW] totem-video-thumbnailer crashed with signal 5 in g_malloc()

2017-06-12 Thread fcole90

Public bug reported:

Every time I open a folder with MTS video files the video thumbnailer
crashes. It would be ok, if it just failed gracefully.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Jun 12 16:58:17 2017
ExecutablePath: /usr/bin/totem-video-thumbnailer
InstallationDate: Installed on 2016-09-09 (275 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 
file:///media/username/0123-4567/PRIVATE/AVCHD/BDMV/STREAM/00139.MTS 
/tmp/.gnome_desktop_thumbnail.59DG1Y
Signal: 5
SourcePackage: gstreamer1.0
StacktraceTop:
 g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
 gst_buffer_new_allocate () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
Title: totem-video-thumbnailer crashed with signal 5 in g_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: lxd sudo

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace third-party-packages xenial

** Information type changed from Private to Public

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

Title:
  totem-video-thumbnailer crashed with signal 5 in g_malloc()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Every time I open a folder with MTS video files the video thumbnailer
  crashes. It would be ok, if it just failed gracefully.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Jun 12 16:58:17 2017
  ExecutablePath: /usr/bin/totem-video-thumbnailer
  InstallationDate: Installed on 2016-09-09 (275 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 
file:///media/username/0123-4567/PRIVATE/AVCHD/BDMV/STREAM/00139.MTS 
/tmp/.gnome_desktop_thumbnail.59DG1Y
  Signal: 5
  SourcePackage: gstreamer1.0
  StacktraceTop:
   g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   gst_buffer_new_allocate () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
  Title: totem-video-thumbnailer crashed with signal 5 in g_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: lxd sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1697481/+subscriptions

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

[Touch-packages] [Bug 1553121] Re: Xenial preseed fails to load key for 3rd party repo with apt-setup/local0/key

2017-06-12 Thread Andy Newton

Just hit this same problem adding the Puppetlabs PC1 repo. As far as I
can tell, the key is deployed, but apt hasn't been updated to use it.

Installation halts at the "select packages" phase. At this point, if I
chroot into /target, the Puppet Labs GPG key is present but if I try to
install puppet-agent, it shows as unauthenticated.

If I run apt-get update and THEN try the install, puppet-agent is
installed OK.

Can confirm that the workaround still works (make PC1 the local1 repo).

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

Title:
  Xenial preseed fails to load key for 3rd party repo with apt-
  setup/local0/key

Status in apt-setup package in Ubuntu:
  Confirmed
Status in base-installer package in Ubuntu:
  Confirmed
Status in console-setup package in Ubuntu:
  Confirmed
Status in debian-installer package in Ubuntu:
  Confirmed

Bug description:
  I have an automated preseed installation that uses these lines to add
  custom repos during the installation:

  d-i apt-setup/local0/repository string deb http://jschule.github.io/ubuntu/ /
  d-i apt-setup/local0/comment string JTS local repository
  d-i apt-setup/local0/source boolean false
  d-i apt-setup/local0/key string http://jschule.github.io/ubuntu/repo.key

  d-i apt-setup/local1/repository string deb 
http://dl.google.com/linux/chrome/deb/ stable main
  d-i apt-setup/local1/comment string Google Chrome Browser
  d-i apt-setup/local1/source boolean false
  d-i apt-setup/local1/key string 
http://dl.google.com/linux/linux_signing_key.pub

  
(seehttps://github.com/jschule/ubuntu/blob/d46f1cef49ed71dc4bfe317119cccd3f39097ef4/preseed/jts.txt
  for complete preseed file that causes the problem).

  In xenial the installation fails because the GPG key for the local0
  repo is not loaded into the system so that it can be used (see
  screenshot). Strangely, "chroot /target apt-key list" shows the key
  9E62229E to be installed.

  Just to be sure that there is no problem with my repo and key I
  started the Xenial live CD and installed my repo there manually. All
  works well. IMHO this shows that the problem is clearly related to the
  automated installation with preseed.

  Maybe this is related to #1512347, that was the only thing I could
  find on Launchpad that is in the same area.

  If you want to reproduce this then you can checkout the scripts from
  https://github.com/jschule/ubuntu/tree/gh-pages/qemu and run "./run.sh
  xenial" to start my installation.

  I found a very ugly workaround by changing the apt-setup lines to
  this:

  d-i apt-setup/local0/repository string deb 
http://archive.canonical.com/ubuntu trusty partner
  d-i apt-setup/local0/source boolean false

  d-i apt-setup/local1/repository string deb http://jschule.github.io/ubuntu/ /
  d-i apt-setup/local1/comment string JTS local repository
  d-i apt-setup/local1/source boolean false
  d-i apt-setup/local1/key string http://jschule.github.io/ubuntu/repo.key

  d-i apt-setup/local2/repository string deb 
http://dl.google.com/linux/chrome/deb/ stable main
  d-i apt-setup/local2/comment string Google Chrome Browser
  d-i apt-setup/local2/source boolean false
  d-i apt-setup/local2/key string 
http://dl.google.com/linux/linux_signing_key.pub

  I suppose that the workaround works because now the local0 repo is one
  where the signing key is already part of Ubuntu. I just hope that
  there is no package in the trusty partner repo that is not also in the
  xenial partner repo.

  For me it is very important that you fix this bug before 16.04 is
  released so that I can continue to use Ubuntu with an automated setup.

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

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

[Touch-packages] [Bug 1697474] Automatically added comment

2017-06-12 Thread Will Cooke

Added to Trello: https://trello.com/c/UbW3eHud/135-bug1697474-map-of-
india-is-incorrect

** Tags removed: desktop-trello-import

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

Title:
  Map of India is incorrect

Status in libtimezonemap package in Ubuntu:
  Confirmed

Bug description:
  A correct map of India is shown here:

  https://www.mapsofworld.com/india/

  The map used in libtimezonemap needs to be updated to match.

  I'm reaching out to Prakash to get some exact details on what should
  be changed.

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

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

[Touch-packages] [Bug 1697474] [NEW] Map of India is incorrect

2017-06-12 Thread Will Cooke

Public bug reported:

A correct map of India is shown here:

https://www.mapsofworld.com/india/

The map used in libtimezonemap needs to be updated to match.

I'm reaching out to Prakash to get some exact details on what should be
changed.

** Affects: libtimezonemap (Ubuntu)
 Importance: High
 Assignee: Will Cooke (willcooke)
 Status: Confirmed

** Changed in: libtimezonemap (Ubuntu)
 Assignee: (unassigned) => Will Cooke (willcooke)

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

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

** Tags added: desktop-trello-import

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

Title:
  Map of India is incorrect

Status in libtimezonemap package in Ubuntu:
  Confirmed

Bug description:
  A correct map of India is shown here:

  https://www.mapsofworld.com/india/

  The map used in libtimezonemap needs to be updated to match.

  I'm reaching out to Prakash to get some exact details on what should
  be changed.

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

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

[Touch-packages] [Bug 1697353] Re: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyb

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

** Changed in: console-setup (Ubuntu)
   Status: New => Confirmed

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

Title:
  package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade:
  trying to overwrite '/lib/systemd/system/console-setup.service', which
  is also in package keyboard-configuration 1.108ubuntu15.3

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 16.04 LTS, try to use kali linux in ubuntu but get this bug.

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: console-setup-linux 1.108ubuntu15.3
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Mon Jun 12 05:36:54 2017
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.3
  InstallationDate: Installed on 2016-07-22 (324 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.2.20
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15.3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1696147] Re: apport failing to collect logs on armhf

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

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

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

Title:
  apport failing to collect logs on armhf

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I simply created the user and proceeded to install, and on the
  "creating user" portion of setup it crashed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubiquity 2.21.63.3
  Uname: Linux 4.4.38-v7+ armv7l
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: armhf
  Date: Tue Jun  6 11:04:46 2017
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/apport/+bug/1696147/+subscriptions

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

[Touch-packages] [Bug 840942] Re: set_size_request is ignored [update-manager details is one line]

2017-06-12 Thread David Pearson

Still Happening on AA (17.10)

see http://i.imgur.com/VlV1bxu.png

for how it looks in Xubuntu

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

Title:
  set_size_request is ignored [update-manager details is one line]

Status in aptdaemon package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in aptdaemon source package in Oneiric:
  Won't Fix
Status in gtk+3.0 source package in Oneiric:
  Won't Fix
Status in aptdaemon source package in Precise:
  Fix Released
Status in gtk+3.0 source package in Precise:
  Confirmed

Bug description:
  update-manager details is one line (the terminal when expanding the
  details expander). This way you can't see what happens and is the
  function useless

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: update-manager 1:0.152.17
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic i686
  Architecture: i386
  Date: Sun Sep  4 14:04:42 2011
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1080106] Re: top destroys readline's history-search-forward/backward

2017-06-12 Thread Bug Watch Updater

** Changed in: procps (Debian)
   Status: New => Fix Released

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

Title:
  top destroys readline's history-search-forward/backward

Status in procps package in Ubuntu:
  New
Status in procps package in Debian:
  Fix Released

Bug description:
  After running top (package procps Version: 1:3.3.3-2ubuntu3 on Ubuntu
  12.10), readline's history-search-forward and history-search-backward
  commands on the bash command line do not work.

  However, after running "less" on any file, the readline commands above
  work again.

  This bug is a known Debian bug as well: Bug #94
  (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=94)

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: procps 1:3.3.3-2ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sat Nov 17 10:43:29 2012
  InstallationDate: Installed on 2011-09-09 (435 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: procps
  UpgradeStatus: Upgraded to quantal on 2012-11-17 (0 days ago)

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

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

[Touch-packages] [Bug 1696480] Re: python3-dbusmock / test_no_adapters test fails with bluez 5.45

2017-06-12 Thread Martin Pitt

I released 0.16.8 upstream and uploaded it to Debian unstable, from
where it should autosync into Ubuntu devel soon.

** Changed in: python-dbusmock (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: python-dbusmock
   Status: Fix Committed => Fix Released

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

Title:
  python3-dbusmock / test_no_adapters test fails with bluez 5.45

Status in python-dbusmock:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in python-dbusmock package in Ubuntu:
  Fix Committed

Bug description:
  
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#bluez
  http://autopkgtest.ubuntu.com/packages/p/python-dbusmock/artful/amd64

  With bluez 5.45 python3-dbusmock tests fail with:

  ==
  FAIL: test_no_adapters (__main__.TestBlueZ5)
  --
  Traceback (most recent call last):
    File "./test_bluez5.py", line 107, in test_no_adapters
  self.assertEqual([l for l in out if 'Waiting to connect' not in l], [])
  AssertionError: Lists differ: ['org.freedesktop.DBus.Mock.MethodCalled', 
'registered', 'unregistered'] != []

  First list contains 3 additional elements.
  First extra element 0:
  'org.freedesktop.DBus.Mock.MethodCalled'

  - ['org.freedesktop.DBus.Mock.MethodCalled', 'registered', 'unregistered']
  + []

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.45-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun  7 18:01:13 2017
  InstallationDate: Installed on 2013-09-03 (1372 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InterestingModules: bnep bluetooth
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:

  rfkill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  upstart.bluetooth.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-dbusmock/+bug/1696480/+subscriptions

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

[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-06-12 Thread Timo Aaltonen

vulkan is on the upload queue along with libdrm, libwacom, xfonts-utils
and libclc

https://launchpad.net/ubuntu/xenial/+queue?queue_state=1

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in vulkan source package in Xenial:
  New
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

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

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

[Touch-packages] [Bug 1566930] Re: wget does not support IPv6 address with scoped zone (RFC 4007)

2017-06-12 Thread Adrian Schmutzler

Maybe this is helpful for fixing:
On a router with LEDE-based OS, I have two different "versions" of wget:

With full wget 1.18, I cannot use an IPv6 address with interface as
described above.

However, with the wget included in BusyBox v1.25.1, the same command is
working!

Command (in both cases):
wget http://[fe80::someip%br-mesh]/dev/firmware/current/release.nfo -P /tmp

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

Title:
  wget does not support IPv6 address with scoped zone (RFC 4007)

Status in wget package in Ubuntu:
  Confirmed

Bug description:
  IMPACT: wget is not usable in the default configuration for LXD
  containers in Xenial

  Summary: A scoped zone address in the form [%

[Touch-packages] [Bug 1689495] Re: unattended-upgrade crashed with AttributeError in _write(): 'NoneType' object has no attribute 'write'

2017-06-12 Thread Robie Basak

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  unattended-upgrade crashed with AttributeError in _write(): 'NoneType'
  object has no attribute 'write'

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  This happened after upgrading it to Artful.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.93.1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu6
  Architecture: amd64
  CrashCounter: 1
  Date: Tue May  9 08:20:24 2017
  ExecutablePath: /usr/bin/unattended-upgrade
  InstallationDate: Installed on 2017-05-05 (3 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/unattended-upgrade -d 3
  ProcEnviron:
   LANGUAGE=en_IE:en
   PATH=(custom, no user)
   LANG=en_IE.UTF-8
  PythonArgs: ['/usr/bin/unattended-upgrade', '-d', '3']
  SourcePackage: unattended-upgrades
  Title: unattended-upgrade crashed with AttributeError in _write(): 'NoneType' 
object has no attribute 'write'
  UpgradeStatus: Upgraded to artful on 2017-05-05 (3 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-06-12 Thread Sandeep

Hi,

Can someone please update about status of libvulkan1 package being back-
ported to Xenial.

Thanks,
~Sandeep

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in vulkan source package in Xenial:
  New
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

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

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

[Touch-packages] [Bug 1689495] Re: unattended-upgrade crashed with AttributeError in _write(): 'NoneType' object has no attribute 'write'

2017-06-12 Thread Robie Basak

The first I knew of it was an apport/whoopsie GUI popup, which then sent
me to this bug IIRC. I installed this machine fresh from an Artful
daily. The only relevant change I think I made was to add an apt proxy
in /etc/apt.conf.d/. I don't have any other information and didn't save
my traceback, assuming it was the same as in this report. I haven't seen
the issue since, though I don't know if that's due to whoopsie
suppression.

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

Title:
  unattended-upgrade crashed with AttributeError in _write(): 'NoneType'
  object has no attribute 'write'

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  This happened after upgrading it to Artful.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.93.1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu6
  Architecture: amd64
  CrashCounter: 1
  Date: Tue May  9 08:20:24 2017
  ExecutablePath: /usr/bin/unattended-upgrade
  InstallationDate: Installed on 2017-05-05 (3 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/unattended-upgrade -d 3
  ProcEnviron:
   LANGUAGE=en_IE:en
   PATH=(custom, no user)
   LANG=en_IE.UTF-8
  PythonArgs: ['/usr/bin/unattended-upgrade', '-d', '3']
  SourcePackage: unattended-upgrades
  Title: unattended-upgrade crashed with AttributeError in _write(): 'NoneType' 
object has no attribute 'write'
  UpgradeStatus: Upgraded to artful on 2017-05-05 (3 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

2017-06-12 Thread Lasse Kuusisto

I have the same problem on both wired and wireless. Today already four
times just randomly wired connection stopped working...

sudo lshw -class network
  *-network 
   description: Wireless interface
   product: Wireless 8260
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:02:00.0
   logical name: wlp2s0
   version: 3a
   serial: 14:ab:c5:2a:d5:1e
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=4.10.0-22-generic firmware=21.302800.0 ip=10.2.27.30 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
   resources: irq:287 memory:e110-e1101fff
  *-network
   description: Ethernet interface
   product: Ethernet Connection I219-V
   vendor: Intel Corporation
   physical id: 1f.6
   bus info: pci@:00:1f.6
   logical name: enp0s31f6
   version: 21
   serial: 3c:52:82:49:ed:95
   capacity: 1Gbit/s
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=3.2.6-k firmware=0.13-4 latency=0 link=no multicast=yes 
port=twisted pair
   resources: irq:279 memory:e140-e141
  *-network
   description: Ethernet interface
   physical id: 2
   logical name: enx6c0b84b29ded
   serial: 6c:0b:84:b2:9d:ed
   capabilities: ethernet physical
   configuration: broadcast=yes driver=cdc_ncm driverversion=22-Aug-2005 
firmware=CDC NCM link=yes multicast=yes

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic

[Touch-packages] [Bug 1681513] Re: Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi adapters from working (mac address randomization)

2017-06-12 Thread fantonia

My problem is a bit different. Eth0 connects at first but then
disconnects. Then reconnect and work for a short time. stress! I solved
it with wicd. I have a Huawei HG8346M router. I've tried other distro
but it's the same thing. Neon 17.10.

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

Title:
  Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi
  adapters from working (mac address randomization)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

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

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

[Touch-packages] [Bug 1697397] [NEW] libldap-2.4.42+dfsg-2ubuntu3.2 crashes libreoffice

2017-06-12 Thread jack

Public bug reported:

Running xubuntu xenial, and after a recent upgrade w/ the following:
libldap-2.4-2:i386 (2.4.42+dfsg-2ubuntu3.2) over (2.4.42+dfsg-2ubuntu3.1)

all libreoffice applications (calc, writer, etc) crash on start, with
the following error:

/usr/lib/libreoffice/program/soffice.bin: symbol lookup error:
/usr/lib/libreoffice/program/../program/libsclo.so: undefined symbol:
_ZN9ScrollBar8SetRangeERK5Range


after investigating, i figured out it seems to be linked to the libldap 
upgrade, and indeed as a temporary workaround downgrading to 
2.4.42+dfsg-2ubuntu3 allows libreoffice to work again.

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

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

Title:
  libldap-2.4.42+dfsg-2ubuntu3.2 crashes libreoffice

Status in openldap package in Ubuntu:
  New

Bug description:
  Running xubuntu xenial, and after a recent upgrade w/ the following:
  libldap-2.4-2:i386 (2.4.42+dfsg-2ubuntu3.2) over (2.4.42+dfsg-2ubuntu3.1)

  all libreoffice applications (calc, writer, etc) crash on start, with
  the following error:

  /usr/lib/libreoffice/program/soffice.bin: symbol lookup error:
  /usr/lib/libreoffice/program/../program/libsclo.so: undefined symbol:
  _ZN9ScrollBar8SetRangeERK5Range

  
  after investigating, i figured out it seems to be linked to the libldap 
upgrade, and indeed as a temporary workaround downgrading to 
2.4.42+dfsg-2ubuntu3 allows libreoffice to work again.

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-12 Thread Housni Alaoui

I was encountering DNS issues on Ubuntu 17.04 using OpenVPN.
Your patched NetworkManager worked for me Nicholas.
Thank you !

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

2017-06-12 Thread Sebastien Bacher

("in progress" is correct, "fix commited" should be set by the SRU team
when they accept the upload according to
https://wiki.ubuntu.com/StableReleaseUpdates)

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

Title:
[xenial] Bluetooth device doesn't play any sound in A2DP mode unless
set to HSP/HFP first

Status in bluez package in Ubuntu:
Invalid
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Xenial:
In Progress

Bug description:
[Impact]
Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP
first. A2DP is the high quality profile used for Bluetooth speakers and music
in general.

[Test Case]
1. Pair a Bluetooth audio device with Ubuntu.
2. Verify in Sound settings you have it set to A2DP mode.
3. Turn off and then on the Bluetooth device.
4. Verify the device has reconnected and if not, force it to in the Bluetooth
indicator menu.
5. Open Sound settings again, select the device and verify it's reappeared in
A2DP mode.
6. Click 'Test Sound'.
Expected: Sound can be heard from the Bluetooth device.

[Regression Potential]
Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main
area affected. A combination of related A2DP bugs in pulseaudio in xenial means
it is difficult to get working at all without this patch. So highly unlikely
Bluetooth audio support could get worse. Since pulseaudio itself is being
modified there is always a regression potential in support for other audio
devices, but several audio devices have been tested and all continue to work
well with the patch.

[Other notes]
Related to bug 1283003 and bug 1438510. Possibly others too.

Please note that Bluetooth and Bluetooth audio support in xenial is
still not perfect. This SRU only aims to address a few of the most
troublesome issues. Please consider the fact that this is an
incremental improvement and some people are still likely to experience
some bugs related to pulseaudio and Bluetooth, even after this SRU.

The patch was authored by Luke Yelavich with help from Konrad
Zapałowicz. And it has received further testing over the past two
months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
here only changes the changelog wording from Luke's original PPA.

[Original Description]
I have a Sennheiser MM 450-X headset.

In 15.10, connection & playback was straightforward.

In 16.04, the headset connects, and shows up as default playback
device on `pavucontrol`, but there is no sound.

A functional workaround is to, after having connected it, to go the
`Configuration` tab, and in the `Profile` dropdown, to choose `...
HSP/HFP`, which will make them play as expected (but in low quality),
then switch to `... A2DP Sink` (they will play in high quality).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm
nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: myuser2936 F pulseaudio
/dev/snd/controlC2: myuser2936 F pulseaudio
/dev/snd/controlC0: myuser2936 F pulseaudio
Date: Mon May 16 14:18:58 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-03-11 (66 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/22/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A88XN-WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

--
Mailing list:

[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

2017-06-12 Thread Sebastien Bacher

It has been sponsored but SRU go first to the "unapproved" queue where a SRU
team member need to review and accept them
https://launchpad.net/ubuntu/xenial/+queue?queue_state=1_text=pulseaudio

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

Title:
[xenial] Bluetooth device doesn't play any sound in A2DP mode unless
set to HSP/HFP first

Status in bluez package in Ubuntu:
Invalid
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Xenial:
In Progress

Bug description:
[Impact]
Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP
first. A2DP is the high quality profile used for Bluetooth speakers and music
in general.

[Other notes]
Related to bug 1283003 and bug 1438510. Possibly others too.

[Original Description]
I have a Sennheiser MM 450-X headset.

In 15.10, connection & playback was straightforward.

In 16.04, the headset connects, and shows up as default playback
device on `pavucontrol`, but there is no sound.

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

[Touch-packages] [Bug 1672171] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler() f

** Information type changed from Private to Public

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from profile_new_connection()
  from profile_handler() from _dbus_object_tree_dispatch_and_unlock()

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Bluetooth device keep disconnect and audio output tab is empty

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bikram14994 F pulseaudio
   /dev/snd/controlC0:  bikram14994 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: Unity:Unity7
  Date: Sun Mar 12 21:52:24 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_bluetooth_transport_set_state () from 
/usr/lib/pulse-10.0/modules/libbluez5-util.so
   ?? () from /usr/lib/pulse-10.0/modules/libbluez5-util.so
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
  Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_set_state()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0Y004V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn0Y004V:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3437
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1690028] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from endpoint_set_configuration() from endpoint_handle

2017-06-12 Thread Jean-Baptiste Lallement

** Tags added: artful

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from
  endpoint_set_configuration() from endpoint_handler() from
  _dbus_object_tree_dispatch_and_unlock()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5a76b9eca937daf6dc05fd32a35fa50e58ccf8f5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1697375] [NEW] crash reports are not uploaded automatically

2017-06-12 Thread Jean-Baptiste Lallement

Public bug reported:

On artful crash reports are not uploaded automatically (several .crash
files in /var/crash and no corresponding upload or .uploaded files)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: whoopsie 0.2.56
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jun 12 09:39:29 2017
InstallationDate: Installed on 2013-09-03 (1377 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: apport-noui N/A
SourcePackage: whoopsie
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful autoreport-false wayland-session

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

Title:
  crash reports are not uploaded automatically

Status in whoopsie package in Ubuntu:
  New

Bug description:
  On artful crash reports are not uploaded automatically (several .crash
  files in /var/crash and no corresponding upload or .uploaded files)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: whoopsie 0.2.56
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 12 09:39:29 2017
  InstallationDate: Installed on 2013-09-03 (1377 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1697375] Re: crash reports are not uploaded automatically

2017-06-12 Thread Jean-Baptiste Lallement

$ grep whoopsie /var/log/syslog
Jun 11 23:17:41 herm whoopsie[1027]: [00:17:41] offline
Jun 11 23:17:42 herm whoopsie[1027]: [00:17:42] Cannot reach: 
https://daisy.ubuntu.com
Jun 11 23:17:42 herm whoopsie[1027]: [00:17:42] Cannot reach: 
https://daisy.ubuntu.com
Jun 11 23:17:42 herm whoopsie[1027]: [00:17:42] Cannot reach: 
https://daisy.ubuntu.com
Jun 12 08:00:14 herm whoopsie[1027]: [09:00:14] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/12
Jun 12 08:00:14 herm whoopsie[1027]: [09:00:14] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/12
Jun 12 08:00:14 herm whoopsie[1027]: [09:00:14] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/12
Jun 12 08:00:14 herm whoopsie[1027]: [09:00:14] online
Jun 12 08:00:14 herm whoopsie[1027]: [09:00:14] offline
Jun 12 08:00:14 herm whoopsie[1027]: [09:00:14] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/12
Jun 12 08:00:14 herm whoopsie[1027]: [09:00:14] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/12
Jun 12 08:00:14 herm whoopsie[1027]: [09:00:14] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/12
Jun 12 08:00:14 herm whoopsie[1027]: [09:00:14] online
Jun 12 08:37:47 herm whoopsie[25826]: [09:37:47] Using lock path: 
/var/lock/whoopsie/lock
Jun 12 08:37:47 herm whoopsie[25826]: [09:37:47] Could not get the Network 
Manager state:
Jun 12 08:37:47 herm whoopsie[25826]: [09:37:47] 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: La propriété « state » 
n'existe pas

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

Title:
  crash reports are not uploaded automatically

Status in whoopsie package in Ubuntu:
  New

Bug description:
  On artful crash reports are not uploaded automatically (several .crash
  files in /var/crash and no corresponding upload or .uploaded files)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: whoopsie 0.2.56
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 12 09:39:29 2017
  InstallationDate: Installed on 2013-09-03 (1377 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1696978] Re: Mir locking up when switching VTs after stopping lightdm

** Summary changed:

- Mir locking up when switching VTs
+ Mir locking up when switching VTs after stopping lightdm

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

Title:
  Mir locking up when switching VTs after stopping lightdm

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  * stop lightdm
  * follow https://wiki.ubuntu.com/Process/Merges/TestPlans/Mir#Test_Plan

  Expected:
  * Switching to Mir VT works

  Current:
  * When trying to switch to the Mir VT, Mir locks up trying to render, never 
completing, and not handling Ctrl+Alt+F* presses

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

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

[Touch-packages] [Bug 1696978] Re: Mir locking up when switching VTs

2017-06-12 Thread Alan Griffiths

The essential step here is stopping lightdm. After which it seems Mir
fails to restart compositing when the VT switches back. This scenario is
low priority.

** Changed in: mir
   Status: Incomplete => Confirmed

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

** Changed in: mir
   Importance: High => Low

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

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

Title:
  Mir locking up when switching VTs

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  * stop lightdm
  * follow https://wiki.ubuntu.com/Process/Merges/TestPlans/Mir#Test_Plan

  Expected:
  * Switching to Mir VT works

  Current:
  * When trying to switch to the Mir VT, Mir locks up trying to render, never 
completing, and not handling Ctrl+Alt+F* presses

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

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2017-06-12 Thread Steve Langasek

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

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Confirmed
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 1692492] Re: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1