[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text

[James Cameron]

G'day Brian.  The patch command automatically applies a patch to a set
of files.  The particular patch has a sacrificial path element so the
--strip 1 option should be used.  The --dry-run option is also useful
for testing.  So it would be "patch --strip 1 --dry-run < file.patch",
where file.patch is what was downloaded from the upstream bug report.
If that works, repeat again without the --dry-run.

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

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in lubuntu-artwork package in Ubuntu:
  Invalid
Status in abiword source package in Xenial:
  Confirmed
Status in gtk+3.0 source package in Xenial:
  Confirmed
Status in lubuntu-artwork source package in Xenial:
  Invalid

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

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

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

[Touch-packages] [Bug 1685193] Re: [17.04] systemd-udevd. Scripts started by a rule won't write to /var/log

[flux242]

what are the intentions?

systemd power management huh? Which of these problems has already been
solved since 15.10 then:

1. System doesn't react on the power supply plugged/unplugged events
2. Lid close events are handled by the systemd by default and not by the 
xfce4-power-manager
3. System doesn't execute pm-utils hooks on sleep/resume events, i.e when the 
power cord is unplugged all powertop's tunable should be in GOOD state. Are 
they?

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

Title:
  [17.04] systemd-udevd. Scripts started by a rule won't write to
  /var/log

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this is rather weird problem but after upgrading to the 17.04 the pm-
  powersave script I start by a udev rule stopped working. After
  debuggin a bit I found a place that causes the error. In the /usr/lib
  /pm-utils/pm-functions there's the init_logfile function that called
  exec to redirect script's output to the /var/log/pm-powersave.log. And
  it fails to do so because root (under which the script is started) has
  no permission to write to anything under the /var/log/

  Inside of that functions I added additional logging to prove that
  1. the script is started under root
  2. the file /var/log/pm-powersave.log exist and it has 644 permissions
  3. the root can read from /var/log/*
  4. /var permissions are 755, /var/log permissions are 775

  If the script is started with 'sudo /usr/sbin/pm-powersave true' then
  it works!

  So what could this be? Could the apparmor prevent udevd to write to
  /var/log ?

  Temporary solution is to write to /tmp/pm-powersave.log

  How to reproduce:
  1. add the following rule to /etc/udev/rules.d/test.rules
  SUBSYSTEM=="power_supply", ATTR{online}=="0", RUN+="/usr/sbin/testudev true"
  SUBSYSTEM=="power_supply", ATTR{online}=="1", RUN+="/usr/sbin/testudev false"
  2. create /usr/sbin/testudev script and make it executable
  #!/usr/bin/env bash

  logger "testudev: I'm: $(whoami)"
  echo test >> /var/log/testudev.log

  3. Plug and unplug the power plug. Check the syslog:
  Apr 21 13:17:06 chrome root: testudev: I'm: root
  Apr 21 13:17:06 chrome systemd-udevd[2]: Process '/usr/sbin/testudev 
false' failed with exit code 1.

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

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

[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text

[Brian]

@James- Thanks, I can do the compile and build easy enough. Only
question I have then is for the patch, is there an automated way to
apply it to the file? I do not have experience in applying changes in
this manner, but I can always just change the code. Just hoping to learn
more here so I can participate better in the future.

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

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in lubuntu-artwork package in Ubuntu:
  Invalid
Status in abiword source package in Xenial:
  Confirmed
Status in gtk+3.0 source package in Xenial:
  Confirmed
Status in lubuntu-artwork source package in Xenial:
  Invalid

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

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

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

[Touch-packages] [Bug 1687353] Re: System freezes due to ALSA error and recovers after significant time

[Leonardo Müller]

The easiest way to reproduce it was in the game Starbound. Teleporting,
quickly the computer would freeze. I could freeze the computer in
seconds doing this.

While the 4.10 kernel available to install with linux-generic-
hwe-16.04-edge has this bug, I believe this problem is corrected in the
4.11 kernel I downloaded at http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.11/

I was able to play for many hours without the problem since I installed
the kernel version 4.11. There are change notes regarding ALSA on
kernel.org, I believe they are related with the problem I was having.

Or I am being absurdly lucky or the bug was corrected on upstream.

** Tags added: kernel-fixed-upstream

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

Title:
  System freezes due to ALSA error and recovers after significant time

Status in alsa-lib package in Ubuntu:
  Confirmed

Bug description:
  Hello

  I have a Lenovo Ideapad 310. I was having issues with power
  management, and was using upstream kernels. I noticed they had
  frequent freezes, so I decided to use the standard from Ubuntu 16.04
  (today, 4.4.0-75). But now it has this freezes too, so something which
  was bugged on the newer kernel was inserted on 4.4.0-75, as previous
  version (4.4.0-72) hadn't this issue.

  What is happening is: the system freezes. The sound that was being
  played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't
  work. The system completely stops. Normally, I would just power the
  computer off keeping the power button pressed. But this time I tried
  to recover it, as the syslog ended always corrupted. I needed to gets
  the logs at least once. So I started to disconnect hardware parts:
  battery charger, external USB HDD (it was not being accessed), USB
  mouse, USB keyboard. When I disconnected the sound jack, I noticed the
  mouse moved, so it was recoverable.

  I waited for 100 seconds until the system recovered. When it
  recovered, looked like nothing had happened, and now I'm writing this
  report from the computer, without restarting.

  Steps to reproduce:
  1) open Audacious or VLC;
  2) play a music/video on Audacious or VLC;
  3) open another program with sound (Steam, a browser (I use Opera), etc);
  4) use the computer until a freeze happens.

  Observations:

  -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?).
  -VLC + Opera + Firefox (on start page) was enough for trigger it once, even 
with the only program with media opened being VLC.

  The freeze I was able to recover had: Opera Developer (YouTube video
  playing) + Audacious (playing) + Steam with audio streams opened on
  pavucontrol. Additionally, Thunderbird and Evince were opened, and
  intel-gpu-overlay was opened inside a Xnest window.

  The syslog says to report to alsa, so I'm writing the report here.
  However, it should be noted that there is a i915 error too, maybe it
  was a consequence, maybe it was the cause.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  $ uname -a
  Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu 
Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  Thank you.

  Edit: one thing I noticed with indicator-multiload, the internal HDD
  activity completely stopped while this problem was happening and soon
  after it started to function. It was like the computer was recovering
  with the internal HDD turned off. The HDD usage ramped up and the
  system returned to normal. May this be related with the power
  management issues?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libasound2 1.1.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Apr 30 23:43:29 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libasound2-data 1.1.0-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
  InstallationDate: Installed on 2016-12-31 (121 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: alsa-lib
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text

[James Cameron]

G'day Brian.  Yes, it needs to be compiled in.  Download the Ubuntu
source package, apply the patch, build the package, then install it.  If
you've not done that before, you may find it quite complicated.  You
might enable deb-src entries in your /etc/apt/sources.list file, then
"apt-get update", then "apt-get source abiword", then apply the patch,
then install build dependencies with "apt-get build-dep abiword", then
build with "dpkg-buildpackage", then install with "dpkg -i".  There are
different ways to do all this, but that's the simplest I can think of.
Sorry, I didn't keep the result.

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

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in lubuntu-artwork package in Ubuntu:
  Invalid
Status in abiword source package in Xenial:
  Confirmed
Status in gtk+3.0 source package in Xenial:
  Confirmed
Status in lubuntu-artwork source package in Xenial:
  Invalid

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

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

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

[Touch-packages] [Bug 1645891] Re: After adding a second monitor, mouse pointer flickers and/or disappears in a zone near the top of first (notebook) monitor, while some apps show slow in ext display.

[Launchpad Bug Tracker]

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

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

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

Title:
  After adding a second monitor, mouse pointer flickers and/or
  disappears in a zone near the top of first (notebook) monitor, while
  some apps show slow in ext display.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  It seems to be duplicate of both :
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1641467
  and 
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1629300  .
  Possibly related to 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223

  A - flickering in first display.
  The zone starts just below the top panel and its height is about 1/7 of the 
screen.
  Flickering starts immediately entering the zone, even half of the pointer may 
be flickering.
  To the centre of the zone, flickering is more prevalent, up to completely 
disappearing. 
  The flickering has a periodic pattern, which seems to be affected by the 
windows displaying in the second (external) monitor !! 

  B - external monitor.
  Some applications show really slow there. Worse case is HipChat (Atlassian 
chat program), which shows fine as long as even a tiny fraction exists on the 
primary display. 
  At the moment the whole window passes to the secondary, then even the scroll 
bar has a delay of a second a move. 

  To check, I have played with the ~/.config/monitors.xml without success.
  It seems that each configuration is saved there, even duplicates, after 
adding the same external monitor and re-configuring it (absolute duplicate in 
monitors.xml)

  C. Side-effects and related phenomena. 
  Some times the "Screen display" control freaks, when enabling the external 
monitor. It may freeze or insist to put them in mirroring. Most of the times it 
just forgets a setup (although in monitors.xml) after adding a different 
external monitor.
  For each workspace, there is a different background, done with Unit5y Tweak 
Tool. 

  All updates have been done, without effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov 29 23:18:52 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.1.6, 4.8.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:222e]
   NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e]
  InstallationDate: Installed on 2016-11-09 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20EN0019US
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=c3151b80-1188-4c23-816c-57ebe18688a8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET57W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN0019US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET57W(1.30):bd08/03/2016:svnLENOVO:pn20EN0019US:pvrThinkPadP50:rvnLENOVO:rn20EN0019US:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EN0019US
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  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
 

[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text

[Brian]

@James- I am sorry, but could you provide a bit of direction on applying
that fix? I understand the + and - aspect, but unsure of where/how to
apply that. My install was just done through package manager, I wonder
if this fix needs to be compiled in?

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

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in lubuntu-artwork package in Ubuntu:
  Invalid
Status in abiword source package in Xenial:
  Confirmed
Status in gtk+3.0 source package in Xenial:
  Confirmed
Status in lubuntu-artwork source package in Xenial:
  Invalid

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

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

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

[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text

[Brian]

thank you James. I will have a look.

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

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in lubuntu-artwork package in Ubuntu:
  Invalid
Status in abiword source package in Xenial:
  Confirmed
Status in gtk+3.0 source package in Xenial:
  Confirmed
Status in lubuntu-artwork source package in Xenial:
  Invalid

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

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

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

[Touch-packages] [Bug 1688689] Re: Owner and group of few files and folders from Bind directory visible as nobody/nogroup within nspawn container

[RussianNeuroMancer]

Example:

~$ LANG=C sudo whoami
sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
~$ LANG=C ls -l /usr/bin/sudo
-rwsr-xr-x 1 nobody nogroup 140944 Jan 14 07:41 /usr/bin/sudo
~$ LANG=C ls -l /var/lib/machines/builder/usr/bin/sudo
-rwsr-xr-x 1 root root 140944 Jan 14 07:41 
/var/lib/machines/builder/usr/bin/sudo


** Summary changed:

- Owner and group of few folders from Bind directory visible as nobody/nogroup 
within nspawn container 
+ Owner and group of few files and folders from Bind directory visible as 
nobody/nogroup within nspawn container

** Description changed:

- Owner and group of few folders from Bind directory visible as
+ Owner and group of few files and folders from Bind directory visible as
  nobody/nogroup when I check permission from within nspawn container.
  
  Create testing.nspawn:
  
  [Files]
  Bind=/patch/to/folder
- Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders in Bind directory inside container is the same as on 
host.
+ Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders and files in Bind directory inside container is the 
same as on host.
  
  Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
  Server 17.10 (systemd 233).

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

Title:
  Owner and group of few files and folders from Bind directory visible
  as nobody/nogroup within nspawn container

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  Owner and group of few files and folders from Bind directory visible
  as nobody/nogroup when I check permission from within nspawn
  container.

  Create testing.nspawn:

  [Files]
  Bind=/patch/to/folder
  Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders and files in Bind directory inside container is the 
same as on host.

  Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
  Server 17.10 (systemd 233).

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

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

[Touch-packages] [Bug 1688689] Re: Owner and group of few folders from Bind directory visible as nobody/nogroup within nspawn container

[RussianNeuroMancer]

Issue is also reproducible for files and folder within container, if
container is btrfs subvolume instead of disk image.

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

Title:
  Owner and group of few files and folders from Bind directory visible
  as nobody/nogroup within nspawn container

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  Owner and group of few folders from Bind directory visible as
  nobody/nogroup when I check permission from within nspawn container.

  Create testing.nspawn:

  [Files]
  Bind=/patch/to/folder
  Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders in Bind directory inside container is the same as on 
host.

  Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
  Server 17.10 (systemd 233).

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

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

[Touch-packages] [Bug 1688689] [NEW] Owner and group of few folders from Bind directory visible as nobody/nogroup within nspawn container

[RussianNeuroMancer]

Public bug reported:

Owner and group of few folders from Bind directory visible as
nobody/nogroup when I check permission from within nspawn container.

Create testing.nspawn:

[Files]
Bind=/patch/to/folder
Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders in Bind directory inside container is the same as on 
host.

Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
Server 17.10 (systemd 233).

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: github.com/systemd/systemd/issues #5900
   https://github.com/systemd/systemd/issues/5900

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/5900
   Importance: Unknown
   Status: Unknown

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

Title:
  Owner and group of few folders from Bind directory visible as
  nobody/nogroup within nspawn container

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  Owner and group of few folders from Bind directory visible as
  nobody/nogroup when I check permission from within nspawn container.

  Create testing.nspawn:

  [Files]
  Bind=/patch/to/folder
  Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders in Bind directory inside container is the same as on 
host.

  Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
  Server 17.10 (systemd 233).

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

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

[Touch-packages] [Bug 1643063] Re: unable to ifup vlan based interface with systemd persistent naming

[Andrei Coada]

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

Check out my alternative workaround from duplicate bug #1628591. In my opinion, 
it's cleaner.
I haven't heard of vconfig to be deprecated.

Anyway... it's funny how we must do workarounds for basic functionality,
such as networking.

In Debian 9 Stretch, you don't have to do any of this. It works out-of-
the-box with both "eth" and "enp" naming conventions.

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

Title:
  unable to ifup vlan based interface with systemd persistent naming

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  root@atlantis:/etc# ifup enp2s0.121
  Cannot find device "enp2s0.121"
  Failed to bring up enp2s0.121.

  Workaround:
  Add
  pre-up /sbin/ip link add link enp2s0 name enp2s0.121 type vlan id 121
  to /etc/network/interfaces declaration.

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

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

[Touch-packages] [Bug 1643063] Re: unable to ifup vlan based interface with systemd persistent naming

[Andrei Coada]

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

** This bug has been marked a duplicate of bug 1628591
   ifup & ifdown don't work for vlan devices when raw device name is the new 
"enp" convention

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

Title:
  unable to ifup vlan based interface with systemd persistent naming

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  root@atlantis:/etc# ifup enp2s0.121
  Cannot find device "enp2s0.121"
  Failed to bring up enp2s0.121.

  Workaround:
  Add
  pre-up /sbin/ip link add link enp2s0 name enp2s0.121 type vlan id 121
  to /etc/network/interfaces declaration.

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

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

[Touch-packages] [Bug 1489999] Re: ifupdown.upstart.if-up script will never fire static-network-up with auto virtual interfaces defined

[Launchpad Bug Tracker]

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

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

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

Title:
  ifupdown.upstart.if-up script will never fire  static-network-up with
  auto virtual interfaces defined

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  The upstart script compares the list of "auto" interfaces from ifquery
  to the ifup.xx files created in /run/network and will only fire the
  static-network-up event when all listed auto interfaces are shown as
  up.  The problem arises if virtual interfaces (eth0:1 eth0:2) are used
  to add additional addresses to a single physical interface.  Virtual
  interfaces are brought up by adding the address to the existing base
  interface, and no corresponding file is created in /run/network for
  the virtual interface (I believe this also holds true for VLAN
  interfaces i.e. eth0.1) .  If the virtual device is brought up at boot
  with an "auto" clause in /etc/network/interfaces then the script will
  see it in the list from ifquery but never see it separately marked as
  up in the run directory.

  The result is that if any virtual interfaces are defined as auto, then
  network boot will stall and system boot will not complete until
  failsafe fires after 120 seconds.

  My temporary solution to this is to patch the script to remove the
  virtual part of the interface name before checking if it has been
  brought up:

  all_interfaces_up() {
  # return true if all interfaces listed in /etc/network/interfaces as 
'auto'
  # are up.  if no interfaces are found there, then "all [given] were 
up"
  local prefix="$1" iface=""
  for iface in $(get_auto_interfaces); do
  >   iface=${iface##:*}
  >   iface=${iface##.*}
  # if cur interface does is not up, then all have not been 
brought up
  [ -f "${prefix}${iface}" ] || return 1
  done
  return 0
  }

  This is an imperfect fix since it is then possible for the static-network-up 
event to fire before all virtual interfaces are indeed up - but if combined 
with ensuring that the interfaces with additional virtual/vlan  definitions are 
the first interfaces defined in /etc/network/interfaces I think this quick 
patch could save a lot of systems an annoying and unneeded 2 minute boot delay!
  A more perfect fix would require a much deeper dive, as a different list of 
"up" interfaces must be found or created...

  I have not checked the history of this script but it has not changed from my 
installed version of ifupdown (0.7.47.2ubuntu4.1)
  to the latest 0.7.54 debian source...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ifupdown 0.7.47.2ubuntu4.1
  ProcVersionSignature: Ubuntu 3.16.0-46.62~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Fri Aug 28 10:46:39 2015
  InstallationDate: Installed on 2015-06-23 (65 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.network.if.up.d.upstart: 2015-08-25T22:38:07.451399

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

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

[Touch-packages] [Bug 1643063] Re: unable to ifup vlan based interface with systemd persistent naming

[Launchpad Bug Tracker]

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

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

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

Title:
  unable to ifup vlan based interface with systemd persistent naming

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  root@atlantis:/etc# ifup enp2s0.121
  Cannot find device "enp2s0.121"
  Failed to bring up enp2s0.121.

  Workaround:
  Add
  pre-up /sbin/ip link add link enp2s0 name enp2s0.121 type vlan id 121
  to /etc/network/interfaces declaration.

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

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

[Touch-packages] [Bug 1628591] Re: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention

[Andrei Coada]

As a workaround, you could add "vlan-raw-device", like this:

auto enp0s8
iface enp0s8 inet manual

auto enp0s8.7
iface enp0s8.7 inet static
  vlan-raw-device enp0s8
  address x.x.x.x/y


It's a pity that such a project doesn't pay more attention to basic features...

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

Title:
  ifup & ifdown don't work for vlan devices when raw device name is the
  new "enp" convention

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  The regular expressions used in  /etc/network/if-post-down.d/vlan and 
/etc/network/if-pre-up.d/vlan
  do not match the name of my network card enp4s0f0.
  This can be fixed by broadening the regular expression.

  This is only a problem when the device is a vlan device!

  See below for the fix that worked on my system.

  if-pre-up:

  #!/bin/sh

  # Most of this stuff is to enable vlans

  case "$IFACE" in
    # Ignore any alias (#272891) which uses :
    *:*)
  exit 0
    ;;
    vlan0*)
  vconfig set_name_type VLAN_PLUS_VID
  VLANID=`echo $IFACE|sed "s/vlan0*//"`
    ;;
    vlan*)
  vconfig set_name_type VLAN_PLUS_VID_NO_PAD
  VLANID=`echo $IFACE|sed "s/vlan0*//"`
    ;;
    eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*.0*)
  vconfig set_name_type DEV_PLUS_VID
  VLANID=`echo $IFACE|sed 
"s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.0*//g"`
  IF_VLAN_RAW_DEVICE=`echo $IFACE|sed 
"s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"`
    ;;
    eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*.*)
  vconfig set_name_type DEV_PLUS_VID_NO_PAD
  VLANID=`echo $IFACE|sed 
"s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.//g"`
  IF_VLAN_RAW_DEVICE=`echo $IFACE|sed 
"s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"`
    ;;
    *.0*)
  # Silently ignore interfaces which we do not (know how to) support
  [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0
  vconfig set_name_type DEV_PLUS_VID
  VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"`
    ;;
    *.*)
  # Silently ignore interfaces which we do not (know how to) support
  [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0
  vconfig set_name_type DEV_PLUS_VID_NO_PAD
  VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"`
    ;;

    *)
  exit 0
    ;;
  esac

  if [ -n "$IF_VLAN_RAW_DEVICE" ] && [ ! -d /sys/class/net/$IFACE ]; then
  if [ ! -x /sbin/vconfig ]; then
  exit 0
  fi
  if ! ip link show dev "$IF_VLAN_RAW_DEVICE" > /dev/null; then
  echo "$IF_VLAN_RAW_DEVICE does not exist, unable to create $IFACE"
  exit 1
  fi
  if [ ! -e "/sys/class/net/$IFACE" ]; then
  ip link set up dev $IF_VLAN_RAW_DEVICE
  vconfig add $IF_VLAN_RAW_DEVICE $VLANID
  fi
  fi

  # This is not vlan specific, and should actually go somewhere else.
  if [ -n "$IF_HW_MAC_ADDRESS" ]; then
  ip link set $IFACE address $IF_HW_MAC_ADDRESS
  fi

  if-post-down:

  #!/bin/sh

  # If IFACE is an automagic vlan interface (without the vlan-raw-device
  # parameter) then let's try to discover the magic here..  Another way would be
  # to just probe for the right device name in /proc/net/vlan

  case "$IFACE" in
    # Ignore any alias (#272891)
    *:*)
  exit 0
    ;;
    eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*\.0*)
  IF_VLAN_RAW_DEVICE=`echo $IFACE|sed 
"s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"`
    ;;
    eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*\.*)
  IF_VLAN_RAW_DEVICE=`echo $IFACE|sed 
"s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"`
    ;;
    # Test for vlan raw device (#196890, #292648)
    *)
  [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0
    ;;
  esac
  if [ ! -x /sbin/vconfig ]; then
  exit 0
  fi

  vconfig rem $IFACE

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

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

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

[Sagar B Hathwar]

After making the required settings in alsamixer, do `sudo alsactl store
0`. This will make your settings persistent on reboot.

By the way, this bug is fixed by one of the 4.4 kernels itself in 16.04

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

Title:
  [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When the headphones are plugged, they are not detected. All sound
  comes from the built in speakers, and none from the headphones.

  The jack works on Windows.

  This bug seems similar to #1184838. However, I'm posting it as the
  hardware is different.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
   /dev/snd/controlC0:  adin   4035 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  2 22:59:12 2016
  InstallationDate: Installed on 2016-07-03 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
   /dev/snd/controlC0:  adin   4035 F pulseaudio
adin  32107 F alsamixer
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Alienware 17 R3, Creative CA0132, Green Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2016
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.15
  dmi.board.name: Alienware 17 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.15:bd07/07/2016:svnAlienware:pnAlienware17R3:pvr1.2.15:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 17 R3
  dmi.product.version: 1.2.15
  dmi.sys.vendor: Alienware

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

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

[Touch-packages] [Bug 1628591] Re: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention

[Andrei Coada]

** Summary changed:

- ifup and ifdown dont work for vlan devices when raw ethernet device name does 
not meet regular conventions
+ ifup & ifdown don't work for vlan devices when raw device name is the new 
"enp" convention

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

Title:
  ifup & ifdown don't work for vlan devices when raw device name is the
  new "enp" convention

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  The regular expressions used in  /etc/network/if-post-down.d/vlan and 
/etc/network/if-pre-up.d/vlan
  do not match the name of my network card enp4s0f0.
  This can be fixed by broadening the regular expression.

  This is only a problem when the device is a vlan device!

  See below for the fix that worked on my system.

  if-pre-up:

  #!/bin/sh

  # Most of this stuff is to enable vlans

  case "$IFACE" in
    # Ignore any alias (#272891) which uses :
    *:*)
  exit 0
    ;;
    vlan0*)
  vconfig set_name_type VLAN_PLUS_VID
  VLANID=`echo $IFACE|sed "s/vlan0*//"`
    ;;
    vlan*)
  vconfig set_name_type VLAN_PLUS_VID_NO_PAD
  VLANID=`echo $IFACE|sed "s/vlan0*//"`
    ;;
    eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*.0*)
  vconfig set_name_type DEV_PLUS_VID
  VLANID=`echo $IFACE|sed 
"s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.0*//g"`
  IF_VLAN_RAW_DEVICE=`echo $IFACE|sed 
"s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"`
    ;;
    eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*.*)
  vconfig set_name_type DEV_PLUS_VID_NO_PAD
  VLANID=`echo $IFACE|sed 
"s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.//g"`
  IF_VLAN_RAW_DEVICE=`echo $IFACE|sed 
"s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"`
    ;;
    *.0*)
  # Silently ignore interfaces which we do not (know how to) support
  [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0
  vconfig set_name_type DEV_PLUS_VID
  VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"`
    ;;
    *.*)
  # Silently ignore interfaces which we do not (know how to) support
  [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0
  vconfig set_name_type DEV_PLUS_VID_NO_PAD
  VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"`
    ;;

    *)
  exit 0
    ;;
  esac

  if [ -n "$IF_VLAN_RAW_DEVICE" ] && [ ! -d /sys/class/net/$IFACE ]; then
  if [ ! -x /sbin/vconfig ]; then
  exit 0
  fi
  if ! ip link show dev "$IF_VLAN_RAW_DEVICE" > /dev/null; then
  echo "$IF_VLAN_RAW_DEVICE does not exist, unable to create $IFACE"
  exit 1
  fi
  if [ ! -e "/sys/class/net/$IFACE" ]; then
  ip link set up dev $IF_VLAN_RAW_DEVICE
  vconfig add $IF_VLAN_RAW_DEVICE $VLANID
  fi
  fi

  # This is not vlan specific, and should actually go somewhere else.
  if [ -n "$IF_HW_MAC_ADDRESS" ]; then
  ip link set $IFACE address $IF_HW_MAC_ADDRESS
  fi

  if-post-down:

  #!/bin/sh

  # If IFACE is an automagic vlan interface (without the vlan-raw-device
  # parameter) then let's try to discover the magic here..  Another way would be
  # to just probe for the right device name in /proc/net/vlan

  case "$IFACE" in
    # Ignore any alias (#272891)
    *:*)
  exit 0
    ;;
    eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*\.0*)
  IF_VLAN_RAW_DEVICE=`echo $IFACE|sed 
"s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"`
    ;;
    eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*\.*)
  IF_VLAN_RAW_DEVICE=`echo $IFACE|sed 
"s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"`
    ;;
    # Test for vlan raw device (#196890, #292648)
    *)
  [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0
    ;;
  esac
  if [ ! -x /sbin/vconfig ]; then
  exit 0
  fi

  vconfig rem $IFACE

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

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

[Touch-packages] [Bug 1628591] Re: ifup and ifdown dont work for vlan devices when raw ethernet device name does not meet regular conventions

[Launchpad Bug Tracker]

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

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

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

Title:
  ifup & ifdown don't work for vlan devices when raw device name is the
  new "enp" convention

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  The regular expressions used in  /etc/network/if-post-down.d/vlan and 
/etc/network/if-pre-up.d/vlan
  do not match the name of my network card enp4s0f0.
  This can be fixed by broadening the regular expression.

  This is only a problem when the device is a vlan device!

  See below for the fix that worked on my system.

  if-pre-up:

  #!/bin/sh

  # Most of this stuff is to enable vlans

  case "$IFACE" in
    # Ignore any alias (#272891) which uses :
    *:*)
  exit 0
    ;;
    vlan0*)
  vconfig set_name_type VLAN_PLUS_VID
  VLANID=`echo $IFACE|sed "s/vlan0*//"`
    ;;
    vlan*)
  vconfig set_name_type VLAN_PLUS_VID_NO_PAD
  VLANID=`echo $IFACE|sed "s/vlan0*//"`
    ;;
    eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*.0*)
  vconfig set_name_type DEV_PLUS_VID
  VLANID=`echo $IFACE|sed 
"s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.0*//g"`
  IF_VLAN_RAW_DEVICE=`echo $IFACE|sed 
"s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"`
    ;;
    eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*.*)
  vconfig set_name_type DEV_PLUS_VID_NO_PAD
  VLANID=`echo $IFACE|sed 
"s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.//g"`
  IF_VLAN_RAW_DEVICE=`echo $IFACE|sed 
"s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"`
    ;;
    *.0*)
  # Silently ignore interfaces which we do not (know how to) support
  [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0
  vconfig set_name_type DEV_PLUS_VID
  VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"`
    ;;
    *.*)
  # Silently ignore interfaces which we do not (know how to) support
  [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0
  vconfig set_name_type DEV_PLUS_VID_NO_PAD
  VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"`
    ;;

    *)
  exit 0
    ;;
  esac

  if [ -n "$IF_VLAN_RAW_DEVICE" ] && [ ! -d /sys/class/net/$IFACE ]; then
  if [ ! -x /sbin/vconfig ]; then
  exit 0
  fi
  if ! ip link show dev "$IF_VLAN_RAW_DEVICE" > /dev/null; then
  echo "$IF_VLAN_RAW_DEVICE does not exist, unable to create $IFACE"
  exit 1
  fi
  if [ ! -e "/sys/class/net/$IFACE" ]; then
  ip link set up dev $IF_VLAN_RAW_DEVICE
  vconfig add $IF_VLAN_RAW_DEVICE $VLANID
  fi
  fi

  # This is not vlan specific, and should actually go somewhere else.
  if [ -n "$IF_HW_MAC_ADDRESS" ]; then
  ip link set $IFACE address $IF_HW_MAC_ADDRESS
  fi

  if-post-down:

  #!/bin/sh

  # If IFACE is an automagic vlan interface (without the vlan-raw-device
  # parameter) then let's try to discover the magic here..  Another way would be
  # to just probe for the right device name in /proc/net/vlan

  case "$IFACE" in
    # Ignore any alias (#272891)
    *:*)
  exit 0
    ;;
    eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*\.0*)
  IF_VLAN_RAW_DEVICE=`echo $IFACE|sed 
"s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"`
    ;;
    eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*\.*)
  IF_VLAN_RAW_DEVICE=`echo $IFACE|sed 
"s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"`
    ;;
    # Test for vlan raw device (#196890, #292648)
    *)
  [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0
    ;;
  esac
  if [ ! -x /sbin/vconfig ]; then
  exit 0
  fi

  vconfig rem $IFACE

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

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

Re: [Touch-packages] [Bug 1684902] Re: browser unity app crashes apparmor profile

[Carl]

Hi Marc Deslauriers,

Thanks for the reply. I had not heard from anyone for a time, so I went
ahead and re-installed the browser app, then reconfigured apparmor to
stop all the system errors. It seemed to have fixed the problem (short
term), but I put the package in you said was missing in the system, and
all seems well in the system.

Did you need a snapshot of any system items to confirm?

By the way, this package was never shown as a missing dependency nor did
apparmor give any obvious error for this package, or even when the
webbrowser-app was removed, and I reconfigured and reinstalled apparmor.
Also, it was never (as far as I know) part of the original .iso for the
install (maybe it was missing from the repository?), nor did the updates
catch it as missing, so really weird.

Thank you for your attention in this matter.

My Best to you and yours,

Carl


On 05/05/2017 09:16 AM, Marc Deslauriers wrote:
> Hi Carl, it looks like you're missing the apparmor-easyprof-ubuntu
> package. That package is necessary for proper operation. Could you
> please reinstall it and try again?
>
> Thanks!
>

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

Title:
  browser unity app crashes apparmor profile

Status in apparmor package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2
  amd64 (A lightweight web browser tailored for Ubuntu, based on the
  Oxide browser engine and using the Ubuntu UI components.), Shown as
  Version 0.23+16.04.20161028-0ubuntu2, if removed from the system,
  causes apparmor to read errors in the system profile and fail to start
  (apparmor).

  I discovered that (per session), you can get apparmor to correct the
  failure and start, but as soon as you reboot, the system returns to
  the default profile set and fails to start apparmor. As far as I can
  tell, it does not indicate that the failure was caused by the browser
  uninstall, just that it failed to start for some reason.

  I tried to send this via apport, but it will not auto-locate the
  program, and since it is integrated with unity and oxide, I think it
  "sees" the program as a required OS file.

  Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) 
