date:20171025

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  ModemManager crashed with SIGSEGV in ffi_call_unix64()

Status in modemmanager package in Ubuntu:
  New

Bug description:
  i got this error after system start and first login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: modemmanager 1.6.8-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 08:33:57 2017
  ExecutablePath: /usr/sbin/ModemManager
  ProcCmdline: /usr/sbin/ModemManager
  SegvAnalysis:
   Segfault happened at: 0x5646e906bc37:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x5646e906bc37) ok
   source "%es:(%rdi)" (0x5646e90ff83f) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ModemManager crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1727227] [NEW] error on boot

2017-10-25 Thread Qube77

Public bug reported:

have run the report

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  387.12  Thu Sep 28 20:18:48 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed Oct 25 09:06:21 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Pegatron 3rd Gen Core processor Graphics Controller [1b0a:20dd]
 NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Pegatron GK107M [GeForce GT 650M] [1b0a:20dd]
InstallationDate: Installed on 2016-10-22 (367 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Novatech Ltd Novatech 15.6 nSpire Laptop
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=0ddc6564-07e2-4ca2-a501-4c6c4f89a96d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/03/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: A35
dmi.board.vendor: Novatech Ltd
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Novatech Ltd
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr206:bd04/03/2012:svnNovatechLtd:pnNovatech15.6nSpireLaptop:pvr1.0:rvnNovatechLtd:rnA35:rvr1.0:cvnNovatechLtd:ct10:cvr1.0:
dmi.product.family: PEGA Family
dmi.product.name: Novatech 15.6 nSpire Laptop
dmi.product.version: 1.0
dmi.sys.vendor: Novatech Ltd
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Oct 25 09:02:37 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2

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


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

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

Title:
  error on boot

Status in xorg package in Ubuntu:
  New

Bug description:
  have run the report

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  387.12  Thu Sep 28 20:18:48 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Oct 25 09:06:21 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Pegatron 3rd Gen Core processor Graphics Controller

[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

2017-10-25 Thread Consumology

After upgrading my laptop to 17.10 I had right click functionality on my
touchpad. Then it was gone, some other people also reported this on
askubuntu but I could not find a related bug. After finding this bug I
installed xserver-xorg-input-synaptics and right click on my touchpad is
back. So the disappearing right click functionality is a problem in
libinput?

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in xorg source package in Artful:
  Confirmed
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

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

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

[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

2017-10-25 Thread Bug Watch Updater

** Changed in: systemd (Debian)
   Status: Unknown => Fix Released

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connected

  When the user purged laptop-mode-tools the system starts successfully
  on battery.

  The user installed a fresh i

[Touch-packages] [Bug 1727237] [NEW] systemd-resolved is not finding a domain

2017-10-25 Thread Mark Shuttleworth

Public bug reported:

I have an odd network situation that I have so far managed to narrow
down to the inability to resolve a domain via systemd-resolved which is
resolvable with nslookup. If I use nslookup against the two nameservers
on this network I get answers for the domain, but ping says it is unable
to resolve the same domain (as do browsers and crucially the captive
portal mechanism).

Here are details:

NSLOOKUP:

~$ nslookup securelogin.arubanetworks.com 208.67.220.220
Server: 208.67.220.220
Address:208.67.220.220#53

Non-authoritative answer:
Name:   securelogin.arubanetworks.com
Address: 172.22.240.242

~$ nslookup securelogin.arubanetworks.com 208.67.222.222
Server: 208.67.222.222
Address:208.67.222.222#53

Non-authoritative answer:
Name:   securelogin.arubanetworks.com
Address: 172.22.240.242


PING:

~$ ping securelogin.arubanetworks.com
ping: securelogin.arubanetworks.com: Name or service not known
mark@mark-X1Y2:~$ 


DIG:

~$ dig @208.67.222.222 securelogin.arubanetworks.com

; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;securelogin.arubanetworks.com. IN  A

;; AUTHORITY SECTION:
arubanetworks.com.  1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

;; Query time: 34 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Wed Oct 25 10:31:10 CEST 2017
;; MSG SIZE  rcvd: 144


MORE DIG:

~$ dig securelogin.arubanetworks.com

; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;securelogin.arubanetworks.com. IN  A

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Oct 25 10:34:01 CEST 2017
;; MSG SIZE  rcvd: 58

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

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  New

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

To manage notifications

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

This issue can be fixed by re-adding the required Start/Stop bits to the
LSB header; however the behaviour of update-rc.d when native systemd
unit files are in use looks odd to me.

Raising an init-system-helpers bug task for foundations team input on
this.

** Also affects: init-system-helpers (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Triaged
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Triaged
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Triaged
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Triaged
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Triaged

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  TBC as not quite sure where the fix for this is.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1727243] [NEW] pam_systemd

2017-10-25 Thread latimerio

Public bug reported:

my auth.log is full of messages like below.
The 79.247.. is my own address and there seems to be something which tries to 
reconnect every other second although I am already in a running session.
What is going on here?

Oct 25 10:38:57 h... sshd[6506]: Accepted publickey for root from 79.247... 
port 52067 ssh2: RSA SHA256:pru...
Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session opened for 
user root by (uid=0)
Oct 25 10:38:57 h... systemd-logind[285]: New session 2373897 of user root.
Oct 25 10:38:57 h... sshd[6506]: pam_systemd(sshd:session): Cannot create 
session: Already running in a session
Oct 25 10:38:57 h... sshd[6506]: Received disconnect from 79.247... port 
52067:11: disconnected by user
Oct 25 10:38:57 h... sshd[6506]: Disconnected from 79.247... port 52067
Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session closed for 
user root
Oct 25 10:38:57 h... systemd-logind[285]: Removed session 2373897.
Oct 25 10:38:59 h... sshd[6524]: Accepted publickey for root from 79.247... 
port 52068 ssh2: RSA SHA256:pru...
Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session opened for 
user root by (uid=0)
Oct 25 10:38:59 h... systemd-logind[285]: New session 2373898 of user root.
Oct 25 10:38:59 h... sshd[6524]: pam_systemd(sshd:session): Cannot create 
session: Already running in a session
Oct 25 10:38:59 h... sshd[6524]: Received disconnect from 79.247... port 
52068:11: disconnected by user
Oct 25 10:38:59 h... sshd[6524]: Disconnected from 79.247... port 52068
Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session closed for 
user root
Oct 25 10:38:59 h... systemd-logind[285]: Removed session 2373898.
Oct 25 10:39:01 h... CRON[6565]: pam_unix(cron:session): session opened for 
user root by (uid=0)
Oct 25 10:39:01 h... CRON[6564]: pam_unix(cron:session): session opened for 
user root by (uid=0)
Oct 25 10:39:01 h... sshd[6562]: Accepted publickey for root from 79.247... 
port 52069 ssh2: RSA SHA256:pru...
Oct 25 10:39:01 h... sshd[6562]: pam_unix(sshd:session): session opened for 
user root by (uid=0)
Oct 25 10:39:01 h... systemd-logind[285]: New session 2373904 of user root.
Oct 25 10:39:01 h... sshd[6562]: pam_systemd(sshd:session): Cannot create 
session: Already running in a session
Oct 25 10:39:01 h... sshd[6562]: Received disconnect from 79.247... port 
52069:11: disconnected by user
Oct 25 10:39:01 h... sshd[6562]: Disconnected from 79.247... port 52069
Oct 25 10:39:01 h... sshd[6562]: pam_unix(sshd:session): session closed for 
user root
Oct 25 10:39:01 h... systemd-logind[285]: Removed session 2373904.
Oct 25 10:39:01 h... CRON[6565]: pam_unix(cron:session): session closed for 
user root
Oct 25 10:39:02 h... sshd[6665]: Accepted publickey for root from 79.247... 
port 52070 ssh2: RSA SHA256:pru...
Oct 25 10:39:02 h... sshd[6665]: pam_unix(sshd:session): session opened for 
user root by (uid=0)
Oct 25 10:39:02 h... systemd-logind[285]: New session 2373945 of user root.
Oct 25 10:39:03 h... sshd[6665]: pam_systemd(sshd:session): Cannot create 
session: Already running in a session
Oct 25 10:39:03 h... sshd[6665]: Received disconnect from 79.247... port 
52070:11: disconnected by user
Oct 25 10:39:03 h... sshd[6665]: Disconnected from 79.247... port 52070
Oct 25 10:39:03 h... sshd[6665]: pam_unix(sshd:session): session closed for 
user root
Oct 25 10:39:03 h... systemd-logind[285]: Removed session 2373945.

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

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

Title:
  pam_systemd

Status in systemd package in Ubuntu:
  New

Bug description:
  my auth.log is full of messages like below.
  The 79.247.. is my own address and there seems to be something which tries to 
reconnect every other second although I am already in a running session.
  What is going on here?

  Oct 25 10:38:57 h... sshd[6506]: Accepted publickey for root from 79.247... 
port 52067 ssh2: RSA SHA256:pru...
  Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session opened for 
user root by (uid=0)
  Oct 25 10:38:57 h... systemd-logind[285]: New session 2373897 of user root.
  Oct 25 10:38:57 h... sshd[6506]: pam_systemd(sshd:session): Cannot create 
session: Already running in a session
  Oct 25 10:38:57 h... sshd[6506]: Received disconnect from 79.247... port 
52067:11: disconnected by user
  Oct 25 10:38:57 h... sshd[6506]: Disconnected from 79.247... port 52067
  Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session closed for 
user root
  Oct 25 10:38:57 h... systemd-logind[285]: Removed session 2373897.
  Oct 25 10:38:59 h... sshd[6524]: Accepted publickey for root from 79.247... 
port 52068 ssh2: RSA SHA256:pru...
  Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session opened for 
user root by (uid=0)
  Oct 25 10:38:59 h... sys

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

Actually this only impacts Xenial; Debian carried a patch from:

pacemaker (1.1.15~rc3-1) unstable; urgency=medium

  [ Christoph Berg ]
  * [23ee108] libcrmservice3.symbols: Exclude systemd symbol on non-linux
  * [41dea05] Fix time formatting on x32
  * [533c5cc] Fix FTBFS on GNU Hurd

  [ Arturo Borrero Gonzalez ]
  * [698053d] d/tests/control: add isolation-container restriction

  [ Ferenc Wágner ]
  * [065159d] New patch Enable-the-init-scripts-on-multi-user-runlevels.patch
  * [7a5008b] New patch Make-the-asciidoc-documentation-reproducible.patch
  * [08a4162] New patch Add-remote_fs-dependencies-to-the-init-scripts.patch
  * [7a65d2c] New upstream release (1.1.15~rc1)
  * [dd9f5f4] Remove upstreamed patches, refresh the rest
  * [0cdd116] Update symbol files
  * [3de7a21] New patch Add-documentation-URIs-to-the-service-files.patch
  * [9faaa02] Move documentation generators into Build-Depends-Indep
  * [9362a46] Move documentation into /usr/share/doc/pacemaker
  * [64c0e84] Move misc documentation files into the pacemaker-doc package
  * [837e74d] New patch Read-default-files-in-pacemaker.service.patch
  * [72fef80] New upstream release (1.1.15~rc2)
  * [69ee575] Remove patch included in 1.1.15~rc2
  * [46dce98] Also add documentation URI to our version of crm_mon.service
  * [8c25aff] New patch to avoid using WIFCONTINUED entirely
  * [a28e0ae] New upstream release (1.1.15~rc3)
  * [a8976fe] Remove freshly upstreamed patches, refresh the rest

 -- Ferenc Wágner   Sat, 28 May 2016 22:28:49 +0200


Which re-enables the default runlevels.

** Changed in: pacemaker (Ubuntu Bionic)
   Status: Triaged => Fix Released

** Changed in: pacemaker (Ubuntu Artful)
   Status: Triaged => Fix Released

** Changed in: pacemaker (Ubuntu Zesty)
   Status: Triaged => Fix Released

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Triaged
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  TBC as not quite sure where the fix for this is.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

Proposed update for xenial

** Patch added: "pacemaker.debdiff"
   
https://bugs.launchpad.net/ubuntu/zesty/+source/pacemaker/+bug/1727063/+attachment/4993845/+files/pacemaker.debdiff

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Triaged
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  TBC as not quite sure where the fix for this is.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

Doing some testing via:

  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3010

before upload to xenial-proposed; not that the act of fixing this
problem will in itself cause the pacemaker daemons to be started on
upgrade.  However it won't be auto-applied on a default install (unlike
the security update that caused the original issue).

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Triaged
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  TBC as not quite sure where the fix for this is.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1337262] Re: kmod should permit use of compressed modules

2017-10-25 Thread Jouni Mettala

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

** Also affects: kmod (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772628
   Importance: Unknown
   Status: Unknown

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

Title:
  kmod should permit use of compressed modules

Status in kmod package in Ubuntu:
  Triaged
Status in kmod package in Debian:
  Unknown

Bug description:
  kmod should permit use of compressed modules. This enables images that
  boot from RAM to be much smaller. In essence this requires only
  changing a build option. Uncompressed modules are still supported.

  A patch is here:
  https://github.com/abligh/kmod/commit/31795c8078ba9ccb6f064d11d0c9e640f8e0fab1

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

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

[Touch-packages] [Bug 1337262] Re: kmod should permit use of compressed modules

2017-10-25 Thread Bug Watch Updater

** Changed in: kmod (Debian)
   Status: Unknown => New

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

Title:
  kmod should permit use of compressed modules

Status in kmod package in Ubuntu:
  Triaged
Status in kmod package in Debian:
  New

Bug description:
  kmod should permit use of compressed modules. This enables images that
  boot from RAM to be much smaller. In essence this requires only
  changing a build option. Uncompressed modules are still supported.

  A patch is here:
  https://github.com/abligh/kmod/commit/31795c8078ba9ccb6f064d11d0c9e640f8e0fab1

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

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

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

Tested OK (pacemaker was restarted after upgrade)

Uploaded to unapproved queue for SRU Team review - I'd suggest we
fasttrack this ASAP into -updates and -security to catch auto updates
for those systems not already updated.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Triaged
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later

2017-10-25 Thread Paul Menzel

I integrated the PPA, but under Ubuntu 16.04.3 LTS no updates are
available. The package *apparmor* 2.10.95-0ubuntu2.7 is installed.

```
$ sudo add-apt-repository ppa:apparmor-dev/apparmor-devel
$ sudo apt-get update
```

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

Title:
  apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"
  w/ 4.14-rc2 and later

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Confirmed
Status in apparmor source package in Zesty:
  Confirmed
Status in apparmor source package in Artful:
  Confirmed

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor
  2.10.95-0ubuntu2.7, in the system log each second the error message
  below is printed to.

  ```
  […]
  [Mi Okt  4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  […]
  ```

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

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

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

** Description changed:

  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.
  
  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker
  
  pacemaker daemons will not be restarted.
  
  [Regression Potential]
- TBC as not quite sure where the fix for this is.
+ Minimal, earlier and later versions provide the defaults in the lsb header.
  
  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).
  
  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.
  
  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.
  
  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)
  
  I have not checked whether this affects trusty environments.
  
  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop entries.
  
  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Triaged
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

