date:20170418

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

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

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

Title:
  System hangs randomly (log shows 'EQ overflowing').

Status in xorg package in Ubuntu:
  Expired

Bug description:
  X Server and then system freezes, ALT+CTRL+Fx doesn't work, sometimes even 
REISUB doesn't work.
  Memtest result is ok, no errors. HDD also is ok. Windows works perfectly on 
the machine.
  It's possible to login via SSH and reboot (but during reboot process it also 
often hangs completely).
  The problem occures randomly during every-day work (usually once or twice a 
day making me loose my work!), like with totally no adequate reasons.
  I'm using AMD Athlon 5350 (SocketAM1 APU) with radeon R3 integrated video.
  My operating system is Ubuntu 16.04.1 LTS with all the last available 
updates. Bug lasts throughout all the time. Tried to reinstall many times 
(MD5sum of the installation image was correct) - nothing changes.

  x-0.log in the attachment

  part of the log:
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x562fc426a5ce]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x562fc424c083]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x562fc4124662]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f7320d91000+0x61f3) 
[0x7f7320d971f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f7320d91000+0x6a5d) 
[0x7f7320d97a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x562fc40b8000+0x94228) [0x562fc414c228]
  (EE) 6: /usr/lib/xorg/Xorg (0x562fc40b8000+0xb96f2) [0x562fc41716f2]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f732524e000+0x354a0) 
[0x7f73252834a0]
  (EE) 8: /lib/x86_64-linux-gnu/libpthread.so.0 (pthread_cond_wait+0xbe) 
[0x7f732503e39e]
  (EE) 9: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x6b77fb) [0x7f731f3027fb]
  (EE) 10: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x6b87c1) [0x7f731f3037c1]
  (EE) 11: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x61bf52) [0x7f731f266f52]
  (EE) 12: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x6d521e) [0x7f731f32021e]
  (EE) 13: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x201de4) [0x7f731ee4cde4]
  (EE) 14: /usr/lib/xorg/modules/libglamoregl.so (glamor_block_handler+0x4b) 
[0x7f73204bcffb]
  (EE) 15: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f732133c000+0x471b2) 
[0x7f73213831b2]
  (EE) 16: /usr/lib/xorg/Xorg (_CallCallbacks+0x34) [0x562fc4111034]
  (EE) 17: /usr/lib/xorg/Xorg (WriteToClient+0x244) [0x562fc426e234]
  (EE) 18: /usr/lib/xorg/Xorg (WriteEventsToClient+0x1e2) [0x562fc4117022]
  (EE) 19: /usr/lib/xorg/Xorg (0x562fc40b8000+0x133b5f) [0x562fc41ebb5f]
  (EE) 20: /usr/lib/xorg/Xorg (DamageReportDamage+0x89) [0x562fc41f1359]
  (EE) 21: /usr/lib/xorg/Xorg (0x562fc40b8000+0x139c1a) [0x562fc41f1c1a]
  (EE) 22: /usr/lib/xorg/Xorg (0x562fc40b8000+0x13d140) [0x562fc41f5140]
  (EE) 23: /usr/lib/xorg/Xorg (0x562fc40b8000+0x4fb87) [0x562fc4107b87]
  (EE) 24: /usr/lib/xorg/Xorg (0x562fc40b8000+0x53bbf) [0x562fc410bbbf]
  (EE) 25: /usr/lib/xorg/Xorg (0x562fc40b8000+0x57c33) [0x562fc410fc33]
  (EE) 26: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f732526e830]
  (EE) 27: /usr/lib/xorg/Xorg (_start+0x29) [0x562fc40f9f59]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Sep 12 14:31:34 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400 / R3 Series] 