updated grub file, (4) reboot
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-04-12 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Package: webbrowser-app
  PackageArchitecture: amd64
  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.8.0-46-generic 
root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Syslog:
   Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is 
enabled
   Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is 
enabled
  Tags:  xenial
  Uname: Linux 4.8.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

[Goyo]

Should we file separate bugs for other applications affected like
epiphany? Pretty sure the underlying cause lies in some common component
but workarounds might be different. Disabling javascript in epiphany
should bring back the old login window but the UI for that was removed
years ago (because it was a "Please break my web" preference in
disguise, how ironic) and even the enable-javascript key in gsettins
seems to be gone.

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in gnome-online-accounts source package in Xenial:
  Triaged
Status in gnome-online-accounts source package in Yakkety:
  Triaged
Status in gnome-online-accounts source package in Zesty:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

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

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

[Touch-packages] [Bug 1688670] [NEW] I can't play You tube videos.

[Ray C Ward]

Public bug reported:

I haven't been able to play you tube videos on the you tube website, the
Google Web Store-You Tube Player, the SMplayer, VML Player or any of
your available applications.  Either the videos are just refused to be
accepted, or on the you tube site, they play way too fast, are choppy,
at best (that includes with the You Tube Player).  I have yet to be able
to play a You Tube video, in any format, successfully since I installed
Ubuntu Kylin (be mistake, I wanted the regular  16.04 Ubuntu).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-51-generic i686
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
BootLog: /dev/sda1: clean, 196491/9707520 files, 2100864/38812672 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri May  5 17:22:49 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller 
[8086:8108] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. System Controller Hub (SCH Poulsbo) 
Graphics Controller [1043:83ce]
InstallationDate: Installed on 2017-04-19 (16 days ago)
InstallationMedia: Ubuntu-Kylin 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215)
MachineType: ASUSTeK Computer INC. 1101HA
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic 
root=UUID=6bee3dab-66d4-4c0b-a66f-e25c50c12b34 ro locale=zh_CN quiet splash 
vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0317
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1101HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0317:bd09/24/2009:svnASUSTeKComputerINC.:pn1101HA:pvrx.x:rvnASUSTeKComputerINC.:rn1101HA:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1101HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri May  5 16:37:29 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  I can't play You tube videos.

Status in xorg package in Ubuntu:
  New

Bug description:
  I haven't been able to play you tube videos on the you tube website,
  the Google Web Store-You Tube Player, the SMplayer, VML Player or any
  of your available applications.  Either the videos are just refused to
  be accepted, or on the you tube site, they play way too fast, are
  choppy, at best (that includes with the You Tube Player).  I have yet
  to be able to play a You Tube video, in any format, successfully since
  I installed Ubuntu Kylin (be mistake, I wanted the regular  16.04
  Ubuntu).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  BootLog: /dev/sda1: clean, 196491/9707520 files, 2100864/38812672 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri May  5 17:22:49 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  