Updates building in:

  https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Triaged
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

this breaks existing configurations with bonding on upgrading from 
229-4ubuntu19 to 229-4ubuntu20
as bond interfaces are now by default configured without ARP. Hence you 
suddenly lose network connectivity on upgrade. Very bad for a SRU.

Plus adding "ARP=yes" to the Link section of a .network file does not
work.

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

Title:
  add bond primary parameter

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

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  network:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

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

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

[Touch-packages] [Bug 1727270] [NEW] package libjasper1:amd64 1.900.1-debian1-2.4ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attem

2017-10-25 Thread Kyle Cleveland

Public bug reported:

Every time I perform an upgrade request, I receive this error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libjasper1:amd64 1.900.1-debian1-2.4ubuntu1.1
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 distro-info-data: Install
 libjasper1: Configure
 distro-info-data: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Oct 25 05:13:02 2017
DuplicateSignature:
 package:libjasper1:amd64:1.900.1-debian1-2.4ubuntu1.1
 Unpacking distro-info-data (0.28ubuntu0.4) over (0.28ubuntu0.3) ...
 dpkg: error processing package libjasper1:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-08 (170 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: jasper
Title: package libjasper1:amd64 1.900.1-debian1-2.4ubuntu1.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libjasper1:amd64 1.900.1-debian1-2.4ubuntu1.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in jasper package in Ubuntu:
  New

Bug description:
  Every time I perform an upgrade request, I receive this error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjasper1:amd64 1.900.1-debian1-2.4ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   distro-info-data: Install
   libjasper1: Configure
   distro-info-data: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Oct 25 05:13:02 2017
  DuplicateSignature:
   package:libjasper1:amd64:1.900.1-debian1-2.4ubuntu1.1
   Unpacking distro-info-data (0.28ubuntu0.4) over (0.28ubuntu0.3) ...
   dpkg: error processing package libjasper1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-08 (170 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: jasper
  Title: package libjasper1:amd64 1.900.1-debian1-2.4ubuntu1.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1727270] Re: package libjasper1:amd64 1.900.1-debian1-2.4ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt

** Tags removed: need-duplicate-check

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

Title:
  package libjasper1:amd64 1.900.1-debian1-2.4ubuntu1.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in jasper package in Ubuntu:
  New

Bug description:
  Every time I perform an upgrade request, I receive this error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjasper1:amd64 1.900.1-debian1-2.4ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   distro-info-data: Install
   libjasper1: Configure
   distro-info-data: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Oct 25 05:13:02 2017
  DuplicateSignature:
   package:libjasper1:amd64:1.900.1-debian1-2.4ubuntu1.1
   Unpacking distro-info-data (0.28ubuntu0.4) over (0.28ubuntu0.3) ...
   dpkg: error processing package libjasper1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-08 (170 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: jasper
  Title: package libjasper1:amd64 1.900.1-debian1-2.4ubuntu1.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

Also tested proposed fix on a three unit gnocchi HA deployment; all
pacemaker updates applied and restarted pacemaker postinst as desired.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Triaged
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

Testing from security-proposed PPA:

Broken install (dpkg-reconfigure pacemaker already run, daemons
stopped):  Packages updated and pacemaker daemon restarted by postinst:
OK

Running install (pacemaker daemons running prior to pkg upgrade):
Packages update, pacemaker daemon stop prior to unpack and restarted by
postinst: OK

>From my perspective the update looks good - but would appreciate a
second pair of eyes on this one.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Triaged
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2017-10-25 Thread Gilles Gravier

** Also affects: gnome-terminal
   Importance: Undecided
   Status: New

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in GNOME Terminal:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  Posting here what gnome says about porting to wayland, and their
  tests:

  GNOME Applications under Wayland
  GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a 
GTK+ application under Wayland simply by:

  GDK_BACKEND=wayland gnome-calculator
  Applications that use Clutter or clutter-gtk also need the Clutter Wayland 
backend enabled:

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

  https://wiki.gnome.org/Initiatives/Wayland/Applications

  ==> so hope the settings are well set at compile time; maybe a
  rebuilt to get sure all apps are ok.

  
  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardva

[Touch-packages] [Bug 1727276] [NEW] When using Ukrainian input it looks like alt is always pressed

2017-10-25 Thread Ihor Romanyshyn

Public bug reported:

Hi people! I have a BIG problem with text input in Ukrainian language.
When i switch input from English to Ukrainian or use dot it looks like
[alt] is pressed continuously after that so if I type some text in
Ukrainian i getting lot of ©®ёэ§²•ъ»«ы (special symbols) instead of my
text. My keyboard is Ok, it's new Ubuntu 17.10 problem... To temporarily
input text as normal I need always press [alt] before input any new
portion of text in Ukrainian, this is frustrating and makes me feel bad.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: keyboard-configuration 1.166ubuntu7
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 25 13:20:00 2017
InstallationDate: Installed on 2017-10-19 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Keyboard:
 XKBLAYOUT=us
 BACKSPACE=guess
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=uk_UA.UTF-8
 SHELL=/bin/bash
SourcePackage: console-setup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  When using Ukrainian input it looks like alt is always pressed

Status in console-setup package in Ubuntu:
  New

Bug description:
  Hi people! I have a BIG problem with text input in Ukrainian language.
  When i switch input from English to Ukrainian or use dot it looks like
  [alt] is pressed continuously after that so if I type some text in
  Ukrainian i getting lot of ©®ёэ§²•ъ»«ы (special symbols) instead of my
  text. My keyboard is Ok, it's new Ubuntu 17.10 problem... To
  temporarily input text as normal I need always press [alt] before
  input any new portion of text in Ukrainian, this is frustrating and
  makes me feel bad.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: keyboard-configuration 1.166ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 13:20:00 2017
  InstallationDate: Installed on 2017-10-19 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Keyboard:
   XKBLAYOUT=us
   BACKSPACE=guess
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread Edward Hope-Morley

Tested proposed package upgrade and works for me -
http://pastebin.ubuntu.com/25815820/

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Triaged
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

@Markus Schade

Could you please elaborate what you mean? and/or open a new bug with a
tag "regression-updates" describing your system?

In systemd, the patch which was added is as following:
https://git.launchpad.net/~ubuntu-core-dev/+git/systemd/tree/debian/patches/networkd-add-support-to-configure-NOARP-ARP-for-interface.patch?h=ubuntu-xenial&id=b84ef89476003b10da06e9bb7d347f3b1e2098cf

Note that whilst Link.ARP setting is added to networkd, there is no
change in behavior. It is a tristate, without a default setting, meaning
kernel default is used.

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

Title:
  add bond primary parameter

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

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  network:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

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

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

[Touch-packages] [Bug 1727278] Re: evolution-addressbook-factory-subprocess crashed with SIGSEGV in std::__cxx11::basic_string, std::allocator >::basic_string()

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  evolution-addressbook-factory-subprocess crashed with SIGSEGV in
  std::__cxx11::basic_string,
  std::allocator >::basic_string()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  It just crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: evolution-data-server 3.26.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 12:33:26 2017
  ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory-subprocess
  InstallationDate: Installed on 2015-12-17 (678 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory-subprocess 
--factory google --bus-name 
org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx3313x4 --own-path 
/org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/3313/4
  SegvAnalysis:
   Segfault happened at: 0x7f860285b0db 
<_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC2ERKS4_+11>: mov
(%rsi),%rax
   PC (0x7f860285b0db) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evolution-data-server
  Title: evolution-addressbook-factory-subprocess crashed with SIGSEGV in 
std::__cxx11::basic_string, std::allocator 
>::basic_string()
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  UserGroups: adm audio cdrom dialout dip docker input lpadmin plugdev 
sambashare sudo tty wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1727278/+subscriptions

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

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

What is the release / package version in use of systemd?

How is the networking configured: netplan, ifupdown, networkd,
networkmanager?

What is the contents of /etc/resolv.conf?

Where does the symlink of /etc/resolv.conf point to? (if it is a
symlink)

What is the contents of /etc/systemd/resolved.conf ?

Is libnss-resolve package installed?

What is the output of $ systemd-resolve --status ?
(if --status option is available)

Is this a captive portal hostage situation with Ubuntu failing to get to
the captive portal to enable internet?

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

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

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

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

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

Also validated that the update fixes an existing machine with the 1.2
update on it (with pacemaker services not running).

Pacemaker started after the update.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Triaged
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1727291] [NEW] fonts-droid-fallback is missing "Provides: fonts-droid"

2017-10-25 Thread Mikko Rantalainen

Public bug reported:

16.04 LTS has renamed package "fonts-droid" as "fonts-droid-fallback" and the 
new package Breaks the old package. However, the new package is missing 
"Provides: fonts-droid" which would allow
existing scripts and 3rd party packages with dependency to "fonts-droid" to 
continue working.

Unless there's some reason not to include "Provides: fonts-droid" I
would request adding it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: fonts-droid-fallback (not installed)
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-lowlatency 4.8.17
Uname: Linux 4.8.0-54-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Wed Oct 25 14:08:54 2017
InstallationDate: Installed on 2015-02-23 (975 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: fonts-android
UpgradeStatus: Upgraded to xenial on 2016-06-10 (502 days ago)

** Affects: fonts-android (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  fonts-droid-fallback is missing "Provides: fonts-droid"

Status in fonts-android package in Ubuntu:
  New

Bug description:
  16.04 LTS has renamed package "fonts-droid" as "fonts-droid-fallback" and the 
new package Breaks the old package. However, the new package is missing 
"Provides: fonts-droid" which would allow
  existing scripts and 3rd party packages with dependency to "fonts-droid" to 
continue working.

  Unless there's some reason not to include "Provides: fonts-droid" I
  would request adding it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: fonts-droid-fallback (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-lowlatency 4.8.17
  Uname: Linux 4.8.0-54-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Oct 25 14:08:54 2017
  InstallationDate: Installed on 2015-02-23 (975 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: fonts-android
  UpgradeStatus: Upgraded to xenial on 2016-06-10 (502 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1727291/+subscriptions

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

[Touch-packages] [Bug 1727063] Update Released

2017-10-25 Thread Andy Whitcroft

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

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Fix Released
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread Andy Whitcroft

Did some touch testing in a VM and confirmed that the 1.2 package loses
its daemons on any kind of reconfigured.  This behaviour is rectified
with the 1.3 package.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Fix Released
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

This bug was fixed in the package pacemaker - 1.1.14-2ubuntu1.3

---
pacemaker (1.1.14-2ubuntu1.3) xenial; urgency=medium

  * Fix default start/stop levels for init scripts, ensuring that
running pacemaker daemons are restarted after package upgrades
(LP: #1727063):
- d/p/Enable-the-init-scripts-on-multi-user-runlevels.patch: Cherry
  picked fix from later package versions.

 -- James Page   Wed, 25 Oct 2017 10:04:30 +0100

** Changed in: pacemaker (Ubuntu Xenial)
   Status: Triaged => Fix Released

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Fix Released
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1727291] Re: fonts-droid-fallback is missing "Provides: fonts-droid"

2017-10-25 Thread Mikko Rantalainen

See also: https://bugs.launchpad.net/ubuntu/+source/fonts-
android/+bug/1536547

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1727291/+attachment/4994138/+files/JournalErrors.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1727291/+attachment/4994139/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1727291/+attachment/4994140/+files/ProcEnviron.txt

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

Title:
  fonts-droid-fallback is missing "Provides: fonts-droid"

Status in fonts-android package in Ubuntu:
  New

Bug description:
  16.04 LTS has renamed package "fonts-droid" as "fonts-droid-fallback" and the 
new package Breaks the old package. However, the new package is missing 
"Provides: fonts-droid" which would allow
  existing scripts and 3rd party packages with dependency to "fonts-droid" to 
continue working.

  Unless there's some reason not to include "Provides: fonts-droid" I
  would request adding it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: fonts-droid-fallback (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-lowlatency 4.8.17
  Uname: Linux 4.8.0-54-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Oct 25 14:08:54 2017
  InstallationDate: Installed on 2015-02-23 (975 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: fonts-android
  UpgradeStatus: Upgraded to xenial on 2016-06-10 (502 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1727291/+subscriptions

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

[Touch-packages] [Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

2017-10-25 Thread Andrea Azzarone

** Branch linked: lp:~azzar1/gtk3/fix-1720400

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

Title:
  /usr/bin/gnome-control-
  
center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

Status in GTK+:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress

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

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

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

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

2017-10-25 Thread Mark Shuttleworth

Yes, this is a captive portal situation on up-to-date 17.10. The captive
portal popup fails with a DNS error looking for
securelogin.arubanetworks.com and then hilarity ensues. Manually editing
/etc/resolv.conf to use one of these DNS servers makes it all work. So
the problem is systemd-resolved which is the default resolv.conf:

~$ cat /etc/resolv.conf 
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53

search invitados

It's all NM:

~$ cat /etc/netplan/01-network-manager-all.yaml 
# Let NetworkManager manage all devices on this system
network:
  version: 2
  renderer: NetworkManager

Should /etc/resolv.conf be a symlink?

libnss-resolve is not installed.

systemd-resolve --status shows the two local DNS servers, as above.

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

Link 7 (wwp0s20f0u6i12)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 4 (wlp4s0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 208.67.222.222
  208.67.220.220
  DNS Domain: invitados

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

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUE

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

I opened LP #1727301 to track this further

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

Title:
  add bond primary parameter

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

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  network:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

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

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

[Touch-packages] [Bug 1726595] Re: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10

2017-10-25 Thread thomas duriez

1- Yes Matlab works as expected without going through ssh.

2- Repeat the above but first do a "ssh -X localhost" triggers the
problem.

3- Both scenarios hold regardless of how I login ("Ubuntu", "Ubuntu on
Xorg" or "Unity").

As you mentionned the DISPLAY variable I checked the following (maybe it was 
obvious, but not to me):
 - ssh@localhost
 - echo $DISPLAY returns localhost:10.0
 - export DISPLAY=:0
 - matlab & then plot(1,1). 
 - it works. (tested in "Ubuntu", "Ubuntu on Xorg" and "Unity")

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

Title:
  Running Matlab (R) from ssh session with X forwarding doesn't work
  anymore in 17.10

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  OBSERVED BEHAVIOR:
  Matlab stays in busy state when using some functions like "plot" or even 
"exit", while executing through a ssh tunnel with X11 forwarding. 

  REPRODUCE THE BUG:

  You need matlab (my version is R2017a) to reproduce the bug. I suspect
  any version >= 2014b would reproduce the bug (HG2 framework), and
  maybe any version.

  1. Connect to self (or from other machine) with X forwarding:
  $ ssh -X user@localhost

  2. Launch matlab
  $ matlab &

  3. Plot something
  >> plot(1,1)

  ADDITIONAL INFORMATION
  - Normal behavior would be appearance of a new window and a single point at 
position (1,1). 
  - No ressources seem to be used. 
  - Opening a figure alone is possible. (>> figure). Opening other windows from 
the graphical user interface is possible 
  - Opening Matlab without the java machine seems to work, but matlab relies 
heavily on java. At least "exit" which doesn't work with java, works without 
java.
  - Providing Matlab with open-jdk version 1.8.0_144 didn't change anything.
  - This used to work perfectly for as long as I have been using Ubuntu (since 
2012).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: openssh-client 1:7.5p1-10
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Oct 23 17:44:23 2017
  ExecutablePath: /usr/bin/ssh
  InstallationDate: Installed on 2017-08-25 (59 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.0.2g  1 Mar 2016
  SourcePackage: openssh
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  modified.conffile..etc.ssh.ssh_config: [modified]
  mtime.conffile..etc.ssh.ssh_config: 2017-10-23T16:25:50.569560

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

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

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

Actually there is. Before this update, bond interfaces (specifically
802.3ad) were defaulting to ARP enabled. After the upgrade, they are
created with NOARP set on the link.

pre-upgrade:

eth0:  
eth1: 
bond0:  

post-upgrade:
eth0:  
eth1: 
bond0:  

Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  add bond primary parameter

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

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  network:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

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

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

[Touch-packages] [Bug 1727306] [NEW] window appears informing you need root privileges

2017-10-25 Thread Александр

Public bug reported:

when you try to install the application window appears informing you
need root privileges, enter your password, only responds to the close
button

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: lightdm 1.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 25 17:01:48 2017
InstallationDate: Installed on 2015-08-27 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: lightdm
UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)

** Affects: lightdm (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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1727306

Title:
  window appears informing you need root privileges

Status in lightdm package in Ubuntu:
  New

Bug description:
  when you try to install the application window appears informing you
  need root privileges, enter your password, only responds to the close
  button

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lightdm 1.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 17:01:48 2017
  InstallationDate: Installed on 2015-08-27 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)

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

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

[Touch-packages] [Bug 1727301] [NEW] 229-4ubuntu20 added ARP option breaks existing bonding interfaces

Public bug reported:

this breaks existing configurations with bonding on upgrading from
229-4ubuntu19 to 229-4ubuntu20 on xenial

as bond interfaces are now by default configured without ARP. Hence you
suddenly lose network connectivity on upgrade. Very bad for a SRU.

Plus adding "ARP=yes" to the Link section of a .network file does not
work.

Before this update, bond interfaces (specifically 802.3ad) were
defaulting to ARP enabled. After the upgrade, they are created with
NOARP set on the link.

pre-upgrade:

eth0: 
eth1: 
bond0: 

post-upgrade:
eth0: 
eth1: 
bond0: 

Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

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


** Tags: regression-updates

** Description changed:

+ this breaks existing configurations with bonding on upgrading from
+ 229-4ubuntu19 to 229-4ubuntu20 on xenial
  
- this breaks existing configurations with bonding on upgrading from 
229-4ubuntu19 to 229-4ubuntu20
- as bond interfaces are now by default configured without ARP. Hence you 
suddenly lose network connectivity on upgrade. Very bad for a SRU.
+ as bond interfaces are now by default configured without ARP. Hence you
+ suddenly lose network connectivity on upgrade. Very bad for a SRU.
  
  Plus adding "ARP=yes" to the Link section of a .network file does not
  work.
  
  Before this update, bond interfaces (specifically 802.3ad) were
  defaulting to ARP enabled. After the upgrade, they are created with
  NOARP set on the link.
  
  pre-upgrade:
  
  eth0: 
  eth1: 
  bond0: 
  
  post-upgrade:
  eth0: 
  eth1: 
  bond0: 
  
  Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  229-4ubuntu20 added ARP option breaks existing bonding interfaces

Status in systemd package in Ubuntu:
  New

Bug description:
  this breaks existing configurations with bonding on upgrading from
  229-4ubuntu19 to 229-4ubuntu20 on xenial

  as bond interfaces are now by default configured without ARP. Hence
  you suddenly lose network connectivity on upgrade. Very bad for a SRU.

  Plus adding "ARP=yes" to the Link section of a .network file does not
  work.

  Before this update, bond interfaces (specifically 802.3ad) were
  defaulting to ARP enabled. After the upgrade, they are created with
  NOARP set on the link.

  pre-upgrade:

  eth0: 
  eth1: 
  bond0: 

  post-upgrade:
  eth0: 
  eth1: 
  bond0: 

  Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

2017-10-25 Thread Andrea Azzarone

** Description changed:

+ Impact
+ ==
+ On artful every time gnome-control-center (goa panel) is used to add a google 
account, gnome-control-center crashes. This is one of the most reported crashes 
after the release.
+ 
+ Test Case
+ =
+ - Open gnome-control-center
+ - Go to online-account panel
+ - Add a Google online account.
+ - gnome-control-center should not crash while adding a google online account.
+ 
+ Regression Potential
+ ===
+ This is a minimal patch approved upsteam but not yet commited. Check if 
closing a gtk window/dialog creates no artifacts both on xorg and on wayland.
+ 
+ Original Bug Report
+ ===
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

Title:
  /usr/bin/gnome-control-
  
center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

Status in GTK+:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  Impact
  ==
  On artful every time gnome-control-center (goa panel) is used to add a google 
account, gnome-control-center crashes. This is one of the most reported crashes 
after the release.

  Test Case
  =
  - Open gnome-control-center
  - Go to online-account panel
  - Add a Google online account.
  - gnome-control-center should not crash while adding a google online account.

  Regression Potential
  ===
  This is a minimal patch approved upsteam but not yet commited. Check if 
closing a gtk window/dialog creates no artifacts both on xorg and on wayland.

  Original Bug Report
  ===
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1722564] Re: apport question will not accept multi-character responses

2017-10-25 Thread Francis Ginther

** Tags added: id-59ef68f44b84c4117299967c

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

Title:
  apport question will not accept multi-character responses

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Artful:
  In Progress

Bug description:
  the newly added cloud-init apport support shows a list of cloud
  providers and asks the user to select one.  There are currently 18
  options.  For any option > 10, apport will just take the '1' that is
  typed as the answer.

  It should obviously wait for more than one character or a carriage
  return.

  
  *** Please select the cloud vendor or environment in which this instance is 
running

  
  Choices:
1: Amazon - Ec2
2: AliYun
3: AltCloud
4: Azure
5: Bigstep
6: CloudSigma
7: CloudStack
8: DigitalOcean
9: GCE - Google Compute Engine
10: MAAS
11: NoCloud
12: OpenNebula
13: OpenStack
14: OVF
15: Scaleway
16: SmartOS
17: VMware
18: Other
C: Cancel
  Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 10 15:21:48 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1712921] Re: enabling networkd appears to eat up entropy

2017-10-25 Thread Francis Ginther

** Tags added: id-59e93e7ff29828fb76a5a779

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

Title:
  enabling networkd appears to eat up entropy

Status in nplan package in Ubuntu:
  In Progress
Status in openssh package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in nplan source package in Artful:
  In Progress
Status in openssh source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Triaged

Bug description:
  enabling networkd appears to eat up entropy

  as seen in openssh autopkgtest failing, when networkd is enabled by
  default.

  See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with
  triggers systemd/234-2ubuntu9

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

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

[Touch-packages] [Bug 839157] wow it's party time!

2017-10-25 Thread ZioTibia81

Hi,

Let  me invite someone to my party, it's going to be a surprise for my
children, here is the invitation
http://www.ledotex.ru/modules/blockuserinfo/img/icon/award.php?UE84MzkxNTdAYnVncy5sYXVuY2hwYWQubmV0

My Best, Stefano Danzi


From: Bug 839157 [mailto:839...@bugs.launchpad.net]
Sent: Wednesday, October 25, 2017 7:14 AM
To: ziotib...@libero.it
Subject: Ocelot

She wants you to  feel guilt. It's  how  she  keeps you in the role she
wants to see you play. Guilt is the only weapon my Ns  have  anymore,
and it's lost  most of it's effectiveness. All I ever have to  do is
remember  how they have done terrible things to my  husband when  he was
a child and never once expressed an ounce of remorse.


Sent from Mail for Windows 10

** Attachment added: "A7435C9644AEB554.jpg"
   
https://bugs.launchpad.net/bugs/839157/+attachment/4994317/+files/A7435C9644AEB554.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/839157

Title:
  Bluetooth applet (OBEX send/browse) does not work since Natty (after
  bluetoothd 4.84 exactly)

Status in bluez package in Ubuntu:
  Expired
Status in gnome-bluetooth package in Ubuntu:
  Invalid

Bug description:
  I have Ubuntu Natty 11.04 and a Nokia N81 (Symbian S60v3.1). In Ubuntu
  10.04 (Lucid) and 10.10 (Maverick) bluetooth file transfers do work
  fast and stable on my hardware. Since Natty it stopped working all
  together!

  UPDATE 26-2-2012: everything works again if the executable
  /usr/sbin/bluetoothd (4.91 in Natty) is replaced with 4.84 or earlier.
  I verified this workaround on several machines and with the Live-CD of
  Natty. Precise alpha 2 is affected too. (see also my comment 30 below)

  The attachment shows  the output of "sudo hcidump -XYt" when browsing
  fails (bluetooth-applet - menu -  - Browse files...)

  Running " bluetooth-applet -d" in a terminal and trying to browse and send 
files shows this:
  ** Message: adding killswitch idx 1 state KILLSWITCH_STATE_UNBLOCKED
  ** Message: adding killswitch idx 4 state KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitch 1 is KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitch 4 is KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED
  ** (bluetooth-applet:4108): DEBUG: Unhandled UUID 
111b--1000-8000-00805f9b34fb (0x111b)
  ** (bluetooth-applet:4108): DEBUG: Unhandled UUID 
5005--1000-8000-0002ee01 (0x5005)
  ** (bluetooth-applet:4108): DEBUG: Unhandled UUID 
5601--1000-8000-0002ee01 (0x5601)
  ** Message: killswitch 1 is KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitch 4 is KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED
  ** (bluetooth-sendto:4120): DEBUG: Unhandled UUID 
111b--1000-8000-00805f9b34fb (0x111b)
  ** (bluetooth-sendto:4120): DEBUG: Unhandled UUID 
5005--1000-8000-0002ee01 (0x5005)
  ** (bluetooth-sendto:4120): DEBUG: Unhandled UUID 
5601--1000-8000-0002ee01 (0x5601)

  And I saw interesting lines in /var/log/auth.log:
  oliverhp dbus-daemon: [system] Rejected send message, 2 matched rules; 
type="method_return", sender=":1.99" (uid=0 pid=3356 comm="/usr/sbin/bluetoothd 
--udev ") interface="(unset)" member="(unset)" error name="(unset)" 
requested_reply=0 destination=":1.139" (uid=1000 pid=3768 
comm="bluetooth-applet -d "))

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: bluez 4.91-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic i686
  Architecture: i386
  Date: Fri Sep  2 00:10:38 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
  MachineType: Hewlett-Packard HP Compaq nx8220 (PY517EA#ABD)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   LANGUAGE=de_CH:en
   PATH=(custom, user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic 
root=UUID=a4380962-8df8-486d-a8e3-2232227f97aa ro nosplash elevator=deadline
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DTV Ver. F.18
  dmi.board.name: 0934
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 43.1D
  dmi.chassis.asset.tag: oliverhp
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DTVVer.F.18:bd07/24/2009:svnHewlett-Packard:pnHPCompaqnx8220(PY517EA#ABD):pvrF.18:rvnHewlett-Packard:rn0934:rvrKBCVersion43.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx8220 (PY517EA#ABD)
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: BR/EDR  Bus:

[Touch-packages] [Bug 1726595] Re: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10

2017-10-25 Thread Andreas Hasenack

Most curious. It would be of tremendous help if you could find another
application that behaves like that, one that is opensource and part of
the ubuntu archive preferably.

DISPLAY being set to, for example, localhost:10.0, is indicating that
the X alls are going through ssh in that particular case. It's setup by
the -X parameter.

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

Title:
  Running Matlab (R) from ssh session with X forwarding doesn't work
  anymore in 17.10

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  OBSERVED BEHAVIOR:
  Matlab stays in busy state when using some functions like "plot" or even 
"exit", while executing through a ssh tunnel with X11 forwarding. 

  REPRODUCE THE BUG:

  You need matlab (my version is R2017a) to reproduce the bug. I suspect
  any version >= 2014b would reproduce the bug (HG2 framework), and
  maybe any version.

  1. Connect to self (or from other machine) with X forwarding:
  $ ssh -X user@localhost

  2. Launch matlab
  $ matlab &

  3. Plot something
  >> plot(1,1)

  ADDITIONAL INFORMATION
  - Normal behavior would be appearance of a new window and a single point at 
position (1,1). 
  - No ressources seem to be used. 
  - Opening a figure alone is possible. (>> figure). Opening other windows from 
the graphical user interface is possible 
  - Opening Matlab without the java machine seems to work, but matlab relies 
heavily on java. At least "exit" which doesn't work with java, works without 
java.
  - Providing Matlab with open-jdk version 1.8.0_144 didn't change anything.
  - This used to work perfectly for as long as I have been using Ubuntu (since 
2012).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: openssh-client 1:7.5p1-10
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Oct 23 17:44:23 2017
  ExecutablePath: /usr/bin/ssh
  InstallationDate: Installed on 2017-08-25 (59 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.0.2g  1 Mar 2016
  SourcePackage: openssh
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  modified.conffile..etc.ssh.ssh_config: [modified]
  mtime.conffile..etc.ssh.ssh_config: 2017-10-23T16:25:50.569560

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

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

[Touch-packages] [Bug 1727317] Re: systemd-journald crashed with SIGABRT in journal_file_find_data_object_with_hash()

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in
  journal_file_find_data_object_with_hash()

Status in systemd package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 12:53:01 2017
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2017-03-28 (210 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80MX
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   journal_file_find_data_object_with_hash () from 
/lib/systemd/libsystemd-shared-234.so
   ?? () from /lib/systemd/libsystemd-shared-234.so
   journal_file_append_entry () from /lib/systemd/libsystemd-shared-234.so
   ?? ()
   ?? ()
  Title: systemd-journald crashed with SIGABRT in 
journal_file_find_data_object_with_hash()
  UpgradeStatus: Upgraded to artful on 2017-10-20 (4 days ago)
  UserGroups:
   
  dmi.bios.date: 12/01/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DCCN34WW(V2.03)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo E31-80
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo E31-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrDCCN34WW(V2.03):bd12/01/2015:svnLENOVO:pn80MX:pvrLenovoE31-80:rvnLENOVO:rnLenovoE31-80:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE31-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MX
  dmi.product.version: Lenovo E31-80
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1727147] Re: [Dell Inspiron 20 - 3064] [Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter] [168c:0042] The bluetooth detection is gone with kernel 4.10.0-38-generic on z

2017-10-25 Thread Taihsiang Ho

After re-installing zesty twice, the BT is detectable. Should be a false
alarm.

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

Title:
  [Dell Inspiron 20 - 3064] [Qualcomm Atheros QCA9377 802.11ac Wireless
  Network Adapter] [168c:0042] The bluetooth detection is gone with
  kernel 4.10.0-38-generic on zesty

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When testing proposed kernel of zesty Linux 201606-22459
  4.10.0-38-generic #42-Ubuntu SMP Tue Oct 10 13:24:27 UTC 2017 x86_64
  x86_64 x86_64 GNU/Linux

  hciconfig did not output anything.

  More information:

  lspci -nn
  ..(skip)
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter [168c:0042] (rev 31)
  ..(skip)

  
  ubuntu@201606-22459:~$ lsmod | grep ath
  ath10k_pci 45056  0
  ath10k_core   348160  1 ath10k_pci
  ath28672  1 ath10k_core
  mac80211  782336  1 ath10k_core
  cfg80211  602112  3 mac80211,ath,ath10k_core

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Oct 24 23:02:24 2017
  InstallationDate: Installed on 2017-10-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=5959297f-2e3f-48a2-bd2f-5ed0caf54d65 ro rootdelay=60 quiet splash 
initcall_debug net.ifnames=0 vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Dell Inc.
  dmi.product.version: 1.0.1

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

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

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Fix Released
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

2017-10-25 Thread Chris J Arges

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

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  In Progress
Status in cloud-init source package in Xenial:
  New
Status in resolvconf source package in Xenial:
  New

Bug description:
  === Begin SRU Template ===
  [Impact] 
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
  the installation environment and also the rescue environment.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in 

http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  
  [Regression Potential] 
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.

  b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]
   
  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.

  ubuntu@manual:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE

[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-25 Thread Chris J Arges

Hello Pieter, 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.2 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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: Confirmed => Fix Committed

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

** Changed in: iproute2 (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed-trusty

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Committed
Status in iproute2 source package in Xenial:
  Fix Committed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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

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

2017-10-25 Thread Chris J Arges

Hello Pieter, or anyone else affected,

Accepted iproute2 into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/3.12.0-2ubuntu1.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-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. 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/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Committed
Status in iproute2 source package in Xenial:
  Fix Committed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread Ryan Beisner

** Tags added: uosci

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Fix Released
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

2017-10-25 Thread Scott Moser

** Description changed:

  === Begin SRU Template ===
- [Impact] 
+ [Impact]
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".
  
  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
  the installation environment and also the rescue environment.
  
  [Test Case]
  There are two tests for this.
  
  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'
  
  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
- described partially in 
-   
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README
+ described partially in
+   
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README
  
- 
- [Regression Potential] 
+ [Regression Potential]
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.
  
  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
- and these files have non-empty values for a variable mentioned above.
- (These files are written by the initramfs code when 'ip=' is seen).
+ and these files have non-empty values for a variable mentioned above.
+ (These files are written by the initramfs code when 'ip=' is seen).
  
  b.) this is not a container.
  
- b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
+ c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.
  
- c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
+ d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.
  
  [Other Info]
-  
+ 
  === End SRU Template ===
  
  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set with
  the DNS server.
  
  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:
  
  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  
  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0
  
  Which correctly includes the DNS server. However:
  
  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com
  
  If restart the interfacE:
  
  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  
  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.
  
  ubuntu@manual:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 192.168.122.2
  search maas
  
  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of data.
  64 bytes from mia07

[Touch-packages] [Bug 1725151] Re: not search in dropbox folders ubuntu 17.10

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

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

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

Title:
  not search in dropbox folders ubuntu 17.10

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  Tracker does not search in ubuntu shell 17.10 files from Dropbox
  folders. Only search files from all folders except files that are in
  dropbox folders.

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

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

[Touch-packages] [Bug 1727339] [NEW] Cups never prompts for username and password

2017-10-25 Thread Karl Kastner

Public bug reported:

To print over a network, I have to provide my credentials that differ
from those on my local workstation. This works, if as long as I hard
code the credentials into /etc/cups/printers.conf with "DeviceURI
smb://user:passowrd@printerurl". This is inconvenient, because I have to
change the password regularly and do not want to update the
printers.conf file every time. Cups should ask for the credentials when
the line "AuthInfoRequired username,password" is added to the printer
configuration, but this does not work for me. It were even better if
cups had a smart password save option, that tries first the old password
and prompts for a new one, whenever the old one does not work anymore.
This is a bug which annoys me since years, but never reported, because
there is the workaround.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4ubuntu0.3
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Oct 25 15:02:10 2017
InstallationDate: Installed on 2015-11-05 (720 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Lpstat:
 device for Lexmark_Lexmark_E232: usb://Lexmark/E232?serial=722DG57
 device for printer: smb://scomp5170/WURprinter_PS_Color
 device for Ricoh-MP-C5503: smb://scomp5170/WURprinter_PS_Color
 device for SCX-470x-Series: 
usb://Samsung/SCX-470x%20Series?serial=Z79JBADC200505H&interface=1
MachineType: Notebook W230SS
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=2329e937-a4e4-4efc-a999-c0fa7d44c92b ro uveau.modeset=0 
acpi_enforce_resources=lax nosplash uveau.modeset=0 acpi_enforce_resources=lax 
acpi_enforce_resources=lax
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W230SS
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: W230SS
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

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


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  Cups never prompts for username and password

Status in cups package in Ubuntu:
  New

Bug description:
  To print over a network, I have to provide my credentials that differ
  from those on my local workstation. This works, if as long as I hard
  code the credentials into /etc/cups/printers.conf with "DeviceURI
  smb://user:passowrd@printerurl". This is inconvenient, because I have
  to change the password regularly and do not want to update the
  printers.conf file every time. Cups should ask for the credentials
  when the line "AuthInfoRequired username,password" is added to the
  printer configuration, but this does not work for me. It were even
  better if cups had a smart password save option, that tries first the
  old password and prompts for a new one, whenever the old one does not
  work anymore. This is a bug which annoys me since years, but never
  reported, because there is the workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 25 15:02:10 2017
  InstallationDate: Installed on 2015-11-05 (720 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lpstat:
   device for Lexmark_Lexmark_E232: usb://Lexmark/E232?serial=722DG57
   device for printer: smb://scomp5170/WURprinter_PS_Color
   device for Ricoh-MP-C5503: smb://scomp5170/WURprinter_PS_Color
   device for SCX-470x-Series: 
usb://Samsung/SCX-470x%20Series?serial=Z79JBADC200505H&interface=1
  MachineType: Notebook W230SS
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=2329e937-a4e4-4efc-a999-c0fa7d44c92b ro uveau.modeset=0 
acpi_enforce_resources=lax nosplash uveau.modeset=0 acpi_enforce_resources=lax 
acpi_enforce_resources=lax
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.versio

[Touch-packages] [Bug 1726395] Re: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell DE

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-screensaver should be removed from ubuntu-desktop Recommends
  because it isn't needed for Gnome Shell DE

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  gnome-screensaver should be removed from ubuntu-desktop Recommends because it 
isn't needed for Gnome Shell Desktop Environment.
  It's 5 years old software (latest release 2012-10-16) and is needed only for 
old GNOME flashback (fallback) session.
  Gnome-screensaver shouldn't be running on GNOME Shell - users can't unlock 
the screen because of important bugs in gnome-screensaver, see bug #1716278 and 
bug #1699670 (Gnome screensaver lock always responses "incorrect password" when 
last active window's language is not the language of the password) for example.

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

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

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

2017-10-25 Thread Scott Moser

I updated some state on the tasks. As justification, this fix is in
resolvconf, so I dropped cloud-init. I had added it thinking it might
need integration, but it did not. Also marked the 'ubuntu' task as
"won't fix". The problem did not currently exist in Artful, and the
solution provided in resolvconf is not relevant there as resolvconf is
not used in Artful.

** No longer affects: cloud-init (Ubuntu)

** No longer affects: cloud-init (Ubuntu Xenial)

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

** Changed in: resolvconf (Ubuntu)
Status: In Progress => Won't Fix

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

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

Title:
[2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
Fix Committed
Status in resolvconf package in Ubuntu:
Won't Fix
Status in resolvconf source package in Xenial:
Confirmed

Bug description:
=== Begin SRU Template ===
[Impact]
Without this fix applied, dns settings provided to the dhcp response
in the initramfs are not reflected in the "real root".

Thus dns resolution does not work. Of most interest was the MAAS use
case of the 'root=http://<>/squashfs' use case. MAAS 2.3 uses this for
the installation environment and also the rescue environment.

[Test Case]
There are two tests for this.

a.) local/non-MAAS test
Download the test case attached.
Run it and follow the instructions.
Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
without the fix there would be no data in /etc/resolv.conf. With the
fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

b.) MAAS test.
For the full maas test, you need to build a image stream for maas
with the fix included in the squashfs image and then import that
stream to maas and use the rescue environment and verify dns.
This process is beyond the scope of the SRU template, but is
described partially in
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

[Regression Potential]
Regression potential should be very low. There are gates in the code
to make sure that this code is inactive other than when it is explicitly
enabled.

net-interface-handler will exit without doing anything unless:
a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
and these files have non-empty values for a variable mentioned above.
(These files are written by the initramfs code when 'ip=' is seen).

b.) this is not a container.

c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
if open-iscsi has written this file due to open-iscsi root, then it
will handle this functionality. resolvconf will get out of the way.

d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
This lowers the scope of changes in runtime to cases with where either the
new flag is seen or cloud-config-url is passed. The MAAS use case will
contain this flag.

[Other Info]

=== End SRU Template ===

Using MAAS 2.3, during commissioning (and likely in the rest of the
ephemeral environment) we have noticed that resolv.conf is not set
with the DNS server.

That said, during the commissioning process, MAAS does not send any
metadata to cloud-init to configure the network, rather, we expect the
image to boot from the network via DHCP. So, cloud-init writes:

ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback

# control-manual ens3
iface ens3 inet dhcp
broadcast 192.168.122.255
dns-nameservers 192.168.122.2
gateway 192.168.122.1
netmask 255.255.255.0

Which correctly includes the DNS server. However:

ubuntu@manual:~$ ping google.com
ping: unknown host google.com

If restart the interfacE:

ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
ifdown: interface ens3 not configured
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/ens3/52:54:00:ea:57:31
Sending on LPF/ens3/52:54:00:ea:57:31
Sending on Socket/fallback
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port

[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later

2017-10-25 Thread Doug Smythies

Further to my comment #32: That setup then breaks lots of stuff if I
subsequently boot a normal default kernel (i.e. 4.4.0-96-generic). I'm
going back to just booting with apparmor disabled.

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

Title:
  apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"
  w/ 4.14-rc2 and later

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Confirmed
Status in apparmor source package in Zesty:
  Confirmed
Status in apparmor source package in Artful:
  Confirmed

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor
  2.10.95-0ubuntu2.7, in the system log each second the error message
  below is printed to.

  ```
  […]
  [Mi Okt  4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  […]
  ```

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

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

[Touch-packages] [Bug 1727350] [NEW] os ubuntu 16.04

2017-10-25 Thread gianni

Public bug reported:

non riesco ad entrare nelle pagine internet e non ad aprire le icone dei 
programmi.scrive lento-
grazie.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Oct 25 15:40:19 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:184a]
 Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
InstallationDate: Installed on 2015-07-20 (828 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=c2b360dd-7125-486f-911b-14f23fa0bc6b ro 
plymouth:debug=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1 
drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 184A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.35
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd02/21/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn184A:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 088B1130591620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Oct 25 13:58:46 2017
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: radeon

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


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

Title:
  os ubuntu 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  non riesco ad entrare nelle pagine internet e non ad aprire le icone dei 
programmi.scrive lento-
  grazie.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 25 15:40:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:184a]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2015-07-20 (828 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=c2b360dd-7125-486f-911b-14f23fa0bc6b ro 
plymouth:debug=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh insta

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread Drew Freiberger

re: init-system-helpers, I noticed the oddity of the init script on a
systemd system as well and found that there's a systemd hack in /lib/lsb
/init-functions.d/40-systemd that allows for multi-startup
compatibility.  I believe invoke-rc.d should check systemd
"enabled/disabled" state instead of just the S/K links in /etc/rcX.d.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  New
Status in pacemaker source package in Xenial:
  Fix Released
Status in init-system-helpers source package in Zesty:
  New
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  New
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  New
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions

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

[Touch-packages] [Bug 1721116] Re: tracker-extract using 700MB-1GB+ of RAM

2017-10-25 Thread Colin Law

I am seeing this with Ubuntu 17.04, using Gnome Shell.

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

Title:
  tracker-extract using 700MB-1GB+ of RAM

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  BEHAVIOR
  The tracker service (showing as "tracker-extract" in the GNOME System 
Monitor) shows that it's using anywhere from 700MB to 1.1GB of RAM. This seems 
like a lot.

  EXPECTED BEHAVIOR
  Tracker uses much less RAM.

  Bug reported using:
  Tracker 2.0.0
  Ubuntu 17.10 beta 2
  Linux kernel 4.13.0-12-generic

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

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

[Touch-packages] [Bug 1668724] Re: fails to mount cgroupfs inside containers running on 16.04

2017-10-25 Thread ChristianEhrhardt

This was removed from Xenial-Proposed as well.
It is still in Y-proposed but that is EOL.


Given the time that has passed and the rather unclear state I'd consider this 
bug incomplete.
In comment #29 Serge outlined that for Trusty all of that not really applies 
(everyone is using backports there?)

I'll update the bug tasks to reflect all that.

@Serge - Please update if you still work on this or have a fix
somewhere.

** Changed in: cgroup-lite (Ubuntu Yakkety)
   Status: Fix Committed => Won't Fix

** Changed in: cgroup-lite (Ubuntu Xenial)
   Status: Fix Committed => Incomplete

** Changed in: cgroup-lite (Ubuntu Trusty)
   Status: New => Incomplete

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

Title:
  fails to mount cgroupfs inside containers running on 16.04

Status in cgroup-lite package in Ubuntu:
  Fix Released
Status in cgroup-lite source package in Precise:
  Won't Fix
Status in cgroup-lite source package in Trusty:
  Incomplete
Status in cgroup-lite source package in Xenial:
  Incomplete
Status in cgroup-lite source package in Yakkety:
  Won't Fix

Bug description:
  I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
  and have noticed that the cgroups-mount script for mounting the
  cgroups inside the containers has stopped working. This is because
  systemd now comounts multiple controllers on a single hierarchy, which
  prevents mounting them individually inside the container.

  ===  SRU Justification 
  Impact: nested containers fail to start
  Reproduce:  create a root owned container;  install lxc and cgroup-lite;  
create a container, and try to start it.  Starting will fail if cgroup-lite is 
running in the first level container without this patch.
  Regression potential:  should be low, it's possible that the regexp is simply 
wrong for some cases.
  ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+subscriptions

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

[Touch-packages] [Bug 1726595] Re: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10

2017-10-25 Thread thomas duriez

I will try. For the moment I double boot 16.04 because I need to have it
working, but I can run tests on spare time. Because I couldn't find
problems when not running the java machine of Matlab  I will focus on
applications relying heavily on java. If you have any suggestion it
would help. Thanks again for your time.

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

Title:
  Running Matlab (R) from ssh session with X forwarding doesn't work
  anymore in 17.10

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  OBSERVED BEHAVIOR:
  Matlab stays in busy state when using some functions like "plot" or even 
"exit", while executing through a ssh tunnel with X11 forwarding. 

  REPRODUCE THE BUG:

  You need matlab (my version is R2017a) to reproduce the bug. I suspect
  any version >= 2014b would reproduce the bug (HG2 framework), and
  maybe any version.

  1. Connect to self (or from other machine) with X forwarding:
  $ ssh -X user@localhost

  2. Launch matlab
  $ matlab &

  3. Plot something
  >> plot(1,1)

  ADDITIONAL INFORMATION
  - Normal behavior would be appearance of a new window and a single point at 
position (1,1). 
  - No ressources seem to be used. 
  - Opening a figure alone is possible. (>> figure). Opening other windows from 
the graphical user interface is possible 
  - Opening Matlab without the java machine seems to work, but matlab relies 
heavily on java. At least "exit" which doesn't work with java, works without 
java.
  - Providing Matlab with open-jdk version 1.8.0_144 didn't change anything.
  - This used to work perfectly for as long as I have been using Ubuntu (since 
2012).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: openssh-client 1:7.5p1-10
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Oct 23 17:44:23 2017
  ExecutablePath: /usr/bin/ssh
  InstallationDate: Installed on 2017-08-25 (59 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.0.2g  1 Mar 2016
  SourcePackage: openssh
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  modified.conffile..etc.ssh.ssh_config: [modified]
  mtime.conffile..etc.ssh.ssh_config: 2017-10-23T16:25:50.569560

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

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

[Touch-packages] [Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

How are eth0/eth1/bond0 configured?
Do you use netplan and networkd?
Do you use ifupdown?

Can you paste the output of $ networkctl?

Copies of the configuration e.g.:

/etc/network/interfaces
/etc/network/interfaces.d/*
/etc/netplan/*
/run/systemd/network/*
/etc/systemd/network/*

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

Title:
  229-4ubuntu20 added ARP option breaks existing bonding interfaces

Status in systemd package in Ubuntu:
  New

Bug description:
  this breaks existing configurations with bonding on upgrading from
  229-4ubuntu19 to 229-4ubuntu20 on xenial

  as bond interfaces are now by default configured without ARP. Hence
  you suddenly lose network connectivity on upgrade. Very bad for a SRU.

  Plus adding "ARP=yes" to the Link section of a .network file does not
  work.

  Before this update, bond interfaces (specifically 802.3ad) were
  defaulting to ARP enabled. After the upgrade, they are created with
  NOARP set on the link.

  pre-upgrade:

  eth0: 
  eth1: 
  bond0: 

  post-upgrade:
  eth0: 
  eth1: 
  bond0: 

  Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1727363] [NEW] Wayland dock "crash" after thumb (horizontal) scroll

You have been subscribed to a public bug:

I'm using Ubuntu 17.10 with 3 monitors (I don't know if this is relevant)
I don't know if this is the right place to leave this issue.
The problem is very simple to reproduce if you have a Logitech MX Master mouse: 
if you make a horizontal scroll through the "thumb scroll wheel", the icons on 
the wayland dock will disappear. To display them again, you need to restart the 
session.
If you tell me where I can pick a log, I'll be happy to provide it.

Sorry for my english.
Regards

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

-- 
Wayland dock "crash" after thumb (horizontal) scroll
https://bugs.launchpad.net/bugs/1727363
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wayland in Ubuntu.

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

[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

2017-10-25 Thread Jim Hodapp

Isak: yeah same here, that usually has to do with bluez still querying
for other devices in the background and sucking up all of the channel
bandwidth. It really needs someone to investigate if we can get bluez to
not consume so much bandwidth, or make the query period more context
sensitive such that it only happens when the BT settings UI is shown or
explicitly told to query for new devices on the command line.

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

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

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

[Touch-packages] [Bug 1727363] [NEW] Wayland dock "crash" after thumb (horizontal) scroll

2017-10-25 Thread Mirko

Public bug reported:

I'm using Ubuntu 17.10 with 3 monitors (I don't know if this is relevant)
I don't know if this is the right place to leave this issue.
The problem is very simple to reproduce if you have a Logitech MX Master mouse:
if you make a horizontal scroll through the "thumb scroll wheel", the icons on
the wayland dock will disappear. To display them again, you need to restart the
session.
If you tell me where I can pick a log, I'll be happy to provide it.

Sorry for my english.
Regards

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

** Attachment added: "Screenshot of the "crashed" dock"

https://bugs.launchpad.net/bugs/1727363/+attachment/4994571/+files/Schermata%20del%202017-10-25%2016-24-23.png

** Description changed:

+ I'm using Ubuntu 17.10.
I don't know if this is the right place to leave this issue, i will try.
The problem is very simple to reproduce if you have a Logitech MX Master
mouse: if you make a horizontal scroll through the "thumb scroll", the icons on
the wayland dock will disappear. To display them again, you need to restart the
session.
If you tell me where I can pick a log, I'll be happy to provide it.

Sorry for my english.
Regards

** Description changed:

- I'm using Ubuntu 17.10.
+ I'm using Ubuntu 17.10 with 3 monitors (I don't know if this is relevant)
I don't know if this is the right place to leave this issue, i will try.
The problem is very simple to reproduce if you have a Logitech MX Master
mouse: if you make a horizontal scroll through the "thumb scroll", the icons on
the wayland dock will disappear. To display them again, you need to restart the
session.
If you tell me where I can pick a log, I'll be happy to provide it.

Sorry for my english.
Regards

** Description changed:

I'm using Ubuntu 17.10 with 3 monitors (I don't know if this is relevant)
- I don't know if this is the right place to leave this issue, i will try.
+ I don't know if this is the right place to leave this issue.
The problem is very simple to reproduce if you have a Logitech MX Master
mouse: if you make a horizontal scroll through the "thumb scroll", the icons on
the wayland dock will disappear. To display them again, you need to restart the
session.
If you tell me where I can pick a log, I'll be happy to provide it.

Sorry for my english.
Regards

** Description changed:

I'm using Ubuntu 17.10 with 3 monitors (I don't know if this is relevant)
I don't know if this is the right place to leave this issue.
- The problem is very simple to reproduce if you have a Logitech MX Master
mouse: if you make a horizontal scroll through the "thumb scroll", the icons on
the wayland dock will disappear. To display them again, you need to restart the
session.
+ The problem is very simple to reproduce if you have a Logitech MX Master
mouse: if you make a horizontal scroll through the "thumb scroll wheel", the
icons on the wayland dock will disappear. To display them again, you need to
restart the session.
If you tell me where I can pick a log, I'll be happy to provide it.

Sorry for my english.
Regards

** Summary changed:

- Wayland dock "crash" after thumb scroll
+ Wayland dock "crash" after thumb (horizontal) scroll

** Package changed: gnome-session (Ubuntu) => wayland (Ubuntu)

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

Title:
Wayland dock "crash" after thumb (horizontal) scroll

Status in wayland package in Ubuntu:
New

Bug description:
I'm using Ubuntu 17.10 with 3 monitors (I don't know if this is relevant)
I don't know if this is the right place to leave this issue.
The problem is very simple to reproduce if you have a Logitech MX Master
mouse: if you make a horizontal scroll through the "thumb scroll wheel", the
icons on the wayland dock will disappear. To display them again, you need to
restart the session.
If you tell me where I can pick a log, I'll be happy to provide it.

Sorry for my english.
Regards

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

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

[Touch-packages] [Bug 1726340] Re: Please add 'dkms' to the dependency list

2017-10-25 Thread dino99

** Description changed:

  Fresh netboot install
  
  I have lost too much time fighting against stupid issues after the first 
installation reboot:
  - third party apps not listed into the menu
  - graphic issue
+ - appimage not installable (miss gconf-service)
  - ...
  
  and finally have glanced at missing 'important' packages, like 'dkms,
- tweaks, dconf' ...
+ tweaks, dconf, gconf-service' ...
  
  not everyone knows about such url: http://www.omgubuntu.co.uk/2017/10
  /things-to-do-after-installing-ubuntu-17-10
  
  at least, if you do not add those to the 'recommended' list, then add
  them to the missing 'suggest' one.
  
  Make our Ubuntu great again.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 23 11:49:08 2017
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Please add 'dkms' to the dependency list

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Fresh netboot install

  I have lost too much time fighting against stupid issues after the first 
installation reboot:
  - third party apps not listed into the menu
  - graphic issue
  - appimage not installable (miss gconf-service)
  - ...

  and finally have glanced at missing 'important' packages, like 'dkms,
  tweaks, dconf, gconf-service' ...

  not everyone knows about such url: http://www.omgubuntu.co.uk/2017/10
  /things-to-do-after-installing-ubuntu-17-10

  at least, if you do not add those to the 'recommended' list, then add
  them to the missing 'suggest' one.

  Make our Ubuntu great again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 23 11:49:08 2017
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

2017-10-25 Thread Balint Reczey

** Summary changed:

- By default settings unattended-upgrade is unable to automatically remove 
packages that become unused in conjunction with updating by other software.
+ By default settings unattended-upgrade does not automatically remove packages 
that become unused in conjunction with updating by other software

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

** Changed in: unattended-upgrades (Ubuntu Artful)
   Status: New => Confirmed

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => Opinion

** Changed in: unattended-upgrades (Ubuntu Artful)
   Status: Confirmed => Opinion

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  Opinion
Status in update-manager source package in Artful:
  New

Bug description:
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path

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

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

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

Title:
  [17.10 regression] AppArmor denial: Failed name lookup - disconnected
  path

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  
  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1726595] Re: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10

2017-10-25 Thread Andreas Hasenack

Ah, Java, I hadn't realised that. I have a couple a
I can try too with ssh -X.

On Oct 25, 2017 12:31, "thomas duriez" <1726...@bugs.launchpad.net>
wrote:

> I will try. For the moment I double boot 16.04 because I need to have it
> working, but I can run tests on spare time. Because I couldn't find
> problems when not running the java machine of Matlab  I will focus on
> applications relying heavily on java. If you have any suggestion it
> would help. Thanks again for your time.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1726595
>
> Title:
>   Running Matlab (R) from ssh session with X forwarding doesn't work
>   anymore in 17.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/
> 1726595/+subscriptions
>

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

Title:
  Running Matlab (R) from ssh session with X forwarding doesn't work
  anymore in 17.10

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  OBSERVED BEHAVIOR:
  Matlab stays in busy state when using some functions like "plot" or even 
"exit", while executing through a ssh tunnel with X11 forwarding. 

  REPRODUCE THE BUG:

  You need matlab (my version is R2017a) to reproduce the bug. I suspect
  any version >= 2014b would reproduce the bug (HG2 framework), and
  maybe any version.

  1. Connect to self (or from other machine) with X forwarding:
  $ ssh -X user@localhost

  2. Launch matlab
  $ matlab &

  3. Plot something
  >> plot(1,1)

  ADDITIONAL INFORMATION
  - Normal behavior would be appearance of a new window and a single point at 
position (1,1). 
  - No ressources seem to be used. 
  - Opening a figure alone is possible. (>> figure). Opening other windows from 
the graphical user interface is possible 
  - Opening Matlab without the java machine seems to work, but matlab relies 
heavily on java. At least "exit" which doesn't work with java, works without 
java.
  - Providing Matlab with open-jdk version 1.8.0_144 didn't change anything.
  - This used to work perfectly for as long as I have been using Ubuntu (since 
2012).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: openssh-client 1:7.5p1-10
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Oct 23 17:44:23 2017
  ExecutablePath: /usr/bin/ssh
  InstallationDate: Installed on 2017-08-25 (59 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.0.2g  1 Mar 2016
  SourcePackage: openssh
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  modified.conffile..etc.ssh.ssh_config: [modified]
  mtime.conffile..etc.ssh.ssh_config: 2017-10-23T16:25:50.569560

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

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

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

2017-10-25 Thread Balint Reczey

Changed to title to reflect that the issue is not about something not
implemented, but something not set as default.

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  Opinion
Status in update-manager source package in Artful:
  New

Bug description:
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

2017-10-25 Thread Balint Reczey

s/to title/the title/

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  Opinion
Status in update-manager source package in Artful:
  New

Bug description:
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1462740] Re: Wifi intermittently stops working since 15.04 upgrade

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

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

Title:
  Wifi intermittently stops working since 15.04 upgrade

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to 15.04 a couple of weeks ago I have been finding
  that sometimes my wifi completely stops working. Restarting network
  manager doesn't help, nor does removing and reinserting the wireless
  driver. I can get network access through an ethernet cable.

  Another, possibly related problem I have been experiencing since
  upgrading to 15.04 is that sometimes wpa_supplicant starts hogging
  CPU, up to 100% on one core. When I kill it, the replacement instance
  of wpa_supplicant continues to hog the CPU. I am not sure whether this
  is caused by the same fault that is causing my wifi to fail. As I send
  this error report, my machine is in such a crippled state with no wifi
  and wpa_supplicant slowing everything to a crawl. I noticed that
  wpa_supplicant was misbehaving only after I had tried removing and
  reinserting the wifi driver, so I don't know whether the wifi failure
  problem caused wpa_supplicant to go bananas, or whether it was the
  fact that I had messed about with the driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: wpasupplicant 2.1-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-lowlatency 3.19.6
  Uname: Linux 3.19.0-18-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun  7 15:01:56 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-06 (93 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to vivid on 2015-05-29 (8 days ago)

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

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

[Touch-packages] [Bug 1435120] Re: hostapd doesn't work with kernels after 3.13.0-26

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

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

Title:
  hostapd doesn't work with kernels after 3.13.0-26

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  work just fine with kernel 3.13.0-26. with 3.13.0-40 and higher (up to
  3.13.0-55) hostapd starting without errors, but AP does nоt appear on
  devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: hostapd 1:2.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Mar 23 11:55:15 2015
  InstallationDate: Installed on 2013-05-15 (676 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to trusty on 2014-05-20 (307 days ago)
  mtime.conffile..etc.default.hostapd: 2014-09-17T17:49:41.076640

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

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

[Touch-packages] [Bug 1347831] Re: hostapd is missing 802.11ac mode support

My understanding is that this is no longer an issue with the current
hostapd.

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

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

Title:
  hostapd is missing 802.11ac mode support

Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  When I try to create an AP using 802.11ac hostapd complains about
  unknown configuration items.

  I have a Compex acWave WLE900VX mini-pcie card that's fully supported
  by the ath10k_pci module.

  I took the example hostapd.conf settings from kernel.org ath10k page:
  http://wireless.kernel.org/en/users/Drivers/ath10k/configuration

  -- start hostapd.conf ---
  interface=wlan0
  driver=nl80211
  ssid=ath10k-test
  hw_mode=a
  channel=36
  ht_capab=[HT40+]
  ieee80211n=1
  ieee80211ac=1
  vht_oper_chwidth=1
  vht_oper_centr_freq_seg0_idx=42
  --- end hostapd.conf ---

  sudo hostapd -dd hostapd.conf
  random: Trying to read entropy from /dev/random
  Configuration file: hostapd.conf
  Line 10: unknown configuration item 'ieee80211ac'
  Line 11: unknown configuration item 'vht_oper_chwidth'
  Line 12: unknown configuration item 'vht_oper_centr_freq_seg0_idx'
  3 errors found in configuration file 'hostapd.conf'

  The solution is to add the following to the ./configure file at
  compile time:

  "CONFIG_IEEE80211AC=y"

  As 802.11ac picks up in popularity everyone is going to want this
  support.

  Thank you!

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

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

[Touch-packages] [Bug 1670494] Re: 'wpa_supplicant -D nl80211 -W' hangs with some Intel cards

I understand this bug will be fixed when Marc rebased Ubuntu wpa package
on top of the Debian's.

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

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

Title:
  'wpa_supplicant -D nl80211 -W' hangs with some Intel cards

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  init_wpa_supplicant() in /etc/wpa_supplicant/functions.sh runs
  wpa_supplicant with the -W option, which causes it to wait for wpa_cli
  to attach.  init_wpa_supplicant() then attaches wpa_cli to
  wpa_supplicant.

  When the nl80211 driver is used with some Intel cards, wpa_supplicant
  automatically defines a second p2p_dev_${WPA_IFACE} interface.  If
  multiple interfaces are defined in wpa_supplicant, then wpa_supplicant
  will wait for multiple wpa_cli instances to attach.  Since
  init_wpa_supplicant() only attaches a single wpa_cli process, this
  causes wpa_supplicant to hang, which ultimately leads to a timeout and
  causes interface configuration to fail.

  This has been fixed upstream: 
http://lists.infradead.org/pipermail/hostap/2015-December/034410.html
  And also in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833402

  However, the updated wpa_supplicant has not made it to Ubuntu (not
  even Zesty), and the "-m ''" workaround mentioned in the mailing list
  thread associated with the upstream fix does not work with the version
  of wpa_supplicant that comes with Ubuntu.

  Could the P2P patches that were merged into Debian be merged into
  Ubuntu?

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

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

[Touch-packages] [Bug 1668724] Re: fails to mount cgroupfs inside containers running on 16.04

2017-10-25 Thread Serge Hallyn

I'll still aim to push this for trusty and xenial.

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

Title:
  fails to mount cgroupfs inside containers running on 16.04

Status in cgroup-lite package in Ubuntu:
  Fix Released
Status in cgroup-lite source package in Precise:
  Won't Fix
Status in cgroup-lite source package in Trusty:
  Incomplete
Status in cgroup-lite source package in Xenial:
  Incomplete
Status in cgroup-lite source package in Yakkety:
  Won't Fix

Bug description:
  I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
  and have noticed that the cgroups-mount script for mounting the
  cgroups inside the containers has stopped working. This is because
  systemd now comounts multiple controllers on a single hierarchy, which
  prevents mounting them individually inside the container.

  ===  SRU Justification 
  Impact: nested containers fail to start
  Reproduce:  create a root owned container;  install lxc and cgroup-lite;  
create a container, and try to start it.  Starting will fail if cgroup-lite is 
running in the first level container without this patch.
  Regression potential:  should be low, it's possible that the regexp is simply 
wrong for some cases.
  ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+subscriptions

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

[Touch-packages] [Bug 1668724] Re: fails to mount cgroupfs inside containers running on 16.04

2017-10-25 Thread Serge Hallyn

Drat.  I do think this should still be pushed.  I don't know when I'll
have time to do it though.  Please keep it open.

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

Title:
  fails to mount cgroupfs inside containers running on 16.04

Status in cgroup-lite package in Ubuntu:
  Fix Released
Status in cgroup-lite source package in Precise:
  Won't Fix
Status in cgroup-lite source package in Trusty:
  Incomplete
Status in cgroup-lite source package in Xenial:
  Incomplete
Status in cgroup-lite source package in Yakkety:
  Won't Fix

Bug description:
  I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
  and have noticed that the cgroups-mount script for mounting the
  cgroups inside the containers has stopped working. This is because
  systemd now comounts multiple controllers on a single hierarchy, which
  prevents mounting them individually inside the container.

  ===  SRU Justification 
  Impact: nested containers fail to start
  Reproduce:  create a root owned container;  install lxc and cgroup-lite;  
create a container, and try to start it.  Starting will fail if cgroup-lite is 
running in the first level container without this patch.
  Regression potential:  should be low, it's possible that the regexp is simply 
wrong for some cases.
  ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+subscriptions

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

[Touch-packages] [Bug 1591533] Re: Can't create Ad-Hoc WiFi connection

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

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

Title:
  Can't create Ad-Hoc WiFi connection

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to create Ad-Hoc WiFi connection from BQ Aquaris M10 Ubuntu 
Edition to Nokia N900, running Qt Mobile Hotspot.
  My desktop PC connects ok, but Ubuntu Touch can't connect with message:
  wlan0: Association request to the driver failed

  I've tried unpotected and WEP protected connection.

  As a consequence to this failure, tablet reboots when next time
  connecting to normal infrastructure AP.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: wpasupplicant 2.4-0ubuntu7~overlay3
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Sat Jun 11 18:49:04 2016
  InstallationDate: Installed on 2016-05-24 (18 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160524-114757)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1251134] Re: wpa_supplicant crashes when coming out of suspend

** Changed in: wpa (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  wpa_supplicant crashes when coming out of suspend

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  Whenever (although possibly not every single time) I come out of
  suspend (i.e. reopening the lid of my laptop) I get a system error
  that wpa_supplicant has crashed. The next time I come out of suspend
  (although sometimes on that occassion) the wireless doesn't reconnect.
  I then need to restart my machine to get the wireless to reconnect.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: wpasupplicant 1.0-3ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 14 07:02:39 2013
  InstallationDate: Installed on 2012-08-17 (453 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: wpa
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (26 days ago)

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

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

[Touch-packages] [Bug 1399888] Re: Wireless network connection terminates and won't reconnect

This is for an outdated version of wpa-supplicant, closing.

** Changed in: wpa (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Wireless network connection terminates and won't reconnect

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  On: Linux x 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 12:06:54 UTC
  2014 x86_64 x86_64 x86_64 GNU/Linux

  Wireless connections terminate without obvious reason. A reconnect is
  not possible.

  Every now and then (every second day) the network connection drops.
  The network indicator shows no signal strenght (empty icon)

  The correct connection is selected, a wealth of other SSIDs are in the
  list.

  A reconnect opens up the password dialog (which is an indication that the old 
error was reintroduced into the code).
  I reported this bug several times. The reason at the time was that 
reconnection would try to fetch the encrypted password and reencrypt it leading 
to a wrong password.

  There is a workaround:
  Disabling and Enabling the network connection reconnects correctly. In the 
code (as I analyzed then), this is due to the fact that the password from 
searing is taken as is and forwarded to the authentication code (not 
reencrypted). The connection gets established again.

  This issue did not occur in 12.04 and 12.10 (due to less connection
  problems or due to a fix is beyond me, I simple confirmed there were
  no connection aborts). It reappeared in 13.x and now is back as an
  annoyance.

  The error numbers then were around 460.000 - 490.000 as far is I
  remember (I have deleted bug reports I considered solved).

  I observed this issue on any Ubuntu machine. I also observed that the
  list of SSIDs is extremely long when this incident arises (approx. 15
  - 20). Maybe a storm of SSID broadcasts is the basic cause but I have
  not done any research beyond what I described here.

  Hope this gets fixed for good now.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: wpasupplicant 2.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec  6 10:27:42 2014
  InstallationDate: Installed on 2013-05-17 (567 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac 
(20130424)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1124789] Re: Unclean termination on dbus-daemon shutdown

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

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

Title:
  Unclean termination on dbus-daemon shutdown

Status in hostap:
  Fix Released
Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  When wpa_supplicant is terminated normally (i.e. with SIGTERM or
  SIGINT or 'wpa_cli terminate'), it brings down any wireless interfaces
  it is managing.  However, if wpa_supplicant is started by dbus
  activation and if the dbus messagebus is then shut down, it terminates
  abruptly and improperly without deconfiguring any network interfaces.

  Note that wpa_supplicant has its PID file installed in
  /run/sendsigs.omit.d, so /etc/init.d/sendsigs makes no attempt to shut
  it down. Since wpa_supplicant is not supervised by upstart, it is
  typical for dbus-daemon to be shut down before wpa_supplicant is.

  This has been reported upstream (along with steps to reproduce and a patch) 
at:
    http://w1.fi/bugz/show_bug.cgi?id=474

  This bug, along with bug 1124803 (in network-manager), means that when I 
connect my laptop to a wifi network, no attempt is made to disconnect from that 
network when shutting the system down. This in turn triggers a bug in my BIOS 
which causes this system to hardlock in the middle of BIOS post when I reboot 
while still connected to a wifi network:
    http://thread.gmane.org/gmane.linux.kernel.wireless.general/102862

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: wpasupplicant 1.0-2ubuntu5
  ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
  Uname: Linux 3.5.0-24-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Wed Feb 13 22:12:08 2013
  MarkForUpload: True
  SourcePackage: wpa
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (116 days ago)

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

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

[Touch-packages] [Bug 1242431] Re: ignores TPTK; can't verify EAPOL-Key integrity

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

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

Title:
  ignores TPTK; can't verify EAPOL-Key integrity

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  ioctl[SIOCSIWENCODEEXT]: Invalid argument
  ioctl[SIOCSIWENCODEEXT]: Invalid argument
  ioctl[SIOCSIWSCAN]: Device or resource busy
  wlan0: Failed to initiate AP scan
  wlan0: Trying to associate with $BSSID (SSID=$BSSID freq=2462 MHz)
  ioctl[SIOCSIWFREQ]: Device or resource busy
  wlan0: Association request to the driver failed
  wlan0: Associated with $BSSID
  wlan0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
  wlan0: WPA: Could not verify EAPOL-Key MIC - dropping packet
  ^C
  # wl
  ioctl[SIOCSIWENCODEEXT]: Invalid argument
  ioctl[SIOCSIWENCODEEXT]: Invalid argument
  wlan0: Trying to associate with 00:22:6b:fc:89:53 (SSID='HringidanET' 
freq=2462 MHz)
  ioctl[SIOCSIWFREQ]: Device or resource busy
  wlan0: Association request to the driver failed
  wlan0: Associated with 00:22:6b:fc:89:53
  wlan0: WPA: Key negotiation completed with 00:22:6b:fc:89:53 [PTK=CCMP 
GTK=TKIP]
  wlan0: CTRL-EVENT-CONNECTED - Connection to 00:22:6b:fc:89:53 completed 
(auth) [id=1 id_str=]

  [time passes]
  wlan0: WPA: Group rekeying completed with $BSSID [GTK=TKIP]

  On the first invocation of wpa_supplicant (by site-local script wl),
  the message integrity code (MIC) check fails repeatedly. But after an
  interrupt, a second invocation (the last two times I tried) succeeded
  immediately. Rekeying usually succeeds.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: wpasupplicant 1.0-3ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic i686
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  Date: Sun Oct 20 20:03:08 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-03-05 (229 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcEnviron:
   TERM=rxvt
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=is_IS.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: Upgraded to raring on 2013-05-06 (167 days ago)

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

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

[Touch-packages] [Bug 1396820] Re: Wireless stopped working after upgrade

This is for an outdated version of wpa-supplicant, closing.

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

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

Title:
  Wireless stopped working after upgrade

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 14.04 connection to the wireless was hardly
  possible. After downgrading the wpasupplicant package to
  1.0-3ubuntu2-mtrudel1 wireless connection was restored.

  System is Ubuntu 14.04.1 LTS on a HP Presario CQ71.

  Sorry I could only send the bug report from the 'repaired' system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: wpasupplicant 1.0-3ubuntu2~mtrudel1
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 27 00:25:52 2014
  InstallationDate: Installed on 2014-01-12 (318 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (221 days ago)

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

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

[Touch-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

** Changed in: wpa (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in wpa package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 LTS
  wpasupplicant 2.1-0ubuntu1

  wpa_supplicant is writing to syslog every couple of minutes. Example
  output:

  May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ 
wlan0: CTRL-EVENT-SCAN-STARTED ]
  May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33

  The message seems harmless as far as the network is concerned, meaning
  there is no problem with the wifi connection. But it's spamming the
  syslog, making it very difficult to find any other thing there, and
  it's generating constant writes to disk, and an unnecessarily large
  syslog file.

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

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

[Touch-packages] [Bug 1293279] Re: computer freezes completely

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

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

Title:
  computer freezes completely

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  Im running Ubuntu 13.10 saucy on a Dell Inspiron 15R 5521. The
  computer completely freezes with no aparent reason. After looking at
  the log, the following message appears consistently just before the
  crash:

  wpa_supplicant[1085]: wlan0: WPA: Group rekeying completed with
  84:c9:b2:d3:b2:89 [GTK=CCMP]

  These are the log messages around the crash (manually forced restart
  at 19:59:52):

  Mar 16 19:28:22 pina wpa_supplicant[1085]: wlan0: WPA: Group rekeying 
completed with 84:c9:b2:d3:b2:89 [GTK=CCMP]
  Mar 16 19:29:05 pina whoopsie[1076]: online
  Mar 16 19:29:06 pina whoopsie[1076]: online
  Mar 16 19:35:02 pina whoopsie[1076]: online
  Mar 16 19:37:02 pina whoopsie[1076]: online
  Mar 16 19:38:07  whoopsie[1076]: last message repeated 3 times
  Mar 16 19:38:08 pina whoopsie[1076]: online
  Mar 16 19:38:22 pina wpa_supplicant[1085]: wlan0: WPA: Group rekeying 
completed with 84:c9:b2:d3:b2:89 [GTK=CCMP]
  Mar 16 19:38:46 pina whoopsie[1076]: online
  Mar 16 19:39:59  whoopsie[1076]: last message repeated 2 times
  Mar 16 19:42:09 pina whoopsie[1076]: online
  Mar 16 19:44:09 pina whoopsie[1076]: online
  Mar 16 19:44:10 pina whoopsie[1076]: online
  Mar 16 19:47:10 pina whoopsie[1076]: online
  Mar 16 19:48:11  whoopsie[1076]: last message repeated 3 times
  Mar 16 19:48:22 pina wpa_supplicant[1085]: wlan0: WPA: Group rekeying 
completed with 84:c9:b2:d3:b2:89 [GTK=CCMP]
  Mar 16 19:48:40 pina whoopsie[1076]: online
  Mar 16 19:49:59  whoopsie[1076]: last message repeated 2 times
  Mar 16 19:51:16 pina whoopsie[1076]: online
  Mar 16 19:51:17 pina whoopsie[1076]: online
  Mar 16 19:56:23 pina whoopsie[1076]: online
  Mar 16 19:57:13 pina whoopsie[1076]: online
  Mar 16 19:59:52 pina kernel: imklog 5.8.11, log source = /proc/kmsg started.
  Mar 16 19:59:52 pina rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" 
x-pid="753" x-info="http://www.rsyslog.com";] start
  Mar 16 19:59:52 pina rsyslogd: rsyslogd's groupid changed to 103
  Mar 16 19:59:52 pina rsyslogd: rsyslogd's userid changed to 101
  Mar 16 19:59:52 pina rsyslogd-2039: Could not open output pipe 
'/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]

  I don't know if the following is useful but if I see the log in a text
  editor, I can see a lot of "NULL" characters, something like:

  Mar 16 19:28:22 pina wpa_supplicant[1085]: wlan0: WPA: Group rekeying 
completed with 84:c9:b2:d3:b2:89 [GTK=CCMP]
  Mar 16 19:29:05 pina whoopsie[1076]: online
  Mar 16 19:29:06 pina whoopsie[1076]: online
  Mar 16 19:35:02 pina whoopsie[1076]: online
  Mar 16 19:37:02 pina whoopsie[1076]: online
  Mar 16 19:38:07  whoopsie[1076]: last message repeated 3 times
  Mar 16 19:38:08 pina whoopsie[1076]: online
  Mar 16 19:38:22 pina wpa_supplicant[1085]: wlan0: WPA: Group rekeying 
completed with 84:c9:b2:d3:b2:89 [GTK=CCMP]
  Mar 16 19:38:46 pina whoopsie[1076]: online
  Mar 16 19:39:59  whoopsie[1076]: last message repeated 2 times
  Mar 16 19:42:09 pina whoopsie[1076]: online
  Mar 16 19:44:09 pina whoopsie[1076]: online
  Mar 16 19:44:10 pina whoopsie[1076]: online
  Mar 16 19:47:10 pina whoopsie[1076]: online
  Mar 16 19:48:11  whoopsie[1076]: last message repeated 3 times
  Mar 16 19:48:22 pina wpa_supplicant[1085]: wlan0: WPA: Group rekeying 
completed with 84:c9:b2:d3:b2:89 [GTK=CCMP]
  Mar 16 19:48:40 pina whoopsie[1076]: online
  Mar 16 19:49:59  whoopsie[1076]: last message repeated 2 times
  Mar 16 19:51:16 pina whoopsie[1076]: online
  Mar 16 19:51:17 pina whoopsie[1076]: online
  Mar 16 19:56:23 pina whoopsie[1076]: online
  Mar 16 19:57:13 pina whoopsie[1076]: online
  
NULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLMar
 16 19:59:52 pina kernel: imklog 5.8.11, log source = /proc/kmsg started.
  Mar 16 19:59:52 pina rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" 
x-pid="753" x-info="http://www.rsyslog.com";] start
  Mar 16 19:59:52 pina rsyslogd: rsyslogd's groupid changed to 103
  Mar 16 19:59:52 pina rsyslogd: rsyslogd's userid changed to 101
  Mar 16 19:59:52 pina rsyslogd-2039: Could not open output pipe 
'/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]

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

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

[Touch-packages] [Bug 1317221] Re: wireless no connection after upgrade from 13.10 to 14.0o4

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

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

Title:
  wireless no connection after upgrade from 13.10 to 14.0o4

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  After upgrade from Kubuntu 13.10 to 14.04 network is still seen, and 
connection continues to be initialized, but is never established.
  After having replaced binary /sbin/wpa_supplicant (version 2.1) by 
/sbin/wpa_supplicant (version 1.0 of Kubuntu 13.10) everything seems to be 
running again smoothly.
  Appended is 1. network configuration and 2. debug output of wpa_supplicant 
v2.1.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: wpasupplicant 2.1-0ubuntu1 [modified: sbin/wpa_supplicant]
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed May  7 19:39:12 2014
  InstallationDate: Installed on 2011-09-30 (950 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
  ProcEnviron:
   LANGUAGE=en_GB:de:es:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (19 days ago)

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

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

[Touch-packages] [Bug 1456221] Re: while installing regional settings

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

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

Title:
  while installing regional settings

Status in wpa package in Ubuntu:
  Invalid

Bug description:
  I just tried to install additional language pack

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: wpasupplicant 2.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  AptdaemonVersion: 1.1.1-1ubuntu5.1
  Architecture: amd64
  CrashReports:
   600:111:116:0:2015-05-18 15:39:26.381760672 +0200:2015-05-18 
15:39:26.381760672 +0200:/var/crash/rsyslog.0.uploaded
   600:0:116:207779:2015-05-18 15:34:47.344107389 +0200:2015-05-18 
15:34:48.344107389 +0200:/var/crash/network-manager.0.crash
   640:0:116:1587420:2015-05-18 15:39:23.263367891 +0200:2015-05-18 
15:39:25.286591098 +0200:/var/crash/rsyslog.0.crash
   600:0:116:207759:2015-05-18 15:34:47.332113265 +0200:2015-05-18 
15:34:48.332113265 +0200:/var/crash/wpasupplicant.0.crash
   644:0:116:0:2015-05-18 15:39:24.607106916 +0200:2015-05-18 
15:39:24.607106916 +0200:/var/crash/rsyslog.0.upload
  Date: Mon May 18 15:34:48 2015
  DuplicateSignature: package:wpasupplicant:2.1-0ubuntu1.2:package 
wpasupplicant is already installed and configured
  ErrorMessage: package wpasupplicant is already installed and configured
  InstallationDate: Installed on 2015-05-18 (0 days ago)
  InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323)
  SourcePackage: wpa
  Title: package wpasupplicant 2.1-0ubuntu1.2 failed to install/upgrade: 
package wpasupplicant is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1503448] Re: package wpasupplicant 2.1-0ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

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

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

Title:
  package wpasupplicant 2.1-0ubuntu1.3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in wpa package in Ubuntu:
  Invalid

Bug description:
  Failed to install software updates

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: wpasupplicant 2.1-0ubuntu1.3
  ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  Date: Tue Oct  6 17:49:32 2015
  DuplicateSignature: package:wpasupplicant:2.1-0ubuntu1.3:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2013-02-02 (976 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: wpa
  Title: package wpasupplicant 2.1-0ubuntu1.3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-08-25 (406 days ago)

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

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

[Touch-packages] [Bug 1727390] [NEW] New bugfix release 17.2.3

2017-10-25 Thread Timo Aaltonen

Public bug reported:

[Impact]

A new upstream bugfix release is available.

FILL

[Test case]

[Regression potential]

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

** Affects: mesa (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: mesa (Ubuntu Artful)
 Importance: Undecided
 Status: New

** Summary changed:

- New bugfix release
+ New bugfix release 17.2.3

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

** Also affects: mesa (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

Title:
  New bugfix release 17.2.3

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  [Impact]

  A new upstream bugfix release is available.

  FILL

  [Test case]

  [Regression potential]

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

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

[Touch-packages] [Bug 1718027] Re: RM: obsolete product

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

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

Title:
  RM: obsolete product

Status in libusermetrics package in Ubuntu:
  Triaged

Bug description:
  libusermetrics was a component of Ubuntu Phone which is no longer
  developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:libusermetrics
  No reverse dependencies found

  $ reverse-depends -b src:libusermetrics
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1646364] Re: fsprotect fails to install on 16.04 server

2017-10-25 Thread Steffen Hemer

Today again stumbled over this problem after initramfs-tools had an
upgrade and nvidia dkms driver wanted to be configured. I have to apply
the mentioned fix every time again since Xenial was released. This is
annoying: can some one backport the mentioned fix from 0.122 ???

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

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

Title:
  fsprotect fails to install on 16.04 server

Status in fsprotect package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  After an apt-get install on a clean 16.04 server install, fsprotect
  fails like so:

  (This is from the second try, but it is exactly the same)

  user@computer:~$ sudo apt-get install fsprotect
  [sudo] password for user: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  fsprotect is already the newest version (1.0.6).
  0 to upgrade, 0 to newly install, 0 to remove and 9 not to upgrade.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up initramfs-tools (0.122ubuntu8.5) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.122ubuntu8.5) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-21-generic
  cp: failed to access '/var/tmp/mkinitramfs_ewwYu8//bin/touch': Too many 
levels of symbolic links
  E: /usr/share/initramfs-tools/hooks/fsprotect failed with return 1.
  update-initramfs: failed for /boot/initrd.img-4.4.0-21-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  user@computer:~$ 

  If I comment out the last line of /usr/share/initramfs-tools/hooks/fsprotect
  #copy_exec /usr/bin/touch "/bin"

  This will happen

  user@computer:~$sudo apt-get install fsprotect 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  fsprotect is already the newest version (1.0.6).
  0 to upgrade, 0 to newly install, 0 to remove and 9 not to upgrade.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up initramfs-tools (0.122ubuntu8.5) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.122ubuntu8.5) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-21-generic
  W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
  user@computer:~$

  I modified /etc/default/grub to make fsprotect active "fsprotect=1G"

  Reboot, and fixed!!!

  uname -a: Linux computer 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 
18:33:37 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
  lsb_release -rd:  Description:Ubuntu 16.04.1 LTS
Release:16.04
  apt-cache policy fsprotect:
fsprotect:
Installed: 1.0.6
Candidate: 1.0.6
Version table:
*** 1.0.6 500
500 http://au.archive.ubuntu.com/ubuntu xenial/universe 
amd64 Packages
500 http://au.archive.ubuntu.com/ubuntu xenial/universe 
i386 Packages
100 /var/lib/dpkg/status

  ubuntu-bug report:
  ProblemType: Bug
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Dec  1 16:11:14 2016
  Dependencies:
   adduser 3.113+nmu3ubuntu4
   apt 1.2.15
   apt-utils 1.2.15
   busybox-initramfs 1:1.22.0-15ubuntu1
   coreutils 8.25-2ubuntu2
   cpio 2.11+dfsg-5ubuntu1
   debconf 1.5.58ubuntu1
   debconf-i18n 1.5.58ubuntu1
   debianutils 4.7
   dpkg 1.18.4ubuntu1.1
   e2fslibs 1.42.13-1ubuntu1
   e2fsprogs 1.42.13-1ubuntu1
   gcc-5-base 5.4.0-6ubuntu1~16.04.4
   gcc-6-base 6.0.1-0ubuntu1
   gnupg 1.4.20-1ubuntu3.1
   gpgv 1.4.20-1ubuntu3.1
   init-system-helpers 1.29ubuntu3
   initramfs-tools 0.122ubuntu8.5
   initramfs-tools-bin 0.122ubuntu8.5
   initramfs-tools-core 0.122ubuntu8.5
   initscripts 2.88dsf-59.3ubuntu2
   insserv 1.14.0-5ubuntu3
   klibc-utils 2.0.4-8ubuntu1.16.04.2
   kmod 22-1ubuntu4
   libacl1 2.2.52-3
   libapt-inst2.0 1.2.15
   libapt-pkg5.0 1.2.15
   libattr1 1:2.4.47-2
   libaudit-common 1:2.4.5-1ubuntu2
   libaudit1 1:2.4.5-1ubuntu2
   libblkid1 2.27.1-6ubuntu3.1
   libbz2-1.0 1.0.6-8
   libc6 2.23-0ubuntu4
   libcomerr2 1.42.13-1ubuntu1
   libdb5.3 5.3.28-11
   libfdisk1 2.27.1-6ubuntu3.1
   libgcc1 1:6.0.1-0ubuntu1
   libgcrypt20 1.6.5-2ubuntu0.2
   libgpg-error0 1.21-2ubuntu1
   libgpm2 1.20.4-6.1
   libklibc 2.0.4-8ubuntu1.16.04

[Touch-packages] [Bug 1364104] Re: wpasupplicant is haaving bug wifi connected but no web connectivity

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

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

Title:
  wpasupplicant is haaving bug wifi connected but no web connectivity

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  I have ASUS NE pce-n5 card installed. The net gets connected Active
  connection information is ok, but there is no net connectivity.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: wpasupplicant 2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep  1 17:27:00 2014
  InstallationDate: Installed on 2014-05-02 (122 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1289047] Re: [Trusty] hostapd package is broken

You can't have the same device managed by both hostapd and network-
manager.

** Changed in: wpa (Ubuntu)
   Status: Triaged => Invalid

** Changed in: hundredpapercuts
   Status: Triaged => Invalid

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

Title:
  [Trusty] hostapd package is broken

Status in One Hundred Papercuts:
  Invalid
Status in wpa package in Ubuntu:
  Invalid

Bug description:
  When trying to create an access point, I am met with a fatal error
  with hostapd:

  nl80211: Could not configure driver mode
  nl80211 driver initialization failed.
  hostapd_free_hapd_data: Interface wlan0 wasn't started

  What worked before no longer works today after a package upgrade.

  After installing hostapd deb from Ubuntu 13.10, it works.

  WORKAROUND: For this to persist through reboots, execute the following in a 
terminal:
  sudo nano /etc/NetworkManager/NetworkManager.conf

  Add the following entry where the x's are replaced with your WiFi MAC 
address, save, and then reboot:
  [keyfile]
  unmanaged-devices=mac:xx:xx:xx:xx:xx:xx

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: hostapd 1:2.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc5-lowlatency x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Thu Mar  6 16:57:20 2014
  InstallationDate: Installed on 2014-02-01 (33 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1713710] Re: RM: obsolete product

** Changed in: click-apparmor (Ubuntu)
   Importance: Undecided => High

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

Title:
  RM: obsolete product

Status in click-apparmor package in Ubuntu:
  Triaged

Bug description:
  click-apparmor was a component of Ubuntu Phone which is no longer
  developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:click-apparmor
  No reverse dependencies found

  $ reverse-depends -b src:click-apparmor
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1630839] Re: Request for applying a patch to support OpenVSwitch in hostapd

Please submit the patch upstream and have it merged there.

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

Title:
  Request for applying a patch to support OpenVSwitch in  hostapd

Status in wpa package in Ubuntu:
  New

Bug description:
  Hello Devs,

  I'm requesting the patch https://github.com/helmut-
  jacob/hostapd/commit/c89daaeca4ee90c8bc158e37acb1b679c823d7ab to be
  applied in hostapd in Ubuntu. I compiled wpa-2.4 from Ubuntu sources
  with the attached patch and worked well with ath9k_htc + OpenVSwitch
  from Ubuntu 16.04.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hostapd 1:2.4-0ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct  5 23:40:38 2016
  InstallationDate: Installed on 2016-01-14 (266 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to xenial on 2016-05-13 (145 days ago)
  modified.conffile..etc.default.hostapd: [modified]
  mtime.conffile..etc.default.hostapd: 2016-10-05T00:16:08.475114

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

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

[Touch-packages] [Bug 1718022] Re: RM: obsolete product