[1002:9830] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Kabini [Radeon HD 8400 
/ R3 Series] [1462:7865]
  InstallationDate: Installed on 2016-08-18 (25 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" -

[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

2017-04-18 Thread Nate Meyers

This bug has been submitted to the linux kernel bug tracker as well

https://bugzilla.kernel.org/show_bug.cgi?id=195457

** Bug watch added: Linux Kernel Bug Tracker #195457
   http://bugzilla.kernel.org/195457

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

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

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

[Touch-packages] [Bug 1664160] Re: [performance] Latency from client to screen is one frame higher under Unity8 than in other nested Mir servers

[Expired for Mir because there has been no activity for 60 days.]

** Changed in: mir
   Status: Incomplete => Expired

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

Title:
  [performance] Latency from client to screen is one frame higher under
  Unity8 than in other nested Mir servers

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Expired
Status in qtmir package in Ubuntu:
  Expired
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Latency from client to screen is one frame higher under Unity8 than in
  nested demo servers.

  While mirvanity is reporting around 50ms windowed under nested Mir
  demo servers, it can only achieve 66ms in Unity8 on the same machine
  with the same Mir release (0.26.1 prerelease).

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

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

[Touch-packages] [Bug 1664160] Re: [performance] Latency from client to screen is one frame higher under Unity8 than in other nested Mir servers

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

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

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

Title:
  [performance] Latency from client to screen is one frame higher under
  Unity8 than in other nested Mir servers

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Expired
Status in qtmir package in Ubuntu:
  Expired
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Latency from client to screen is one frame higher under Unity8 than in
  nested demo servers.

  While mirvanity is reporting around 50ms windowed under nested Mir
  demo servers, it can only achieve 66ms in Unity8 on the same machine
  with the same Mir release (0.26.1 prerelease).

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

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

[Touch-packages] [Bug 1664065] Re: Canon mf4880 driver and cups install correctly. but no print

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

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

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

Title:
  Canon mf4880 driver and cups install correctly. but no print

Status in cups package in Ubuntu:
  Expired

Bug description:
  Everything install correctly. printer was discovered in usb and
  network mode both. Print job with finish without error, but no print
  on the printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cups 2.1.3-4
  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
  Date: Sun Feb 12 16:43:21 2017
  InstallationDate: Installed on 2015-12-29 (411 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat: device for Canon_MF4800_Series: cnusb:/dev/usb/lp0
  MachineType: Acer Aspire TC-605
  Papersize: letter
  PpdFiles: Canon_MF4800_Series: Canon MF4800 Series UFRII LT ver.3.0
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=daaeeb49-534f-4636-895e-a56cafb78c19 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to yakkety on 2017-02-12 (0 days ago)
  dmi.bios.date: 03/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-A4
  dmi.board.name: Aspire TC-605
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-A4:bd03/21/2014:svnAcer:pnAspireTC-605:pvr:rvnAcer:rnAspireTC-605:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Aspire TC-605
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1664160] Re: [performance] Latency from client to screen is one frame higher under Unity8 than in other nested Mir servers

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

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

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

Title:
  [performance] Latency from client to screen is one frame higher under
  Unity8 than in other nested Mir servers

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Expired
Status in qtmir package in Ubuntu:
  Expired
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Latency from client to screen is one frame higher under Unity8 than in
  nested demo servers.

  While mirvanity is reporting around 50ms windowed under nested Mir
  demo servers, it can only achieve 66ms in Unity8 on the same machine
  with the same Mir release (0.26.1 prerelease).

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

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

[Touch-packages] [Bug 1662645] Re: owncloud account does NOT support httpS

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

** Changed in: account-plugins (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  owncloud account does NOT support httpS

Status in account-plugins package in Ubuntu:
  Expired

Bug description:
  Ubuntu 15.04 OTA14
  Clean system
  in the account page there is Ubuntu One and owncloud.

  When I try to set the URL of my owncloud server httpS://owncloud/owncloud,
  I get an "invalid URL error"

  It works fine with http://owncloud but this is not very secure,
  and this disable access to my owncloud from outside home : firewall
  allows only httpS.

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

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

[Touch-packages] [Bug 1652282] Re: Wayland default policy prohibits root applications

2017-04-18 Thread Jeremy Bicha

It was announced today that the Ubuntu Desktop Team currently intends to
default to GNOME on Wayland for Ubuntu 18.04 LTS.

** Tags removed: gnome3-ppa third-party-packages yakkety
** Tags added: wayland

** Package changed: wayland (Ubuntu) => gparted (Ubuntu)

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

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

** Summary changed:

- Wayland default policy prohibits root applications
+ GParted does not work in GNOME on Wayland

** Changed in: ubuntu-gnome
   Status: New => Triaged

** Changed in: ubuntu-gnome
   Importance: Undecided => High

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

Title:
  GParted does not work in GNOME on Wayland

Status in GParted:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gparted package in Ubuntu:
  Triaged

Bug description:
  I have found that after switching from Xorg to Wayland on Ubuntu GNOME
  16.10 with GNOME 3.22 that GParted does not run when I try to run it
  as root. That is when I click the icon and enter my password nothing
  happens. I have found that when running what is run when the icon is
  clicked that the output in Terminal is (gparted-pkexec):

  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/boot.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:16832): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/boot.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/tmp.mount.

  So I am now unable to launch and use GParted as root which is really
  the only way I can run it in order to make changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gparted 0.25.0-1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec 23 11:13:13 2016
  InstallationDate: Installed on 2016-05-15 (221 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gparted
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago)

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

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

[Touch-packages] [Bug 1628866] Re: After upgrading to 16.10, Chrome has become unusable because of extremely slow update

2017-04-18 Thread Colan Schwartz

** Tags added: 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/1628866

Title:
  After upgrading to 16.10, Chrome has become unusable because of
  extremely slow update

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Both Chrome and Firefox actually were extremely slow regarding visual
  update (1 second after clicking a tab, lagging when entering text).
  Examining this old report: https://bugs.launchpad.net/ubuntu-
  gnome/+bug/1386721, I tried disbling bootloader graphics and VESA
  framebuffer, which suddenly made firefox behave as it used to, but
  chrome shows no improvement.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  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:Unity7
  Date: Thu Sep 29 12:19:56 2016
  DistUpgraded: 2016-09-28 22:48:16,082 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2016-04-28 (153 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BTS26N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-09-28 (0 days ago)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET28W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS26N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTS26N00
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Sep 29 12:15:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1628866/+subscriptions

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

[Touch-packages] [Bug 1683990] [NEW] [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all

2017-04-18 Thread Clare

Public bug reported:

I have had no sound since original (fairly recent) purchase. I purchased
online from Dell.

Sound preferences were originally showing in upper right hand corner of
the screen, but the sliders for changing volume were grayed out, and
choosing sound test had no audible or visual result.

Now sound preferences are not showing in upper right corner at all, and
system preferences --> sound no longer shows 'sound test' as an option.

I tried to fix original problem myself by killing then re-starting pulseaudio
No effect. Also I tried commands 

apt-get purge pulseaudio 
and then later 
apt-get install pulseaudio

it seemed to be after that when the sound preferences stopped showing in
upper right corner, but I also did a general ubuntu update at the same
time (and there is still a restart required for update for 'Latitude
E5X60 System Update' 68614)

Release: Ubuntu 16.04.2 LTS
Package: N: Unable to locate package pkgname

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  clare  2105 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 18 22:44:33 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
InstallationDate: Installed on 2017-01-05 (104 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
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:  clare  2105 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all
UpgradeStatus: Upgraded to xenial on 2017-02-10 (67 days ago)
dmi.bios.date: 08/26/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.4
dmi.board.name: 0FFPFD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd08/26/2016:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn0FFPFD:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision 3510
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have had no sound since original (fairly recent) purchase. I
  purchased online from Dell.

  Sound preferences were originally showing in upper right hand corner
  of the screen, but the sliders for changing volume were grayed out,
  and choosing sound test had no audible or visual result.

  Now sound preferences are not showing in upper right corner at all,
  and system preferences --> sound no longer shows 'sound test' as an
  option.

  I tried to fix original problem myself by killing then re-starting pulseaudio
  No effect. Also I tried commands 

  apt-get purge pulseaudio 
  and then later 
  apt-get install pulseaudio

  it seemed to be after that when the sound preferences stopped showing
  in upper right corner, but I also did a general ubuntu update at the
  same time (and there is still a restart required for update for
  'Latitude E5X60 System Update' 68614)

  Release: Ubuntu 16.04.2 LTS
  Package: N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clare  2105 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 18 22:44:33 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2017-01-05 (104 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  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:

[Touch-packages] [Bug 1628866] Re: After upgrading to 16.10, Chrome has become unusable because of extremely slow update

2017-04-18 Thread T Martin

This bug began affecting me on April 16, 2017.  I'm using Chrome 57 and
when I move one window to my bottom 2x2 vertical desktop, the UI is
extremely laggy.  Moving it back to desktop 1 resolves the issue
immediately.

$ uname -a
Linux eldritch 4.8.0-46-generic #49~16.04.1-Ubuntu SMP Fri Mar 31 14:51:03 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux


Does not seem to affect Firefox.

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

Title:
  After upgrading to 16.10, Chrome has become unusable because of
  extremely slow update

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Both Chrome and Firefox actually were extremely slow regarding visual
  update (1 second after clicking a tab, lagging when entering text).
  Examining this old report: https://bugs.launchpad.net/ubuntu-
  gnome/+bug/1386721, I tried disbling bootloader graphics and VESA
  framebuffer, which suddenly made firefox behave as it used to, but
  chrome shows no improvement.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  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:Unity7
  Date: Thu Sep 29 12:19:56 2016
  DistUpgraded: 2016-09-28 22:48:16,082 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2016-04-28 (153 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BTS26N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-09-28 (0 days ago)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET28W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS26N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTS26N00
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Sep 29 12:15:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1628866/+subscriptions

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

[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

2017-04-18 Thread Nate Meyers

Same issue with asus zenbook 3, same audio card. In addition the built
in speaker output is broken, it can only be 0% or 100%, no in between.
Seemingly related.

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

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

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

[Touch-packages] [Bug 1681038] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

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

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

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Apr  8 12:26:01 2017
  DpkgHistoryLog:
   Start-Date: 2017-04-08  12:25:53
   Commandline: apt-get -f install
   Requested-By: abdul (1000)
   Remove: printer-driver-splix:amd64 (2.0.0+svn315-4fakesync1), 
bluez-cups:amd64 (5.37-0ubuntu5), printer-driver-hpcups:amd64 
(3.16.3+repack0-1), printer-driver-postscript-hp:amd64 (3.16.3+repack0-1), 
hplip:amd64 (3.16.3+repack0-1), printer-driver-gutenprint:amd64 (5.2.11-1), 
cups-core-drivers:amd64 (2.1.3-4ubuntu0.2), cups-daemon:amd64 (2.1.3-4), 
cups:amd64 (2.1.3-4ubuntu0.2), indicator-printers:amd64 
(0.1.7+15.04.20150220-0ubuntu2)
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-02-14 (52 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20351
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic 
root=UUID=f95918d9-59c9-4fc3-91a3-c5236d029fec ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic 
root=UUID=f95918d9-59c9-4fc3-91a3-c5236d029fec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN28WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN28WW:bd09/23/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1683483] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2017-04-18 Thread Apport retracing service

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

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 #1681038, 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 1681038
   package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  Impossible to actualize, many errors!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Mon Apr 17 21:27:32 2017
  DpkgTerminalLog:
   Removing cups-daemon (2.1.3-4) ...
   Job for cups.service canceled.
   invoke-rc.d: initscript cups, action "stop" failed.
   dpkg: error processing package cups-daemon (--remove):
subprocess installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-06-28 (293 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer AOA150
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=c0b8ad0e-eb56-45e6-91c3-bba6b84af2c2 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=c0b8ad0e-eb56-45e6-91c3-bba6b84af2c2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3310
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3310:bd10/06/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: AOA150
  dmi.product.version: 1
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1683483] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2017-04-18 Thread Seth Arnold

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

** Information type changed from Private Security to Public

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  Impossible to actualize, many errors!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Mon Apr 17 21:27:32 2017
  DpkgTerminalLog:
   Removing cups-daemon (2.1.3-4) ...
   Job for cups.service canceled.
   invoke-rc.d: initscript cups, action "stop" failed.
   dpkg: error processing package cups-daemon (--remove):
subprocess installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-06-28 (293 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer AOA150
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=c0b8ad0e-eb56-45e6-91c3-bba6b84af2c2 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=c0b8ad0e-eb56-45e6-91c3-bba6b84af2c2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3310
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3310:bd10/06/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: AOA150
  dmi.product.version: 1
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1683350] Re: package phpmyadmin 4:4.0.10-1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 29

2017-04-18 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 debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1683350

Title:
  package phpmyadmin 4:4.0.10-1 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 29

Status in debconf package in Ubuntu:
  New
Status in phpmyadmin package in Ubuntu:
  New

Bug description:
  package phpmyadmin 4:4.0.10-1 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 29

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: phpmyadmin 4:4.0.10-1
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-106-generic i686
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: i386
  Date: Mon Apr 17 18:07:19 2017
  DpkgTerminalLog:
   Removing phpmyadmin (4:4.0.10-1) ...
   Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at 
/usr/share/perl5/Debconf/Question.pm line 72.
   Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\${ <-- HERE ([^}]+)}/ at /usr/share/perl5/Debconf/Config.pm 
line 30.
   Can't locate object method "new" via package "Text::Iconv" (perhaps you 
forgot to load "Text::Iconv"?) at /usr/share/perl5/Debconf/Encoding.pm line 65.
  DuplicateSignature: package:phpmyadmin:4:4.0.10-1:subprocess installed 
pre-removal script returned error exit status 29
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 29
  InstallationDate: Installed on 2016-01-17 (455 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.0.1ubuntu2.17
  SourcePackage: phpmyadmin
  Title: package phpmyadmin 4:4.0.10-1 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 29
  UpgradeStatus: Upgraded to trusty on 2017-03-31 (16 days ago)

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

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

[Touch-packages] [Bug 1683350] Re: package phpmyadmin 4:4.0.10-1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 29

2017-04-18 Thread Seth Arnold

** Information type changed from Private Security to Public

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

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

Title:
  package phpmyadmin 4:4.0.10-1 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 29

Status in debconf package in Ubuntu:
  New
Status in phpmyadmin package in Ubuntu:
  New

Bug description:
  package phpmyadmin 4:4.0.10-1 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 29

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: phpmyadmin 4:4.0.10-1
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-106-generic i686
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: i386
  Date: Mon Apr 17 18:07:19 2017
  DpkgTerminalLog:
   Removing phpmyadmin (4:4.0.10-1) ...
   Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at 
/usr/share/perl5/Debconf/Question.pm line 72.
   Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\${ <-- HERE ([^}]+)}/ at /usr/share/perl5/Debconf/Config.pm 
line 30.
   Can't locate object method "new" via package "Text::Iconv" (perhaps you 
forgot to load "Text::Iconv"?) at /usr/share/perl5/Debconf/Encoding.pm line 65.
  DuplicateSignature: package:phpmyadmin:4:4.0.10-1:subprocess installed 
pre-removal script returned error exit status 29
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 29
  InstallationDate: Installed on 2016-01-17 (455 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.0.1ubuntu2.17
  SourcePackage: phpmyadmin
  Title: package phpmyadmin 4:4.0.10-1 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 29
  UpgradeStatus: Upgraded to trusty on 2017-03-31 (16 days ago)

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

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

[Touch-packages] [Bug 1683268] Re: Evince/Okular displays incorrect characters (Regression?)

2017-04-18 Thread mogliii

Update: Tried opening the test file with different programs. Here is a
summary.

Bad: Gimp, Inkscape, Okular, Evince, Libreoffice, pdf2svg (open svg file in 
Inkscape)
Good: Firefox, Imagemagick, pdf2gs (open ps file in evince)

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

Title:
  Evince/Okular displays incorrect characters (Regression?)

Status in poppler package in Ubuntu:
  New

Bug description:
  See https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/518236

  There seems to be a regression bug exactly as described in the linked
  bug report, in the currently fully patched ubuntu 16.04.

  I found this problem recently with a pdf prepared by origin on
  windows. The file contains mu characters. I came accross this bug
  report, and the datasheet posted by the OP, on page 6, lower right,
  shows missing characters in Okular 0.24.2 with PDF Backend 0.6.5. (I
  am attaching two images, one by okular and one by Firefox). Evince
  also renders wrongly.

  libpoppler is 0.41.0-0ubuntu1.1.

  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

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

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

[Touch-packages] [Bug 1683268] Re: Evince/Okular displays incorrect characters (Regression?)

2017-04-18 Thread mogliii

This is a small pdf (2x1 cm^2) with 1 um (u = greek symbol) created in
Origin on Windows.

** Attachment added: "Graph1.pdf"

https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1683268/+attachment/4864500/+files/Graph1.pdf

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

Title:
Evince/Okular displays incorrect characters (Regression?)

Status in poppler package in Ubuntu:
New

Bug description:
See https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/518236

There seems to be a regression bug exactly as described in the linked
bug report, in the currently fully patched ubuntu 16.04.

I found this problem recently with a pdf prepared by origin on
windows. The file contains mu characters. I came accross this bug
report, and the datasheet posted by the OP, on page 6, lower right,
shows missing characters in Okular 0.24.2 with PDF Backend 0.6.5. (I
am attaching two images, one by okular and one by Firefox). Evince
also renders wrongly.

libpoppler is 0.41.0-0ubuntu1.1.

Description: Ubuntu 16.04.2 LTS
Release: 16.04

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

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

[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

2017-04-18 Thread Lev Popov

I've installed 1:8.0-0ubuntu3.3~xenial1 from testing PPA and it partly
fixed the issue.

My headphones are Plantronics BackBeat PRO.

A2DP works perfectly fine when connection is initiated by linux machine,
but when it's initiated by headphones, when they turn on, there is no
sound. In syslog:

Apr 19 02:14:07 xps pulseaudio[11005]: [pulseaudio] module-bluez5-device.c: 
Default profile not connected, selecting off profile
Apr 19 02:14:10 xps bluetoothd[12649]: 
/org/bluez/hci0/dev_0C_E0_E4_45_40_F2/fd7: fd(25) ready
Apr 19 02:14:10 xps pulseaudio[11005]: [pulseaudio] bluez5-util.c: Transport 
TryAcquire() failed for transport /org/bluez/hci0/dev_0C_E0_E4_45_40_F2/fd7 
(Operation Not Authorized)
Apr 19 02:14:20 xps pulseaudio[11005]: [pulseaudio] sink-input.c: Failed to 
create sink input: sink is suspended.
Apr 19 02:14:20 xps pulseaudio[11005]: [pulseaudio] sink-input.c: Failed to 
create sink input: sink is suspended.
Apr 19 02:14:20 xps pulseaudio[11005]: [pulseaudio] sink-input.c: Failed to 
create sink input: sink is suspended.
Apr 19 02:14:21 xps pulseaudio[11005]: [pulseaudio] sink-input.c: Failed to 
create sink input: sink is suspended.
Apr 19 02:14:21 xps pulseaudio[11005]: [pulseaudio] sink-input.c: Failed to 
create sink input: sink is suspended.
Apr 19 02:14:21 xps pulseaudio[11005]: [pulseaudio] sink-input.c: Failed to 
create sink input: sink is suspended.

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Touch-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()

2017-04-18 Thread Török Edwin

FWIW this crash has jut occured for me on Zesty while running the audio
tests from checkbox-ng. It is not easily reproducible though (it
happened the first time I run the tests, but didn't the second time).

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

[Touch-packages] [Bug 1682499] Re: disable dnssec

2017-04-18 Thread Török Edwin

systemd version 232-21ubuntu3: verified OK.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  disable dnssec

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

Bug description:
  [Impact]

   * dnssec functionality in systemd-resolved prevents network access in
  certain intra and extra net cases, due to failure to correctly
  validate dnssec entries. As a work-around we should disable dnssec by
  default.

  [Test Case]

   * Validate systemd-resolved is compiled with --with-default-dnssec=no
   * Validate that systemd-resolve --status says that DNSSEC setting is no

  $ systemd-resolve --status

  good output:
  ...
DNSSEC setting: no
  DNSSEC supported: no
  ...

  bad output:
  ...
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes
  ...

  [Regression Potential]

   * People who expect DNSSEC to be available by default will need to
  re-enable it by modifying systemd-resolve configuration file

  [Other Info]

   * See duplicate bugs and other bug reports in systemd for scenarios
  of DNS resolution failures when DNSSEC is enabled.

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

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

[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2017-04-18 Thread Brian Murray

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

** Tags removed: regression-update

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1683066] Re: Broken DNS when using Three UK mobile internet (17.04 zesty)

2017-04-18 Thread DieterDrewanz

>From here I picked idea of testing different wlan connections (router
and smart phone as hot spot) and looking for differences.  Although
there was another reason for this bug and this bug is not similar but
some similar error messages.

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

Title:
  Broken DNS when using Three UK mobile internet (17.04 zesty)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When connected via 4G to Three/3 (UK), DNS lookups fail (though the
  internet is otherwise working).

  The connection receives the correct DNS servers, but as far as I can
  work out systemd-resolve is unaware of them.

  Connection info screenshot is attached.

  DNS lookups time out:

  $ nslookup www.bbc.co.uk
  ;; connection timed out; no servers could be reached

  However they work when manually specifying the DNS server:

  $ nslookup www.bbc.co.uk 217.171.132.0
  Server:   217.171.132.0
  Address:  217.171.132.0#53

  Non-authoritative answer:
  www.bbc.co.uk canonical name = www.bbc.net.uk.
  Name: www.bbc.net.uk
  Address: 212.58.246.54
  Name: www.bbc.net.uk
  Address: 212.58.244.26

  Connections to IP addresses work (though redirect to a Three page at
  present):

  $ curl http://212.58.246.54 -v
  * Rebuilt URL to: http://212.58.246.54/
  *   Trying 212.58.246.54...
  * TCP_NODELAY set
  * Connected to 212.58.246.54 (212.58.246.54) port 80 (#0)
  > GET / HTTP/1.1
  > Host: 212.58.246.54
  > User-Agent: curl/7.52.1
  > Accept: */*
  >
  < HTTP/1.1 302 Moved Temporarily
  < Location: http://mbbinfo.three.co.uk/payg_mbb_data_usage2.html
  < Content-Type: text/plain; charset=UTF-8
  < Content-Length: 0
  <
  * Curl_http_done: called premature == 0
  * Connection #0 to host 212.58.246.54 left intact

  Below is the output of systemd-resolve --status:

  $ systemd-resolve --status
  Global
   DNS Servers: 8.8.8.8
    8.8.4.4
    2001:4860:4860::
    2001:4860:4860::8844
    DNSSEC NTA: 10.in-addr.arpa
    16.172.in-addr.arpa
    168.192.in-addr.arpa
    17.172.in-addr.arpa
    18.172.in-addr.arpa
    19.172.in-addr.arpa
    20.172.in-addr.arpa
    21.172.in-addr.arpa
    22.172.in-addr.arpa
    23.172.in-addr.arpa
    24.172.in-addr.arpa
    25.172.in-addr.arpa
    26.172.in-addr.arpa
    27.172.in-addr.arpa
    28.172.in-addr.arpa
    29.172.in-addr.arpa
    30.172.in-addr.arpa
    31.172.in-addr.arpa
    corp
    d.f.ip6.arpa
    home
    internal
    intranet
    lan
    local
    private
    test

  Link 4 (wlp4s0)
    Current Scopes: none
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 3 (wwp0s20f0u6i12)
    Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 2 (enp0s31f6)
    Current Scopes: none
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Note: Everything works fine on Wi-Fi, this problem is only happening
  on 4G.

  Note 2: I removed the automatically added UdevDb.txt and
  CurrentDmesg.txt attachments as they contained serial numbers of
  devices in my computer (such as for my SSD).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 15 20:54:33 2017
  InstallationDate: Installed on 2017-04-08 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407)
  MachineType: LENOVO 20HDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=88cb6912-997a-41b4-a0f8-050239177218 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET53W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information

[Touch-packages] [Bug 1683066] Re: Broken DNS when using Three UK mobile internet (17.04 zesty)

2017-04-18 Thread DieterDrewanz

>From here I picked idea of testing different wlan connections (router
and smart phone as hot spot) and looking for differences.  Although
there was another reason for this bug and this bug is not similar but
some similar error messages.

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

Title:
  Broken DNS when using Three UK mobile internet (17.04 zesty)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When connected via 4G to Three/3 (UK), DNS lookups fail (though the
  internet is otherwise working).

  The connection receives the correct DNS servers, but as far as I can
  work out systemd-resolve is unaware of them.

  Connection info screenshot is attached.

  DNS lookups time out:

  $ nslookup www.bbc.co.uk
  ;; connection timed out; no servers could be reached

  However they work when manually specifying the DNS server:

  $ nslookup www.bbc.co.uk 217.171.132.0
  Server:   217.171.132.0
  Address:  217.171.132.0#53

  Non-authoritative answer:
  www.bbc.co.uk canonical name = www.bbc.net.uk.
  Name: www.bbc.net.uk
  Address: 212.58.246.54
  Name: www.bbc.net.uk
  Address: 212.58.244.26

  Connections to IP addresses work (though redirect to a Three page at
  present):

  $ curl http://212.58.246.54 -v
  * Rebuilt URL to: http://212.58.246.54/
  *   Trying 212.58.246.54...
  * TCP_NODELAY set
  * Connected to 212.58.246.54 (212.58.246.54) port 80 (#0)
  > GET / HTTP/1.1
  > Host: 212.58.246.54
  > User-Agent: curl/7.52.1
  > Accept: */*
  >
  < HTTP/1.1 302 Moved Temporarily
  < Location: http://mbbinfo.three.co.uk/payg_mbb_data_usage2.html
  < Content-Type: text/plain; charset=UTF-8
  < Content-Length: 0
  <
  * Curl_http_done: called premature == 0
  * Connection #0 to host 212.58.246.54 left intact

  Below is the output of systemd-resolve --status:

  $ systemd-resolve --status
  Global
   DNS Servers: 8.8.8.8
    8.8.4.4
    2001:4860:4860::
    2001:4860:4860::8844
    DNSSEC NTA: 10.in-addr.arpa
    16.172.in-addr.arpa
    168.192.in-addr.arpa
    17.172.in-addr.arpa
    18.172.in-addr.arpa
    19.172.in-addr.arpa
    20.172.in-addr.arpa
    21.172.in-addr.arpa
    22.172.in-addr.arpa
    23.172.in-addr.arpa
    24.172.in-addr.arpa
    25.172.in-addr.arpa
    26.172.in-addr.arpa
    27.172.in-addr.arpa
    28.172.in-addr.arpa
    29.172.in-addr.arpa
    30.172.in-addr.arpa
    31.172.in-addr.arpa
    corp
    d.f.ip6.arpa
    home
    internal
    intranet
    lan
    local
    private
    test

  Link 4 (wlp4s0)
    Current Scopes: none
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 3 (wwp0s20f0u6i12)
    Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 2 (enp0s31f6)
    Current Scopes: none
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Note: Everything works fine on Wi-Fi, this problem is only happening
  on 4G.

  Note 2: I removed the automatically added UdevDb.txt and
  CurrentDmesg.txt attachments as they contained serial numbers of
  devices in my computer (such as for my SSD).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 15 20:54:33 2017
  InstallationDate: Installed on 2017-04-08 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407)
  MachineType: LENOVO 20HDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=88cb6912-997a-41b4-a0f8-050239177218 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET53W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information

[Touch-packages] [Bug 1535840] Re: systemd ignoring /etc/modules due to blacklist

2017-04-18 Thread Ingo Fischer

I tried that but I had no success.

I now have the /etc/init.d/watchdog start in /etc/rc.local (systemctl
did not worked that way) and so start using that

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

Title:
  systemd ignoring /etc/modules due to blacklist

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I tried the daily build of 16.04 32-bit to test out the watchdog
  daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in
  /etc/modules so it is loaded at boot-time, as watchdog timer modules
  are not normally auto-loaded due to the risk of an unexpected reboot.

  However I now find that systemd is choosing to ignore my command to
  load the module in /etc/modules since it appears in the watchdog
  blacklist. Typical syslog entries look like this:

  Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is 
blacklisted
  Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is 
blacklisted

  This is just dumb! I have explicitly told the system to load the
  module, an action that works perfectly well using modprobe or by
  adding it to the start script for the watchdog, and yet systemd
  chooses to override that because of the blacklist for auto-loaded
  modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf).

  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy systemd
  systemd:
Installed: 228-4ubuntu1
Candidate: 228-4ubuntu1
Version table:
   *** 228-4ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  What I expect to happen is modules added to /etc/modules are loaded at
  boot time, and not subject to the blacklist for hardware detect /
  automatic loading.

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

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

[Touch-packages] [Bug 1682913] Re: Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games

2017-04-18 Thread Timo Aaltonen

GLESv1 support will be removed upstream soon, so it's not coming back

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

Title:
  Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games

Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  I've just upgraded Ubuntu from 16.10 to 17.04. Afterwards, I noticed 
graphical issues in some games, that render partially black. E.g.:
  - menu of Payday 2: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546364727/C1182DAE4DA1A6CB638A2D42FA33541629F2/
  - menu of Faeria: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546272628/52E8E6F366A54299597774C22D78771EA0F074ED/

  I've traced the issue to a missing lib, libgles1, which for some
  reason has been removed from the 17.04 repos, as using Oibaf's PPA and
  manually installing the lib from it fixes the issues on these games.

  So, please build a version for Mesa 17.0.3 and put it in the repos,
  it's needed by some games.

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

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

[Touch-packages] [Bug 1683066] Re: Broken DNS when using Three UK mobile internet (17.04 zesty)

2017-04-18 Thread DieterDrewanz

Similar trouble I  have on connections with
systemd-resolve --status
DNSSEC supported: yes

Working with no trouble are connections with
DNSSEC supported: no

Using an old android smartphone or an old|really stupid wlan-router
lacks this support and therefore dns resolving is not disturbed. Yeah
these idea l will need to install bug-fix in future when available (will
solve hen-egg problem).

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

Title:
  Broken DNS when using Three UK mobile internet (17.04 zesty)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When connected via 4G to Three/3 (UK), DNS lookups fail (though the
  internet is otherwise working).

  The connection receives the correct DNS servers, but as far as I can
  work out systemd-resolve is unaware of them.

  Connection info screenshot is attached.

  DNS lookups time out:

  $ nslookup www.bbc.co.uk
  ;; connection timed out; no servers could be reached

  However they work when manually specifying the DNS server:

  $ nslookup www.bbc.co.uk 217.171.132.0
  Server:   217.171.132.0
  Address:  217.171.132.0#53

  Non-authoritative answer:
  www.bbc.co.uk canonical name = www.bbc.net.uk.
  Name: www.bbc.net.uk
  Address: 212.58.246.54
  Name: www.bbc.net.uk
  Address: 212.58.244.26

  Connections to IP addresses work (though redirect to a Three page at
  present):

  $ curl http://212.58.246.54 -v
  * Rebuilt URL to: http://212.58.246.54/
  *   Trying 212.58.246.54...
  * TCP_NODELAY set
  * Connected to 212.58.246.54 (212.58.246.54) port 80 (#0)
  > GET / HTTP/1.1
  > Host: 212.58.246.54
  > User-Agent: curl/7.52.1
  > Accept: */*
  >
  < HTTP/1.1 302 Moved Temporarily
  < Location: http://mbbinfo.three.co.uk/payg_mbb_data_usage2.html
  < Content-Type: text/plain; charset=UTF-8
  < Content-Length: 0
  <
  * Curl_http_done: called premature == 0
  * Connection #0 to host 212.58.246.54 left intact

  Below is the output of systemd-resolve --status:

  $ systemd-resolve --status
  Global
   DNS Servers: 8.8.8.8
    8.8.4.4
    2001:4860:4860::
    2001:4860:4860::8844
    DNSSEC NTA: 10.in-addr.arpa
    16.172.in-addr.arpa
    168.192.in-addr.arpa
    17.172.in-addr.arpa
    18.172.in-addr.arpa
    19.172.in-addr.arpa
    20.172.in-addr.arpa
    21.172.in-addr.arpa
    22.172.in-addr.arpa
    23.172.in-addr.arpa
    24.172.in-addr.arpa
    25.172.in-addr.arpa
    26.172.in-addr.arpa
    27.172.in-addr.arpa
    28.172.in-addr.arpa
    29.172.in-addr.arpa
    30.172.in-addr.arpa
    31.172.in-addr.arpa
    corp
    d.f.ip6.arpa
    home
    internal
    intranet
    lan
    local
    private
    test

  Link 4 (wlp4s0)
    Current Scopes: none
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 3 (wwp0s20f0u6i12)
    Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 2 (enp0s31f6)
    Current Scopes: none
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Note: Everything works fine on Wi-Fi, this problem is only happening
  on 4G.

  Note 2: I removed the automatically added UdevDb.txt and
  CurrentDmesg.txt attachments as they contained serial numbers of
  devices in my computer (such as for my SSD).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 15 20:54:33 2017
  InstallationDate: Installed on 2017-04-08 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407)
  MachineType: LENOVO 20HDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=88cb6912-997a-41b4-a0f8-050239177218 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET53W (1.28 )
  dmi.board.asset.tag: Not

[Touch-packages] [Bug 1683066] Re: Broken DNS when using Three UK mobile internet (17.04 zesty)

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

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

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

Title:
  Broken DNS when using Three UK mobile internet (17.04 zesty)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When connected via 4G to Three/3 (UK), DNS lookups fail (though the
  internet is otherwise working).

  The connection receives the correct DNS servers, but as far as I can
  work out systemd-resolve is unaware of them.

  Connection info screenshot is attached.

  DNS lookups time out:

  $ nslookup www.bbc.co.uk
  ;; connection timed out; no servers could be reached

  However they work when manually specifying the DNS server:

  $ nslookup www.bbc.co.uk 217.171.132.0
  Server:   217.171.132.0
  Address:  217.171.132.0#53

  Non-authoritative answer:
  www.bbc.co.uk canonical name = www.bbc.net.uk.
  Name: www.bbc.net.uk
  Address: 212.58.246.54
  Name: www.bbc.net.uk
  Address: 212.58.244.26

  Connections to IP addresses work (though redirect to a Three page at
  present):

  $ curl http://212.58.246.54 -v
  * Rebuilt URL to: http://212.58.246.54/
  *   Trying 212.58.246.54...
  * TCP_NODELAY set
  * Connected to 212.58.246.54 (212.58.246.54) port 80 (#0)
  > GET / HTTP/1.1
  > Host: 212.58.246.54
  > User-Agent: curl/7.52.1
  > Accept: */*
  >
  < HTTP/1.1 302 Moved Temporarily
  < Location: http://mbbinfo.three.co.uk/payg_mbb_data_usage2.html
  < Content-Type: text/plain; charset=UTF-8
  < Content-Length: 0
  <
  * Curl_http_done: called premature == 0
  * Connection #0 to host 212.58.246.54 left intact

  Below is the output of systemd-resolve --status:

  $ systemd-resolve --status
  Global
   DNS Servers: 8.8.8.8
    8.8.4.4
    2001:4860:4860::
    2001:4860:4860::8844
    DNSSEC NTA: 10.in-addr.arpa
    16.172.in-addr.arpa
    168.192.in-addr.arpa
    17.172.in-addr.arpa
    18.172.in-addr.arpa
    19.172.in-addr.arpa
    20.172.in-addr.arpa
    21.172.in-addr.arpa
    22.172.in-addr.arpa
    23.172.in-addr.arpa
    24.172.in-addr.arpa
    25.172.in-addr.arpa
    26.172.in-addr.arpa
    27.172.in-addr.arpa
    28.172.in-addr.arpa
    29.172.in-addr.arpa
    30.172.in-addr.arpa
    31.172.in-addr.arpa
    corp
    d.f.ip6.arpa
    home
    internal
    intranet
    lan
    local
    private
    test

  Link 4 (wlp4s0)
    Current Scopes: none
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 3 (wwp0s20f0u6i12)
    Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 2 (enp0s31f6)
    Current Scopes: none
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Note: Everything works fine on Wi-Fi, this problem is only happening
  on 4G.

  Note 2: I removed the automatically added UdevDb.txt and
  CurrentDmesg.txt attachments as they contained serial numbers of
  devices in my computer (such as for my SSD).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 15 20:54:33 2017
  InstallationDate: Installed on 2017-04-08 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407)
  MachineType: LENOVO 20HDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=88cb6912-997a-41b4-a0f8-050239177218 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET53W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias:

[Touch-packages] [Bug 1628866] Re: After upgrading to 16.10, Chrome has become unusable because of extremely slow update

2017-04-18 Thread Colan Schwartz

I removed the duplicate marker as I don't believe this to be a duplicate
of bug #1615871 (Poor performance with WebKit on yakkety with Intel
modesetting enabled).

The upstream bug is really
https://bugs.chromium.org/p/chromium/issues/detail?id=683486 , but I
can't find any way to add the remote watch.  Can someone help?

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

Title:
  After upgrading to 16.10, Chrome has become unusable because of
  extremely slow update

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Both Chrome and Firefox actually were extremely slow regarding visual
  update (1 second after clicking a tab, lagging when entering text).
  Examining this old report: https://bugs.launchpad.net/ubuntu-
  gnome/+bug/1386721, I tried disbling bootloader graphics and VESA
  framebuffer, which suddenly made firefox behave as it used to, but
  chrome shows no improvement.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  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:Unity7
  Date: Thu Sep 29 12:19:56 2016
  DistUpgraded: 2016-09-28 22:48:16,082 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2016-04-28 (153 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BTS26N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-09-28 (0 days ago)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET28W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS26N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTS26N00
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Sep 29 12:15:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1628866/+subscriptions

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

[Touch-packages] [Bug 1682934] Re: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

2017-04-18 Thread Brian Murray

How did you go about upgrading from 16.10 to 17.04? If you used ubuntu-
release-upgrader please include the logs in /var/log/dist-upgrade/ so I
can better sort out how things went awry.

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

Title:
  package python3 3.5.1-4 failed to install/upgrade: pre-dependency
  problem - not installing python3

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Got this error while using "Transmageddon Video Transcoder" and again
  while updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

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

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

[Touch-packages] [Bug 1683923] Re: Empty extglob patterns hang bash

2017-04-18 Thread John Valko

Also, I built the vanilla bash 4.3 and 4.4 sources and they do not
appear to be affected by this bug.

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

Title:
  Empty extglob patterns hang bash

Status in bash package in Ubuntu:
  New

Bug description:
  Bash hangs when extglobs with no patterns are specified.

  Example:

  $ echo !()

  should print the contents of the current directory, but actually makes
  bash hang with 100% CPU usage. Also affects other pattern types, e.g.
  @() and ?(). Non-empty patterns work correctly.

  After executing a command containing such a glob, a SIGKILL is
  required to terminate the process.

  Additional info:

  $ lsb_release  -rd
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04

  $ apt-cache policy bash
  bash:
Installed: 4.3-7ubuntu1.5
Candidate: 4.3-7ubuntu1.5
Version table:
   *** 4.3-7ubuntu1.5 0
  500 http://mirrors.linode.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://mirrors.linode.com/ubuntu/ trusty-security/main amd64 
Packages

  100 /var/lib/dpkg/status
   4.3-6ubuntu1 0
  500 http://mirrors.linode.com/ubuntu/ trusty/main amd64 Packages

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

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

[Touch-packages] [Bug 1683923] [NEW] Empty extglob patterns hang bash

2017-04-18 Thread John Valko

Public bug reported:

Bash hangs when extglobs with no patterns are specified.

Example:

$ echo !()

should print the contents of the current directory, but actually makes
bash hang with 100% CPU usage. Also affects other pattern types, e.g.
@() and ?(). Non-empty patterns work correctly.

After executing a command containing such a glob, a SIGKILL is required
to terminate the process.

Additional info:

$ lsb_release  -rd
Description:Ubuntu 14.04.4 LTS
Release:14.04

$ apt-cache policy bash
bash:
  Installed: 4.3-7ubuntu1.5
  Candidate: 4.3-7ubuntu1.5
  Version table:
 *** 4.3-7ubuntu1.5 0
500 http://mirrors.linode.com/ubuntu/ trusty-updates/main amd64 Packages
500 http://mirrors.linode.com/ubuntu/ trusty-security/main amd64 
Packages

100 /var/lib/dpkg/status
 4.3-6ubuntu1 0
500 http://mirrors.linode.com/ubuntu/ trusty/main amd64 Packages

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

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

Title:
  Empty extglob patterns hang bash

Status in bash package in Ubuntu:
  New

Bug description:
  Bash hangs when extglobs with no patterns are specified.

  Example:

  $ echo !()

  should print the contents of the current directory, but actually makes
  bash hang with 100% CPU usage. Also affects other pattern types, e.g.
  @() and ?(). Non-empty patterns work correctly.

  After executing a command containing such a glob, a SIGKILL is
  required to terminate the process.

  Additional info:

  $ lsb_release  -rd
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04

  $ apt-cache policy bash
  bash:
Installed: 4.3-7ubuntu1.5
Candidate: 4.3-7ubuntu1.5
Version table:
   *** 4.3-7ubuntu1.5 0
  500 http://mirrors.linode.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://mirrors.linode.com/ubuntu/ trusty-security/main amd64 
Packages

  100 /var/lib/dpkg/status
   4.3-6ubuntu1 0
  500 http://mirrors.linode.com/ubuntu/ trusty/main amd64 Packages

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

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

[Touch-packages] [Bug 1628866] Re: After upgrading to 16.10, Chrome has become unusable because of extremely slow update

2017-04-18 Thread Colan Schwartz

** This bug is no longer a duplicate of bug 1615871
   Poor performance with WebKit on yakkety with Intel modesetting enabled

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

Title:
  After upgrading to 16.10, Chrome has become unusable because of
  extremely slow update

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Both Chrome and Firefox actually were extremely slow regarding visual
  update (1 second after clicking a tab, lagging when entering text).
  Examining this old report: https://bugs.launchpad.net/ubuntu-
  gnome/+bug/1386721, I tried disbling bootloader graphics and VESA
  framebuffer, which suddenly made firefox behave as it used to, but
  chrome shows no improvement.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  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:Unity7
  Date: Thu Sep 29 12:19:56 2016
  DistUpgraded: 2016-09-28 22:48:16,082 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2016-04-28 (153 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BTS26N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-09-28 (0 days ago)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET28W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS26N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTS26N00
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Sep 29 12:15:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1628866/+subscriptions

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

[Touch-packages] [Bug 1683908] Re: Z system has no network after do-release-upgrade from Yakkety to Zesty

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

netcfg is irrelevant here.

this is a known issue, and SRU is in progress to resolve this.

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

** This bug has been marked a duplicate of bug 1682437
   udev does not preserve virtio interface names on s390x upgrades

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

Title:
  Z system has no network after do-release-upgrade from Yakkety to Zesty

Status in systemd package in Ubuntu:
  New

Bug description:
  do-release-upgrade was performed on a zKVM guest instance, upgrading
  Yakkety to Zesty. After reboot the system was no longer available on
  the network. The interface name changed from eth0 to enc1. The
  following change was required:

  ubuntu@s5lp6-gen01:~$ diff interfaces.ori /etc/network/interfaces
  11,12c11,12
  < auto eth0
  < iface eth0 inet static
  ---
  > auto enc1
  > iface enc1 inet static

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

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

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2017-04-18 Thread Marco Venturini

@Andrei

Yes it does, thanks a lot.

Still there is some strange behavior that may be due to this driver.

For instance if follow those steps the audio stops playing until the system is 
rebooted
1) Open a flac or mp3 with vlc 
2) ... audio plays nicely
3) Open PulseAudio volume control 
4) wait 10-20 s
5) ... audio stops playing

To me the current behavior it's not a big deal, but if it can be useful
to debug the driver i can provide additional information.

Thanks Again,
Marco

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1683908] [NEW] Z system has no network after do-release-upgrade from Yakkety to Zesty

You have been subscribed to a public bug:

do-release-upgrade was performed on a zKVM guest instance, upgrading
Yakkety to Zesty. After reboot the system was no longer available on the
network. The interface name changed from eth0 to enc1. The following
change was required:

ubuntu@s5lp6-gen01:~$ diff interfaces.ori /etc/network/interfaces
11,12c11,12
< auto eth0
< iface eth0 inet static
---
> auto enc1
> iface enc1 inet static

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


** Tags: s390x
-- 
Z system has no network after do-release-upgrade from Yakkety to Zesty
https://bugs.launchpad.net/bugs/1683908
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1604872] Re: Apps can't connect to the user's session bus, even though it exists

2017-04-18 Thread Steve Beattie

This issue was fixed in Ubuntu 16.04 LTS in apparmor 2.10.95-0ubuntu2.2
(by way of 2.10.95-0ubuntu2.1, which was superceded in xenial-proposed).
Marking that task closed.

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

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

Title:
  Apps can't connect to the user's session bus, even though it exists

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Systemd user sessions makes telepathy unhappy because access to
  /run/user//bus is denied

  [Test Case]

  $ sudo apt install dbus-user-session empathy

  Restart the session (or reboot) and then start empathy:

  $ empathy

  In 16.04, you may need to set correctly DBUS_SESSION_BUS_ADDRESS
  before launching empathy:

  $ DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus" empathy

  Without this bug fix, empathy fails with "Error contacting the account
  manager", and dmesg shows several denial messages like so:

  [ 63.960358] audit: type=1400 audit(1469458539.595:27):
  apparmor="DENIED" operation="connect" profile="/usr/lib/telepathy
  /mission-control-5" name="/run/user/1000/bus" pid=4563 comm="mission-
  control" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000

  [Regression Potential]

  None. The fix simply adds permissions to the dbus-session-strict
  abstraction. This change will not introduce any new AppArmor denials
  since policy is being loosened instead of being restricted.

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

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

[Touch-packages] [Bug 1683804] Re: Word doubled in French translation of an error message of rmdir

2017-04-18 Thread Olivier Febwin

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

** Changed in: ubuntu-translations
   Status: New => Fix Committed

** Changed in: coreutils (Ubuntu)
 Assignee: (unassigned) => Olivier Febwin (febcrash)

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Olivier Febwin (febcrash)

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

Title:
  Word doubled in French translation of an error message of rmdir

Status in Ubuntu Translations:
  Fix Committed
Status in coreutils package in Ubuntu:
  Fix Committed

Bug description:
  In Ubuntu 17.04, the following command line:

  rmdir non-existent-directory

  outputs:
  rmdir: impossible de de supprimer 'non-existent-directory': Aucun fichier ou 
dossier de ce type

  This output should be:
  rmdir: impossible de supprimer 'non-existent-directory': Aucun fichier ou 
dossier de ce type

  "de de" → "de"

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

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

[Touch-packages] [Bug 1588069] Re: parser doesn't catch conflicting change_profile exec modes (safe/unsafe)

2017-04-18 Thread Steve Beattie

This was fixed in Ubuntu 16.04 LTS in apparmor 2.10.95-0ubuntu2.2
(including the changes in 2.10.95-0ubuntu2.1, which was superceded in
xenial-proposed by 2.10.95-0ubuntu2.2). Marking that task closed.

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

Title:
  parser doesn't catch conflicting change_profile exec modes
  (safe/unsafe)

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Applications which use libapparmor's aa_change_onexec() to set up an
  AppArmor profile transition across an upcoming exec() could not pre-
  initialize the environment up until the upstream fix for bug #1584069
  was in place. That upstream fix had a flaw in that conflicting
  safe/unsafe change_profile transitions were allowed by
  apparmor_parser. apparmor_parser should detect conflicting rules and
  fail to compile the profile.

  [Test Case]

  The upstream fix for this bug includes exhaustive tests for
  conflicting safe/unsafe change_profile transitions. These tests run at
  build time.

  If a manual test is desired, see the original report below for steps.

  [Regression Potential]

  Regression potential for this change is small since it is actually a
  bug fix for the changes introduced in bug #1584069. The regression
  potential for the changes for bug #1584069 are considerable and listed
  in that bug report.

  [Original Report]

  The ability to specify change_profile exec modes (safe/unsafe) is a
  recently merged feature. A missing piece is that the parser doesn't
  detect conflicting exec modes on the same exec condition. The
  following profile should fail to compile:

  /t {
    change_profile safe /foo -> /bar,
    change_profile unsafe /foo -> /bar,
  }

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

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

[Touch-packages] [Bug 1683804] Re: Word doubled in French translation of an error message of rmdir

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

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

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

Title:
  Word doubled in French translation of an error message of rmdir

Status in Ubuntu Translations:
  Fix Committed
Status in coreutils package in Ubuntu:
  Fix Committed

Bug description:
  In Ubuntu 17.04, the following command line:

  rmdir non-existent-directory

  outputs:
  rmdir: impossible de de supprimer 'non-existent-directory': Aucun fichier ou 
dossier de ce type

  This output should be:
  rmdir: impossible de supprimer 'non-existent-directory': Aucun fichier ou 
dossier de ce type

  "de de" → "de"

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

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

[Touch-packages] [Bug 1528230] Re: [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py -- ONEXEC - check current 'unconfined' != expected

2017-04-18 Thread Steve Beattie

This was fixed in Ubuntu 16.04 lts in apparmor 2.10.95-0ubuntu2.2;
closing that task.

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

Title:
  [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py --
  ONEXEC - check current 'unconfined' != expected

Status in AppArmor:
  Fix Released
Status in QA Regression Testing:
  Invalid
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  The AppArmor regression tests are ran as part of the kernel SRU
  verification process. One of the tests, onexec.sh, contains a racy
  section that introduces intermittent failures. Such failures introduce
  doubt in the kernel SRU process and generate additional work to verify
  that the failures can be ignored.

  [Test Case]

  Since the fix is to the onexec.sh test itself, the best test case is
  to simply run the test. The QRT test-apparmor.py script runs this
  test, among many others, and should be used for verification.

  [Regression Potential]

  None. The fix is to the test and does not affect code that is user-
  facing.

  [Original Report]

  New ADT test failure in Vivid:

    running onexec
    ONEXEC - check current 'unconfined' != expected 
'/tmp/testlibIUFsmN/source/vivid/apparmor-2.9.1/tests/regression/apparmor/onexec'
    Fatal Error (onexec): Unable to run test sub-executable

  Full log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid/vivid/ppc64el/l/linux/20151218_175610@/log.gz

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

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

[Touch-packages] [Bug 1683911] [NEW] ifup places illegally named variables into the environment

2017-04-18 Thread LaMont Jones

Public bug reported:

When dhclient brings up interface eth0.55, the environment passed to scripts 
includes:
IFUPDOWN_eth0=parent-lock
IFUPDOWN_eth0.55=post-up
IFACE=eth0.55
LOGICAL=eth0.55
ADDRFAM=inet
METHOD=dhcp
MODE=start
PHASE=post-up
VERBOSITY=0
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

IFUPDOWN_eth0.55 is not a valid name for an environment variable.

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

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

Title:
  ifup places illegally named variables into the environment

Status in ifupdown package in Ubuntu:
  New

Bug description:
  When dhclient brings up interface eth0.55, the environment passed to scripts 
includes:
  IFUPDOWN_eth0=parent-lock
  IFUPDOWN_eth0.55=post-up
  IFACE=eth0.55
  LOGICAL=eth0.55
  ADDRFAM=inet
  METHOD=dhcp
  MODE=start
  PHASE=post-up
  VERBOSITY=0
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  IFUPDOWN_eth0.55 is not a valid name for an environment variable.

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

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

Do someone plan to fix this issue?

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  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 670178] Re: SVG file rendered incorrectly

2017-04-18 Thread Bug Watch Updater

** Changed in: librsvg
   Status: Confirmed => Fix Released

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

Title:
  SVG file rendered incorrectly

Status in librsvg:
  Fix Released
Status in librsvg package in Ubuntu:
  Triaged

Bug description:
  The attached stars.svg is rendered incorrectly in Eye of Gnome,
  Nautilus preview, Gimp import, Evince etc. The top left star does not
  have its shadow.

  Works correctly in inkscape, Firefox, Chrome.

  Created in inkscape.

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

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

[Touch-packages] [Bug 1682934] Re: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

2017-04-18 Thread Dave Kuhlman

I attempted to upgrade to Ubuntu 17.04 zesty.  That seems to have
failed.  Now, when I do `sudo aptitude full-upgrade`, I get the
following error messages:

# =
The following packages will be upgraded:
  python3
The following partially installed packages will be configured:
  gedit python3-minimal python3-uno python3.5 python3.5-minimal
  rhythmbox-plugin-magnatune rhythmbox-plugins ubuntu-gnome-desktop
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/8,696 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?]
Setting up python3.5-minimal (3.5.3-1) ...
Traceback (most recent call last):
  File "/usr/lib/python3.5/py_compile.py", line 6, in 
import importlib._bootstrap_external
  File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
import types
  File "/usr/lib/python3.5/types.py", line 166, in 
import functools as _functools
  File "/usr/lib/python3.5/functools.py", line 23, in 
from weakref import WeakKeyDictionary
  File "/usr/lib/python3.5/weakref.py", line 12, in 
from _weakref import (
ImportError: cannot import name '_remove_dead_weakref'
dpkg: error processing package python3.5-minimal (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of python3-minimal:
 python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
  Package python3.5-minimal is not configured yet.

dpkg: error processing package python3-minimal (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup 
error from a previous failure.
Errors were encountered while processing:
 python3.5-minimal
 python3-minimal
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up python3.5-minimal (3.5.3-1) ...
Traceback (most recent call last):
  File "/usr/lib/python3.5/py_compile.py", line 6, in 
import importlib._bootstrap_external
  File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
import types
  File "/usr/lib/python3.5/types.py", line 166, in 
import functools as _functools
  File "/usr/lib/python3.5/functools.py", line 23, in 
from weakref import WeakKeyDictionary
  File "/usr/lib/python3.5/weakref.py", line 12, in 
from _weakref import (
ImportError: cannot import name '_remove_dead_weakref'
dpkg: error processing package python3.5-minimal (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of python3-minimal:
 python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
  Package python3.5-minimal is not configured yet.

dpkg: error processing package python3-minimal (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python3.5:
 python3.5 depends on python3.5-minimal (= 3.5.3-1); however:
  Package python3.5-minimal is not configured yet.

dpkg: error processing package python3.5 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of rhythmbox-plugins:
 rhythmbox-plugins depends on python3.5; however:
  Package python3.5 is not configured yet.

dpkg: error processing package rhythmbox-plugins (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of rhythmbox-plugin-magnatune:
 rhythmbox-plugin-magnatune depends on rhythmbox-plugins; however:
  Package rhythmbox-plugins is not configured yet.

dpkg: error processing package rhythmbox-plugin-magnatune (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python3-uno:
 python3-uno depends on python3.5; however:
  Package python3.5 is not configured yet.

dpkg: error processing package python3-uno (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gedit:
 gedit depends on python3.5; however:
  Package python3.5 is not configured yet.

dpkg: error processing package gedit (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of ubuntu-gnome-desktop:
 ubuntu-gnome-desktop depends on gedit; however:
  Package gedit is not configured yet.

dpkg: error processing package ubuntu-gnome-desktop (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 python3.5-minimal
 python3-minimal
 python3.5
 rhythmbox-plugins
 rhythmbox-plugin-magnatune
 python3-uno
 gedit
 ubuntu-gnome-desktop
# =

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

[Touch-packages] [Bug 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in

2017-04-18 Thread Ola Persson

I eventually solved this by first deleting
/usr/share/doc/libperl5.22/changelog.Debian.gz and then running sudo apt
--fix-broken install. This fixed the libperl-issue, however I still had
problems scanning. That seemed to be an issue with changed user-
permissions during the upgrade to 17.04. simple-scan worked using sudo
and after adding my user-account to the groups saned, scanner and lp
scanning worked again as expected without using sudo, even after reboot.

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

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  Don't run aplication after upgrade from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun Apr 24 21:08:20 2016
  DpkgTerminalLog:
   Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ...
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  DuplicateSignature:
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1672542] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

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-21ubuntu3
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/1672542

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

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

Bug description:
  [Impact]

   * Due to upgraded netcat in zesty, ADT testcase 12 started to hang upon 
calls to netcat.
   * The upgraded netcat changed default behaviour from -q0 (quit straight 
away) to -q-1 (wait infinity)
   * Proposed fix is an upstream cherry-pick to add a `-w1` option (quit after 
1 second) which resolves the test-suite hang and is compatible across Ubuntu 
and Fedora (uses nmap netcat).

  [Test Case]

   * ADT tests should pass on kvm architectures.

  [Regression Potential]

   * This is a testsuite fix for netcat-openbsd compat, does not affect
  systemd runtime binaries / libraries.

  [Other Info]
   
   * Original bug report.

  Testing failed on:
    amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
    i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
    ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz

  Upstream tests time out. Last thing displayed in the logs before the
  timeout is the login prompt from a container running one of the tests.

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

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

[Touch-packages] [Bug 1668347] Re: Unable to set bridge_portpriority with networkd

Hello Ryan, 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-21ubuntu3
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/1668347

Title:
  Unable to set bridge_portpriority with networkd

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

Bug description:
  [Impact]

   * Netplan uses systemd-netword provider to configure all sorts of networking 
settings
   * However, unlike ifupdown, released versions of systemd do not support 
setting bridgeport priority, aka
  `brctl setportprio   `
   * This prevents full migration from ifupdown to netplan/systemd-networkd for 
projects like MAAS that do need to configure equal cost; yet differential 
priority bridge ports.
   * This is proposal to cherrypick this functionality which essentially 
accepts one more key in the .network units; and send those values via netlink.

  [Test Case]

   * networkd-test.py is executed as part of autopkgtests that
  configures a bridge, and sets various valid bridge port priorities and
  verifies from sysfs that those were correctly set by systemd.

   * Alternativey create a bridge .link unit, and specify .network unit
  for a bridge port and use Priority=4 setting in the [Bridge] section
  in the said unit to modify bridge port priority.

  
  [Regression Potential] 

   * This is an upstream cherrypick of functionality that will be
  included in 234 release. However, since MAAS and netplan target stable
  releases, I would like to cherrypick this functionality all the way
  back to xenial. This almost a feature, rather than a bugfix, but it is
  so small and accompanied by regression testsuite that it is almost a
  tiny bugfix.

  [Other Info]
   
   * Original request to support this feature.

  
  1. root@ubuntu:/run/systemd/network# lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04

  2. root@ubuntu:/run/systemd/network# apt-cache policy systemd
  systemd:
    Installed: 232-18ubuntu1
    Candidate: 232-18ubuntu1
    Version table:
   *** 232-18ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  3. Using a networkd config like this:

  # cat 10-netplan-eth1.network
  [Match]
  MACAddress=52:54:00:12:34:02
  Name=eth1

  [Network]
  Bridge=br0
  LinkLocalAddressing=no
  IPv6AcceptRA=no

  [Bridge]
  Cost=50
  Priority=28

  %  cat /sys/class/net/br0/brif/eth1/priority
  28

  4. %  cat /sys/class/net/br0/brif/eth1/priority
  32

  When using ifupdown and /etc/network/interfaces to configure a bridge
  users are able to specify a bridge port priority:

  auto br0
  iface br0 inet static
    address 192.168.1.1
    bridge_ports eth1 eth2
    bridge_portprio eth1 28
    bridge_portprio eth2 14

  Which results in the bridge hook scripts running:

  brctl setportprio br0 eth1 28

  which is visible via:

  /sys/class/net/br0/brif/eth2/priority

  Note, networkd does not mention PortPriority under netdev Bridge section,
  however, PathCost is mentioned.  It appears networkd is missing an 
implementation.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Mon Feb 27 17:11:32 2017
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=900c1e3f-f682-4455-949c-ebdbf60ac6f5 ro console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date:

[Touch-packages] [Bug 1682484] Re: systemd: Logging from gnome session is passed on to all syslog facilities

Hello Dimitri, 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-21ubuntu3
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/1682484

Title:
  systemd: Logging from gnome session is passed on to all syslog
  facilities

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * untagged messages in journal do not have any syslog facility specified, 
this may result in spamming logs.
   * The solution is to cherrypick upstream fix which sanity checks and 
provides default syslog facility, e.g. it sets user facility on user/desktop 
session syslog/journal entries.

  [Test Case]

   * launch gnome terminal
   * check output of $ journalctl -o verbose -e
   * entries from gnome-terminal (e.g. "Allocating size to GtkBox without 
calling gtk_widget_get_preferred_width/height()") should have a syslog 
facility listed as one of the variables.

  
  [Regression Potential] 

   * We are changing (fixing regression) in logging, thus release images
  have those messages untagged, and may require different filtering
  rules before this update is applied.

  [Other Info]
   
   * Original bug report from debian.

  Bug imported from Debian https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=837893

  Package: systemd
  Version: 231-6
  Severity: normal

  Since recently, log messages from programs running under the gnome
  session have started appearing in all logs in /var/logs, including
  /var/logs/kern.log, even though my rsyslog configuration has not
  changed, and correctly only routes kern.* there.

  This is very annoying since it fills the logs with messages that don't
  belong there, and makes running logcheck tedious.

  It seems this is a recent regression, since before I was able to route
  these messages to a low-priority log using the following rsyslog
  configuration:

    user.=info;user.=notice;\
    user.=warn  -/var/log/user-low.log

  If I look at the messages directly with journalctl -o verbose, it seems
  they do not set the syslog facility, which should make them end up with
  user facility, but doesn't.

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

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

[Touch-packages] [Bug 1682437] Re: udev does not preserve virtio interface names on s390x upgrades

Hello Dimitri, 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-21ubuntu3
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: Triaged => 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/1682437

Title:
  udev does not preserve virtio interface names on s390x upgrades

Status in Release Notes for Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * Upgrading s390x, kvm/qemu instances from yakkety to zesty results in a 
change of network interface names (e.g. from eth0 to stable/predictable bus_id 
name enc3, just like on z/VM and LPAR).
   * This obviously results in loss of network connectivity as 
/etc/network/interfaces no longer matches the network interface names 
configured by systemd.
   * The proposal is to generate udev rules on upgrade to preserve active 
interface names, in a very similar fashion to the no longer in use 
net-persistent-name generator.

  [Test Case]

   * Install zesty from scratch in kvm/qemu, network interfaces should use enc* 
names.
   * Install yakkety, upgrade to zesty, network intefaces should use eth* names 
after upgrade and reboot.

  [Regression Potential]

   * This solution is similar to previous upgrades to stable networking
  names for other types of network interfaces. This will make upgraded
  systems look different from freshly installed systems. For users
  aiming to have homogenious environments it is recommended to remove
  /etc/udev/rules.d/70-persistent-net.rules and readjust
  networking/daemon/firewall configurations to the new stable names
  enc*.

  [Other Info]
   
   * Original bug report filed in debian.

  Package: udev
  Version: 232-20
  Severity: important

  Dear Maintainer,

  systemd 232-20 introduce the patch to generate stable interface names
  for virtio network interfaces on s390x. This is a good thing, and
  those names should be used for new installations.

  However, when upgrading existing virtual machines installations the
  new udev causes interfaces to be renamed from eth0 -> enc1 thus
  breaking networking configuration and possibly other configs
  (e.g. daemons, firewalls etc).

  Therefore on upgrade (but not clean installs) something like
  persistent net rules should be generated to preserve ethX interface
  names and thus not break networking configuration.

  I will attach a proposed patch to achieve this shortly for review.

  It is important to fix this in stretch such that upgrades to stretch
  are flawless.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1682437/+subscriptions

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

[Touch-packages] [Bug 1682499] Re: disable dnssec

Hello Dimitri, 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-21ubuntu3
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/1682499

Title:
  disable dnssec

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

Bug description:
  [Impact]

   * dnssec functionality in systemd-resolved prevents network access in
  certain intra and extra net cases, due to failure to correctly
  validate dnssec entries. As a work-around we should disable dnssec by
  default.

  [Test Case]

   * Validate systemd-resolved is compiled with --with-default-dnssec=no
   * Validate that systemd-resolve --status says that DNSSEC setting is no

  $ systemd-resolve --status

  good output:
  ...
DNSSEC setting: no
  DNSSEC supported: no
  ...

  bad output:
  ...
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes
  ...

  [Regression Potential]

   * People who expect DNSSEC to be available by default will need to
  re-enable it by modifying systemd-resolve configuration file

  [Other Info]

   * See duplicate bugs and other bug reports in systemd for scenarios
  of DNS resolution failures when DNSSEC is enabled.

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

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

[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour

2017-04-18 Thread Tessa

Note that so far I haven't seen this since upgrading to 17.04, but I'm
keeping an eye on it.

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

2017-04-18 Thread Fred Senior

Other *nix machines and Macs their resolve.conf on my LAN just append
the dns server address that is configured om their network manager or
network preferences. Why Ubuntu does not follow this I do not
understand.

It stops my Ubuntu devices resolving FQDN's on the the LAN. I have to
manually edit /etc/resolv.conf to fix this.

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

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

[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour

2017-04-18 Thread Claudio de Souza

I am having the same problem.

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

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

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

[Touch-packages] [Bug 1683884] [NEW] openresolv is less crippled than debian-resolvconf for security-focused configurations

2017-04-18 Thread Jason A. Donenfeld

Public bug reported:

Ubuntu relies on Debian's own "resolvconf" which is vastly inferior to
Openresolv and makes it impossible to securely set up DNS servers for
ephemeral secure tunnel interfaces.

Specifically, Debian's "resolvconf" relies on a hard coded list of
interface templates. For virtual interfaces or renamed interfaces --
such as those used for creating secure tunnels -- the DNS entries will
be lowest priority. This means it's not possible to override the current
DNS with a DNS bound to particular arbitrarily-named interface. In other
words, Debian's "resolvconf" explicitly ties interface naming templates
to interface metrics. Openresolv has the `-m` option for this. Using `-m
0` will give an interface's DNS servers top priority.

Secondly, and importantly, Debian's "resolvconf" does not support the
`-x` option, which specifies that a DNS servers of an interface should
be the _exclusive_ servers in use. This option is necessary to prevent
leaking DNS queries over another interface. Even with the aforementioned
`-m 0` option, an attacker could DoS the top priority DNS server in
order to leak queries to the second priority DNS server. Openresolv's
`-x` option fixes this, by allowing marking an interface as having
"exclusive" control over DNS.

Therefore, I'd suggest that either:
a) Ubuntu switch to using Openresolv by default instead of its own 
"resolvconf". The openresolv package already "Provides: resolvconf",so it 
should be a drop-in replacement; or
b) Debian's "resolvconf" backport these useful and necessary features from 
Openresolv.

For my specific usage, the recommendation in
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1680811 might
work as a fix for the `-m 0` issue, but it is less than ideal and does
accomplish `-x`. Therefore, I recommend doing either (a) or (b),
preferably (a).

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

** Description changed:

  Ubuntu relies on Debian's own "resolvconf" which is vastly inferior to
  Openresolv and makes it impossible to securely set up DNS servers for
  ephemeral secure tunnel interfaces.
  
  Specifically, Debian's "resolvconf" relies on a hard coded list of
  interface templates. For virtual interfaces or renamed interfaces --
  such as those used for creating secure tunnels -- the DNS entries will
  be lowest priority. This means it's not possible to override the current
  DNS with a DNS bound to particular arbitrarily-named interface. In other
  words, Debian's "resolvconf" explicitly ties interface naming templates
  to interface metrics. Openresolv has the `-m` option for this. Using `-m
  0` will give an interface's DNS servers top priority.
  
  Secondly, and importantly, Debian's "resolvconf" does not support the
  `-x` option, which specifies that a DNS servers of an interface should
  be the _exclusive_ servers in use. This option is necessary to prevent
  leaking DNS queries over another interface. Even with the aforementioned
  `-m 0` option, an attacker could DoS the top priority DNS server in
  order to leak queries to the second priority DNS server. Openresolv's
  `-x` option fixes this, by allowing marking an interface as having
  "exclusive" control over DNS.
  
  Therefore, I'd suggest that either:
- a) Ubuntu switch to using Openresolv by default instead of its own 
"resolvconf". The openresolv package already "Provides: openresolv",so it 
should be a drop-in replacement; or
+ a) Ubuntu switch to using Openresolv by default instead of its own 
"resolvconf". The openresolv package already "Provides: resolvconf",so it 
should be a drop-in replacement; or
  b) Debian's "resolvconf" backport these useful and necessary features from 
Openresolv.
  
  For my specific usage, the recommendation in
  https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1680811 might
  work as a fix for the `-m 0` issue, but it is less than ideal and does
  accomplish `-x`. Therefore, I recommend doing either (a) or (b),
  preferably (a).

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

Title:
  openresolv is less crippled than debian-resolvconf for security-
  focused configurations

Status in resolvconf package in Ubuntu:
  New

Bug description:
  Ubuntu relies on Debian's own "resolvconf" which is vastly inferior to
  Openresolv and makes it impossible to securely set up DNS servers for
  ephemeral secure tunnel interfaces.

  Specifically, Debian's "resolvconf" relies on a hard coded list of
  interface templates. For virtual interfaces or renamed interfaces --
  such as those used for creating secure tunnels -- the DNS entries will
  be lowest priority. This means it's not possible to override the
  current DNS with a DNS bound to particular arbitrarily-named
  interface. In other words, Debian's "resolvconf" explicitly ties
  interface naming templates to

[Touch-packages] [Bug 1384357] Re: Current composition is not canceled when a text input field is cleared programmatically

2017-04-18 Thread Olivier Tilloy

didUpdateTextOfFocusedElementByNonUserInput was removed from
WebViewClient by
https://chromium.googlesource.com/chromium/src/+/1c4ff63fc531d7bbb626329b8e7648ecc4b94b22.

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

Title:
  Current composition is not canceled when a text input field is cleared
  programmatically

Status in Oxide:
  In Progress
Status in ubuntu-keyboard:
  Invalid
Status in webbrowser-app:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

   1) on a touch device, browse to http://mikeasoft.com/~mike/oxide-clear.html
   2) focus the text field and type any word in it (e.g. "Ubuntu")
   3) tap the "X" below the text field, this clears it
   4) press backspace on the OSK

  Expected result: nothing happens

  Current result: the previous preedit is restored and backspace deletes
  the last letter (in that example, the text field now contains "Ubunt")

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

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

[Touch-packages] [Bug 1384357] Re: Current composition is not canceled when a text input field is cleared programmatically

2017-04-18 Thread Olivier Tilloy

The issue still exists and can also be observed on desktop with ubuntu-
keyboard.

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

Title:
  Current composition is not canceled when a text input field is cleared
  programmatically

Status in Oxide:
  In Progress
Status in ubuntu-keyboard:
  Invalid
Status in webbrowser-app:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

   1) on a touch device, browse to http://mikeasoft.com/~mike/oxide-clear.html
   2) focus the text field and type any word in it (e.g. "Ubuntu")
   3) tap the "X" below the text field, this clears it
   4) press backspace on the OSK

  Expected result: nothing happens

  Current result: the previous preedit is restored and backspace deletes
  the last letter (in that example, the text field now contains "Ubunt")

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

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

[Touch-packages] [Bug 1682437] Re: udev does not preserve virtio interface names on s390x upgrades

** Description changed:

+ [Impact]
+ 
+  * Upgrading s390x, kvm/qemu instances from yakkety to zesty results in a 
change of network interface names (e.g. from eth0 to stable/predictable bus_id 
name enc3, just like on z/VM and LPAR).
+  * This obviously results in loss of network connectivity as 
/etc/network/interfaces no longer matches the network interface names 
configured by systemd.
+  * The proposal is to generate udev rules on upgrade to preserve active 
interface names, in a very similar fashion to the no longer in use 
net-persistent-name generator.
+ 
+ [Test Case]
+ 
+  * Install zesty from scratch in kvm/qemu, network interfaces should use enc* 
names.
+  * Install yakkety, upgrade to zesty, network intefaces should use eth* names 
after upgrade and reboot.
+ 
+ [Regression Potential]
+ 
+  * This solution is similar to previous upgrades to stable networking
+ names for other types of network interfaces. This will make upgraded
+ systems look different from freshly installed systems. For users aiming
+ to have homogenious environments it is recommended to remove
+ /etc/udev/rules.d/70-persistent-net.rules and readjust
+ networking/daemon/firewall configurations to the new stable names enc*.
+ 
+ [Other Info]
+  
+  * Original bug report filed in debian.
+ 
  Package: udev
  Version: 232-20
  Severity: important
  
  Dear Maintainer,
  
  systemd 232-20 introduce the patch to generate stable interface names
  for virtio network interfaces on s390x. This is a good thing, and
  those names should be used for new installations.
  
  However, when upgrading existing virtual machines installations the
  new udev causes interfaces to be renamed from eth0 -> enc1 thus
  breaking networking configuration and possibly other configs
  (e.g. daemons, firewalls etc).
  
  Therefore on upgrade (but not clean installs) something like
  persistent net rules should be generated to preserve ethX interface
  names and thus not break networking configuration.
  
  I will attach a proposed patch to achieve this shortly for review.
  
  It is important to fix this in stretch such that upgrades to stretch
  are flawless.

** Also affects: systemd (Ubuntu Zesty)
   Importance: High
 Assignee: Dimitri John Ledkov (xnox)
   Status: Triaged

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

Title:
  udev does not preserve virtio interface names on s390x upgrades

Status in Release Notes for Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Zesty:
  Triaged

Bug description:
  [Impact]

   * Upgrading s390x, kvm/qemu instances from yakkety to zesty results in a 
change of network interface names (e.g. from eth0 to stable/predictable bus_id 
name enc3, just like on z/VM and LPAR).
   * This obviously results in loss of network connectivity as 
/etc/network/interfaces no longer matches the network interface names 
configured by systemd.
   * The proposal is to generate udev rules on upgrade to preserve active 
interface names, in a very similar fashion to the no longer in use 
net-persistent-name generator.

  [Test Case]

   * Install zesty from scratch in kvm/qemu, network interfaces should use enc* 
names.
   * Install yakkety, upgrade to zesty, network intefaces should use eth* names 
after upgrade and reboot.

  [Regression Potential]

   * This solution is similar to previous upgrades to stable networking
  names for other types of network interfaces. This will make upgraded
  systems look different from freshly installed systems. For users
  aiming to have homogenious environments it is recommended to remove
  /etc/udev/rules.d/70-persistent-net.rules and readjust
  networking/daemon/firewall configurations to the new stable names
  enc*.

  [Other Info]
   
   * Original bug report filed in debian.

  Package: udev
  Version: 232-20
  Severity: important

  Dear Maintainer,

  systemd 232-20 introduce the patch to generate stable interface names
  for virtio network interfaces on s390x. This is a good thing, and
  those names should be used for new installations.

  However, when upgrading existing virtual machines installations the
  new udev causes interfaces to be renamed from eth0 -> enc1 thus
  breaking networking configuration and possibly other configs
  (e.g. daemons, firewalls etc).

  Therefore on upgrade (but not clean installs) something like
  persistent net rules should be generated to preserve ethX interface
  names and thus not break networking configuration.

  I will attach a proposed patch to achieve this shortly for review.

  It is important to fix this in stretch such that upgrades to stretch
  are flawless.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1682437/+subscriptions

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

[Touch-packages] [Bug 670178] Re: SVG file rendered incorrectly

2017-04-18 Thread madbiologist

Oops, I meant to say that the fix will be in the next release in the
2.41 series (2.41.x).

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

Title:
  SVG file rendered incorrectly

Status in librsvg:
  Confirmed
Status in librsvg package in Ubuntu:
  Triaged

Bug description:
  The attached stars.svg is rendered incorrectly in Eye of Gnome,
  Nautilus preview, Gimp import, Evince etc. The top left star does not
  have its shadow.

  Works correctly in inkscape, Firefox, Chrome.

  Created in inkscape.

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

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

[Touch-packages] [Bug 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in

2017-04-18 Thread Hans Joachim Desserud

** Tags added: zesty

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

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  Don't run aplication after upgrade from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun Apr 24 21:08:20 2016
  DpkgTerminalLog:
   Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ...
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  DuplicateSignature:
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1672542] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

** Description changed:

+ [Impact]
+ 
+  * Due to upgraded netcat in zesty, ADT testcase 12 started to hang upon 
calls to netcat.
+  * The upgraded netcat changed default behaviour from -q0 (quit straight 
away) to -q-1 (wait infinity)
+  * Proposed fix is an upstream cherry-pick to add a `-w1` option (quit after 
1 second) which resolves the test-suite hang and is compatible across Ubuntu 
and Fedora (uses nmap netcat).
+ 
+ [Test Case]
+ 
+  * ADT tests should pass on kvm architectures.
+ 
+ [Regression Potential]
+ 
+  * This is a testsuite fix for netcat-openbsd compat, does not affect
+ systemd runtime binaries / libraries.
+ 
+ [Other Info]
+  
+  * Original bug report.
+ 
  Testing failed on:
    amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
    i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
    ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz
  
  Upstream tests time out. Last thing displayed in the logs before the
  timeout is the login prompt from a container running one of the tests.

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

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Zesty:
  In Progress

Bug description:
  [Impact]

   * Due to upgraded netcat in zesty, ADT testcase 12 started to hang upon 
calls to netcat.
   * The upgraded netcat changed default behaviour from -q0 (quit straight 
away) to -q-1 (wait infinity)
   * Proposed fix is an upstream cherry-pick to add a `-w1` option (quit after 
1 second) which resolves the test-suite hang and is compatible across Ubuntu 
and Fedora (uses nmap netcat).

  [Test Case]

   * ADT tests should pass on kvm architectures.

  [Regression Potential]

   * This is a testsuite fix for netcat-openbsd compat, does not affect
  systemd runtime binaries / libraries.

  [Other Info]
   
   * Original bug report.

  Testing failed on:
    amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
    i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
    ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz

  Upstream tests time out. Last thing displayed in the logs before the
  timeout is the login prompt from a container running one of the tests.

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

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

[Touch-packages] [Bug 1668347] Re: Unable to set bridge_portpriority with networkd

** Description changed:

+ [Impact]
+ 
+  * Netplan uses systemd-netword provider to configure all sorts of networking 
settings
+  * However, unlike ifupdown, released versions of systemd do not support 
setting bridgeport priority, aka
+ `brctl setportprio   `
+  * This prevents full migration from ifupdown to netplan/systemd-networkd for 
projects like MAAS that do need to configure equal cost; yet differential 
priority bridge ports.
+  * This is proposal to cherrypick this functionality which essentially 
accepts one more key in the .network units; and send those values via netlink.
+ 
+ [Test Case]
+ 
+  * networkd-test.py is executed as part of autopkgtests that configures
+ a bridge, and sets various valid bridge port priorities and verifies
+ from sysfs that those were correctly set by systemd.
+ 
+  * Alternativey create a bridge .link unit, and specify .network unit
+ for a bridge port and use Priority=4 setting in the [Bridge] section in
+ the said unit to modify bridge port priority.
+ 
+ 
+ [Regression Potential] 
+ 
+  * This is an upstream cherrypick of functionality that will be included
+ in 234 release. However, since MAAS and netplan target stable releases,
+ I would like to cherrypick this functionality all the way back to
+ xenial. This almost a feature, rather than a bugfix, but it is so small
+ and accompanied by regression testsuite that it is almost a tiny bugfix.
+ 
+ [Other Info]
+  
+  * Original request to support this feature.
+ 
+ 
  1. root@ubuntu:/run/systemd/network# lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04
  
  2. root@ubuntu:/run/systemd/network# apt-cache policy systemd
  systemd:
-   Installed: 232-18ubuntu1
-   Candidate: 232-18ubuntu1
-   Version table:
-  *** 232-18ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 232-18ubuntu1
+   Candidate: 232-18ubuntu1
+   Version table:
+  *** 232-18ubuntu1 500
+ 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  3. Using a networkd config like this:
  
- # cat 10-netplan-eth1.network 
+ # cat 10-netplan-eth1.network
  [Match]
  MACAddress=52:54:00:12:34:02
  Name=eth1
  
  [Network]
  Bridge=br0
  LinkLocalAddressing=no
  IPv6AcceptRA=no
  
  [Bridge]
  Cost=50
  Priority=28
  
- %  cat /sys/class/net/br0/brif/eth1/priority 
+ %  cat /sys/class/net/br0/brif/eth1/priority
  28
  
- 
- 4. %  cat /sys/class/net/br0/brif/eth1/priority 
+ 4. %  cat /sys/class/net/br0/brif/eth1/priority
  32
- 
  
  When using ifupdown and /etc/network/interfaces to configure a bridge
  users are able to specify a bridge port priority:
  
  auto br0
  iface br0 inet static
-   address 192.168.1.1
-   bridge_ports eth1 eth2
-   bridge_portprio eth1 28
-   bridge_portprio eth2 14
+   address 192.168.1.1
+   bridge_ports eth1 eth2
+   bridge_portprio eth1 28
+   bridge_portprio eth2 14
  
  Which results in the bridge hook scripts running:
  
  brctl setportprio br0 eth1 28
  
  which is visible via:
  
  /sys/class/net/br0/brif/eth2/priority
  
  Note, networkd does not mention PortPriority under netdev Bridge section,
  however, PathCost is mentioned.  It appears networkd is missing an 
implementation.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Mon Feb 27 17:11:32 2017
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=900c1e3f-f682-4455-949c-ebdbf60ac6f5 ro console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.1-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-zesty
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-zesty:cvnQEMU:ct1:cvrpc-i440fx-zesty:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-zesty
  dmi.sys.vendor: QEMU

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

Title:
  Unable to set bridge_portpriority with networkd

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Zesty:
  In Progress

Bug description:
  [Impact]

   * Netplan uses systemd-netword provider to configure all sorts of

[Touch-packages] [Bug 1683872] Re: package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from o

2017-04-18 Thread Hans Joachim Desserud

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1574351, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1574351
   package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite 
shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different 
from other instances of package libperl5.22:i386

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

Title:
  package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz',
  which is different from other instances of package libperl5.24:i386

Status in perl package in Ubuntu:
  New

Bug description:
  I think it occured while trying to scan and install scanner drivers.
  Never had an issue with scanning in 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libperl5.24 5.24.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 18 18:55:31 2017
  DuplicateSignature:
   package:libperl5.24:5.24.1-2ubuntu1
   Unpacking libperl5.24:i386 (5.24.1-2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-DyYUm9/4-libperl5.24_5.24.1-2ubuntu1_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from other 
instances of package libperl5.24:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from other 
instances of package libperl5.24:i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: perl
  Title: package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', which is 
different from other instances of package libperl5.24:i386
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)

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

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

[Touch-packages] [Bug 670178] Re: SVG file rendered incorrectly

2017-04-18 Thread madbiologist

Fixed upstream.  Will be in librsvg 2.41.

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

Title:
  SVG file rendered incorrectly

Status in librsvg:
  Confirmed
Status in librsvg package in Ubuntu:
  Triaged

Bug description:
  The attached stars.svg is rendered incorrectly in Eye of Gnome,
  Nautilus preview, Gimp import, Evince etc. The top left star does not
  have its shadow.

  Works correctly in inkscape, Firefox, Chrome.

  Created in inkscape.

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

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

[Touch-packages] [Bug 1682484] Re: systemd: Logging from gnome session is passed on to all syslog facilities

** Description changed:

+ [Impact]
+ 
+  * untagged messages in journal do not have any syslog facility specified, 
this may result in spamming logs.
+  * The solution is to cherrypick upstream fix which sanity checks and 
provides default syslog facility, e.g. it sets user facility on user/desktop 
session syslog/journal entries.
+ 
+ [Test Case]
+ 
+  * launch gnome terminal
+  * check output of $ journalctl -o verbose -e
+  * entries from gnome-terminal (e.g. "Allocating size to GtkBox without 
calling gtk_widget_get_preferred_width/height()") should have a syslog 
facility listed as one of the variables.
+ 
+ 
+ [Regression Potential] 
+ 
+  * We are changing (fixing regression) in logging, thus release images
+ have those messages untagged, and may require different filtering rules
+ before this update is applied.
+ 
+ [Other Info]
+  
+  * Original bug report from debian.
+ 
  Bug imported from Debian https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=837893
  
  Package: systemd
  Version: 231-6
  Severity: normal
  
  Since recently, log messages from programs running under the gnome
  session have started appearing in all logs in /var/logs, including
  /var/logs/kern.log, even though my rsyslog configuration has not
  changed, and correctly only routes kern.* there.
  
  This is very annoying since it fills the logs with messages that don't
  belong there, and makes running logcheck tedious.
  
  It seems this is a recent regression, since before I was able to route
  these messages to a low-priority log using the following rsyslog
  configuration:
  
-   user.=info;user.=notice;\
-   user.=warn  -/var/log/user-low.log
+   user.=info;user.=notice;\
+   user.=warn  -/var/log/user-low.log
  
  If I look at the messages directly with journalctl -o verbose, it seems
  they do not set the syslog facility, which should make them end up with
  user facility, but doesn't.

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

Title:
  systemd: Logging from gnome session is passed on to all syslog
  facilities

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Zesty:
  Confirmed

Bug description:
  [Impact]

   * untagged messages in journal do not have any syslog facility specified, 
this may result in spamming logs.
   * The solution is to cherrypick upstream fix which sanity checks and 
provides default syslog facility, e.g. it sets user facility on user/desktop 
session syslog/journal entries.

  [Test Case]

   * launch gnome terminal
   * check output of $ journalctl -o verbose -e
   * entries from gnome-terminal (e.g. "Allocating size to GtkBox without 
calling gtk_widget_get_preferred_width/height()") should have a syslog 
facility listed as one of the variables.

  
  [Regression Potential] 

   * We are changing (fixing regression) in logging, thus release images
  have those messages untagged, and may require different filtering
  rules before this update is applied.

  [Other Info]
   
   * Original bug report from debian.

  Bug imported from Debian https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=837893

  Package: systemd
  Version: 231-6
  Severity: normal

  Since recently, log messages from programs running under the gnome
  session have started appearing in all logs in /var/logs, including
  /var/logs/kern.log, even though my rsyslog configuration has not
  changed, and correctly only routes kern.* there.

  This is very annoying since it fills the logs with messages that don't
  belong there, and makes running logcheck tedious.

  It seems this is a recent regression, since before I was able to route
  these messages to a low-priority log using the following rsyslog
  configuration:

    user.=info;user.=notice;\
    user.=warn  -/var/log/user-low.log

  If I look at the messages directly with journalctl -o verbose, it seems
  they do not set the syslog facility, which should make them end up with
  user facility, but doesn't.

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

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

[Touch-packages] [Bug 1682499] Re: disable dnssec

** Description changed:

- because pitti says so
+ [Impact]
  
- cherrypick from debian
+  * dnssec functionality in systemd-resolved prevents network access in
+ certain intra and extra net cases, due to failure to correctly validate
+ dnssec entries. As a work-around we should disable dnssec by default.
+ 
+ [Test Case]
+ 
+  * Validate systemd-resolved is compiled with --with-default-dnssec=no
+  * Validate that systemd-resolve --status says that DNSSEC setting is no
+ 
+ [Regression Potential]
+ 
+  * People who expect DNSSEC to be available by default will need to re-
+ enable it by modifying systemd-resolve configuration file
+ 
+ [Other Info]
+  
+  * See duplicate bugs and other bug reports in systemd for scenarios of DNS 
resolution failures when DNSSEC is enabled.

** Description changed:

  [Impact]
  
-  * dnssec functionality in systemd-resolved prevents network access in
+  * dnssec functionality in systemd-resolved prevents network access in
  certain intra and extra net cases, due to failure to correctly validate
  dnssec entries. As a work-around we should disable dnssec by default.
  
  [Test Case]
  
-  * Validate systemd-resolved is compiled with --with-default-dnssec=no
-  * Validate that systemd-resolve --status says that DNSSEC setting is no
+  * Validate systemd-resolved is compiled with --with-default-dnssec=no
+  * Validate that systemd-resolve --status says that DNSSEC setting is no
+ 
+ $ systemd-resolve --status
+ 
+ good output:
+ ...
+   DNSSEC setting: no
+ DNSSEC supported: no
+ ...
+ 
+ bad output:
+ ...
+   DNSSEC setting: allow-downgrade
+ DNSSEC supported: yes
+ ...
  
  [Regression Potential]
  
-  * People who expect DNSSEC to be available by default will need to re-
+  * People who expect DNSSEC to be available by default will need to re-
  enable it by modifying systemd-resolve configuration file
  
  [Other Info]
-  
-  * See duplicate bugs and other bug reports in systemd for scenarios of DNS 
resolution failures when DNSSEC is enabled.
+ 
+  * See duplicate bugs and other bug reports in systemd for scenarios of
+ DNS resolution failures when DNSSEC is enabled.

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

Title:
  disable dnssec

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Zesty:
  Confirmed

Bug description:
  [Impact]

   * dnssec functionality in systemd-resolved prevents network access in
  certain intra and extra net cases, due to failure to correctly
  validate dnssec entries. As a work-around we should disable dnssec by
  default.

  [Test Case]

   * Validate systemd-resolved is compiled with --with-default-dnssec=no
   * Validate that systemd-resolve --status says that DNSSEC setting is no

  $ systemd-resolve --status

  good output:
  ...
DNSSEC setting: no
  DNSSEC supported: no
  ...

  bad output:
  ...
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes
  ...

  [Regression Potential]

   * People who expect DNSSEC to be available by default will need to
  re-enable it by modifying systemd-resolve configuration file

  [Other Info]

   * See duplicate bugs and other bug reports in systemd for scenarios
  of DNS resolution failures when DNSSEC is enabled.

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

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

[Touch-packages] [Bug 1683875] [NEW] package python-tdb 1.3.8-2 failed to install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1

2017-04-18 Thread Артём

Public bug reported:

python-samba

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-tdb 1.3.8-2
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon Apr 17 19:41:06 2017
ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1
InstallationDate: Installed on 2017-03-14 (35 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: tdb
Title: package python-tdb 1.3.8-2 failed to install/upgrade: подпроцесс 
установлен сценарий pre-removal возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package python-tdb 1.3.8-2 failed to install/upgrade: подпроцесс
  установлен сценарий pre-removal возвратил код ошибки 1

Status in tdb package in Ubuntu:
  New

Bug description:
  python-samba

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-tdb 1.3.8-2
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Apr 17 19:41:06 2017
  ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 
1
  InstallationDate: Installed on 2017-03-14 (35 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: tdb
  Title: package python-tdb 1.3.8-2 failed to install/upgrade: подпроцесс 
установлен сценарий pre-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1683872] Re: package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from o

2017-04-18 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 perl in Ubuntu.
https://bugs.launchpad.net/bugs/1683872

Title:
  package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz',
  which is different from other instances of package libperl5.24:i386

Status in perl package in Ubuntu:
  New

Bug description:
  I think it occured while trying to scan and install scanner drivers.
  Never had an issue with scanning in 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libperl5.24 5.24.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 18 18:55:31 2017
  DuplicateSignature:
   package:libperl5.24:5.24.1-2ubuntu1
   Unpacking libperl5.24:i386 (5.24.1-2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-DyYUm9/4-libperl5.24_5.24.1-2ubuntu1_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from other 
instances of package libperl5.24:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from other 
instances of package libperl5.24:i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: perl
  Title: package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', which is 
different from other instances of package libperl5.24:i386
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)

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

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

[Touch-packages] [Bug 1683872] [NEW] package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from

2017-04-18 Thread Ola Persson

Public bug reported:

I think it occured while trying to scan and install scanner drivers.
Never had an issue with scanning in 16.10

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libperl5.24 5.24.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Tue Apr 18 18:55:31 2017
DuplicateSignature:
 package:libperl5.24:5.24.1-2ubuntu1
 Unpacking libperl5.24:i386 (5.24.1-2ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-DyYUm9/4-libperl5.24_5.24.1-2ubuntu1_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', 
which is different from other instances of package libperl5.24:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from other 
instances of package libperl5.24:i386
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: perl
Title: package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', which is 
different from other instances of package libperl5.24:i386
UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)

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


** Tags: amd64 apport-package need-duplicate-check package-conflict zesty

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

Title:
  package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz',
  which is different from other instances of package libperl5.24:i386

Status in perl package in Ubuntu:
  New

Bug description:
  I think it occured while trying to scan and install scanner drivers.
  Never had an issue with scanning in 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libperl5.24 5.24.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 18 18:55:31 2017
  DuplicateSignature:
   package:libperl5.24:5.24.1-2ubuntu1
   Unpacking libperl5.24:i386 (5.24.1-2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-DyYUm9/4-libperl5.24_5.24.1-2ubuntu1_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from other 
instances of package libperl5.24:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from other 
instances of package libperl5.24:i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: perl
  Title: package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', which is 
different from other instances of package libperl5.24:i386
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)

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

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

[Touch-packages] [Bug 1683868] [NEW] package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1

2017-04-18 Thread Артём

Public bug reported:

Python-Samba crashed my system... Now i dont do any update to system,
and reached error messages.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-crypto 2.6.1-6ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon Apr 17 19:41:07 2017
ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1
InstallationDate: Installed on 2017-03-14 (35 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: python-crypto
Title: package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to install/upgrade: 
подпроцесс установлен сценарий pre-removal возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-crypto (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to
  install/upgrade: подпроцесс установлен сценарий pre-removal возвратил
  код ошибки 1

Status in python-crypto package in Ubuntu:
  New

Bug description:
  Python-Samba crashed my system... Now i dont do any update to system,
  and reached error messages.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-crypto 2.6.1-6ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Apr 17 19:41:07 2017
  ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 
1
  InstallationDate: Installed on 2017-03-14 (35 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: python-crypto
  Title: package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to 
install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код 
ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1562002] Re: Nautilus: lag after choosing action in top right menu

2017-04-18 Thread Mantas Kriaučiūnas

I'm confirming, that gtk+3.0 version 3.18.9-1ubuntu3.3 from xenial-
proposed fixes nautilus (and GNOME-Desktop) freezing issue after
clicking any action in the Nautilus menu button on the right (tested
with "Invert selection", "New Tab", "Select All"). Tested in GNOME-
flashback and GNOME Shell sessions.

adminas@K101:~$ dpkg -s libgtk-3-0 |grep Ver
Version: 3.18.9-1ubuntu3.3


** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Nautilus: lag after choosing action in top right menu

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  Fix Committed

Bug description:
  # Impact
  This is known to affect Nautilus, but can potentially affect other 
applications too (the upstream bug has an example test app attached).

  See also the duplicate bug 1644393, which is another appearance of the
  same bug but with other symptoms.

  # Proposed Fix
  The proposed fix is an upstream commit taken from gtk-3-20 branch:
  https://git.gnome.org/browse/gtk+/commit/?id=10c3a2483635d1c1

  # Test Case
  https://bugzilla.gnome.org/show_bug.cgi?id=769287#c0 has a test case.

  # Regression Potential
  The bug is fixed in GTK+ 3.20.9, so the fix was already present in the 
version that shipped with Yakkety. I am not aware of any regressions.

  -
  choosing action like New Tab, New Folder, Select Items Matching, will make 
nautilus lag (unresponsive)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 25 20:52:21 2016
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+685+36'"
  InstallationDate: Installed on 2016-03-24 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1683804] Re: Word doubled in French translation of an error message of rmdir

2017-04-18 Thread Hans Joachim Desserud

Thanks for taking your time to report this issue and help making Ubuntu
better.

It looks like rmdir is part of the coreutils package and that this is
the string in question:
https://translations.launchpad.net/ubuntu/zesty/+source/coreutils/+pots/coreutils/fr/1167/+translate

** Package changed: ubuntu => coreutils (Ubuntu)

** Tags added: zesty

** Also affects: ubuntu-translations
   Importance: Undecided
   Status: New

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

Title:
  Word doubled in French translation of an error message of rmdir

Status in Ubuntu Translations:
  New
Status in coreutils package in Ubuntu:
  New

Bug description:
  In Ubuntu 17.04, the following command line:

  rmdir non-existent-directory

  outputs:
  rmdir: impossible de de supprimer 'non-existent-directory': Aucun fichier ou 
dossier de ce type

  This output should be:
  rmdir: impossible de supprimer 'non-existent-directory': Aucun fichier ou 
dossier de ce type

  "de de" → "de"

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

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

[Touch-packages] [Bug 1683804] [NEW] Word doubled in French translation of an error message of rmdir

You have been subscribed to a public bug:

In Ubuntu 17.04, the following command line:

rmdir non-existent-directory

outputs:
rmdir: impossible de de supprimer 'non-existent-directory': Aucun fichier ou 
dossier de ce type

This output should be:
rmdir: impossible de supprimer 'non-existent-directory': Aucun fichier ou 
dossier de ce type

"de de" → "de"

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


** Tags: bot-comment
-- 
Word doubled in French translation of an error message of rmdir
https://bugs.launchpad.net/bugs/1683804
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to coreutils in Ubuntu.

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

[Touch-packages] [Bug 1683860] [NEW] Search domains are not considered for split-tunnelling connections

2017-04-18 Thread Lastique

Public bug reported:

For split-tunnelling VPN connections (i.e. when the "Use only for
resources on this connection" checkbox is set in the IPv4 -> Routes
menu), the IPv4 -> Search Domains field has no effect.

For example, my VPN connection has the following parameters:

[ipv4]
dns=xxx.xxx.xxx.xxx;
dns-search=mydomain.net;
ignore-auto-dns=true
method=auto
never-default=true

After connecting, `systemd-resolve --status` shows for this connection:

Link 5 (tun0)
  Current Scopes: DNS
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes
 DNS Servers: xxx.xxx.xxx.xxx
  DNS Domain: ~mydomain.net

Note that there is a ~ character before the domain name, which has a
special semantics in systemd-resolved (as I understand, such entries are
not used as search names).

As a result, the search name is not used to complete simple names:

systemd-resolve foo
foo: resolve call failed: All attempts to contact name servers or networks 
failed
ping foo
ping: foo: Name or service not known
ping foo.mydomain.net
64 bytes from xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx): icmp_seq=1 ttl=62 time=5.33 ms


Note that the search domains work if the VPN connection is configured as 
non-split-tunnelling connection. In this case `systemd-resolve --status` shows 
"DNS Domain: mydomain.net" (without ~) and `systemd-resolve foo` and `ping foo` 
work as expected.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3
Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Apr 18 18:46:53 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-05-01 (717 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-04-18T18:41:39.752743
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages zesty

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

Title:
  Search domains are not considered for split-tunnelling connections

Status in network-manager package in Ubuntu:
  New

Bug description:
  For split-tunnelling VPN connections (i.e. when the "Use only for
  resources on this connection" checkbox is set in the IPv4 -> Routes
  menu), the IPv4 -> Search Domains field has no effect.

  For example, my VPN connection has the following parameters:

  [ipv4]
  dns=xxx.xxx.xxx.xxx;
  dns-search=mydomain.net;
  ignore-auto-dns=true
  method=auto
  never-default=true

  After connecting, `systemd-resolve --status` shows for this
  connection:

  Link 5 (tun0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes
   DNS Servers: xxx.xxx.xxx.xxx
DNS Domain: ~mydomain.net

  Note that there is a ~ character before the domain name, which has a
  special semantics in systemd-resolved (as I understand, such entries
  are not used as search names).

  As a result, the search name is not used to complete simple names:

  systemd-resolve foo
  foo: resolve call failed: All attempts to contact name servers or networks 
failed
  ping foo
  ping: foo: Name or service not known
  ping foo.mydomain.net
  64 bytes from xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx): icmp_seq=1 ttl=62 time=5.33 
ms

  
  Note that the search domains work if the VPN connection is configured as 
non-split-tunnelling connection. In this case `systemd-resolve --status` shows 
"DNS Domain: mydomain.net" (without ~) and `systemd-resolve foo` and `ping foo` 
work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Apr 18 18:46:53 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-01 (717 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid

[Touch-packages] [Bug 1683592] Re: tzdata doesn't set a reasonable default via debconf

We *do* select Etc/UTC as the default if the package is completely
unconfigured, as far as I can tell?

(zesty-amd64)root@nosferatu:~# apt-get purge tzdata
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  tzdata*
0 upgraded, 0 newly installed, 1 to remove and 117 not upgraded.
After this operation, 3082 kB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 11681 files and directories currently installed.)
Removing tzdata (2017b-1) ...
Purging configuration files for tzdata (2017b-1) ...
(zesty-amd64)root@nosferatu:~# rm -f /etc/localtime /etc/timezone 
(zesty-amd64)root@nosferatu:~# apt-get install tzdata
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  tzdata
0 upgraded, 1 newly installed, 0 to remove and 117 not upgraded.
Need to get 0 B/203 kB of archives.
After this operation, 3082 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package tzdata.
(Reading database ... 9783 files and directories currently installed.)
Preparing to unpack .../tzdata_2017b-1_all.deb ...
Unpacking tzdata (2017b-1) ...
Setting up tzdata (2017b-1) ...

Current default time zone: 'Etc/UTC'
Local time is now:  Tue Apr 18 15:38:41 UTC 2017.
Universal Time is now:  Tue Apr 18 15:38:41 UTC 2017.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

(zesty-amd64)root@nosferatu:~#


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

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

Title:
  tzdata doesn't set a reasonable default via debconf

Status in tzdata package in Ubuntu:
  Incomplete

Bug description:
  In cases where we don't prompt the user for a timezone value, the
  tzdata package should have a default value - Etc/UTC, which
  debootstrap currently populates for us but should really be handled in
  the package.

  This matters more now that we are demoting tzdata from the minimal set
  and users might have occasion to non-interactively install it on an
  existing system.

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

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

[Touch-packages] [Bug 1386553] Re: AMR audio codec not supported

** Changed in: ubuntu-touch-meta (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  AMR audio codec not supported

Status in Canonical System Image:
  Fix Released
Status in gst-libav1.0 package in Ubuntu:
  Invalid
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu RTM:
  Fix Released

Bug description:
  AMR audio codec is not supported currently. This is relevant for MMS
  videos, as AMR is the default for audio.

  With gstreamer debug env var GST_DEBUG=*:3 I see:

  0:00:39.390824849 23581 0xb3f053b0 WARN uridecodebin
  gsturidecodebin.c:939:unknown_type_cb: warning: No
  decoder available for type 'audio/AMR,
  codec_data=(buffer)001164616d726170706c010085, rate=(int)8000,
  channels

  $ system-image-cli -i
  current build number: 131
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-10-27 15:32:17
  version version: 131
  version ubuntu: 20141027.1
  version device: 20141015-32e0f27
  version custom: 1413941794

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

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

[Touch-packages] [Bug 1565908] Re: Allow calendar policy to read from device time zone

** Changed in: canonical-devices-system-image
 Assignee: Łukasz Zemczak (sil2100) => (unassigned)

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

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

Title:
  Allow calendar policy to read from device time zone

Status in Canonical System Image:
  Confirmed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu RTM:
  Confirmed

Bug description:
  qtorganizer5-eds needs to detect device current timezone to be able to
  save events in the correct tz. To do that we need read access to
  /etc/writable/timezone.

  Would be nice to have that policy on calendar policy file.

  This is part of the solution for bug #1563742

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

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

[Touch-packages] [Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job

2017-04-18 Thread Alexey

Unchecking "Auto power-on" in Blueman PowerManager plugin configuration
solved this issue for me.

Additionally (or alternatively) consider unchecking "Blueman Applet" in
"Startup Applications Preferences".

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

Title:
  Bluetooth won't stay disabled after reboot due to early upstart job

Status in rfkill package in Ubuntu:
  Confirmed

Bug description:
  Using a Dell XPS 13 with Ubuntu 12.04.

  In order to restore RF interfaces to their previous state between
  boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-
  store.conf (run while shutting down) and rfkill-restore.conf (run when
  starting up). However, while rfkill-restore.conf starts on the Upstart
  local-filesystems signal, there is a high probability that the RF kill
  switches in /sys/class/rfkill/ still won't yet be populated (i.e.
  every time on the Dell XPS 13). This results in behavior like the
  following:

  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  Bluetooth should have stayed disabled, but since the kill switches
  weren't present when rfkill-restore was run, the kill switch states
  were not restored.

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

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

I will look into reviewing the SRU uploads today or tomorrow. Thanks!

-- 
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:
  Confirmed
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 1604869] Re: address-book-app binary package uninstallable on yakkety arm64 due to missing unity8 binaries

** Changed in: address-book-app
   Status: In Progress => Fix Released

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

Title:
  address-book-app binary package uninstallable on yakkety arm64 due to
  missing unity8 binaries

Status in address-book-app:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Released

Bug description:
  As the title says. Currently yakkety has no unity8 for arm64 due to
  missing oxide-qt binaries (see LP: #1582638). This means all address-
  book-app arm64 landings will be blocked in -proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1604869/+subscriptions

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

[Touch-packages] [Bug 1583271] Re: drop libertine-demo & ubuntu-pd

** Changed in: ubuntu-system-image
   Status: In Progress => Invalid

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

Title:
  drop libertine-demo & ubuntu-pd

Status in The Avila project:
  New
Status in Canonical System Image:
  Fix Released
Status in Ubuntu system image:
  Invalid
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu RTM:
  Fix Released

Bug description:
  Moving to deliver legacy Xapps in the puritine click via the store requires 
that we drop the libertine-demo pkg from the image.
  As well, this means that xorg and other libertine pkgs can now be seeded into 
the normal ubuntu images (non-pd)

  note, this bug must be done in coordination with these
  bug 1583268
  bug 1583265

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

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

[Touch-packages] [Bug 1619468] Re: Uninstallable ubuntu-touch-meta

Yes, livecd-roofs has a few hints set up for the installation of ubuntu-
touch to succeed for some arches. That being said - yakkety is not a
target for us anyway right now, closing as Won't Fix.

** Changed in: ubuntu-touch-meta (Ubuntu Yakkety)
   Status: In Progress => Won't Fix

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

Title:
  Uninstallable ubuntu-touch-meta

Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta source package in Yakkety:
  Won't Fix

Bug description:
  ubuntu-touch -> depends qml-module-ubuntu-components-gles on amd64

  ubuntu-touch -> depends ubuntu-sdk-libs -> depends qml-module-ubuntu-
  components on amd64

  the -gles and non-gles conflict resulting in ubuntu-meta uninstallable

  This is critical and prevents migration of many packages.

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

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

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2017-04-18 Thread Andrei Aldea

You're welcome guys, glad to be of help.

@Venkat How exactly did you get microsd to work? Is this on the Asus
E200HA? I don't believe mine works as of now.

@Marco  Indeed 17.04 requires you to remove the default kernel after the
install. Does the line you added fix your sound issue?

Cheers,
Andrei

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Fix Committed

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

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1632772] Re: GNOME on Wayland does not start from LightDM

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

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

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

Title:
  GNOME on Wayland does not start from LightDM

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1632772] Re: GNOME on Wayland does not start from LightDM

2017-04-18 Thread Jeremy Bicha

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

** Changed in: ubuntu-gnome
   Status: New => Confirmed

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

Title:
  GNOME on Wayland does not start from LightDM

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1680496] Re: black screen when using 'GNOME Wayland' with lightdm on zesty

2017-04-18 Thread Jeremy Bicha

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

** This bug has been marked a duplicate of bug 1632772
   GNOME on Wayland does not start from LightDM

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

Title:
  black screen when using 'GNOME Wayland' with lightdm on zesty

Status in Ubuntu GNOME:
  New
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  In an up to date Ubuntu 17.04 amd64 vm, if I:

  1. install ubuntu-gnome-desktop
  2. select lightdm as the default
  3. sudo service lightdm stop ; sudo service lightdm start
  4. login choosing 'GNOME Wayland'

  the screen goes black with a flashing cursor in the upper left. If I
  'dpkg-reconfigure -plow lightdm' and choose 'gdm3', then stop lightdm
  and start gdm3, then I can login to a wayland gnome3 desktop.

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

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

[Touch-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

2017-04-18 Thread James Gross

Ah, so this code:

if dpkg --compare-versions "$2" le-nl "1.2.2-0ubuntu4"; then
mkdir -p /etc/NetworkManager/conf.d || true
# for old versions, override the global config with a null 
config
touch 
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf

Should have ge-nl rather than le-nl?  Seems like it's backwards and that
all new installs need the override, rather than old installs.

Also, why the decision to only do a netplan on install?

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:
   
  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

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

[Touch-packages] [Bug 446657] Re: Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends

2017-04-18 Thread spike speigel

For anyone who might find their way here while using newer versions of
Ubuntu such as 16.04 LTS, 16.10, 17.04...

This might be the solution.  Worked for me:

https://github.com/blueman-project/blueman/issues/682

** Bug watch added: github.com/blueman-project/blueman/issues #682
   https://github.com/blueman-project/blueman/issues/682

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

Title:
  Bluetooth's on/off status doesn't update from the SetProperty D-Bus
  method that bluetoothd sends

Status in GNOME Bluetooth:
  Unknown
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in bluez package in Fedora:
  Unknown

Bug description:
  Binary package hint: gnome-bluetooth

  Gnome's bluetooth applet should get a bluetooth device's on/off status
  through dbus from SetProperty setting sent by bluetoothd. This
  information was given in
  http://permalink.gmane.org/gmane.linux.bluez.kernel/4302 There is a
  setting controlling this feature: RememberPowered=true in
  /etc/bluetooth/main.conf

  Questions:
  Is the dbus message is even sent? If it is sent, why gnome-bluetooth doesn't 
do anything for it? Does bluez's SetProperty actually find the last (if even 
saved) bluetooth status?

  ProblemType: Bug
  Architecture: i386
  Date: Thu Oct  8 20:54:15 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: wl
  Package: gnome-bluetooth 2.28.1-0ubuntu1
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
  SourcePackage: gnome-bluetooth
  Uname: Linux 2.6.31-12-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/446657/+subscriptions

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

[Touch-packages] [Bug 1683836] [NEW] WIFI stoped working when updating 16.10 -> 17.04

2017-04-18 Thread jkn

Public bug reported:

Network manager detects 'Bus 001 Device 004: ID 148f:5370 Ralink
Technology, Corp. RT5370 Wireless Adapter'. It detects WIFI network, but
fails to connect. I booted with older kernel vmlinuz-4.8.0-46-generic:
same result.  I installed ubuntu 16.10 to same computer and WIFI does
work.  Password is OK.

Authentication seems to fail in Ubuntu 17.04:
Apr 18 17:13:01 k10 NetworkManager[727]: 
[1492524781.2784] policy: auto-activating connection 'ZyXELbb3a'
[1492524781.2798] device (wlxc83a35cde1eb): Activation: starting connection 
'ZyXELbb3a' (5362ba4d-c40e-40a3-8e17-4e3deaab48ae)
[1492524781.2801] device (wlxc83a35cde1eb): state change: disconnected -> 
prepare (reason 'none') [30 40 0]
[1492524781.6699] device (wlxc83a35cde1eb): set-hw-addr: set-cloned MAC address 
to C8:3A:35:CD:E1:EB (permanent)
[1492524781.9391] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
[1492524781.9394] device (wlxc83a35cde1eb): Activation: (wifi) access point 
'ZyXELbb3a' has security, but secrets are required.
[1492524781.9395] device (wlxc83a35cde1eb): state change: config -> need-auth 
(reason 'none') [50 60 0]
[1492524781.9748] device (wlxc83a35cde1eb): state change: need-auth -> prepare 
(reason 'none') [60 40 0]
[1492524781.9782] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
[1492524781.9792] device (wlxc83a35cde1eb): Activation: (wifi) connection 
'ZyXELbb3a' has security, and secrets exist.  No new secrets needed.
[1492524781.9796] Config: added 'ssid' value 'ZyXELbb3a'
[1492524781.9800] Config: added 'scan_ssid' value '1'
[1492524781.9803] Config: added 'key_mgmt' value 'WPA-PSK'
[1492524781.9806] Config: added 'auth_alg' value 'OPEN'
[1492524781.9808] Config: added 'psk' value ''
[1492524781.9821] sup-iface[0x55d34390d2d0,wlxc83a35cde1eb]: config: set 
interface ap_scan to 1
[1492524782.0010] device (wlxc83a35cde1eb): supplicant interface state: 
inactive -> scanning
[1492524783.3941] device (wlxc83a35cde1eb): supplicant interface state: 
scanning -> authenticating
[1492524783.5787] device (wlxc83a35cde1eb): supplicant interface state: 
authenticating -> disconnected
[1492524793.5868] device (wlxc83a35cde1eb): supplicant interface state: 
disconnected -> scanning
[1492524794.9891] device (wlxc83a35cde1eb): supplicant interface state: 
scanning -> authenticating
[1492524795.1145] device (wlxc83a35cde1eb): supplicant interface state: 
authenticating -> disconnected


Ubuntu 16.10 is same to authentication:
Apr 18 13:46:10 k15 NetworkManager[714]: 
[1492512370.3874] policy: auto-activating connection 'ZyXELbb3a'
[1492512370.3884] device (wlxc83a35cde1eb): Activation: starting connection 
'ZyXELbb3a' (fd199068-2375-4268-bb74-d60484d1fadb)
[1492512370.3886] device (wlxc83a35cde1eb): state change: disconnected -> 
prepare (reason 'none') [30 40 0]
[1492512370.3887] manager: NetworkManager state is now CONNECTING
[1492512370.3895] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
[1492512370.3897] device (wlxc83a35cde1eb): Activation: (wifi) access point 
'ZyXELbb3a' has security, but secrets are required.
[1492512370.3898] device (wlxc83a35cde1eb): state change: config -> need-auth 
(reason 'none') [50 60 0]
[1492512370.3936] device (wlxc83a35cde1eb): state change: need-auth -> prepare 
(reason 'none') [60 40 0]
[1492512370.3940] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
[1492512370.3943] device (wlxc83a35cde1eb): Activation: (wifi) connection 
'ZyXELbb3a' has security, and secrets exist.  No new secrets needed.
[1492512370.3943] Config: added 'ssid' value 'ZyXELbb3a'
[1492512370.3944] Config: added 'scan_ssid' value '1'
[1492512370.3944] Config: added 'key_mgmt' value 'WPA-PSK'
[1492512370.3944] Config: added 'auth_alg' value 'OPEN'
[1492512370.3944] Config: added 'psk' value ''
[1492512370.3949] sup-iface[0x55da7c3f2210,wlxc83a35cde1eb]: config: set 
interface ap_scan to 1
[1492512371.8005] device (wlxc83a35cde1eb): supplicant interface state: 
inactive -> authenticating
[1492512371.8071] device (wlxc83a35cde1eb): supplicant interface state: 
authenticating -> associating
[1492512371.8216] device (wlxc83a35cde1eb): supplicant interface state: 
associating -> 4-way handshake
[1492512371.8482] device (wlxc83a35cde1eb): supplicant interface state: 4-way 
handshake -> completed
[1492512371.8482] device (wlxc83a35cde1eb): Activation: (wifi) Stage 2 of 5 
(Device Configure) successful.  Connected to wireless network 'ZyXELbb3a'.
[1492512371.8483] device (wlxc83a35cde1eb): state change: config -> ip-config 
(reason 'none') [50 70 0]
[1492512371.8623] dhcp4 (wlxc83a35cde1eb): activation: beginning transaction 
(timeout in 45 seconds)
Apr 18 13:46:11 k15 NetworkManager[714]:   [1492512371.9292] dhcp4 
(wlxc83a35cde1eb): dhclient started with pid 1027

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3
ProcVersionSignature:

[Touch-packages] [Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job

2017-04-18 Thread spike speigel

@aapo-rantalainen

This might be the solution.  Worked for me:

https://github.com/blueman-project/blueman/issues/682

** Bug watch added: github.com/blueman-project/blueman/issues #682
   https://github.com/blueman-project/blueman/issues/682

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

Title:
  Bluetooth won't stay disabled after reboot due to early upstart job

Status in rfkill package in Ubuntu:
  Confirmed

Bug description:
  Using a Dell XPS 13 with Ubuntu 12.04.

  In order to restore RF interfaces to their previous state between
  boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-
  store.conf (run while shutting down) and rfkill-restore.conf (run when
  starting up). However, while rfkill-restore.conf starts on the Upstart
  local-filesystems signal, there is a high probability that the RF kill
  switches in /sys/class/rfkill/ still won't yet be populated (i.e.
  every time on the Dell XPS 13). This results in behavior like the
  following:

  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  Bluetooth should have stayed disabled, but since the kill switches
  weren't present when rfkill-restore was run, the kill switch states
  were not restored.

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

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

[Touch-packages] [Bug 1296114] Re: [desktop] Bluetooth is always enabled after reboot even if it was disabled

2017-04-18 Thread spike speigel

@cibersheep

This might be the solution.  Worked for me:

https://github.com/blueman-project/blueman/issues/682

** Bug watch added: github.com/blueman-project/blueman/issues #682
   https://github.com/blueman-project/blueman/issues/682

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

Title:
  [desktop] Bluetooth is always enabled after reboot even if it was
  disabled

Status in Bluetooth Menu:
  Invalid
Status in indicator-bluetooth package in Ubuntu:
  Invalid
Status in rfkill package in Ubuntu:
  Incomplete
Status in urfkill package in Ubuntu:
  Triaged

Bug description:
  If bluetooth was disabled using the switcher in the bluetooth
  indicator, after reboot it becomes enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 22 22:34:52 2014
  InstallationDate: Installed on 2014-01-27 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: 
Connecting to session manager

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

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

[Touch-packages] [Bug 1682386] Re: systemd-resolved can not resolve .coop domain names

2017-04-18 Thread Quentin Henriet

Same problem after upgrading my two computers from Xubuntu 16.10 and
from Kubuntu 16.10 to X/Kubuntu 17.04 today.

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

Title:
  systemd-resolved can not resolve .coop domain names

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu Gnome 17.04, systemd version 232-21ubuntu2.

  I found that .coop domain nomes are not being resolved. If I switch to
  another DNS server (instead of 127.0.0.53, which is the current
  default in 17.04), then .coop domains are resolved:

  $ nslookup
  > www.somenergia.coop
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find www.somenergia.coop: SERVFAIL
  > server 8.8.8.8
  Default server: 8.8.8.8
  Address: 8.8.8.8#53
  > www.somenergia.coop
  Server:   8.8.8.8
  Address:  8.8.8.8#53

  Non-authoritative answer:
  Name: www.somenergia.coop
  Address: 164.132.200.9
  >

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

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

[Touch-packages] [Bug 1680496] Re: black screen when using 'GNOME Wayland' with lightdm on zesty

2017-04-18 Thread Sebastien Bacher

duplicate bug #1632772?

@Jeremy, that gdm commit suggests it's not a technical reason but that
they assume that if wayland is not using in gdm that's because it's not
working on the configuration so there is no point listing a session
which is not going to work

https://git.gnome.org/browse/gdm/commit/?id=246d9a23

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

Title:
  black screen when using 'GNOME Wayland' with lightdm on zesty

Status in Ubuntu GNOME:
  New
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  In an up to date Ubuntu 17.04 amd64 vm, if I:

  1. install ubuntu-gnome-desktop
  2. select lightdm as the default
  3. sudo service lightdm stop ; sudo service lightdm start
  4. login choosing 'GNOME Wayland'

  the screen goes black with a flashing cursor in the upper left. If I
  'dpkg-reconfigure -plow lightdm' and choose 'gdm3', then stop lightdm
  and start gdm3, then I can login to a wayland gnome3 desktop.

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

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

[Touch-packages] [Bug 1682386] Re: systemd-resolved can not resolve .coop domain names