[Touch-packages] [Bug 1688668] Re: package account-plugin-facebook (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also

[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 account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1688668

Title:
  package account-plugin-facebook (not installed) failed to
  install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf', which is also in package kaccounts-
  providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  while installing ubuntu desktop from lubuntu netbook got the crash as 
mentioned.
  regards
  govindanarayanabhat

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-facebook (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22~16.04.1-lowlatency 4.10.8
  Uname: Linux 4.10.0-20-lowlatency i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Sat May  6 04:42:06 2017
  DuplicateSignature:
   package:account-plugin-facebook:(not installed)
   Unpacking account-plugin-facebook (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-facebook_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2015-07-27 (648 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: account-plugins
  Title: package account-plugin-facebook (not installed) failed to 
install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1688668] [NEW] package account-plugin-facebook (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is al

[Govinda Narayana Bhat]

Public bug reported:

while installing ubuntu desktop from lubuntu netbook got the crash as mentioned.
regards
govindanarayanabhat

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-facebook (not installed)
ProcVersionSignature: Ubuntu 4.10.0-20.22~16.04.1-lowlatency 4.10.8
Uname: Linux 4.10.0-20-lowlatency i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
Date: Sat May  6 04:42:06 2017
DuplicateSignature:
 package:account-plugin-facebook:(not installed)
 Unpacking account-plugin-facebook (0.12+16.04.20160126-0ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-facebook_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
  trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', 
which is also in package kaccounts-providers 4:15.12.3-0ubuntu1
ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
InstallationDate: Installed on 2015-07-27 (648 days ago)
InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: account-plugins
Title: package account-plugin-facebook (not installed) failed to 
install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 package-conflict xenial

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

Title:
  package account-plugin-facebook (not installed) failed to
  install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf', which is also in package kaccounts-
  providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  while installing ubuntu desktop from lubuntu netbook got the crash as 
mentioned.
  regards
  govindanarayanabhat

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-facebook (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22~16.04.1-lowlatency 4.10.8
  Uname: Linux 4.10.0-20-lowlatency i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Sat May  6 04:42:06 2017
  DuplicateSignature:
   package:account-plugin-facebook:(not installed)
   Unpacking account-plugin-facebook (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-facebook_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2015-07-27 (648 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: account-plugins
  Title: package account-plugin-facebook (not installed) failed to 
install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1651623] Re: adt tests fail on zesty for apport

[Brian Murray]

The tests for artful are now failing for a different reason:

==
ERROR: test_add_gdb_info_abort_glib (__main__.T)
add_gdb_info() with glib assertion
--
Traceback (most recent call last):
  File "./test_report.py", line 852, in test_add_gdb_info_abort_glib
self.assertTrue(pr['AssertionMessage'].startswith('ERROR::2:main: 
assertion failed (1 < 0):'),
  File "/usr/lib/python3.5/collections/__init__.py", line 989, in __getitem__
raise KeyError(key)
KeyError: 'AssertionMessage'

I've spent some time digging into this and it seems "print
__glib_assert_msg" is behaving differently and has been for a bit.

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

Title:
  adt tests fail on zesty for apport

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Yakkety:
  New
Status in apport source package in Zesty:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz

  fails.

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

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

[Touch-packages] [Bug 1688663] [NEW] udev 97-hid2hci.rules missing usb id for logitech dinovo 2

[Jesús Diéguez Fernández]

Public bug reported:

Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech
dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor
after being installed using another keyboard and mouse.

In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech
devices:

# Logitech devices
KERNEL=="hiddev*", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \
  RUN+="hid2hci --method=logitech-hid --devpath=%p"
# Logitech, Inc. diNovo Edge Keyboard
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \
  RUN+="hid2hci --method=logitech-hid --devpath=%p"

lsusb shows in my computer:

Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless Desktop

The id is almost equal (c714 <> c704). After adding a new line with the
missing id, the keyboard and mouse started to work:

# Logitech, Inc. diNovo 2
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \
  RUN+="hid2hci --method=logitech-hid --devpath=%p"

I've also followed these other bugs to find out the file that I needed
to modify and that my keyboard needs hidraw instead of hiddev:

https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920

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


** Tags: 97-hid2hci.rules bluetooth dinovo logitech udev

** Attachment added: "IMG_20170505_181434.jpg"
   
https://bugs.launchpad.net/bugs/1688663/+attachment/4872443/+files/IMG_20170505_181434.jpg

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

Title:
  udev 97-hid2hci.rules missing usb id for logitech dinovo 2

Status in bluez package in Ubuntu:
  New

Bug description:
  Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech
  dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor
  after being installed using another keyboard and mouse.

  In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech
  devices:

  # Logitech devices
  KERNEL=="hiddev*", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"
  # Logitech, Inc. diNovo Edge Keyboard
  KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"

  lsusb shows in my computer:

  Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless
  Desktop

  The id is almost equal (c714 <> c704). After adding a new line with
  the missing id, the keyboard and mouse started to work:

  # Logitech, Inc. diNovo 2
  KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"

  I've also followed these other bugs to find out the file that I needed
  to modify and that my keyboard needs hidraw instead of hiddev:

  https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940
  https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920

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

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

[Touch-packages] [Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Balint Reczey]

>> 1.c does lvm also fail in privileged containers?  I can see no use to
>> running it (for now) in an unprivileged container, so the same solution
>> as 1.a seems reasonable.
>
> It also fails in privileged containers in the same way (see 2.b in
> comment 20). Note that it works if I manually start the socket after
> boot.

It seems /lib/systemd/system/lvm2-monitor.service also needs the
"ConditionVirtualization=!container" line.

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1442896] Re: Bluetooth mouse disconnects and reconnects every few seconds

[Konrad Zapałowicz]

@mcumpa could you post the syslog as well as HCI trace for your case?

1. syslog

Please enable the debug output first by typing:

$ sudo sed -i 's/bluetoothd/bluetoothd \-d/g'
/lib/systemd/system/bluetooth.service


2. HCI trace

Execute:

$ sudo btmon --write ~/hcitrace.snoop

before you start reproducing the issue [but might be after pairing to
limit the log size]. It is important not to make the test too long so
that the HCI trace is easier to read and understand.

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

Title:
  Bluetooth mouse disconnects and reconnects every few seconds

Status in Bluez Utilities:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I have a bluetooth mouse (Genius Traveller 9005BT) that I have been
  using without problems with Ubuntu for over a year. Since a few weeks
  ago, however, it started disconnecting and reconnected from the
  computer. The symptoms are like this:

  1. The mouse works, and the bluetooth icon on the computer is visible (in 
gnome-shell's top bar)
  2. The mouse stops working, but the bluetooth icon is still visible. This 
state lasts between 1 and 10 seconds.
  3. The bluetooth icon vanishes. This can last for half a second if I keep 
trying to use the mouse, to forever I I leave the mouse alone
  4. The bluetooth icon reappears and the mouse starts working again. This 
state last from 2-3 seconds if I don't move the mouse, to seemingly forever if 
I continuously move the mouse

  This seems to occur only after a suspend/resume cycle, and rebooting
  the computer fixes the issue.

  The only thing I see in syslog is this when the mouse reconnects:
  Apr 11 10:03:10 tadzim3 kernel: [52026.494469] hid-generic 
0005:0458:0139.002F: unknown main item tag 0x0
  Apr 11 10:03:10 tadzim3 kernel: [52026.494540] input: Traveler 9005BT as 
/devices/pci:00/:00:14.0/usb2/2-4/2-4:1.0/bluetooth/hci0/hci0:512/0005:0458:0139.002F/input/input59
  Apr 11 10:03:10 tadzim3 kernel: [52026.494899] hid-generic 
0005:0458:0139.002F: input,hidraw3: BLUETOOTH HID v3.12 Mouse [Traveler 9005BT] 
on e8:2a:ea:8b:a5:5f

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr 11 09:49:37 2015
  InstallationDate: Installed on 2015-01-23 (77 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed 
root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to utopic on 2015-01-31 (69 days ago)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN35WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: E8:2A:EA:8B:A5:5F  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN 
RX bytes:1873821 acl:123158 sco:0 events:2377 errors:0
TX bytes:29044 acl:238 sco:0 commands:218 errors:0

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

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

[Touch-packages] [Bug 1442896] Re: Bluetooth mouse disconnects and reconnects every few seconds

[Miguel Cumpa]

Hi, I use ubuntu 16.04 and I have the same problem. The bluetooth is 
disconnected and when I try to connect it manually I can not.
My laptop is a lenovo z470 and i have the same model of mouse genius traveler 
9005bt.

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Fri 2017-05-05 15:38:57 PET; 33min ago
 Docs: man:bluetoothd(8)
 Main PID: 18775 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
   └─18775 /usr/lib/bluetooth/bluetoothd

May 05 15:56:28 cumpa bluetoothd[18775]: Can't get HIDP connection info
May 05 15:56:33 cumpa bluetoothd[18775]: connect error: Host is down (112)


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

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

Title:
  Bluetooth mouse disconnects and reconnects every few seconds

Status in Bluez Utilities:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I have a bluetooth mouse (Genius Traveller 9005BT) that I have been
  using without problems with Ubuntu for over a year. Since a few weeks
  ago, however, it started disconnecting and reconnected from the
  computer. The symptoms are like this:

  1. The mouse works, and the bluetooth icon on the computer is visible (in 
gnome-shell's top bar)
  2. The mouse stops working, but the bluetooth icon is still visible. This 
state lasts between 1 and 10 seconds.
  3. The bluetooth icon vanishes. This can last for half a second if I keep 
trying to use the mouse, to forever I I leave the mouse alone
  4. The bluetooth icon reappears and the mouse starts working again. This 
state last from 2-3 seconds if I don't move the mouse, to seemingly forever if 
I continuously move the mouse

  This seems to occur only after a suspend/resume cycle, and rebooting
  the computer fixes the issue.

  The only thing I see in syslog is this when the mouse reconnects:
  Apr 11 10:03:10 tadzim3 kernel: [52026.494469] hid-generic 
0005:0458:0139.002F: unknown main item tag 0x0
  Apr 11 10:03:10 tadzim3 kernel: [52026.494540] input: Traveler 9005BT as 
/devices/pci:00/:00:14.0/usb2/2-4/2-4:1.0/bluetooth/hci0/hci0:512/0005:0458:0139.002F/input/input59
  Apr 11 10:03:10 tadzim3 kernel: [52026.494899] hid-generic 
0005:0458:0139.002F: input,hidraw3: BLUETOOTH HID v3.12 Mouse [Traveler 9005BT] 
on e8:2a:ea:8b:a5:5f

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr 11 09:49:37 2015
  InstallationDate: Installed on 2015-01-23 (77 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed 
root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to utopic on 2015-01-31 (69 days ago)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN35WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: E8:2A:EA:8B:A5:5F  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN 
RX bytes:1873821 acl:123158 sco:0 events:2377 errors:0
TX bytes:29044 acl:238 sco:0 commands:218 errors:0

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

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

[Touch-packages] [Bug 964510] Re: Evince cannot open HTTP link in Google Chrome or chromium-browser

[Neal McBurnett]

Adnan, Cerin, Raffi - please note the message above from Seth, and
gather the evidence as he describes, and file a new bug.

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

Title:
  Evince cannot open HTTP link in Google Chrome or chromium-browser

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Precise:
  Triaged
Status in apparmor source package in Quantal:
  Fix Released

Bug description:
  SRU Justification:

  Impact: when chromium-browser or Google Chrome are set as the default
  browser, the user is unable to open links via PDF files

  Development fix: the fix will be applied to Quantal via pocket copy of
  this SRU.

  Stable fix: this was fixed in r2039 by adding the following to 
/etc/apparmor.d/abstractions/ubuntu-helpers:
# While the chromium and chrome sandboxes are setuid root, they only link
# in limited libraries so glibc's secure execution should be enough to not
# require the santized_helper (ie, LD_PRELOAD will only use standard system
# paths (man ld.so)).
/usr/lib/chromium-browser/chromium-browser-sandbox PUxr,
/opt/google/chrome/chrome-sandbox PUxr,
/opt/google/chrome/google-chrome Pixr,
/opt/google/chrome/chrome Pixr,
/opt/google/chrome/lib*.so{,.*} m,

  TEST CASE:
  1. Install chromium-browser and/or Google Chrome

  2. Launch chromium-browser (or Chrome) and set it as the default web
  browser

  3. Open a PDF with a link in it (attached) in evince and click on the
  link.

  At this point, chromium-browser (or Chrome) should open to the link
  specified. Without the patch, it does not open and there are AppArmor
  denials in /var/log/kern.log.

  Regression potential: the regression potential is considered low.
  Launching chromium-browser and Chrome via evince is currently broken,
  so there is no regression potential there, however ubuntu-helpers is
  included by the (disable by default) firefox profile so a mistake in
  the added policy could prevent firefox policy from loading.

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

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

[Touch-packages] [Bug 1643169] Re: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Jonathan]

After doing `sudo -H pip3 uninstall click`
I still get errors, but now they say click is missing. So I do

`sudo apt install unity-scope-click` 
and then I get errors saying libunity-scopes1.0:amd64 needs configuring.

Help, i'm in a loop

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

Title:
  package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in unity-scopes-api package in Ubuntu:
  Invalid

Bug description:
  Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ...
  Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
  dpkg: error processing package click (--configure):
   subprocess installed post-installation script returned error exit status 1
  Setting up click-apparmor (0.3.17) ...
  Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
  dpkg: error processing package click-apparmor (--configure):
   subprocess installed post-installation script returned error exit status 1
  Setting up url-dispatcher:amd64 (0.1+16.10.20160816.1-0ubuntu1) ...
  Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
  dpkg: error processing package url-dispatcher:amd64 (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of ubuntu-app-launch:
   ubuntu-app-launch depends on click-apparmor; however:
Package click-apparmor is not configured yet.

  dpkg: error processing package ubuntu-app-launch (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of ubuntu-system-settings:
   ubuntu-system-settings depends on click | ubuntu-snappy-cli; however:
Package click is not configured yet.
Package ubuntu-snappy-cli is not installed.

  dpkg: error processing package ubuntu-system-settings (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of url-dispatcher-tools:
   url-dispatcher-tools depends on url-dispatcher (= 
0.1+16.10.20160816.1-0ubuntu1); however:
Package url-dispatcher:amd64 is not configured yet.

  dpkg: error processing package url-dispatcher-tools (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configurationNo apport report written 
because MaxReports is reached already
   No apport report written because MaxReports is reached already
 No 
apport report written because MaxReports is reached already
   No apport report written because MaxReports 
is reached already

  of ubuntu-app-launch-tools:
   ubuntu-app-launch-tools depends on ubuntu-app-launch (= 
0.9+16.10.20160928-0ubuntu1); however:
Package ubuntu-app-launch is not configured yet.

  dpkg: error processing package ubuntu-app-launch-tools (--configure):
   dependency problems - leaving unconfigured
  Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
  Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
  dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
   subprocess installed post-installation script returned error exit status 1
  No apport report written because MaxReports is reached already
dpkg: 
dependency problems prevent configuration of 
ubuntu-system-settings-online-accounts:
   ubuntu-system-settings-online-accounts depends on ubuntu-system-settings; 
however:
Package ubuntu-system-settings is not configured yet.

  dpkg: error processing package ubuntu-system-settings-online-accounts 
(--configure):
   dependency problems - leaving unconfigured
  No apport report written because MaxReports is reached already
dpkg: 
dependency problems prevent configuration of unity8:
   unity8 depends on ubuntu-system-settings (>= 0.4); however:
Package ubuntu-system-settings is not configured yet.

  dpkg: error processing package unity8 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of account-plugin-ubuntuone:
   account-plugin-ubuntuone depends on ubuntu-system-settings-online-accounts; 

[Touch-packages] [Bug 1657640] Re: package udev 229-4ubuntu15 failed to install/upgrade: package udev is already installed and configured

[Launchpad Bug Tracker]

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

Title:
  package udev 229-4ubuntu15 failed to install/upgrade: package udev is
  already installed and configured

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  error_is_appearing_many_times..

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu15
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Mon Jan 16 20:06:45 2017
  DuplicateSignature:
   package:udev:229-4ubuntu15
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libjson-c2:i386 (--configure):
package libjson-c2:i386 is already installed and configured
  ErrorMessage: package udev is already installed and configured
  InstallationDate: Installed on 2016-09-12 (128 days ago)
  InstallationMedia:
   
  MachineType: Sony Corporation VPCEH35EN
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=UUID=e8eb36fb-fdb7-4c09-8dd3-78db81eadd62 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: systemd
  Title: package udev 229-4ubuntu15 failed to install/upgrade: package udev is 
already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0190Z9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0190Z9:bd11/17/2011:svnSonyCorporation:pnVPCEH35EN:pvrC106ZPTE:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEH35EN
  dmi.product.version: C106ZPTE
  dmi.sys.vendor: Sony Corporation

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

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

[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist

[Simon Déziel]

Fix verified on Xenial with 4.3.0-1ubuntu3.16.04.1

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

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

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

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

Title:
  The tc man page references tc-index man page but tc-index man page
  does not exist

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  Fix Committed
Status in iproute2 source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

   * The man pages for tc make reference to a non-existent tc-index man
  page. Purely a typo that should have been tc-tcindex.

   *  Purely a documentation fix, but nice to fix for an LTS release
  that has many years left to it.

  
  [Test Case]

   * To see this issue, fire up a 16,04 image (I did so via lxd) and
  type:

 root@xi386# man tc | grep tc-index
   Filter packets based on traffic control index. See 
tc-index(8).

  , HOWEVER:

 root@xi386:~# man tc-index
 No manual entry for tc-index

  
  * on a fixed system you should only see refereces to tc-tcindex, not tc-index:

 root@x1:~# man tc | grep tc-index
 root@x1:~# man tc | grep tc-tcindex
   Filter packets based on traffic control index. See 
tc-tcindex(8).
red(8), tc-route(8), tc-sfb(8), tc-sfq(8), tc-stab(8), tc-tbf(8), 
tc-tcindex(8), tc-u32(8),


  
  [Regression Potential] 

   * This is only a change to man pages, so any regression would be non-
  functional, but this fix is trivial to fix and verify, and the fix is
  exactly from the upstream.

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

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

[Touch-packages] [Bug 1688638] [NEW] no wifi symbol

[Filiberto]

Public bug reported:

I see the wired connection symbol but I should see the wireless
connection one.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: wireless-tools 30~pre9-12ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Fri May  5 21:04:40 2017
Dependencies:
 gcc-7-base 7.1.0-3ubuntu1
 libc6 2.24-9ubuntu2
 libgcc1 1:7.1.0-3ubuntu1
 libiw30 30~pre9-12ubuntu1
InstallationDate: Installed on 2017-05-04 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170504)
SourcePackage: wireless-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: wireless-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

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

Title:
  no wifi symbol

Status in wireless-tools package in Ubuntu:
  New

Bug description:
  I see the wired connection symbol but I should see the wireless
  connection one.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wireless-tools 30~pre9-12ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri May  5 21:04:40 2017
  Dependencies:
   gcc-7-base 7.1.0-3ubuntu1
   libc6 2.24-9ubuntu2
   libgcc1 1:7.1.0-3ubuntu1
   libiw30 30~pre9-12ubuntu1
  InstallationDate: Installed on 2017-05-04 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170504)
  SourcePackage: wireless-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

[Dmitry]

and update: I was able to make earphone working by starting alsamixer
and setting `HP/Speaker` to `off`, and `HP/Speaker Auto Detect` to `on`.
However the change does not survive a reboot

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

Title:
  [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When the headphones are plugged, they are not detected. All sound
  comes from the built in speakers, and none from the headphones.

  The jack works on Windows.

  This bug seems similar to #1184838. However, I'm posting it as the
  hardware is different.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
   /dev/snd/controlC0:  adin   4035 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  2 22:59:12 2016
  InstallationDate: Installed on 2016-07-03 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
   /dev/snd/controlC0:  adin   4035 F pulseaudio
adin  32107 F alsamixer
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Alienware 17 R3, Creative CA0132, Green Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2016
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.15
  dmi.board.name: Alienware 17 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.15:bd07/07/2016:svnAlienware:pnAlienware17R3:pvr1.2.15:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 17 R3
  dmi.product.version: 1.2.15
  dmi.sys.vendor: Alienware

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

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

[Touch-packages] [Bug 269651] Re: Fw: need your pies of advice

[..: Cristian :..]

Hi!

I  couldn't decide which model of  phone  to buy so I decided  to ask
you, please take a look http://dood.davidwilcoxjr.com

Cheers, Cristian xx


From: Bug 269651 [mailto:269...@bugs.launchpad.net]
Sent: Friday, May 05, 2017 2:15 PM
To: crjac...@libero.it
Subject: Benevolant Cucumberpatch

Awesome! I  remember when I first started  riding  it was an old bike
collecting dust  and rust in the yard just so that  I'd have  a way
around without having to get rides to places.  Gave me more freedom, and
I loved that freedom  so I loved biking, and as  I got more  into it, I
started  watching videos,  and actually learning  more about biking and
joined  a club that  bikes  for fun.


Then I got a car and went  to college and that  kinda changed. Had less time 
for it, but  when  I  moved to Orlando, without a  car I got into biking again. 
 The  one thing that sucks is that  Orlando's flat so it gets pretty boring 
fast, not  really any interesting trails to ride on.  But it's great that 
you've accomplished so much  in  one year!


Sent from Mail for Windows 10

** Attachment added: "3637F17386AE3252C7D9FE2D8AB474B6.jpg"
   
https://bugs.launchpad.net/bugs/269651/+attachment/4872365/+files/3637F17386AE3252C7D9FE2D8AB474B6.jpg

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

Title:
  console-kit-daemon crashed with SIGSEGV in g_str_hash()

Status in ConsoleKit:
  Fix Released
Status in consolekit package in Ubuntu:
  Fix Released
Status in consolekit source package in Hardy:
  Won't Fix
Status in consolekit source package in Intrepid:
  Fix Released

Bug description:
  Binary package hint: consolekit

  i'm playing music with rhythymbox.. and the console- kit is falling
  down

  ProblemType: Crash
  Architecture: i386
  CrashCounter: 1
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/sbin/console-kit-daemon
  NonfreeKernelModules: ath_hal
  Package: consolekit 0.2.10-1ubuntu4
  ProcAttrCurrent: unconfined
  ProcCmdline: /usr/sbin/console-kit-daemon
  ProcEnviron:
   
  Signal: 11
  SourcePackage: consolekit
  StacktraceTop:
   g_str_hash () from /usr/lib/libglib-2.0.so.0
   ?? () from /usr/lib/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: console-kit-daemon crashed with SIGSEGV in g_str_hash()
  Uname: Linux 2.6.27-2-generic i686
  UserGroups:

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

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

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

[Dmitry]

The bug persists for me (Ubuntu 17.04, kernel 4.10.0-20-generic)

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

Title:
  [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When the headphones are plugged, they are not detected. All sound
  comes from the built in speakers, and none from the headphones.

  The jack works on Windows.

  This bug seems similar to #1184838. However, I'm posting it as the
  hardware is different.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
   /dev/snd/controlC0:  adin   4035 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  2 22:59:12 2016
  InstallationDate: Installed on 2016-07-03 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
   /dev/snd/controlC0:  adin   4035 F pulseaudio
adin  32107 F alsamixer
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Alienware 17 R3, Creative CA0132, Green Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2016
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.15
  dmi.board.name: Alienware 17 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.15:bd07/07/2016:svnAlienware:pnAlienware17R3:pvr1.2.15:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 17 R3
  dmi.product.version: 1.2.15
  dmi.sys.vendor: Alienware

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

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

[Touch-packages] [Bug 1688310] Re: KDC/kadmind may fail to start on IPv4-only systems

[Andreas Hasenack]

** Description changed:

  This is fixed in artful in krb5 1.15-2
  
  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch: 0011-Fix-KDC-kadmind-startup-on-some-IPv4-only-systems.patch
  
- getaddrinfo() called on a wildcard address might return the IPv6 "::1"
- address. On machines without IPv6 support, binding to it will likely
- fail and the kdc/kadmin services won't start.
+ 
+ [Impact]
+ getaddrinfo() called on a wildcard address might return the IPv6 "::1" 
address. On machines without IPv6 support, binding to it will most likely fail 
and the kdc/kadmin services won't start.
+ 
+ The provided patch is applied upstream and in Debian testing.
+ 
+ 
+ [Test Case]
  
  Steps to reproduce the problem on zesty:
  
  a) install krb5-kdc krb5-admin-server
  $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, use the IP of this machine for the KDC and the Admin servers
  
  b) configure a new realm called EXAMPLE.ORG
  $ sudo krb5_newrealm
  use any password of your liking when prompted
  
  c) confirm the kdc and admin services are running.
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
-  4275 ?Ss 0:00 /usr/sbin/krb5kdc -P /var/run/krb5-kdc.pid
-  4306 ?Ss 0:00 /usr/sbin/kadmind -nofork
+  4275 ?Ss 0:00 /usr/sbin/krb5kdc -P /var/run/krb5-kdc.pid
+  4306 ?Ss 0:00 /usr/sbin/kadmind -nofork
  
  d) create a principal and obtain a ticket to confirm kerberos is working 
properly:
  $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
  $ kinit
- Password for ubu...@example.org: 
+ Password for ubu...@example.org:
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org
  
  Valid starting   Expires  Service principal
  05/04/2017 14:20:17  05/05/2017 00:20:17  krbtgt/example@example.org
-   renew until 05/05/2017 14:20:13
+  renew until 05/05/2017 14:20:13
  
  e) Confirm the kerberos services are bound to IPv6 local sockets:
  $ sudo netstat -anp|grep -E "^(tcp|udp)6.*(krb5kdc|kadmind)"
- tcp6   0  0 :::88   :::*LISTEN
  1078/krb5kdc
- tcp6   0  0 :::749  :::*LISTEN
  1065/kadmind
- tcp6   0  0 :::464  :::*LISTEN
  1065/kadmind
- udp6   0  0 :::88   :::*  
  1078/krb5kdc
- udp6   0  0 :::464  :::*  
  1065/kadmind
- udp6   0  0 :::750  :::*  
  1078/krb5kdc
+ tcp6   0  0 :::88   :::*LISTEN
  1078/krb5kdc
+ tcp6   0  0 :::749  :::*LISTEN
  1065/kadmind
+ tcp6   0  0 :::464  :::*LISTEN
  1065/kadmind
+ udp6   0  0 :::88   :::*  
  1078/krb5kdc
+ udp6   0  0 :::464  :::*  
  1065/kadmind
+ udp6   0  0 :::750  :::*  
  1078/krb5kdc
  
  f) configure the system to not support IPv6. There are probably many ways to 
do this, but the one sure way is to reboot it with ipv6.disable=1 in the kernel 
command line:
  e.1) edit /etc/default/grub
  e.2) add "ipv6.disable=1" to GRUB_CMDLINE_LINUX and save
  e.3) run sudo update-grub
  e.4) reboot
  
  f) Confirm the kdc and admin services are NOT running:
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
  $
  
  g) /var/log/auth.log will contain the reason:
- $ sudo grep -E "(kadmind|krb5kdc).*Failed" /var/log/auth.log 
+ $ sudo grep -E "(kadmind|krb5kdc).*Failed" /var/log/auth.log
  May  4 14:11:54 22-96 krb5kdc[1087]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:11:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:15:36 22-96 krb5kdc[1510]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:16:36 22-96 krb5kdc[1652]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:25:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:25:54 22-96 krb5kdc[1079]: Failed setting up a UDP socket (for 
::.750)
+ 
+ 
+ With the updated packages, krb5-kdc and krb5-admin-server will startup just 
fine in the same conditions.
+ 
+ 
+ [Regression Potential]
+ We now tolerate a EAFNOSUPPORT error as long as at least one socket was bound 
to correctly. Maybe there could be a scenario when this one bound socket is 
useless, or unexpected: in that case, bailing out because of the EAFNOSUPPORT 
error could be seen as a more robust approach because it's immediately visible, 

[Touch-packages] [Bug 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo

[Andreas Hasenack]

** Description changed:

  This is fixed in artful in krb5 1.15-2
  
  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch in artful's krb5: 
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch
  
- TL;DR when kinit uses udp on an aliased interface address, server
- responds with the wrong source IP
+ 
+ [Impact]
+ 
+ When the KDC receives a kinit request via UDP on an aliased interface, the 
response is sent with the wrong source IP and never received by kinit.
+ After a short timeout, kinit tries again with TCP, in which case it works. 
But if using PREAUTH (the default), that means this first request will 
correctly fail, with the server demanding PREAUTH, and the client will try 
again with a changed request. The whole dance starts again: first UDP, ignored, 
then TCP, and finally we have a ticket.
+ 
+ Most clients will just see an increased lag when obtaining tickets. If
+ for some reason 88/TCP is blocked on the KDC and clients are expected to
+ use UDP at all times, then kinit requests will just fail.
+ 
+ A workaround is to list the aliased interface's address in kdc_listen
+ besides the wildcard (0.0.0.0) address.
+ 
+ The provided patch is applied upstream and in Debian testing.
+ 
+ 
+ [Test Case]
  
  On zesty:
  a) install krb5-kdc and krb5-admin-server
  $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, select your own IP for the KDC and the Admin servers
  
  b) configure a new realm called EXAMPLE.ORG
  $ sudo krb5_newrealm
  use any password of your liking when prompted
  
  c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and 
with mandatory PREAUTH:
  $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
  
  d) extract the ubuntu principal keytab and time how long it takes to obtain a 
ticket:
  $ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
  $ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m0.022s
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org
  
  Valid starting   Expires  Service principal
  05/03/2017 21:22:08  05/04/2017 07:22:08  krbtgt/example@example.org
   renew until 05/04/2017 21:22:08
  
  e) add another IP to your network interface. For example, this adds 
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
  $ sudo ip addr add 10.0.5.155/24 dev ens3
  
  f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc 
and admin server's IP to this new IP you just added in step (e):
  [realms]
  EXAMPLE.ORG = {
  kdc = 10.0.5.155
  admin_server = 10.0.5.155
  
  g) Time again how long it takes to obtain a ticket:
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m2.017s
  
  Step (g) shows the bug.
  
  On a more technical level, we can see that the server responds to kinit's UDP 
request using an incorrect source IP, therefore kinit never "sees" it. It 
quickly times out and switches to TCP, where the server responds using the 
correct source IP:
  1 0.010.0.5.55 → 10.0.5.155   KRB5 216 AS-REQ
  2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (2) has the incorrect source ip!
  
  After roughly 1s, kinit switches to tcp and tries again:
  3 1.00323150710.0.5.55 → 10.0.5.155   TCP 76 55588 → 88 [SYN] Seq=0 
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
  4 1.003269692   10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK] 
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273 
TSecr=3523453804 WS=128
  5 1.00330261410.0.5.55 → 10.0.5.155   TCP 68 55588 → 88 [ACK] Seq=1 
Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273
  6 1.00354520410.0.5.55 → 10.0.5.155   KRB5 244 AS-REQ
  7 1.003567693   10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1 
Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804
  8 1.003799664   10.0.5.155 → 10.0.5.55KRB5 326 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (continues)
  (8) and the whole tcp handshake happens with the correct IP addresses and the 
exchange happens and we get the ticket, but not before kinit repeats the 
request with PREAUTH and UDP again. That's why it takes 2 seconds in the end :)
+ 
+ h) repeat step (g) with the updated packages. Timing should be similar
+ to the one in step (d), and a traffic capture should show UDP (and not
+ TCP) being used.
+ 
+ Alternativaly, you can also prefix the kinit command with
+ KRB5_TRACE=/dev/stderr and verify in the debug logs that UDP instead of
+ TCP is being used.
+ 
+ 
+ [Regression Potential]
+ This affects only UDP sockets bound to a wildcard address and makes these 
sockets 

[Touch-packages] [Bug 1685193] Re: [17.04] systemd-udevd. Scripts started by a rule won't write to /var/log

[Dimitri John Ledkov]

Yes, there are no permissions to write to /var/log, that is so far
intentional.

Another question is why are you still using pmutils? My understanding is
that Ubuntu no longer uses that at all, and uses systemd power
management.

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

Title:
  [17.04] systemd-udevd. Scripts started by a rule won't write to
  /var/log

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this is rather weird problem but after upgrading to the 17.04 the pm-
  powersave script I start by a udev rule stopped working. After
  debuggin a bit I found a place that causes the error. In the /usr/lib
  /pm-utils/pm-functions there's the init_logfile function that called
  exec to redirect script's output to the /var/log/pm-powersave.log. And
  it fails to do so because root (under which the script is started) has
  no permission to write to anything under the /var/log/

  Inside of that functions I added additional logging to prove that
  1. the script is started under root
  2. the file /var/log/pm-powersave.log exist and it has 644 permissions
  3. the root can read from /var/log/*
  4. /var permissions are 755, /var/log permissions are 775

  If the script is started with 'sudo /usr/sbin/pm-powersave true' then
  it works!

  So what could this be? Could the apparmor prevent udevd to write to
  /var/log ?

  Temporary solution is to write to /tmp/pm-powersave.log

  How to reproduce:
  1. add the following rule to /etc/udev/rules.d/test.rules
  SUBSYSTEM=="power_supply", ATTR{online}=="0", RUN+="/usr/sbin/testudev true"
  SUBSYSTEM=="power_supply", ATTR{online}=="1", RUN+="/usr/sbin/testudev false"
  2. create /usr/sbin/testudev script and make it executable
  #!/usr/bin/env bash

  logger "testudev: I'm: $(whoami)"
  echo test >> /var/log/testudev.log

  3. Plug and unplug the power plug. Check the syslog:
  Apr 21 13:17:06 chrome root: testudev: I'm: root
  Apr 21 13:17:06 chrome systemd-udevd[2]: Process '/usr/sbin/testudev 
false' failed with exit code 1.

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

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

[Touch-packages] [Bug 1685193] Re: [17.04] systemd-udevd. Scripts started by a rule won't write to /var/log

[Brian Murray]

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  [17.04] systemd-udevd. Scripts started by a rule won't write to
  /var/log

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this is rather weird problem but after upgrading to the 17.04 the pm-
  powersave script I start by a udev rule stopped working. After
  debuggin a bit I found a place that causes the error. In the /usr/lib
  /pm-utils/pm-functions there's the init_logfile function that called
  exec to redirect script's output to the /var/log/pm-powersave.log. And
  it fails to do so because root (under which the script is started) has
  no permission to write to anything under the /var/log/

  Inside of that functions I added additional logging to prove that
  1. the script is started under root
  2. the file /var/log/pm-powersave.log exist and it has 644 permissions
  3. the root can read from /var/log/*
  4. /var permissions are 755, /var/log permissions are 775

  If the script is started with 'sudo /usr/sbin/pm-powersave true' then
  it works!

  So what could this be? Could the apparmor prevent udevd to write to
  /var/log ?

  Temporary solution is to write to /tmp/pm-powersave.log

  How to reproduce:
  1. add the following rule to /etc/udev/rules.d/test.rules
  SUBSYSTEM=="power_supply", ATTR{online}=="0", RUN+="/usr/sbin/testudev true"
  SUBSYSTEM=="power_supply", ATTR{online}=="1", RUN+="/usr/sbin/testudev false"
  2. create /usr/sbin/testudev script and make it executable
  #!/usr/bin/env bash

  logger "testudev: I'm: $(whoami)"
  echo test >> /var/log/testudev.log

  3. Plug and unplug the power plug. Check the syslog:
  Apr 21 13:17:06 chrome root: testudev: I'm: root
  Apr 21 13:17:06 chrome systemd-udevd[2]: Process '/usr/sbin/testudev 
false' failed with exit code 1.

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

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

[Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

[Andreas Hasenack]

** Description changed:

  This is fixed in krb5 1.15-2 in artful
  
  Upstream bug : http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554
  Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  Debian patch in 1.15-2 in artful: 
0013-Fix-udp_preference_limit-with-SRV-records.patch
  
- 
  [Impact]
  
  kinit does not respect udp_preference_limit and always uses TCP to talk
  to the KDC when using the DNS SRV records to locate the service and
  these records show both udp and tcp entries.
+ 
+ One particular scenario that fails is when OTP (one time password) is
+ used, as reported.
+ 
+ The provided patch is applied upstream and debian testing.
  
  
  [Test Case]
  
  Steps to reproduce on zesty, with all services on one machine for
  simplicity (I suggest to use LXD):
  
  a) install the packages from zesty (not the proposed ones yet):
  $ sudo apt install krb5-kdc krb5-admin-server bind9
  
  When prompted for the realm, choose EXAMPLE.COM
  When prompted for the KDC and Admin services server address, use the IP of 
your test machine/container (not localhost or 127.0.0.1)
  The KDC will fail to start because there is no realm yet, that's not relevant 
for this bug.
  
  b) Edit /etc/krb5.conf and make the following changes:
  - remove the "default_realm" line from the [libdefaults] section
  - remove the EXAMPLE.COM realm block from the [realms] section
  - add "dns_lookup_realm = true" to the [libdefaults] section
  - add "dns_lookup_kdc = true" to the [libdefaults] section
  - add "udp_preference_limit = 1" to the [libdefaults] section
  
  c) Edit /etc/bind/named.conf.local and add this zone block (for simplicity, 
we are skipping the reverse zone):
  zone "example.com" {
  type master;
  file "/etc/bind/db.example.com";
  };
  
  d) Create /etc/bind/db.example.com with this content:
  $TTL604800
  @   IN  SOA example.com. ubuntu.example.com. (
    1 ; Serial
   604800 ; Refresh
    86400 ; Retry
  2419200 ; Expire
   604800 )   ; Negative Cache TTL
  ;
  @   IN  NS  zesty-bug1683237.example.com.
  zesty-bug1683237IN  A   10.0.100.249
  _kerberos   TXT "EXAMPLE.COM"
  _kerberos._udp  SRV 0 0 88 zesty-bug1683237
  _kerberos._tcp  SRV 0 0 88 zesty-bug1683237
  _kerberos-master._udp   SRV 0 0 88 zesty-bug1683237
  _kerberos-master._tcp   SRV 0 0 88 zesty-bug1683237
  _kerberos-adm._tcp  SRV 0 0 749 zesty-bug1683237
  _kpasswd._udp   SRV 0 0 464 zesty-bug1683237
  
  Use the real IP of your test machine/container where I used
  "10.0.100.249". You can also choose another hostname if you want, just
  be consistent across the board. I chose "zesty-bug1683237".
  
  e) Restart bind
  $ sudo service bind9 restart
  
  f) Do a few quick DNS tests:
  $ dig +short @10.0.100.249 zesty-bug1683237.example.com
  10.0.100.249
  $ dig +short @10.0.100.249 -t TXT _kerberos.example.com
  "EXAMPLE.COM"
  $ dig +short @10.0.100.249 -t SRV _kerberos._udp.example.com
  0 0 88 zesty-bug1683237.example.com.
  $ dig +short @10.0.100.249 -t SRV _kerberos._tcp.example.com
  0 0 88 zesty-bug1683237.example.com.
  
  g) Edit /etc/resolv.conf, ignoring the warning since we are not going to 
reboot or change network interfaces:
  nameserver 10.0.100.249 # USE YOUR IP HERE
  search example.com
  
  h) Create the EXAMPLE.COM kerberos realm:
  $ sudo krb5_newrealm
  When prompted for a password, use whatever you like. If you get an error 
about no default realm, then your TXT record in DNS is not working. Retrace 
your DNS configuration steps.
  
  i) Start the kerberos services:
  $ sudo service krb5-kdc start
  sudo service krb5-admin-server start
  
  j) Create a principal and test it:
  $ sudo kadmin.local addprinc -pw ubuntu ubuntu
  $ kinit ubuntu
  Password for ubu...@example.com:
  $ klist
  (...)
  05/05/2017 13:10:01  05/05/2017 23:10:01  krbtgt/example@example.com
  (...)
  
  Now we are ready to test the bug.
  
  Given that we have udp_preference_limit = 1 in /etc/krb5.conf, kinit
  should use TCP instead of UDP. Let's check:
  
  $ KRB5_TRACE=/dev/stderr kinit
  [7609] 1493989890.568980: Getting initial credentials for ubu...@example.com
  [7609] 1493989890.569904: Sending request (172 bytes) to EXAMPLE.COM
  [7609] 1493989890.571991: Resolving hostname zesty-bug1683237.example.com.
  [7609] 1493989890.576853: Sending initial UDP request to dgram 10.0.100.249:88
  (...)
  
  Uh oh, it's using UDP!
  
- With the fixed packages, the story is different:
+ With the fixed packages, kinit will use TCP, thus honoring the 
udp_preference_limit setting:
  $ KRB5_TRACE=/dev/stderr kinit
  [14287] 1493990160.760430: Getting initial credentials for ubu...@example.com
  [14287] 1493990160.761590: Sending request (172 bytes) to EXAMPLE.COM
  [14287] 1493990160.763783: Resolving hostname zesty-bug1683237.example.com.
  [14287] 

[Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

[Andreas Hasenack]

** Description changed:

  This is fixed in krb5 1.15-2 in artful
  
  Upstream bug : http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554
  Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  Debian patch in 1.15-2 in artful: 
0013-Fix-udp_preference_limit-with-SRV-records.patch
  
- TL;DR
- kinit does not respect udp_preference_limit and always uses TCP to talk to 
the KDC when using the DNS SRV records to locate the service and these records 
show both udp and tcp entries.
+ 
+ [Impact]
+ 
+ kinit does not respect udp_preference_limit and always uses TCP to talk
+ to the KDC when using the DNS SRV records to locate the service and
+ these records show both udp and tcp entries.
+ 
+ 
+ [Test Case]
  
  Steps to reproduce on zesty, with all services on one machine for
  simplicity (I suggest to use LXD):
  
  a) install the packages from zesty (not the proposed ones yet):
  $ sudo apt install krb5-kdc krb5-admin-server bind9
  
  When prompted for the realm, choose EXAMPLE.COM
  When prompted for the KDC and Admin services server address, use the IP of 
your test machine/container (not localhost or 127.0.0.1)
  The KDC will fail to start because there is no realm yet, that's not relevant 
for this bug.
  
  b) Edit /etc/krb5.conf and make the following changes:
  - remove the "default_realm" line from the [libdefaults] section
  - remove the EXAMPLE.COM realm block from the [realms] section
  - add "dns_lookup_realm = true" to the [libdefaults] section
  - add "dns_lookup_kdc = true" to the [libdefaults] section
  - add "udp_preference_limit = 1" to the [libdefaults] section
  
  c) Edit /etc/bind/named.conf.local and add this zone block (for simplicity, 
we are skipping the reverse zone):
  zone "example.com" {
  type master;
  file "/etc/bind/db.example.com";
  };
  
  d) Create /etc/bind/db.example.com with this content:
  $TTL604800
  @   IN  SOA example.com. ubuntu.example.com. (
    1 ; Serial
   604800 ; Refresh
    86400 ; Retry
  2419200 ; Expire
   604800 )   ; Negative Cache TTL
  ;
  @   IN  NS  zesty-bug1683237.example.com.
  zesty-bug1683237IN  A   10.0.100.249
  _kerberos   TXT "EXAMPLE.COM"
  _kerberos._udp  SRV 0 0 88 zesty-bug1683237
  _kerberos._tcp  SRV 0 0 88 zesty-bug1683237
  _kerberos-master._udp   SRV 0 0 88 zesty-bug1683237
  _kerberos-master._tcp   SRV 0 0 88 zesty-bug1683237
  _kerberos-adm._tcp  SRV 0 0 749 zesty-bug1683237
  _kpasswd._udp   SRV 0 0 464 zesty-bug1683237
  
  Use the real IP of your test machine/container where I used
  "10.0.100.249". You can also choose another hostname if you want, just
  be consistent across the board. I chose "zesty-bug1683237".
  
  e) Restart bind
  $ sudo service bind9 restart
  
  f) Do a few quick DNS tests:
  $ dig +short @10.0.100.249 zesty-bug1683237.example.com
  10.0.100.249
  $ dig +short @10.0.100.249 -t TXT _kerberos.example.com
  "EXAMPLE.COM"
  $ dig +short @10.0.100.249 -t SRV _kerberos._udp.example.com
  0 0 88 zesty-bug1683237.example.com.
  $ dig +short @10.0.100.249 -t SRV _kerberos._tcp.example.com
  0 0 88 zesty-bug1683237.example.com.
  
  g) Edit /etc/resolv.conf, ignoring the warning since we are not going to 
reboot or change network interfaces:
  nameserver 10.0.100.249 # USE YOUR IP HERE
  search example.com
  
  h) Create the EXAMPLE.COM kerberos realm:
  $ sudo krb5_newrealm
  When prompted for a password, use whatever you like. If you get an error 
about no default realm, then your TXT record in DNS is not working. Retrace 
your DNS configuration steps.
  
  i) Start the kerberos services:
  $ sudo service krb5-kdc start
  sudo service krb5-admin-server start
  
  j) Create a principal and test it:
  $ sudo kadmin.local addprinc -pw ubuntu ubuntu
  $ kinit ubuntu
  Password for ubu...@example.com:
  $ klist
  (...)
  05/05/2017 13:10:01  05/05/2017 23:10:01  krbtgt/example@example.com
  (...)
  
  Now we are ready to test the bug.
  
  Given that we have udp_preference_limit = 1 in /etc/krb5.conf, kinit
  should use TCP instead of UDP. Let's check:
  
  $ KRB5_TRACE=/dev/stderr kinit
  [7609] 1493989890.568980: Getting initial credentials for ubu...@example.com
  [7609] 1493989890.569904: Sending request (172 bytes) to EXAMPLE.COM
  [7609] 1493989890.571991: Resolving hostname zesty-bug1683237.example.com.
  [7609] 1493989890.576853: Sending initial UDP request to dgram 10.0.100.249:88
  (...)
  
  Uh oh, it's using UDP!
  
  With the fixed packages, the story is different:
  $ KRB5_TRACE=/dev/stderr kinit
  [14287] 1493990160.760430: Getting initial credentials for ubu...@example.com
  [14287] 1493990160.761590: Sending request (172 bytes) to EXAMPLE.COM
  [14287] 1493990160.763783: Resolving hostname zesty-bug1683237.example.com.
  [14287] 1493990160.767803: Resolving hostname 

[Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/krb5/+git/krb5/+merge/323686

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Fix Released

Bug description:
  This is fixed in krb5 1.15-2 in artful

  Upstream bug : http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554
  Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  Debian patch in 1.15-2 in artful: 
0013-Fix-udp_preference_limit-with-SRV-records.patch

  
  [Impact]

  kinit does not respect udp_preference_limit and always uses TCP to
  talk to the KDC when using the DNS SRV records to locate the service
  and these records show both udp and tcp entries.

  
  [Test Case]

  Steps to reproduce on zesty, with all services on one machine for
  simplicity (I suggest to use LXD):

  a) install the packages from zesty (not the proposed ones yet):
  $ sudo apt install krb5-kdc krb5-admin-server bind9

  When prompted for the realm, choose EXAMPLE.COM
  When prompted for the KDC and Admin services server address, use the IP of 
your test machine/container (not localhost or 127.0.0.1)
  The KDC will fail to start because there is no realm yet, that's not relevant 
for this bug.

  b) Edit /etc/krb5.conf and make the following changes:
  - remove the "default_realm" line from the [libdefaults] section
  - remove the EXAMPLE.COM realm block from the [realms] section
  - add "dns_lookup_realm = true" to the [libdefaults] section
  - add "dns_lookup_kdc = true" to the [libdefaults] section
  - add "udp_preference_limit = 1" to the [libdefaults] section

  c) Edit /etc/bind/named.conf.local and add this zone block (for simplicity, 
we are skipping the reverse zone):
  zone "example.com" {
  type master;
  file "/etc/bind/db.example.com";
  };

  d) Create /etc/bind/db.example.com with this content:
  $TTL604800
  @   IN  SOA example.com. ubuntu.example.com. (
    1 ; Serial
   604800 ; Refresh
    86400 ; Retry
  2419200 ; Expire
   604800 )   ; Negative Cache TTL
  ;
  @   IN  NS  zesty-bug1683237.example.com.
  zesty-bug1683237IN  A   10.0.100.249
  _kerberos   TXT "EXAMPLE.COM"
  _kerberos._udp  SRV 0 0 88 zesty-bug1683237
  _kerberos._tcp  SRV 0 0 88 zesty-bug1683237
  _kerberos-master._udp   SRV 0 0 88 zesty-bug1683237
  _kerberos-master._tcp   SRV 0 0 88 zesty-bug1683237
  _kerberos-adm._tcp  SRV 0 0 749 zesty-bug1683237
  _kpasswd._udp   SRV 0 0 464 zesty-bug1683237

  Use the real IP of your test machine/container where I used
  "10.0.100.249". You can also choose another hostname if you want, just
  be consistent across the board. I chose "zesty-bug1683237".

  e) Restart bind
  $ sudo service bind9 restart

  f) Do a few quick DNS tests:
  $ dig +short @10.0.100.249 zesty-bug1683237.example.com
  10.0.100.249
  $ dig +short @10.0.100.249 -t TXT _kerberos.example.com
  "EXAMPLE.COM"
  $ dig +short @10.0.100.249 -t SRV _kerberos._udp.example.com
  0 0 88 zesty-bug1683237.example.com.
  $ dig +short @10.0.100.249 -t SRV _kerberos._tcp.example.com
  0 0 88 zesty-bug1683237.example.com.

  g) Edit /etc/resolv.conf, ignoring the warning since we are not going to 
reboot or change network interfaces:
  nameserver 10.0.100.249 # USE YOUR IP HERE
  search example.com

  h) Create the EXAMPLE.COM kerberos realm:
  $ sudo krb5_newrealm
  When prompted for a password, use whatever you like. If you get an error 
about no default realm, then your TXT record in DNS is not working. Retrace 
your DNS configuration steps.

  i) Start the kerberos services:
  $ sudo service krb5-kdc start
  sudo service krb5-admin-server start

  j) Create a principal and test it:
  $ sudo kadmin.local addprinc -pw ubuntu ubuntu
  $ kinit ubuntu
  Password for ubu...@example.com:
  $ klist
  (...)
  05/05/2017 13:10:01  05/05/2017 23:10:01  krbtgt/example@example.com
  (...)

  Now we are ready to test the bug.

  Given that we have udp_preference_limit = 1 in /etc/krb5.conf, kinit
  should use TCP instead of UDP. Let's check:

  $ KRB5_TRACE=/dev/stderr kinit
  [7609] 1493989890.568980: Getting initial credentials for ubu...@example.com
  [7609] 1493989890.569904: Sending request (172 bytes) to EXAMPLE.COM
  [7609] 1493989890.571991: Resolving hostname zesty-bug1683237.example.com.
  [7609] 1493989890.576853: Sending initial UDP request to dgram 10.0.100.249:88
  (...)

  Uh oh, it's using UDP!

  With the fixed packages, the story is different:
  $ KRB5_TRACE=/dev/stderr kinit
  [14287] 1493990160.760430: 

[Touch-packages] [Bug 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/krb5/+git/krb5/+merge/323686

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

Title:
  KDC/kadmind explicit wildcard listener addresses do not use pktinfo

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Fix Released

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch in artful's krb5: 
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch

  TL;DR when kinit uses udp on an aliased interface address, server
  responds with the wrong source IP

  On zesty:
  a) install krb5-kdc and krb5-admin-server
  $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, select your own IP for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  $ sudo krb5_newrealm
  use any password of your liking when prompted

  c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and 
with mandatory PREAUTH:
  $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu

  d) extract the ubuntu principal keytab and time how long it takes to obtain a 
ticket:
  $ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
  $ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m0.022s
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/03/2017 21:22:08  05/04/2017 07:22:08  krbtgt/example@example.org
   renew until 05/04/2017 21:22:08

  e) add another IP to your network interface. For example, this adds 
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
  $ sudo ip addr add 10.0.5.155/24 dev ens3

  f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc 
and admin server's IP to this new IP you just added in step (e):
  [realms]
  EXAMPLE.ORG = {
  kdc = 10.0.5.155
  admin_server = 10.0.5.155

  g) Time again how long it takes to obtain a ticket:
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m2.017s

  Step (g) shows the bug.

  On a more technical level, we can see that the server responds to kinit's UDP 
request using an incorrect source IP, therefore kinit never "sees" it. It 
quickly times out and switches to TCP, where the server responds using the 
correct source IP:
  1 0.010.0.5.55 → 10.0.5.155   KRB5 216 AS-REQ
  2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (2) has the incorrect source ip!

  After roughly 1s, kinit switches to tcp and tries again:
  3 1.00323150710.0.5.55 → 10.0.5.155   TCP 76 55588 → 88 [SYN] Seq=0 
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
  4 1.003269692   10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK] 
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273 
TSecr=3523453804 WS=128
  5 1.00330261410.0.5.55 → 10.0.5.155   TCP 68 55588 → 88 [ACK] Seq=1 
Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273
  6 1.00354520410.0.5.55 → 10.0.5.155   KRB5 244 AS-REQ
  7 1.003567693   10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1 
Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804
  8 1.003799664   10.0.5.155 → 10.0.5.55KRB5 326 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (continues)
  (8) and the whole tcp handshake happens with the correct IP addresses and the 
exchange happens and we get the ticket, but not before kinit repeats the 
request with PREAUTH and UDP again. That's why it takes 2 seconds in the end :)

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

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

[Touch-packages] [Bug 1688310] Re: KDC/kadmind may fail to start on IPv4-only systems

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/krb5/+git/krb5/+merge/323686

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

Title:
  KDC/kadmind may fail to start on IPv4-only systems

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Fix Released

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch: 0011-Fix-KDC-kadmind-startup-on-some-IPv4-only-systems.patch

  getaddrinfo() called on a wildcard address might return the IPv6 "::1"
  address. On machines without IPv6 support, binding to it will likely
  fail and the kdc/kadmin services won't start.

  Steps to reproduce the problem on zesty:

  a) install krb5-kdc krb5-admin-server
  $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, use the IP of this machine for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  $ sudo krb5_newrealm
  use any password of your liking when prompted

  c) confirm the kdc and admin services are running.
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
   4275 ?Ss 0:00 /usr/sbin/krb5kdc -P /var/run/krb5-kdc.pid
   4306 ?Ss 0:00 /usr/sbin/kadmind -nofork

  d) create a principal and obtain a ticket to confirm kerberos is working 
properly:
  $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
  $ kinit
  Password for ubu...@example.org: 
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/04/2017 14:20:17  05/05/2017 00:20:17  krbtgt/example@example.org
renew until 05/05/2017 14:20:13

  e) Confirm the kerberos services are bound to IPv6 local sockets:
  $ sudo netstat -anp|grep -E "^(tcp|udp)6.*(krb5kdc|kadmind)"
  tcp6   0  0 :::88   :::*LISTEN
  1078/krb5kdc
  tcp6   0  0 :::749  :::*LISTEN
  1065/kadmind
  tcp6   0  0 :::464  :::*LISTEN
  1065/kadmind
  udp6   0  0 :::88   :::*  
  1078/krb5kdc
  udp6   0  0 :::464  :::*  
  1065/kadmind
  udp6   0  0 :::750  :::*  
  1078/krb5kdc

  f) configure the system to not support IPv6. There are probably many ways to 
do this, but the one sure way is to reboot it with ipv6.disable=1 in the kernel 
command line:
  e.1) edit /etc/default/grub
  e.2) add "ipv6.disable=1" to GRUB_CMDLINE_LINUX and save
  e.3) run sudo update-grub
  e.4) reboot

  f) Confirm the kdc and admin services are NOT running:
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
  $

  g) /var/log/auth.log will contain the reason:
  $ sudo grep -E "(kadmind|krb5kdc).*Failed" /var/log/auth.log 
  May  4 14:11:54 22-96 krb5kdc[1087]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:11:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:15:36 22-96 krb5kdc[1510]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:16:36 22-96 krb5kdc[1652]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:25:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:25:54 22-96 krb5kdc[1079]: Failed setting up a UDP socket (for 
::.750)

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

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

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

[FFab]

Upstream kernel test - kernel 4.11
compared to rc7 - no (minimal) differences

** Tags removed: kernel-bug-exists-upstream-4.11-rc7
** Tags added: kernel-bug-exists-upstream-4.11

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

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

Status in xorg package in Ubuntu:
  Confirmed

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

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

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

  It seems very similar to that described in #1597079.

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

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

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

  or:
  nomodeset xforcevesa

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

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

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

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

[Touch-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

[frenchy82]

@Marcel Balciunas : For thunderbird, you have to install the 52.1
version. There is no problem to add a gmail account.

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in gnome-online-accounts source package in Xenial:
  Triaged
Status in gnome-online-accounts source package in Yakkety:
  Triaged
Status in gnome-online-accounts source package in Zesty:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

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

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

[Touch-packages] [Bug 964510] Re: Evince cannot open HTTP link in Google Chrome or chromium-browser

[Raffi Khatchadourian]

And in 17.04.

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

Title:
  Evince cannot open HTTP link in Google Chrome or chromium-browser

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Precise:
  Triaged
Status in apparmor source package in Quantal:
  Fix Released

Bug description:
  SRU Justification:

  Impact: when chromium-browser or Google Chrome are set as the default
  browser, the user is unable to open links via PDF files

  Development fix: the fix will be applied to Quantal via pocket copy of
  this SRU.

  Stable fix: this was fixed in r2039 by adding the following to 
/etc/apparmor.d/abstractions/ubuntu-helpers:
# While the chromium and chrome sandboxes are setuid root, they only link
# in limited libraries so glibc's secure execution should be enough to not
# require the santized_helper (ie, LD_PRELOAD will only use standard system
# paths (man ld.so)).
/usr/lib/chromium-browser/chromium-browser-sandbox PUxr,
/opt/google/chrome/chrome-sandbox PUxr,
/opt/google/chrome/google-chrome Pixr,
/opt/google/chrome/chrome Pixr,
/opt/google/chrome/lib*.so{,.*} m,

  TEST CASE:
  1. Install chromium-browser and/or Google Chrome

  2. Launch chromium-browser (or Chrome) and set it as the default web
  browser

  3. Open a PDF with a link in it (attached) in evince and click on the
  link.

  At this point, chromium-browser (or Chrome) should open to the link
  specified. Without the patch, it does not open and there are AppArmor
  denials in /var/log/kern.log.

  Regression potential: the regression potential is considered low.
  Launching chromium-browser and Chrome via evince is currently broken,
  so there is no regression potential there, however ubuntu-helpers is
  included by the (disable by default) firefox profile so a mistake in
  the added policy could prevent firefox policy from loading.

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

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

[Touch-packages] [Bug 1668813] Please test proposed package

[Steve Langasek]

Hello Jay, or anyone else affected,

Accepted iproute2 into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/4.3.0-1ubuntu3.16.10.1 in
a few hours, and then in the -proposed repository.

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

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

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

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

Title:
  The tc man page references tc-index man page but tc-index man page
  does not exist

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  Fix Committed
Status in iproute2 source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

   * The man pages for tc make reference to a non-existent tc-index man
  page. Purely a typo that should have been tc-tcindex.

   *  Purely a documentation fix, but nice to fix for an LTS release
  that has many years left to it.

  
  [Test Case]

   * To see this issue, fire up a 16,04 image (I did so via lxd) and
  type:

 root@xi386# man tc | grep tc-index
   Filter packets based on traffic control index. See 
tc-index(8).

  , HOWEVER:

 root@xi386:~# man tc-index
 No manual entry for tc-index

  
  * on a fixed system you should only see refereces to tc-tcindex, not tc-index:

 root@x1:~# man tc | grep tc-index
 root@x1:~# man tc | grep tc-tcindex
   Filter packets based on traffic control index. See 
tc-tcindex(8).
red(8), tc-route(8), tc-sfb(8), tc-sfq(8), tc-stab(8), tc-tbf(8), 
tc-tcindex(8), tc-u32(8),


  
  [Regression Potential] 

   * This is only a change to man pages, so any regression would be non-
  functional, but this fix is trivial to fix and verify, and the fix is
  exactly from the upstream.

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

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

[Touch-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Jeremy Bicha]

** Tags added: gnome-1710 wayland

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions

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

[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist

[Steve Langasek]

Hello Jay, or anyone else affected,

Accepted iproute2 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/4.3.0-1ubuntu3.16.04.1 in
a few hours, and then in the -proposed repository.

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

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

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

** Changed in: iproute2 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: iproute2 (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  The tc man page references tc-index man page but tc-index man page
  does not exist

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  Fix Committed
Status in iproute2 source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

   * The man pages for tc make reference to a non-existent tc-index man
  page. Purely a typo that should have been tc-tcindex.

   *  Purely a documentation fix, but nice to fix for an LTS release
  that has many years left to it.

  
  [Test Case]

   * To see this issue, fire up a 16,04 image (I did so via lxd) and
  type:

 root@xi386# man tc | grep tc-index
   Filter packets based on traffic control index. See 
tc-index(8).

  , HOWEVER:

 root@xi386:~# man tc-index
 No manual entry for tc-index

  
  * on a fixed system you should only see refereces to tc-tcindex, not tc-index:

 root@x1:~# man tc | grep tc-index
 root@x1:~# man tc | grep tc-tcindex
   Filter packets based on traffic control index. See 
tc-tcindex(8).
red(8), tc-route(8), tc-sfb(8), tc-sfq(8), tc-stab(8), tc-tbf(8), 
tc-tcindex(8), tc-u32(8),


  
  [Regression Potential] 

   * This is only a change to man pages, so any regression would be non-
  functional, but this fix is trivial to fix and verify, and the fix is
  exactly from the upstream.

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

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

[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Ubuntu Foundations Team Bug Bot]

The attachment "0001-ITS-8648-add-back-mutex-for-sasl_client_init.patch"
seems to be a patch.  If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Segmentation fault on a slave slapd (sync replication with kerberos
  authentication)

Status in openldap package in Ubuntu:
  New

Bug description:
  I have a slapd problem on a freshly installed 16.04 machine:

  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]

  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not 
occuring. 

  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1

  GDB debug:

  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $

buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)

  Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7f2e95b79700 (LWP 42141)]
  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2

  
  (gdb) thr apply all bt

  Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 5 (Thread 0x7f2e95378700 (LWP 42142)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)):
  #0  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #1  0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #2  0x7f2ea5303d69 in sasl_client_init () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #3  0x7f2ea594da6c in ldap_int_sasl_init () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #4  0x7f2ea594db2c in ldap_int_sasl_open () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #5  0x7f2ea594e2d4 in ldap_int_sasl_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #6  0x7f2ea5951828 in ldap_sasl_interactive_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #7  0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #8  0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, 
sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063
  #9  0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) 
at ../../../../servers/slapd/syncrepl.c:618
  #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at 
../../../../servers/slapd/syncrepl.c:1548
  #11 0x7f2ea59463a2 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at 
pthread_create.c:333
  #13 0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)):
  ---Type  to continue, or q  to quit---
  #0  

[Touch-packages] [Bug 1291458] Re: Volume buttons change ringtone volume when screen is off

[Matthew Paul Thomas]

** No longer affects: ubuntu-ux

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

Title:
  Volume buttons change ringtone volume when screen is off

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  This is a rather bigger topic for user experience design, but one
  thing that should at least happen asap is volume buttons should be
  disabled when screen is off, otherwise your you-thought-silenced-phone
  suddenly blares a ring tone.

  Steps to repro:
  * suspend your phone
  * press volume buttons

  Expected result:
  * nothing happens

  Current result:
  * volume changes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140306-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: armhf
  Date: Wed Mar 12 13:14:37 2014
  InstallationDate: Installed on 2014-03-12 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140312)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

  -

  : "When the screen is
  off, to minimize accidental volume changes, the keys should have
  effect only if any audio is currently playing, and they should not
  turn on the screen."

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

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

[Touch-packages] [Bug 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot

[Matthew Paul Thomas]

** No longer affects: ubuntu-ux

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

Title:
  Hot-swapped SIMs should be detected and prompt user to reboot

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.

  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their
  device.

  : ‘If you
  insert a new SIM, a “Changing SIM” dialog should appear with the text
  “To use this new SIM, we need to restart.” and buttons “Later” and
  “Restart Now”.’

  Summary of required work:
   - enabling ofono hotswap support through environment variable
   - adding the modal dialog to unity8 side
   - modify i-network to detect the hotswapping and trickering
     the dialog from unity8

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

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

[Touch-packages] [Bug 1541588] Re: [System Settings] Changes needed for the UI on a tablet device

[Matthew Paul Thomas]

** No longer affects: ubuntu-ux

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

Title:
  [System Settings] Changes needed for the UI on a tablet device

Status in Canonical System Image:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  Note for design: can we simply avoid referring to the/this phone as in
  most uses its not necessary for clarity, and then the same text can
  always apply..

  Main panel:
  Hide Cellular
  Hide Hotspot
  Hide Phone
  About this phone -> About this device or just About
  Reset phone -> Reset device or just Reset

  Background
  Ensure default for images is landscape

  Sound:
  Hide Ringer, Phone Calls and Messages sections

  Security and Privacy
  Hide SIM PIN
  Locking and unlocking > Lock security "Unlock the phone using" --> "Unlock 
the device using"
  Locking and unlocking > Lock when idle  "Lock the phone when..." --> "Lock 
the device when ..."
  "Phone won't lock..." --> Device won't lock ..."

  About this device
  Hide IMEI
  Developer mode >  "this phone" --> "this device"

  A minor point but what happens when we search in settings for hidden
  stuff

  
  
  Note from design:

  - The text in the UI should never refer to "Phone", "Tablet" or
  "Desktop".  Instead the word "Device" should be used.

  - e.g. "About This Computer" or "About This Phone" is incorrect. This
  wording should be changed to "About this device" in both the indicator
  and System Settings to be convergence friendly.

  - This change applies to all device references in the UI.

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

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

[Touch-packages] [Bug 1651500] Re: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all

[madbiologist]

The fix for this issue will be in the 4.12 kernel. Ubuntu 17.10 "Artful
Aardvark" is scheduled for release on 19th October 2017 and will be
based on a 4.12 or later kernel. If you want to try the 4.12 kernel on
your Ubuntu 16.04.1 LTS "Xenial Xerus" installation, when the 4.12
kernel is released you can get it from the mainline kernel PPA page at
http://kernel.ubuntu.com/~kernel-ppa/mainline/ and instructions on how
to install and uninstall it are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds

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

Title:
  [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  1. Release of ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2. version of the package
  AlsaMixer v1.1.0

  
  3. I expect to hear sound from speaker

  4. I can not any sound from speaker

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hamda  1627 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec 20 22:51:08 2016
  InstallationDate: Installed on 2016-12-15 (5 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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:  hamda  1627 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X441SA.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X441SA
  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.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X441SA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1687200] Re: [X441SA, Realtek ALC3236, Speaker, Internal] Playback problem No Sound on internal Speaker, But Normal with Headphones Jack

[madbiologist]

The fix for this issue will be in the 4.12 kernel. Ubuntu 17.10 "Artful
Aardvark" is scheduled for release on 19th October 2017 and will be
based on a 4.12 or later kernel. If you want to try the 4.12 kernel on
your Ubuntu 17.04 "Zesty Zapus" installation, when the 4.12 kernel is
released you can get it from the mainline kernel PPA page at
http://kernel.ubuntu.com/~kernel-ppa/mainline/ and instructions on how
to install and uninstall it are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds

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

Title:
  [X441SA, Realtek ALC3236, Speaker, Internal] Playback problem No Sound
  on internal Speaker, But Normal with Headphones Jack

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  how to Patch This https://patchwork.kernel.org/patch/9596699/ ?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1545 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 29 21:20:53 2017
  InstallationDate: Installed on 2017-04-23 (6 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: Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [X441SA, Realtek ALC3236, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to zesty on 2017-04-29 (0 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X441SA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X441SA
  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.:bvrX441SA.300:bd06/13/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X441SA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-04-25T03:57:03.973122

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

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

[Akli LE COQ]

Thanks Andrei.

However, I can't run the script. I get the following on the terminal :

akli@asus:~$ cd /home/akli/
akli@asus:~$ sudo chmod u+x e200ha_with_sound.sh
[sudo] Mot de passe de akli : 
akli@asus:~$ sudo ./e200ha_with_sound.sh
./e200ha_with_sound.sh: 8: ./e200ha_with_sound.sh: Syntax error: newline 
unexpected
akli@asus:~$ 

I read and followed the github instructions. Did I miss something to run
the script ?

Thanks for your help.

-- 
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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

[Yevheniy]

It is still present in Kubuntu 17.04

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

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

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

Bug description:
  [Triage Notes]

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

  [Original Description]

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

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

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

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

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

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

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

[Touch-packages] [Bug 1564252] Re: [HDA-Intel - HDA Intel PCH, recording] No sound from external microphone on headset

[madbiologist]

The fix for this issue will be in the 4.12 kernel. Ubuntu 17.10 "Artful
Aardvark" is scheduled for release on 19th October 2017 and will be
based on a 4.12 or later kernel. If you want to try the 4.12 kernel on
your Ubuntu 16.04 "Xenial Xerus" installation, when the 4.12 kernel is
released you can get it from the mainline kernel PPA page at
http://kernel.ubuntu.com/~kernel-ppa/mainline/ and instructions on how
to install and uninstall it are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds

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

Title:
  [HDA-Intel - HDA Intel PCH, recording] No sound from external
  microphone on headset

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  No sound from external microphone on headset. Work well in windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2273 F pulseaudio
   /dev/snd/pcmC1D0p:   ubuntu 2273 F...m pulseaudio
   /dev/snd/controlC1:  ubuntu 2273 F pulseaudio
  CasperVersion: 1.368
  CurrentDesktop: Unity
  Date: Thu Mar 31 06:18:30 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2273 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2273 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551JM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04

[Dimitri John Ledkov]

May 05 10:45:13 s1lp15 sshd[138567]: fatal: ssh_sandbox_violation:
unexpected system call (arch:0x8016,syscall:201 @ 0x3ffb853fb32)
[preauth]

Syscall 201 is
{ "geteuid", 201 },
from seccomp sources.

It seems like more syscalls are used, when encryption enabled, at least
on Ubuntu, when hardware accelerated crypto is enabled.

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Zesty:
  Fix Committed
Status in openssh source package in Artful:
  Triaged

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk
  debug1: Host '10.245.208.7' is known and matches the ECDSA host key.
  debug1: Found key in /home/fheimes/.ssh/known_hosts:87
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_EXT_INFO received

[Touch-packages] [Bug 1685399] Re: [2.2] MAAS should delete cached apt lists before running apt update

[Scott Moser]

I've talked about this with Robie Basak before.
For cloud-images building, it seems like it makes sense to clear out apt cache 
for updates and security.  In the best case scenario, those files are up to 
date and apt wont re-download.  That lasts only until the next SRU or security 
update, so it is not a long term win.

So it seems to make good sense to just clean those out, leaving only release 
files.
That will fix this problem for all stable releases where the release pocket is 
frozen.  The problem will still exist during the development cycle of a 
release, but that seems much less impact.


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

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

Title:
  [2.2] MAAS should delete cached apt lists before running apt update

Status in APT:
  New
Status in cloud-images:
  New
Status in MAAS:
  Won't Fix
Status in apt package in Ubuntu:
  New

Bug description:
  I have a local Ubuntu mirror that sometimes lags slightly behind the
  official mirror.

  Thus, if I commission a MAAS node while the local mirror is lagging
  behind the images synced to MAAS (which are expecting the current
  packages), "apt-get update" does not overwrite the local apt lists,
  prints errors about hash mismatches, and later may fail to download
  packages which are more up to date in the main archive than the local
  mirror.

  There is a way to prevent this issue: the first thing we should always
  do, before performing any actions with 'apt', is:

  rm -rf /var/cache/apt/lists/*
  apt-get update

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

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

[Touch-packages] [Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc

[Vance Morris]

Forcing a reload of the LPAR brings the system back online with juju,
lxd, and df happy again.

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

Title:
   Too many levels of symbolic links /proc/sys/fs/binfmt_misc

Status in binfmt-support package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  At first I thought this was an LXD issue, but it turns out the issue
  is in systemd

  https://github.com/lxc/lxd/issues/1727#issuecomment-194416558

  ls -l  /proc/sys/fs/binfmt_misc  fails with error:

  Too many levels of symbolic links

  
  I restarted binfmt manually by running:

  sudo /usr/sbin/update-binfmts --disable
  sudo /usr/sbin/update-binfmts --enable

  I think using systemd to do this would have also worked:

  sudo service binfmt-support restart

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

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

[Touch-packages] [Bug 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04

[Dimitri John Ledkov]

May 05 10:45:13 s1lp15 sshd[138567]: debug3: send packet: type 52 [preauth]
May 05 10:45:13 s1lp15 sshd[138567]: debug1: Enabling compression at level 6. 
[preauth]
May 05 10:45:13 s1lp15 sshd[138567]: debug3: mm_request_send entering: type 26 
[preauth]
May 05 10:45:13 s1lp15 sshd[138567]: debug3: mm_send_keystate: Finished sending 
state [preauth]
May 05 10:45:13 s1lp15 sshd[138567]: fatal: ssh_sandbox_violation: unexpected 
system call (arch:0x8016,syscall:201 @ 0x3ffb853fb32) [preauth]
May 05 10:45:13 s1lp15 sshd[138567]: debug1: monitor_read_log: child log fd 
closed
May 05 10:45:13 s1lp15 sshd[138567]: fatal: privsep_preauth: preauth child 
exited with status 1
May 05 10:45:13 s1lp15 sshd[138567]: debug1: do_cleanup
May 05 10:45:13 s1lp15 sshd[138567]: debug3: PAM: sshpam_thread_cleanup entering

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Zesty:
  Fix Committed
Status in openssh source package in Artful:
  Triaged

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  

[Touch-packages] [Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc

[Vance Morris]

2c - just hit this myself on xenail s390x with a soaking openstack-on-
lxd installation.

masking proc-sys-fs-binfmt_misc.automount seemed to be a bad idea...
systemd is in a bad state..

ubuntu@zs93kvi:~$ systemctl -a | grep binfmt
  proc-sys-fs-binfmt_misc.automount 
loadedactive running  Arbitrary Executable File 
Formats File System Automount Point
  proc-sys-fs-binfmt_misc.mount 
loadedinactive   dead Arbitrary Executable File 
Formats File System
  systemd-binfmt.service
loadedinactive   dead Set Up Additional Binary 
Formats
ubuntu@zs93kvi:~$ sudo systemctl mask proc-sys-fs-binfmt_misc.automount
Created symlink from /etc/systemd/system/proc-sys-fs-binfmt_misc.automount to 
/dev/null.
ubuntu@zs93kvi:~$ 
Broadcast message from systemd-journald@zs93kvi (Fri 2017-05-05 10:25:46 EDT):

systemd[1]: Caught , dumped core as pid 23484.


Broadcast message from systemd-journald@zs93kvi (Fri 2017-05-05 10:25:46 EDT):

systemd[1]: Freezing execution.

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

Title:
   Too many levels of symbolic links /proc/sys/fs/binfmt_misc

Status in binfmt-support package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  At first I thought this was an LXD issue, but it turns out the issue
  is in systemd

  https://github.com/lxc/lxd/issues/1727#issuecomment-194416558

  ls -l  /proc/sys/fs/binfmt_misc  fails with error:

  Too many levels of symbolic links

  
  I restarted binfmt manually by running:

  sudo /usr/sbin/update-binfmts --disable
  sudo /usr/sbin/update-binfmts --enable

  I think using systemd to do this would have also worked:

  sudo service binfmt-support restart

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

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

[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Ryan Tandy]

Thanks for opening the new bug.

I have a patch under review right now for a suspiciously similar issue.

Are you able to build and test a patched package, and see if it fixes 
your problem? If you need help modifying the package, I can upload it to 
a PPA for you later on.


** Changed in: openldap (Ubuntu)
 Assignee: (unassigned) => Ryan Tandy (rtandy)

** Patch added: "0001-ITS-8648-add-back-mutex-for-sasl_client_init.patch"
   
https://bugs.launchpad.net/bugs/1688575/+attachment/4872308/+files/0001-ITS-8648-add-back-mutex-for-sasl_client_init.patch

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

Title:
  Segmentation fault on a slave slapd (sync replication with kerberos
  authentication)

Status in openldap package in Ubuntu:
  New

Bug description:
  I have a slapd problem on a freshly installed 16.04 machine:

  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]

  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not 
occuring. 

  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1

  GDB debug:

  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $

buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)

  Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7f2e95b79700 (LWP 42141)]
  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2

  
  (gdb) thr apply all bt

  Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 5 (Thread 0x7f2e95378700 (LWP 42142)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)):
  #0  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #1  0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #2  0x7f2ea5303d69 in sasl_client_init () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #3  0x7f2ea594da6c in ldap_int_sasl_init () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #4  0x7f2ea594db2c in ldap_int_sasl_open () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #5  0x7f2ea594e2d4 in ldap_int_sasl_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #6  0x7f2ea5951828 in ldap_sasl_interactive_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #7  0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #8  0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, 
sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063
  #9  0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) 
at ../../../../servers/slapd/syncrepl.c:618
  #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at 
../../../../servers/slapd/syncrepl.c:1548
  #11 0x7f2ea59463a2 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at 
pthread_create.c:333
  #13 0x7f2ea45b282d in 

[Touch-packages] [Bug 1649097] Re: any source package signature is not valid

[Julian Andres Klode]

We actually fixed this in 1.4~beta3 (zesty, artful):

apt (1.4~beta3) unstable; urgency=medium

  [ David Kalnischkies ]
  * default to --no-check for dpkg-source call (Closes: 724744)


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

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

Title:
  any source package signature is not valid

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  In short:

  The GPG key 105BE7F7, with that 'linux' source package is signed,
  revoked on 08/16/16 (4 months ago!)


  How to reproduce:

  $ apt-get source linux-image-$(uname -r)
  ...
  Picking 'linux' as source package instead of 'linux-image-4.4.0-53-generic'
  ...
  Get:2 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main linux 
4.4.0-53.74 (tar) [133 MB]
  ...
  gpgv: Signature made Пт 02 дек 2016 18:32:18 MSK using RSA key ID 105BE7F7
  gpgv: Can't check signature: public key not found
  dpkg-source: warning: failed to verify signature on ./linux_4.4.0-53.74.dsc
  ...

  ### if you add this key:

  $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 105BE7F7
  $ apt-key list
  ...
  pub   4096R/105BE7F7 2011-09-06
  uid  Brad Figg 
  sub   4096R/F336E4D5 2011-09-06

  pub   4096R/105BE7F7 2014-06-16 [revoked: 2016-08-16]
  uid  Brad Figg 

  ### THE KEY IS REVOKED 4 MONTHS AGO!

  ### Additional info:
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ### My unmodified /etc/apt/sources.list in attachment.
  ### Note, /etc/apt/sources.list.d/ directory is empty.

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

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

[Otto]

Update to post #17...
The fix unfortunately did not fix all DNS problems. nslookup and dig can 
resolve local hosts, BUT ping and ssh both report 'Name or Service not known'. 
Looks like the HOSTS is still required.

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

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 1688034] Re: 1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

[Brian Candler]

I guess this also makes 1.8.16-0ubuntu1.3 a "security" update, since
sudo+sssd now enforces policy which it should have done before, but
didn't.

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

Title:
  1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

Status in sudo package in Ubuntu:
  New

Bug description:
  ubuntu 16.04, enrolled with freeipa-client to FreeIPA 4.4.0 (under
  CentOS 7)

  With sudo 1.8.16-0ubuntu1, everything is fine:

  brian.candler@api-dev:~$ sudo -s
  [sudo] password for brian.candler:
  root@api-dev:~#

  After update to 1.8.16-0ubuntu1.3, it no longer works:

  brian.candler@api-dev:~$ sudo -k
  brian.candler@api-dev:~$ sudo -s
  [sudo] password for brian.candler:
  brian.candler is not allowed to run sudo on api-dev.int.example.com.  This 
incident will be reported.

  This is repeatable: downgrade sudo and it works again.

  Seems very likely related to change made as part of #1607666, which
  changes how sudo policies are matched, but has unexpected regression.

  --- Additional info ---

  The sudo policy in IPA is extremely simple. It has a single rule,
  which says:

  - applies to users in groups "system_administrators" and 
"security_administrators"
  - applies to any host
  - applies to any command

  In LDAP under ou=sudoers tree, the groups are flattened out:

  # system administrators on all hosts, sudoers, ipa.example.com
  dn: cn=system administrators on all hosts,ou=sudoers,dc=ipa,dc=example,dc=com
  sudoRunAsGroup: ALL
  objectClass: sudoRole
  objectClass: top
  sudoUser: brian.candler
  sudoUser: ...
  sudoUser: ... list more users
  sudoUser: ...
  sudoRunAsUser: ALL
  sudoCommand: ALL
  sudoHost: ALL
  cn: system administrators on all hosts

  Under cn=sudorules,cn=sudo it refers to the groups rather than the
  individuals:

  # 59ffb10a-9c61-11e6-b5b8-00163efd5284, sudorules, sudo, ipa.example.com
  dn: 
ipaUniqueID=59ffb10a-9c61-11e6-b5b8-00163efd5284,cn=sudorules,cn=sudo,dc=ipa,dc=example,dc=com
  ipaSudoRunAsUserCategory: all
  ipaSudoRunAsGroupCategory: all
  description: admins have full sudo access on any host they can ssh into
  cmdCategory: all
  hostCategory: all
  memberUser: 
cn=system_administrators,cn=groups,cn=accounts,dc=ipa,dc=example,dc=com
  memberUser: 
cn=security_administrators,cn=groups,cn=accounts,dc=ipa,dc=example,dc=com
  objectClass: ipasudorule
  objectClass: ipaassociation
  ipaEnabledFlag: TRUE
  cn: system administrators on all hosts
  ipaUniqueID: 59ffb10a-9c61-11e6-b5b8-00163efd5284

  I have no workaround other than downgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.4.0-1016.25-aws 4.4.59
  Uname: Linux 4.4.0-1016-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed May  3 16:01:23 2017
  Ec2AMI: ami-a8d2d7ce
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/90-cloud-init-users: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

[Touch-packages] [Bug 1688575] [NEW] Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Suho Meso]

Public bug reported:

I have a slapd problem on a freshly installed 16.04 machine:

slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]

I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl 
for one of them (doesn't matter which one) the problem is not occuring. 

Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
slapd 2.4.42+dfsg-2ubuntu3.1
libsasl2-2:amd64 2.1.26.dfsg1-14build1
libsasl2-modules:amd64 2.1.26.dfsg1-14build1
libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1

GDB debug:

Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap 
-g openldap -f /etc/ldap/slapd.conf -d 256
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $

buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
590c82ab slapd starting
[New Thread 0x7f2e96b7b700 (LWP 42139)]
[New Thread 0x7f2e9637a700 (LWP 42140)]
[New Thread 0x7f2e95b79700 (LWP 42141)]
[New Thread 0x7f2e95378700 (LWP 42142)]
[New Thread 0x7f2e94b77700 (LWP 42143)]
590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)

Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f2e95b79700 (LWP 42141)]
0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2


(gdb) thr apply all bt

Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
#2  0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at 
pthread_create.c:333
#3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f2e95378700 (LWP 42142)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
#2  0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at 
pthread_create.c:333
#3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)):
#0  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
#1  0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2
#2  0x7f2ea5303d69 in sasl_client_init () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
#3  0x7f2ea594da6c in ldap_int_sasl_init () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
#4  0x7f2ea594db2c in ldap_int_sasl_open () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
#5  0x7f2ea594e2d4 in ldap_int_sasl_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
#6  0x7f2ea5951828 in ldap_sasl_interactive_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
#7  0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
#8  0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, 
sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063
#9  0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) at 
../../../../servers/slapd/syncrepl.c:618
#10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at 
../../../../servers/slapd/syncrepl.c:1548
#11 0x7f2ea59463a2 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
#12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at 
pthread_create.c:333
#13 0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)):
---Type  to continue, or q  to quit---
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
#2  0x7f2ea487c6ba in start_thread (arg=0x7f2e9637a700) at 
pthread_create.c:333
#3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f2e96b7b700 (LWP 42139)):
#0  0x7f2ea45b2e23 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84
#1  0x561fbc55a8f0 in slapd_daemon_task (ptr=) at 
../../../../servers/slapd/daemon.c:2539
#2  0x7f2ea487c6ba in start_thread (arg=0x7f2e96b7b700) at 
pthread_create.c:333
#3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f2ea5d96740 (LWP 42138)):
#0  0x7f2ea487d98d in pthread_join 

[Touch-packages] [Bug 1643379] Re: ca-certificates in xenial still trusts CNNIC

[Marc Deslauriers]

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

** Changed in: ca-certificates (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  ca-certificates in xenial still trusts CNNIC

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  CNNIC has been distrusted by Mozilla in April 2015
  (https://blog.mozilla.org/security/2015/04/02/distrusting-new-cnnic-
  certificates/). The technical implementation involves blacklisting by
  notBefore date, which is unfortunately not replicatable by ca-
  certificates. There should be some kind of action here of pulling the
  root certificate at some point rather than continue to provide it with
  blanket trust. (And it's only one example, Startcom and Wosign are
  more recent ones.)

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

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

[Touch-packages] [Bug 1684902] Re: browser unity app crashes apparmor profile

[Marc Deslauriers]

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Invalid

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

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

Title:
  browser unity app crashes apparmor profile

Status in apparmor package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2
  amd64 (A lightweight web browser tailored for Ubuntu, based on the
  Oxide browser engine and using the Ubuntu UI components.), Shown as
  Version 0.23+16.04.20161028-0ubuntu2, if removed from the system,
  causes apparmor to read errors in the system profile and fail to start
  (apparmor).

  I discovered that (per session), you can get apparmor to correct the
  failure and start, but as soon as you reboot, the system returns to
  the default profile set and fails to start apparmor. As far as I can
  tell, it does not indicate that the failure was caused by the browser
  uninstall, just that it failed to start for some reason.

  I tried to send this via apport, but it will not auto-locate the
  program, and since it is integrated with unity and oxide, I think it
  "sees" the program as a required OS file.

  Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) 
updated grub file, (4) reboot
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-04-12 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Package: webbrowser-app
  PackageArchitecture: amd64
  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.8.0-46-generic 
root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Syslog:
   Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is 
enabled
   Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is 
enabled
  Tags:  xenial
  Uname: Linux 4.8.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Otto]

In my case after a 17.04 installation I needed a HOSTS file in order to
resolve local hosts. After applying the fix in post #8 both local and
remote hosts were resolved by the router DNS server (as was the case in
the past).

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

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 1649097] Re: any source package signature is not valid

[Marc Deslauriers]

I am closing this bug report as there is no actionable item.

As mentioned above, source packages are verified using the Ubuntu
archive key, not by using the developer's signature.

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

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

Title:
  any source package signature is not valid

Status in apt package in Ubuntu:
  Invalid

Bug description:
  In short:

  The GPG key 105BE7F7, with that 'linux' source package is signed,
  revoked on 08/16/16 (4 months ago!)


  How to reproduce:

  $ apt-get source linux-image-$(uname -r)
  ...
  Picking 'linux' as source package instead of 'linux-image-4.4.0-53-generic'
  ...
  Get:2 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main linux 
4.4.0-53.74 (tar) [133 MB]
  ...
  gpgv: Signature made Пт 02 дек 2016 18:32:18 MSK using RSA key ID 105BE7F7
  gpgv: Can't check signature: public key not found
  dpkg-source: warning: failed to verify signature on ./linux_4.4.0-53.74.dsc
  ...

  ### if you add this key:

  $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 105BE7F7
  $ apt-key list
  ...
  pub   4096R/105BE7F7 2011-09-06
  uid  Brad Figg 
  sub   4096R/F336E4D5 2011-09-06

  pub   4096R/105BE7F7 2014-06-16 [revoked: 2016-08-16]
  uid  Brad Figg 

  ### THE KEY IS REVOKED 4 MONTHS AGO!

  ### Additional info:
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ### My unmodified /etc/apt/sources.list in attachment.
  ### Note, /etc/apt/sources.list.d/ directory is empty.

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

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

[Touch-packages] [Bug 1650818] Re: Clipboard contents accessible outside user session potentially giving the attacker root access

[Marc Deslauriers]

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

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

Title:
  Clipboard contents accessible outside user session potentially giving
  the attacker root access

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Device: mako
  Channel: rc-proposed

  Clipboard contents from the last session is accessible outside user
  session potentially giving the attacker root access when having
  physical access if the user had his password in it. That way it can
  also give the attacker access to user's other account passwords and
  other more or less relevant information that can be on the clipboard
  at that time.

  Context menu with working "Select All" and "Paste" menu items can be
  invoked on login screen's "Passphrase" and "Passcode" fields.

  Context menu with working "Select All" and "Paste" menu items can be
  invoked on "Emergency Calls" number field.

  If the user locks the device without manually clearing the clipboard,
  contents of his session's clipboard can be accessed outside of his
  session by simply executing a "Paste" action on the above mentioned
  fields.

  Potential attacker could then get the root access if the user had his
  root passphrase/passcode stored in the clipboard or just view the
  clipboard's contents by executing paste in the "Emergency Call".

  This issue is especially impacting the users who use password managers
  or store their passwords in a file.

  Videos demonstrating the vulnerability in action (too big for the
  attachment, sry):

  https://youtu.be/fExDXYe3EJs

  https://youtu.be/1W8lQWUPwBE

  STEPS TO REPRODUCE:

  1] Login into the user session on your device.
  2] Focus any textfield.
  3] Write your Passcode/Passphrase, select it and copy it.
  4] From the System indicator panel click on "Lock" to lock your device or 
simply use the lock button.
  5] Go to the "Emergency Call" and invoke the context menu onto the input 
field.
  6] Click the "Paste" menu item to view your "Passcode".
  7] Go to the login screen an invoke the context menu onto the input field.
  8] Click the "Paste" menu item to login into your account without ever 
writing your password.
  9] Go to terminal and paste your password into the modal window's input field 
and click "OK"
  10] When in terminal, type "sudo -s" and click Enter.
  11] When prompted, paste the clipboard contents into terminal and click enter 
to get the root access to the device.

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

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

[Touch-packages] [Bug 1662513] Re: Update to 9.21 in Trusty

[Marc Deslauriers]

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

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

Title:
  Update to 9.21 in Trusty

Status in libav package in Ubuntu:
  Confirmed

Bug description:
  version 9.21:
  - mpeg12: move setting first_field to mpeg_field_start() (libav/999)
  - mpeg12: avoid signed overflow in bitrate calculation (libav/981)
  - mpegvideo_parser: avoid signed overflow in bitrate calculation (libav/981)
  - avformat/output-example: Declare link dependency on libswscale in the 
Makefile
  - build: output-example: Add avutil to ELIBS in link command

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

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

[Touch-packages] [Bug 1679989] Re: CVE-2016-10165: heap OOB read parsing crafted ICC profile

[Marc Deslauriers]

** Also affects: lcms2 (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

** Also affects: lcms2 (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: lcms2 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: lcms2 (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  CVE-2016-10165: heap OOB read parsing crafted ICC profile

Status in lcms2 package in Ubuntu:
  Confirmed
Status in lcms2 source package in Precise:
  Confirmed
Status in lcms2 source package in Trusty:
  Confirmed
Status in lcms2 source package in Xenial:
  Confirmed
Status in lcms2 source package in Yakkety:
  Confirmed
Status in lcms2 source package in Zesty:
  Confirmed
Status in lcms2 source package in Artful:
  Confirmed
Status in lcms2 package in Debian:
  Fix Released

Bug description:
  The Type_MLU_Read function in cmstypes.c in Little CMS (aka lcms2)
  allows remote attackers to obtain sensitive information or cause a
  denial of service via an image with a crafted ICC profile, which
  triggers an out-of-bounds heap read.

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

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

[Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

[Andreas Hasenack]

** Description changed:

  This is fixed in krb5 1.15-2 in artful
  
  Upstream bug : http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554
  Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  Debian patch in 1.15-2 in artful: 
0013-Fix-udp_preference_limit-with-SRV-records.patch
  
  TL;DR
- kinit does not respect udp_preference_limit and always uses TCP to talk to 
the KDC when using the DNS SRV records to locate the service and these records 
show udp and tcp entries.
+ kinit does not respect udp_preference_limit and always uses TCP to talk to 
the KDC when using the DNS SRV records to locate the service and these records 
show both udp and tcp entries.
  
  Steps to reproduce on zesty, with all services on one machine for
  simplicity (I suggest to use LXD):
  
  a) install the packages from zesty (not the proposed ones yet):
  $ sudo apt install krb5-kdc krb5-admin-server bind9
  
  When prompted for the realm, choose EXAMPLE.COM
  When prompted for the KDC and Admin services server address, use the IP of 
your test machine/container (not localhost or 127.0.0.1)
  The KDC will fail to start because there is no realm yet, that's not relevant 
for this bug.
  
  b) Edit /etc/krb5.conf and make the following changes:
  - remove the "default_realm" line from the [libdefaults] section
  - remove the EXAMPLE.COM realm block from the [realms] section
  - add "dns_lookup_realm = true" to the [libdefaults] section
  - add "dns_lookup_kdc = true" to the [libdefaults] section
  - add "udp_preference_limit = 1" to the [libdefaults] section
  
  c) Edit /etc/bind/named.conf.local and add this zone block (for simplicity, 
we are skipping the reverse zone):
  zone "example.com" {
  type master;
  file "/etc/bind/db.example.com";
  };
  
  d) Create /etc/bind/db.example.com with this content:
  $TTL604800
  @   IN  SOA example.com. ubuntu.example.com. (
    1 ; Serial
   604800 ; Refresh
    86400 ; Retry
  2419200 ; Expire
   604800 )   ; Negative Cache TTL
  ;
  @   IN  NS  zesty-bug1683237.example.com.
  zesty-bug1683237IN  A   10.0.100.249
  _kerberos   TXT "EXAMPLE.COM"
  _kerberos._udp  SRV 0 0 88 zesty-bug1683237
  _kerberos._tcp  SRV 0 0 88 zesty-bug1683237
  _kerberos-master._udp   SRV 0 0 88 zesty-bug1683237
  _kerberos-master._tcp   SRV 0 0 88 zesty-bug1683237
  _kerberos-adm._tcp  SRV 0 0 749 zesty-bug1683237
  _kpasswd._udp   SRV 0 0 464 zesty-bug1683237
  
  Use the real IP of your test machine/container where I used
  "10.0.100.249". You can also choose another hostname if you want, just
  be consistent across the board. I chose "zesty-bug1683237".
  
  e) Restart bind
  $ sudo service bind9 restart
  
  f) Do a few quick DNS tests:
  $ dig +short @10.0.100.249 zesty-bug1683237.example.com
  10.0.100.249
  $ dig +short @10.0.100.249 -t TXT _kerberos.example.com
  "EXAMPLE.COM"
  $ dig +short @10.0.100.249 -t SRV _kerberos._udp.example.com
  0 0 88 zesty-bug1683237.example.com.
  $ dig +short @10.0.100.249 -t SRV _kerberos._tcp.example.com
  0 0 88 zesty-bug1683237.example.com.
  
  g) Edit /etc/resolv.conf, ignoring the warning since we are not going to 
reboot or change network interfaces:
  nameserver 10.0.100.249 # USE YOUR IP HERE
  search example.com
  
  h) Create the EXAMPLE.COM kerberos realm:
  $ sudo krb5_newrealm
  When prompted for a password, use whatever you like. If you get an error 
about no default realm, then your TXT record in DNS is not working. Retrace 
your DNS configuration steps.
  
  i) Start the kerberos services:
  $ sudo service krb5-kdc start
  sudo service krb5-admin-server start
  
  j) Create a principal and test it:
  $ sudo kadmin.local addprinc -pw ubuntu ubuntu
  $ kinit ubuntu
  Password for ubu...@example.com:
  $ klist
  (...)
  05/05/2017 13:10:01  05/05/2017 23:10:01  krbtgt/example@example.com
  (...)
  
  Now we are ready to test the bug.
  
  Given that we have udp_preference_limit = 1 in /etc/krb5.conf, kinit
  should use TCP instead of UDP. Let's check:
  
  $ KRB5_TRACE=/dev/stderr kinit
  [7609] 1493989890.568980: Getting initial credentials for ubu...@example.com
  [7609] 1493989890.569904: Sending request (172 bytes) to EXAMPLE.COM
  [7609] 1493989890.571991: Resolving hostname zesty-bug1683237.example.com.
  [7609] 1493989890.576853: Sending initial UDP request to dgram 10.0.100.249:88
  (...)
  
  Uh oh, it's using UDP!
  
  With the fixed packages, the story is different:
  $ KRB5_TRACE=/dev/stderr kinit
  [14287] 1493990160.760430: Getting initial credentials for ubu...@example.com
  [14287] 1493990160.761590: Sending request (172 bytes) to EXAMPLE.COM
  [14287] 1493990160.763783: Resolving hostname zesty-bug1683237.example.com.
  [14287] 1493990160.767803: Resolving hostname zesty-bug1683237.example.com.
  [14287] 1493990160.770588: 

[Touch-packages] [Bug 1681077] Re: ideviceinfo (libimobiledevice): GnuTLS error: Error in the pull function

[Marc Deslauriers]

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

Title:
  ideviceinfo (libimobiledevice): GnuTLS error: Error in the pull
  function

Status in Libimobiledevice:
  New
Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  Cannot connect to IPhone 5S with ifuse or ideviceinfo due to GnuTLS
  error.

  Reproducable on Ubuntu 16.04.2 LTS and Ubuntu 15.04.

  ideviceinfo 
  GnuTLS error: Error in the pull function.
  ERROR: Could not connect to lockdownd, error code -5

  As far as I know from google, the current IOS 10 release uses TLS instead of 
the insecure SSLv3.
  libimobiledevice (used by ideviceinfo) must be configured to use GnuTLS with 
TLS to successfully connect to IOS 10.
  For IOS 9 there are some (not recommended because insecure) hacks to 
re-enable SSLv3 to get it working.
  But I couldn't find any instructions how to get this working without 
compromising security.

  Other idevice tools like idevicebackup also don't work.

  Successfully using ifuse and idevicebackup for backup purposes is
  quite urgent for me to have a recent backup in case attackers could
  manage to remotely compromise or erase iphones as mentioned in the
  latest news.

  lsb_release -rd
  Description:Ubuntu 16.04.2 LTS
  Release:16.04

  
  Paket: libimobiledevice6
  Zustand: Installiert
  Automatisch installiert: ja
  Multi-Arch: same
  Version: 1.2.0+dfsg-3~ubuntu0.2
  Priorität: optional
  Bereich: libs
  Verwalter: Ubuntu Developers 
  Architektur: amd64
  Unkomprimierte Größe: 181 k
  Hängt ab von: libc6 (>= 2.15), libgcrypt20 (>= 1.6.1), libgnutls30 (>= 3.4.2),
libplist3 (>= 1.11), libtasn1-6 (>= 4.5), libusbmuxd4 (>= 
1.0.10)
  Empfiehlt: usbmuxd
  Schlägt vor: libusbmuxd-tools
  Kollidiert mit: libiphone0
  Beschädigt: libimobiledevice6:i386 (!= 1.2.0+dfsg-3~ubuntu0.2)
  Ersetzt: libimobiledevice0, libimobiledevice1, libiphone0,
   libimobiledevice6:i386 (< 1.2.0+dfsg-3~ubuntu0.2)
  Beschreibung: Bibliothek zur Kommunikation mit dem iPhone und iPod Touch.
   Die Bibliothek libimobiledevice beherrscht die nativen USB-Protokolle von
   Apple, welche von iPhone und iPod Touch verwendet werden. Im Gegensatz zu
   anderen Projekten hängt libimobiledevice nicht von der Verwendung 
irgendwelcher
   vorhandener Apple-Bibliotheken ab.
  Homepage: http://libimobiledevice.org/

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

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

[Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

[Andreas Hasenack]

** Description changed:

+ This is fixed in krb5 1.15-2 in artful
+ 
+ Upstream bug : http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554
+ Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
+ Debian patch in 1.15-2 in artful: 
0013-Fix-udp_preference_limit-with-SRV-records.patch
+ 
+ TL;DR
+ kinit does not respect udp_preference_limit and always uses TCP to talk to 
the KDC when using the DNS SRV records to locate the service and these records 
show udp and tcp entries.
+ 
+ Steps to reproduce on zesty, with all services on one machine for
+ simplicity (I suggest to use LXD):
+ 
+ a) install the packages from zesty (not the proposed ones yet):
+ $ sudo apt install krb5-kdc krb5-admin-server bind9
+ 
+ When prompted for the realm, choose EXAMPLE.COM
+ When prompted for the KDC and Admin services server address, use the IP of 
your test machine/container (not localhost or 127.0.0.1)
+ The KDC will fail to start because there is no realm yet, that's not relevant 
for this bug.
+ 
+ b) Edit /etc/krb5.conf and make the following changes:
+ - remove the "default_realm" line from the [libdefaults] section
+ - remove the EXAMPLE.COM realm block from the [realms] section
+ - add "dns_lookup_realm = true" to the [libdefaults] section
+ - add "dns_lookup_kdc = true" to the [libdefaults] section
+ - add "udp_preference_limit = 1" to the [libdefaults] section
+ 
+ c) Edit /etc/bind/named.conf.local and add this zone block (for simplicity, 
we are skipping the reverse zone):
+ zone "example.com" {
+ type master;
+ file "/etc/bind/db.example.com";
+ };
+ 
+ d) Create /etc/bind/db.example.com with this content:
+ $TTL604800
+ @   IN  SOA example.com. ubuntu.example.com. (
+   1 ; Serial
+  604800 ; Refresh
+   86400 ; Retry
+ 2419200 ; Expire
+  604800 )   ; Negative Cache TTL
+ ;
+ @   IN  NS  zesty-bug1683237.example.com.
+ zesty-bug1683237IN  A   10.0.100.249
+ _kerberos   TXT "EXAMPLE.COM"
+ _kerberos._udp  SRV 0 0 88 zesty-bug1683237
+ _kerberos._tcp  SRV 0 0 88 zesty-bug1683237
+ _kerberos-master._udp   SRV 0 0 88 zesty-bug1683237
+ _kerberos-master._tcp   SRV 0 0 88 zesty-bug1683237
+ _kerberos-adm._tcp  SRV 0 0 749 zesty-bug1683237
+ _kpasswd._udp   SRV 0 0 464 zesty-bug1683237
+ 
+ Use the real IP of your test machine/container where I used
+ "10.0.100.249". You can also choose another hostname if you want, just
+ be consistent across the board. I chose "zesty-bug1683237".
+ 
+ e) Restart bind
+ $ sudo service bind9 restart
+ 
+ f) Do a few quick DNS tests:
+ $ dig +short @10.0.100.249 zesty-bug1683237.example.com
+ 10.0.100.249
+ $ dig +short @10.0.100.249 -t TXT _kerberos.example.com
+ "EXAMPLE.COM"
+ $ dig +short @10.0.100.249 -t SRV _kerberos._udp.example.com
+ 0 0 88 zesty-bug1683237.example.com.
+ $ dig +short @10.0.100.249 -t SRV _kerberos._tcp.example.com
+ 0 0 88 zesty-bug1683237.example.com.
+ 
+ g) Edit /etc/resolv.conf, ignoring the warning since we are not going to 
reboot or change network interfaces:
+ nameserver 10.0.100.249 # USE YOUR IP HERE
+ search example.com
+ 
+ h) Create the EXAMPLE.COM kerberos realm:
+ $ sudo krb5_newrealm
+ When prompted for a password, use whatever you like. If you get an error 
about no default realm, then your TXT record in DNS is not working. Retrace 
your DNS configuration steps.
+ 
+ i) Start the kerberos services:
+ $ sudo service krb5-kdc start
+ sudo service krb5-admin-server start
+ 
+ j) Create a principal and test it:
+ $ sudo kadmin.local addprinc -pw ubuntu ubuntu
+ $ kinit ubuntu
+ Password for ubu...@example.com: 
+ $ klist
+ (...)
+ 05/05/2017 13:10:01  05/05/2017 23:10:01  krbtgt/example@example.com
+ (...)
+ 
+ 
+ Now we are ready to test the bug.
+ 
+ Give that we have udp_preference_limit = 1 in /etc/krb5.conf, kinit
+ should use TCP instead of UDP. Let's check:
+ 
+ $ KRB5_TRACE=/dev/stderr kinit
+ [7609] 1493989890.568980: Getting initial credentials for ubu...@example.com
+ [7609] 1493989890.569904: Sending request (172 bytes) to EXAMPLE.COM
+ [7609] 1493989890.571991: Resolving hostname zesty-bug1683237.example.com.
+ [7609] 1493989890.576853: Sending initial UDP request to dgram 10.0.100.249:88
+ (...)
+ 
+ Uh oh, it's using UDP!
+ 
+ With the fixed packages, the story is different:
+ $ KRB5_TRACE=/dev/stderr kinit
+ [14287] 1493990160.760430: Getting initial credentials for ubu...@example.com
+ [14287] 1493990160.761590: Sending request (172 bytes) to EXAMPLE.COM
+ [14287] 1493990160.763783: Resolving hostname zesty-bug1683237.example.com.
+ [14287] 1493990160.767803: Resolving hostname zesty-bug1683237.example.com.
+ [14287] 1493990160.770588: Initiating TCP connection to stream 10.0.100.249:88
+ [14287] 1493990160.771724: Sending TCP request to stream 10.0.100.249:88
+ (...)
+ 
+ And if udp_preference_limit is removed from 

[Touch-packages] [Bug 1684902] Re: browser unity app crashes apparmor profile

[Marc Deslauriers]

Hi Carl, it looks like you're missing the apparmor-easyprof-ubuntu
package. That package is necessary for proper operation. Could you
please reinstall it and try again?

Thanks!

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

Title:
  browser unity app crashes apparmor profile

Status in apparmor package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2
  amd64 (A lightweight web browser tailored for Ubuntu, based on the
  Oxide browser engine and using the Ubuntu UI components.), Shown as
  Version 0.23+16.04.20161028-0ubuntu2, if removed from the system,
  causes apparmor to read errors in the system profile and fail to start
  (apparmor).

  I discovered that (per session), you can get apparmor to correct the
  failure and start, but as soon as you reboot, the system returns to
  the default profile set and fails to start apparmor. As far as I can
  tell, it does not indicate that the failure was caused by the browser
  uninstall, just that it failed to start for some reason.

  I tried to send this via apport, but it will not auto-locate the
  program, and since it is integrated with unity and oxide, I think it
  "sees" the program as a required OS file.

  Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) 
updated grub file, (4) reboot
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-04-12 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Package: webbrowser-app
  PackageArchitecture: amd64
  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.8.0-46-generic 
root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Syslog:
   Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is 
enabled
   Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is 
enabled
  Tags:  xenial
  Uname: Linux 4.8.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1688034] Re: 1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

[Brian Candler]

I found out how to enable debugging for sudoers:

Debug sudo /var/log/sudo-debug all@info
Debug sudoers.so /var/log/sudoers-debug all@info

With the *new* sudo I get the following logged matching 'sssd':

May  5 12:40:06 sudo[17912] sssd/ldap sudoHost 'ALL' ... MATCH!
May  5 12:40:06 sudo[17912] sssd/ldap sudoUser '%system_administrators' ... not 
(brian.candler)
May  5 12:40:06 sudo[17912] sssd/ldap sudoUser '%security_administrators' ... 
not (brian.candler)

But with the *old* sudo I get:

May  5 12:41:48 sudo[18384] sssd/ldap sudoHost 'ALL' ... MATCH!
May  5 12:41:48 sudo[18384] sssd/ldap sudoRunAsUser 'ALL' ... MATCH!
May  5 12:41:48 sudo[18384] sssd/ldap sudoCommand 'ALL' ... MATCH!

It seems to be a behaviour change with group checking.

The 'brian.candler' user *is* a member of one of those groups in IPA;
but those groups are not posix groups so they are not visible using
(e.g.) "id"

I was able to solve the problem by adding

objectClass: posixgroup
gidNumber: 

to those group objects.  After this, the sudoers log shows:

May  5 13:11:50 sudo[19545] sssd/ldap sudoHost 'ALL' ... MATCH!
May  5 13:11:50 sudo[19545] sssd/ldap sudoUser '%system_administrators' ... not 
(brian.candler)
May  5 13:11:50 sudo[19545] sssd/ldap sudoUser '%security_administrators' ... 
MATCH! (brian.candler)
May  5 13:11:50 sudo[19545] sssd/ldap sudoRunAsUser 'ALL' ... MATCH!
May  5 13:11:50 sudo[19545] sssd/ldap sudoCommand 'ALL' ... MATCH!

So: arguably this is not a bug, but a bug fix.  Still, it would be nice
if the release notes explained the potential for regression.

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

Title:
  1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

Status in sudo package in Ubuntu:
  New

Bug description:
  ubuntu 16.04, enrolled with freeipa-client to FreeIPA 4.4.0 (under
  CentOS 7)

  With sudo 1.8.16-0ubuntu1, everything is fine:

  brian.candler@api-dev:~$ sudo -s
  [sudo] password for brian.candler:
  root@api-dev:~#

  After update to 1.8.16-0ubuntu1.3, it no longer works:

  brian.candler@api-dev:~$ sudo -k
  brian.candler@api-dev:~$ sudo -s
  [sudo] password for brian.candler:
  brian.candler is not allowed to run sudo on api-dev.int.example.com.  This 
incident will be reported.

  This is repeatable: downgrade sudo and it works again.

  Seems very likely related to change made as part of #1607666, which
  changes how sudo policies are matched, but has unexpected regression.

  --- Additional info ---

  The sudo policy in IPA is extremely simple. It has a single rule,
  which says:

  - applies to users in groups "system_administrators" and 
"security_administrators"
  - applies to any host
  - applies to any command

  In LDAP under ou=sudoers tree, the groups are flattened out:

  # system administrators on all hosts, sudoers, ipa.example.com
  dn: cn=system administrators on all hosts,ou=sudoers,dc=ipa,dc=example,dc=com
  sudoRunAsGroup: ALL
  objectClass: sudoRole
  objectClass: top
  sudoUser: brian.candler
  sudoUser: ...
  sudoUser: ... list more users
  sudoUser: ...
  sudoRunAsUser: ALL
  sudoCommand: ALL
  sudoHost: ALL
  cn: system administrators on all hosts

  Under cn=sudorules,cn=sudo it refers to the groups rather than the
  individuals:

  # 59ffb10a-9c61-11e6-b5b8-00163efd5284, sudorules, sudo, ipa.example.com
  dn: 
ipaUniqueID=59ffb10a-9c61-11e6-b5b8-00163efd5284,cn=sudorules,cn=sudo,dc=ipa,dc=example,dc=com
  ipaSudoRunAsUserCategory: all
  ipaSudoRunAsGroupCategory: all
  description: admins have full sudo access on any host they can ssh into
  cmdCategory: all
  hostCategory: all
  memberUser: 
cn=system_administrators,cn=groups,cn=accounts,dc=ipa,dc=example,dc=com
  memberUser: 
cn=security_administrators,cn=groups,cn=accounts,dc=ipa,dc=example,dc=com
  objectClass: ipasudorule
  objectClass: ipaassociation
  ipaEnabledFlag: TRUE
  cn: system administrators on all hosts
  ipaUniqueID: 59ffb10a-9c61-11e6-b5b8-00163efd5284

  I have no workaround other than downgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.4.0-1016.25-aws 4.4.59
  Uname: Linux 4.4.0-1016-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed May  3 16:01:23 2017
  Ec2AMI: ami-a8d2d7ce
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/90-cloud-init-users: parsed OK
   /etc/sudoers.d/README: parsed OK

To manage notifications about this bug go to:

[Touch-packages] [Bug 1323594] Re: vpn auto-connect works, but doesn't connect automatically when network is available.

[Marzanna]

I have this bug in freshly installed Xubuntu 17.04.
Ethernet doesn't connect automatically with VPN.

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

Title:
  vpn auto-connect works, but doesn't connect automatically when network
  is available.

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I'm having a bug in Ubuntu Trusty Tahr 14.04 LTS. The issue I'm having
  is that with a connection set to auto-connect to a PPTP-vpn, it does
  not auto-connect when (wireless)-network becomes available.

  Syslog returns this error:

   [1401130450.367538] [nm-vpn-connection.c:1374]
  get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were
  available for this request.

  However it does connect when when connecting to the particular
  connection manually. e.g. I select the wireless network in the
  network-manager.

  This bug seems related to bugs:
  #280571
  #1297849
  #1247682 
  #1298047

  The difference between my situation and the others is that vpn-
  autoconnect does work, it just doesn't work automatically.

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

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

[Touch-packages] [Bug 1687372] Re: This error are occures

[Marc Deslauriers]

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

** Information type changed from Private Security to Public

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

Title:
  This error are occures

Status in xorg package in Ubuntu:
  New

Bug description:
  plz tell me how to resolve this error

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon May  1 13:05:07 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2017-05-01 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: LENOVO 20236
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=6827b158-7150-43fb-b29b-6e56548bc52c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 78CN24WW(V2.02)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G500
  dmi.modalias: 
dmi:bvnLENOVO:bvr78CN24WW(V2.02):bd09/23/2013:svnLENOVO:pn20236:pvrLenovoG500:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG500:
  dmi.product.name: 20236
  dmi.product.version: Lenovo G500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon May  1 12:43:16 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5543 
   vendor CMO
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

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

[Jarno Suni]

Though even Software Updater could be more informative on how to free
more space on /boot: Bug #1460396

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

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

Status in initramfs-tools:
  Confirmed
Status in Software Updater:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

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

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

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

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

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

[Jarno Suni]

Michael Baker, the bug report Bug #1357093 that you referred to has been
re-reported as Bug #1675079 and Bug #1624644

If you disable automatic installation of updates, and install them by
Software Updater only, it will prevent you from installing kernel
updates, retaining the system in intact state, if there is too little
space left, and let you remove extra kernels by "sudo apt autoremove
--purge" (in 16.04-), right?

Whatever front-end is used to install kernels, be it apt, unattended-
upgrades whatnot, it should check if there is enough space for the
kernel in /boot, to prevent system from becoming broken by the
installation. It might be difficult in general, as initrd.img files size
may vary depending on dkms, linux-image-extra whatnot and there may be
backup initrd.img files generated, too.

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

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

Status in initramfs-tools:
  Confirmed
Status in Software Updater:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

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

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

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

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

[Touch-packages] [Bug 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04

[Dimitri John Ledkov]

This does not appear to work with 7.5 either

** Changed in: openssh (Ubuntu Artful)
   Status: Fix Released => Triaged

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Zesty:
  Fix Committed
Status in openssh source package in Artful:
  Triaged

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk
  debug1: Host '10.245.208.7' is known and matches the ECDSA host key.
  debug1: Found key in /home/fheimes/.ssh/known_hosts:87
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications 

[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware

[Konrad Zapałowicz]

Now I understand your use-case.

You probably could achieve similar with $ systemctl status
bluetooth.service. Also hcitool can tell if the adapter is up and
running but keep in mind that hcitool is depreciated and no longer
maintained by the upstream.

As for the man entry suggestion yes that could be something to consider
given that the default man page is quite vague nevertheless this, as
whole bluez, comes straight from the upstream.

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

Title:
  bluetoothctl systematically hangs when there is no bluetooth hardware

Status in bluez package in Ubuntu:
  New

Bug description:
  On a machine WITH bluetooth hardware, the 'bluetoothctl' command works 
correctly.
  For example, the command 'bluetoothctl < /dev/null' terminates correctly.

  On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command 
systematically hangs.
  Even the command 'bluetoothctl < /dev/null' systematically hangs.

  $ bluetoothctl &
  [1] 6208

  $ ps -l $!
  F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTYTIME CMD
  0 T  1001  6208  2525  0  80   0 -  9578 signal pts/1  0:00 bluetoothctl

  [1]+  Stopped bluetoothctl

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr  4 20:09:39 2016
  InstallationDate: Installed on 2015-07-20 (259 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterestingModules: bluetooth
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed 
root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago)
  dmi.bios.date: 06/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  hciconfig:
   
  rfkill:
   
  syslog:
   avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)...
   avril 03 15:10:45 urbah-sirius NetworkManager[986]:   Loaded device 
plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5).

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

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

[Touch-packages] [Bug 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq

[Fodder]

In the page source, the error seems to occur when there are dns-prefetch
entries on a web page, as this is the only reference to the host that
was being repeated in my log (), and with dnsmasq turned off (so it
should just use the dns servers from my ISP) cf.shareasimage.com can't
be resolved

$ nslookup cf.shareasimage.com
Server: 127.0.0.53
Address:127.0.0.53#53

Non-authoritative answer:
*** Can't find cf.shareasimage.com: No answer


The parent domain can be found though:
nslookup shareasimage.com
Server: 127.0.0.53
Address:127.0.0.53#53

Non-authoritative answer:
Name:   shareasimage.com
Address: 52.32.185.55
Name:   shareasimage.com
Address: 54.191.249.219

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

Title:
  Non existent host causes 100% cpu utilization by systemd-resolved and
  dnsmasq

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] 

[Touch-packages] [Bug 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04

[Dimitri John Ledkov]

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

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Zesty:
  Fix Committed
Status in openssh source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk
  debug1: Host '10.245.208.7' is known and matches the ECDSA host key.
  debug1: Found key in /home/fheimes/.ssh/known_hosts:87
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: publickey,password
  

[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware

[Etienne URBAH]

My particular use case is to detect, inside a shell script, if there is
any bluetooth hardware at all.

Since 'bluetoothctl' systematically hangs when there is NO bluetooth
hardware, I can NOT use the 'bluetoothctl' command to achieve this use
case.

But I have found a good alternate method :

if  rfkill  list  |  grep  -q  -i  Bluetooth;  then  ...;  fi

So, the issue is NOT blocking for me.

But I suggest that 'man bluetoothctl' should indicate that
'bluetoothctl' waits (possibly indefinitely) for answers from the
'bluetoothd' daemon, and therefore is NOT adequate for scripting.

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

Title:
  bluetoothctl systematically hangs when there is no bluetooth hardware

Status in bluez package in Ubuntu:
  New

Bug description:
  On a machine WITH bluetooth hardware, the 'bluetoothctl' command works 
correctly.
  For example, the command 'bluetoothctl < /dev/null' terminates correctly.

  On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command 
systematically hangs.
  Even the command 'bluetoothctl < /dev/null' systematically hangs.

  $ bluetoothctl &
  [1] 6208

  $ ps -l $!
  F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTYTIME CMD
  0 T  1001  6208  2525  0  80   0 -  9578 signal pts/1  0:00 bluetoothctl

  [1]+  Stopped bluetoothctl

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr  4 20:09:39 2016
  InstallationDate: Installed on 2015-07-20 (259 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterestingModules: bluetooth
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed 
root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago)
  dmi.bios.date: 06/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  hciconfig:
   
  rfkill:
   
  syslog:
   avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)...
   avril 03 15:10:45 urbah-sirius NetworkManager[986]:   Loaded device 
plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5).

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

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

[Touch-packages] [Bug 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq

[Fodder]

** Attachment added: "ad server entries for dnsmasq"
   
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364/+attachment/4872273/+files/adblock

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

Title:
  Non existent host causes 100% cpu utilization by systemd-resolved and
  dnsmasq

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1

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

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

[Touch-packages] [Bug 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq

[Fodder]

I uncommented dns-loop-detect in /etc/dnsmasq.conf, but this didn't
change anything.

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

Title:
  Non existent host causes 100% cpu utilization by systemd-resolved and
  dnsmasq

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1

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

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

[Touch-packages] [Bug 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq

[Fodder]

This is a workstation, not a virtual

dnsmasq and systemd are installed from the ubuntu repos (I'm on 17.04)

I've done a full uninstall of dnsmasq (apt-get remove --auto-remove
--purge dnsmasq, manually deleting /etc/dnsamsq.d, apt list --installed
*dnsmasq* to confirm everything was removed and then apt-get install
dnsmasq

I have a cron script that generates a config file for dnsmasq that
directs a number of ad server domains to 127.0.0.1.  The file has a
series of address= entries and is copied into /etc/dnsmasq.d

Upon further investigation it isn't an invalid host that seems to be
causing the problem, but if I go to the following page in firefox (again
normal install from repos), it generates the error consistently:
http://science.howstuffworks.com/reverse-osmosis.htm

** Attachment added: "shell script that generates ad blocker config file for 
dnsmasq"
   
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364/+attachment/4872272/+files/update_bannerhosts

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

Title:
  Non existent host causes 100% cpu utilization by systemd-resolved and
  dnsmasq

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded 

[Touch-packages] [Bug 1640320] Re: FTBFS in zesty

[Launchpad Bug Tracker]

This bug was fixed in the package location-service -
3.0.0+16.10.20160912-0ubuntu3

---
location-service (3.0.0+16.10.20160912-0ubuntu3) artful; urgency=high

  [ Tiago Stürmer Daitx ]
  * Fix zesty FTBFS by adding the missing vector includes

  [ Balint Reczey ]
  * Build-depend on googletest instead of google-mock and libgtest-dev
  * Don't FTBFS with google-mock installed (LP: #1640320)
  * Don't ship google test files in binary packages

 -- Balint Reczey   Thu, 23 Mar 2017 12:04:47 +

** Changed in: location-service (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  FTBFS in zesty

Status in location-service package in Ubuntu:
  Fix Released

Bug description:
  FTBFS in zesty during a no change rebuild against new boost

  Please see build logs at: https://launchpad.net/ubuntu/+source
  /location-service/3.0.0+16.10.20160912-0ubuntu2

  Please help fix this

  [ 10%] Building CXX object 
src/location_service/com/ubuntu/location/CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
  cd 
/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service/com/ubuntu/location
 && /usr/bin/g++   -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_NET_CPP=1 
-DCOM_UBUNTU_LOCATION_SERVICE_HAVE_UBUNTU_PLATFORM_HARDWARE_API 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GEOCLUE 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GPS 
-Dubuntu_location_service_connectivity_EXPORTS 
-I/<>/location-service-3.0.0+16.10.20160912/3rd-party 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/json-c 
-I/<>/location-service-3.0.0+16.10.20160912/include/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/src/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service
 -I/usr/include/ubuntu  -g -O2 
-fdebug-prefix-map=/<>/location-service-3.0.0+16.10.20160912=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -Wall -fno-strict-aliasing -pedantic -Wextra 
-fPIC -Wno-error=unused-local-typedefs -fPIC   -o 
CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
 -c 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/connectivity/wireless_network.cpp
  In file included from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.h:21:0,
   from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.cpp:19:
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:57:14:
 error: ‘vector’ in namespace ‘std’ does not name a template type
   std::vector xtra_hosts
^~
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:59:10:
 warning: extra ‘;’ [-Wpedantic]
   };
^
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:66:18:
 error: ‘vector’ in namespace ‘std’ does not name a template type
   virtual std::vector download_xtra_data(const Configuration& 
config) = 0;
^~
  make -f po/CMakeFiles/pofiles_70.dir/build.make 
po/CMakeFiles/pofiles_70.dir/depend

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

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

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

[PcB Computer Support]

give more space for /boot 1gb ?

PcB-iPhone Communication

Am 05.05.2017 um 13:09 schrieb Bill Meier <798...@bugs.launchpad.net>:

Why not just write a little GUI app for us , so that we "command line 
illiterates" can take  care of this. We need to select what we want 
deleted, just getting rid of the old, I understand, may not be what is 
wanted.


Bill


> On 05/05/2017 03:13 AM, Michael Baker wrote:
> On booting I am told that a system program has encountered an error and asked 
> if I want to send a report. On saying yes I'm told that the bug has already 
> been reported and that it is "update-initramfs should produce a more helpful 
> error when there isn't enough free space".
> This is so far from what is happening that it is infuriating.
> The basis of the problem is that /boot is not being cleaned up automatically.
> This was a bug which was supposedly fixed in 16.04 UTS, but apparently not.
> As a retired software engineer I know that I can clean up /boot manually, and 
> have done so many times.
> However I shouldn't have to.
> Please stop classifying the /boot partition being full as "update-initramfs 
> should produce a more helpful error when there isn't enough free space".
> This bug (/boot not being cleaned up automatically) should be given the 
> highest possible importance.
> It must be a complete turn of to any ubuntu user who does not have computer 
> science skills (and to many who do).

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/798414

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

Status in initramfs-tools:
 Confirmed
Status in Software Updater:
 New
Status in dpkg package in Ubuntu:
 Invalid
Status in initramfs-tools package in Ubuntu:
 In Progress

Bug description:
 Binary package hint: initramfs-tools

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

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

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

 WORKAROUND:

 Remove unused kernels using computer janitor (not in repositories for
 14.04 or later) or manually free space on your partition containing
 the /boot file system.

 See instructions here
 https://help.ubuntu.com/community/RemoveOldKernels

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

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

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

Status in initramfs-tools:
  Confirmed
Status in Software Updater:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

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

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

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

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

[Touch-packages] [Bug 1679784] Re: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt

[farina benedetto]

** Branch unlinked: lp:software-properties

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

Title:
  Changing from Xorg video driver to NVIDIA driver using Software &
  Updates does not display debconf prompt

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  Confirmed
Status in software-properties source package in Xenial:
  Confirmed
Status in software-properties source package in Yakkety:
  Fix Released

Bug description:
  [SRU Justification]
  software-properties does not display debconf prompts. while most debconf 
prompts have default answers and this is fine, for installing dkms modules on a 
SecureBoot-capable system we specifically have a critical debconf prompt with 
no possible default answer that users need to step through in order for their 
dkms modules to be usable.

  [Test case]
  1. sudo apt-add-repository ppa:vorlon/debconf-tests
  2. sudo apt update
  3. Launch Settings -> Software & Updates -> Additional Drivers
  4. Confirm that you are offered the option of using the 'noisy-fake-driver' 
package.
  5. Select this driver and apply changes.
  6. Confirm that no debconf prompt is shown, and the driver package fails to 
install ('dpkg -l noisy-fake-driver' shows 'iF').
  7. Reset the package state by removing the driver again.
  8. Enable -proposed.
  9. Run update-manager and verify that the new software-properties package is 
successfully installed from -proposed, pulling in libgtk2-perl in the process.
  10. Close Software & Updates and re-launch it.
  11. Select the 'noisy-fake-driver' package again.
  12. Confirm that you are shown a debconf prompt, and the driver package 
installs successfully.

  [Regression potential]
  The actual code change is small and self-contained, but the fix also requires 
pulling in new package dependencies which will also need to be promoted from 
universe to main in the process.  We need to take extra care to ensure the 
upgrade path is correct.  This SRU should also be done serially one release at 
a time to gather feedback at each stage.

  [Original bug description]
  I've encountered this repeatedly.

  In the first installation -- on updating via Software Updater, this
  crashed on upgrading the shim-signed package.

  On suggestions from here:

  I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work,
  however when I now try to swap the display driver, from xorg -->
  nvidia. This now triggered the same issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  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
  Date: Tue Apr  4 18:21:32 2017
  DuplicateSignature:
   package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
   Processing triggers for shim-signed 
(1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
   Running in non-interactive mode, doing nothing.
   dpkg: error processing package shim-signed (--configure):
    subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: shim-signed
  Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[Marco Bianchi]

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

I have tried all the above but did not work for me? I was running Ubuntu
16.04.2 LTS Xenial with no problem until two days ago. Then, after I did
a routine software update which I was prompted to do but Ubuntu software
updater, I had an error saying something went wrong. After I rebooted
the machine, I had no longer ethernet.

My card is realtek.

The command below 
sudo lshw -C network

gave me -network UNCLAIMED

and doing ifconfig i do not see any ethernet connection there.

For now, I was able to get on the web and post this message to you only
because I had a backup exact copy of my 120gb SSD, hence I was able to
just change the SSD and get back to the Ubuntu system I had BEFORE the
update. I think this is a serious bug in Ubuntu, if did not have backup,
would have caused a lot of inconvenience, with me being unable to go on
the web using my Desktop PC.

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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

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

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

[Bill Meier]

Why not just write a little GUI app for us , so that we "command line 
illiterates" can take  care of this. We need to select what we want 
deleted, just getting rid of the old, I understand, may not be what is 
wanted.


Bill


On 05/05/2017 03:13 AM, Michael Baker wrote:
> On booting I am told that a system program has encountered an error and asked 
> if I want to send a report. On saying yes I'm told that the bug has already 
> been reported and that it is "update-initramfs should produce a more helpful 
> error when there isn't enough free space".
> This is so far from what is happening that it is infuriating.
> The basis of the problem is that /boot is not being cleaned up automatically.
> This was a bug which was supposedly fixed in 16.04 UTS, but apparently not.
> As a retired software engineer I know that I can clean up /boot manually, and 
> have done so many times.
> However I shouldn't have to.
> Please stop classifying the /boot partition being full as "update-initramfs 
> should produce a more helpful error when there isn't enough free space".
> This bug (/boot not being cleaned up automatically) should be given the 
> highest possible importance.
> It must be a complete turn of to any ubuntu user who does not have computer 
> science skills (and to many who do).
>

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

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

Status in initramfs-tools:
  Confirmed
Status in Software Updater:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

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

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

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

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/RemoveOldKernels

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

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