date:20170927

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

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

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

Title:
  sudoers not honoring hostnames

Status in hostname package in Ubuntu:
  Confirmed

Bug description:
  New Kubuntu 16.04 install, adding features from previous 15.04
  install. Added exact copy of /etc/sudoers.d/apt from 15.04 to 16.04
  but it does not work as expected. File contents:

  myusername myhostname = NOPASSWD: /usr/bin/apt, /usr/bin/apt-get,
  /usr/bin/add-apt-repository

  results in 15.04 in user "myusername" being able to run apt, apt-get,
  and add-apt-repository from the CLI using sudo without a password
  prompt. However, same exact syntax in 16.04 results in password
  prompt.

  In the 16.04 install, changing "myhostname" to "ALL" resumes the no
  password behavior. Both installs have exact same /etc/hosts files,
  running on bare metal on the same system, and the "hostname" command
  results in the same reply with the correct hostname. I have compared
  the subject files several times and there are no differences. No
  errors editing any of the files using visudo. Permissions and syntax
  same on both systems.

  This leads me to conclude sudoers is not honoring the hostname in the
  sudoers file(s).

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

-- 
Mailing list: https://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 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.

On Wed, Sep 27, 2017 at 08:36:13PM -, Balint Reczey wrote:
> On Wed, Sep 27, 2017 at 2:42 PM, Julian Andres Klode
>  wrote:
> > Hmm, I thought we would not do that anymore, and packages get marked as
> > manual when removing a meta package, but I might be missing something.
> 
> I ran this on zesty, but if meta packages are handled differently then
> I could imagine a similar
> case when meta packages are not involved.

I ran the same metapackage removal test on Xenial, so if Julian is right
and this is a regression its a rather old one. Do you have any more
details about your thoughts Julian?

--
Brian Murray

-- 
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 is unable to 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:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in gnome-software source package in Artful:
  New
Status in unattended-upgrades source package in Artful:
  New
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 1718717] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

2017-09-27 Thread Bug Watch Updater

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

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in CUPS:
  New
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  after updates of cups-filter and reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 21 17:43:42 2017
  ExecutablePath: /usr/sbin/cupsd
  Lpstat:
   device for HP-LaserJet-4200: hp:/net/hp_LaserJet_4200?ip=192.168.10.21
   device for PDF: cups-pdf:/
  MachineType: Dell Inc. OptiPlex 960
  Papersize: a4
  PpdFiles:
   PDF: Generic CUPS-PDF Printer (w/ options)
   HP-LaserJet-4200: HP LaserJet 4200 Series Postscript (recommended)
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f32dc0c7954 : cmpq   
$0x0,(%rdi)
   PC (0x7f32dc0c7954) ok
   source "$0x0" ok
   destination "(%rdi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: Upgraded to artful on 2017-09-19 (2 days ago)
  UserGroups:
   
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0Y958C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0Y958C:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1582950] Re: broken apport hook: TypeError: a bytes-like object is required, not 'str'

** Changed in: apport (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  broken apport hook: TypeError: a bytes-like object is required, not
  'str'

Status in apport package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  The apport hook for ubiquity appears broken. (Ignore the Wnck error,
  that's bug 1580412).

  $ ubuntu-bug ubiquity
  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
  dpkg-query: no packages found matching ubiquity
  ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 61, in 
add_info
  if 'Buffer I/O error on device' in syslog:
  TypeError: a bytes-like object is required, not 'str'

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 17 17:31:33 2016
  InstallationDate: Installed on 2012-10-18 (1307 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: ubiquity
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (17 days ago)

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

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

[Touch-packages] [Bug 1582950] Re: broken apport hook: TypeError: a bytes-like object is required, not 'str'

** Branch linked: lp:~ubuntu-core-dev/ubuntu/artful/apport/ubuntu

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

Title:
  broken apport hook: TypeError: a bytes-like object is required, not
  'str'

Status in apport package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  The apport hook for ubiquity appears broken. (Ignore the Wnck error,
  that's bug 1580412).

  $ ubuntu-bug ubiquity
  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
  dpkg-query: no packages found matching ubiquity
  ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 61, in 
add_info
  if 'Buffer I/O error on device' in syslog:
  TypeError: a bytes-like object is required, not 'str'

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 17 17:31:33 2016
  InstallationDate: Installed on 2012-10-18 (1307 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: ubiquity
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (17 days ago)

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

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

[Touch-packages] [Bug 1720019] [NEW] org.PulseAudio1 was not provided by any .service files

2017-09-27 Thread jimav

Public bug reported:

Whenever a program starts which uses audio many errors appear in syslog
like these:

indicator-sound[1922]: message repeated 15 times: [ volume-control-
pulse.vala:735: unable to get pulse unix socket:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.PulseAudio1 was not provided by any .service files]

unity-panel-ser[2249]: track_menus: assertion 'IS_WINDOW_MENU(menus)' failed
Sep 27 14:46:23 lxjima indicator-sound[1922]: volume-control-pulse.vala:735: 
unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files

STEPS TO REPRODUCE:

1. tail -f /var/log/syslog (in another terminal). 
2. Start firefox, chromium, or audacity

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity:Unity7
Date: Wed Sep 27 14:48:15 2017
InstallationDate: Installed on 2017-01-19 (251 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to zesty on 2017-07-26 (63 days ago)
dmi.bios.date: 09/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1408
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6T
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1408:bd09/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug zesty

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

Title:
  org.PulseAudio1 was not provided by any .service files

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Whenever a program starts which uses audio many errors appear in
  syslog like these:

  indicator-sound[1922]: message repeated 15 times: [ volume-control-
  pulse.vala:735: unable to get pulse unix socket:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.PulseAudio1 was not provided by any .service files]

  unity-panel-ser[2249]: track_menus: assertion 'IS_WINDOW_MENU(menus)' failed
  Sep 27 14:46:23 lxjima indicator-sound[1922]: volume-control-pulse.vala:735: 
unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files

  STEPS TO REPRODUCE:

  1. tail -f /var/log/syslog (in another terminal). 
  2. Start firefox, chromium, or audacity

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Wed Sep 27 14:48:15 2017
  InstallationDate: Installed on 2017-01-19 (251 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to zesty on 2017-07-26 (63 days ago)
  dmi.bios.date: 09/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1408
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T
  dmi.board.vendor: ASUSTeK Computer INC.

[Touch-packages] [Bug 1709500] Re: [UIFe] Headerbar buttons that are highlighted/coloured in Adwaita are not coloured at all in Ambiance.

2017-09-27 Thread Gunnar Hjalmarsson

This is fine from a docs POV. Unfortunately we don't ship any Ubuntu
specific screenshots in the 17.10 desktop guide.

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

Title:
  [UIFe] Headerbar buttons that are highlighted/coloured in Adwaita are
  not coloured at all in Ambiance.

Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in ubuntu-themes source package in Artful:
  Confirmed

Bug description:
  Using Ambiance on artful, the "action buttons" used in GtkHeaderBar
  are using a color similar to bar background which makes them not stand
  out. One example is the file-roller extract dialog, when using Adwaita
  the "extract" button is blue which make it an obvious click target,
  that's not the case under our themes

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

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

[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

2017-09-27 Thread Jeremy Bicha

Doug, this bug is mentioned in the release notes:

https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes/#Desktop

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

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

Status in gdm3 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

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

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

[Touch-packages] [Bug 1655982] Re: cups-browsed fails to start in containers after apparmor stacking backport to xenial

2017-09-27 Thread Emily Ratliff

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

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

Title:
  cups-browsed fails to start in containers after apparmor stacking
  backport to xenial

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  The SRU of apparmor stacking for the Ubuntu 16.04 LTS kernel causes a
  regression in cups-browsed (shipped by cups) which now fails to start
  and gets respawned in a loop by systemd until it completely gives up.

  To reproduce:
   - lxc launch ubuntu:16.04 xen
   - lxc exec xen -- apt update
   - lxc exec xen -- apt dist-upgrade -y
   - lxc exec xen -- apt install cups -y

  You'll get:

  root@xen:~# systemctl status cups-browsed
  ● cups-browsed.service - Make remote CUPS printers available locally
 Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: signal) since Thu 2017-01-12 14:09:38 UTC; 8min ago
   Main PID: 7725 (code=killed, signal=SEGV)

  Jan 12 14:09:38 xen systemd[1]: Started Make remote CUPS printers available 
locally.
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=11/SEGV
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Unit entered failed 
state.
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Failed with result 
'signal'.


  And in dmesg (in a loop):
  [95217.312576] audit: type=1400 audit(1484230171.171:1004): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=16941 comm="apparmor_parser"
  [95217.313011] audit: type=1400 audit(1484230171.171:1005): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cupsd" pid=16941 comm="apparmor_parser"
  [95217.313202] audit: type=1400 audit(1484230171.171:1006): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cupsd//third_party" pid=16941 comm="apparmor_parser"
  [95218.126005] audit: type=1400 audit(1484230171.983:1007): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17074 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95218.126018] audit: type=1400 audit(1484230171.983:1008): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17074 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95222.686493] audit: type=1400 audit(1484230176.542:1009): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17553 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95222.686624] audit: type=1400 audit(1484230176.542:1010): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17553 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95224.324494] audit: type=1400 audit(1484230178.182:1011): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cups-browsed" pid=17681 comm="apparmor_parser"
  [95224.610016] audit: type=1400 audit(1484230178.466:1012): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cups-browsed" name="/run/systemd/journal/stdout" pid=17765 
comm="cups-browsed" requested_mask="wr" denied_mask="wr" fsuid=10 
ouid=10
  [95224.610029] audit: type=1400 audit(1484230178.466:1013): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cups-browsed" name="/run/systemd/journal/stdout" pid=17765 
comm="cups-browsed" requested_mask="wr" denied_mask="wr" fsuid=10 
ouid=10
  [95224.610046] audit: type=1400 audit(1484230178.466:1014): apparmor="DENIED" 
operation="file_mmap" namespace="root//lxd-xen_" 
profile="/usr/sbin/cups-browsed" name="/usr/sbin/cups-browsed" pid=17765 
comm="cups-browsed" requested_mask="rm" denied_mask="rm" fsuid=10 
ouid=10

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

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

[Touch-packages] [Bug 1719934] Re: Missing fonts in list of languages

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)

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

Title:
  Missing fonts in list of languages

Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  There is a font missing on the ISO and one of the language is shown as
  unicode characters (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 11:22:24 2017
  InstallationDate: Installed on 2013-09-03 (1484 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  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/1719934/+subscriptions

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

[Touch-packages] [Bug 1539995] Re: apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

** Tags removed: rls-aa-incoming
** Tags added: rls-bb-incoming

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

Title:
  apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

Status in apport package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Partial Upgrade failed (crash)
  Ubuntu Mate 16 Alpha install testing on different machines.
  This machine Dell Optiplex 960

  linuxpusher@linuxpusher-OptiPlex-960:~$ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  
  linuxpusher@linuxpusher-OptiPlex-960:~$ sudo lshw
  [sudo] password for linuxpusher: 
  linuxpusher-optiplex-960  
  description: Computer
  width: 64 bits
  capabilities: smbios-2.5 vsyscall32
*-core
 description: Motherboard
 physical id: 0
   *-memory
description: System memory
physical id: 0
size: 7819MiB
   *-cpu
product: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
vendor: Intel Corp.
physical id: 1
bus info: cpu@0
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl 
aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 xsave lahf_lm dtherm tpr_shadow vnmi flexpriority
   *-pci
description: Host bridge
product: 4 Series Chipset DRAM Controller
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 03
width: 32 bits
clock: 33MHz
configuration: driver=agpgart-intel
resources: irq:0
  *-display:0
   description: VGA compatible controller
   product: 4 Series Chipset Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:33 memory:fe80-febf 
memory:d000-dfff ioport:ecb0(size=8)
  *-display:1 UNCLAIMED
   description: Display controller
   product: 4 Series Chipset Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2.1
   bus info: pci@:00:02.1
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: pm bus_master cap_list
   configuration: latency=0
   resources: memory:fe70-fe7f
  *-communication:0
   description: Communication controller
   product: 4 Series Chipset HECI Controller
   vendor: Intel Corporation
   physical id: 3
   bus info: pci@:00:03.0
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi bus_master cap_list
   configuration: driver=mei_me latency=0
   resources: irq:34 memory:feda6000-feda600f
  *-ide
   description: IDE interface
   product: 4 Series Chipset PT IDER Controller
   vendor: Intel Corporation
   physical id: 3.2
   bus info: pci@:00:03.2
   version: 03
   width: 32 bits
   clock: 66MHz
   capabilities: ide pm msi bus_master cap_list
   configuration: driver=ata_generic latency=0
   resources: irq:18 ioport:fe80(size=8) ioport:fe90(size=4) 
ioport:fea0(size=8) ioport:feb0(size=4) ioport:fef0(size=16)
  *-communication:1
   description: Serial controller
   product: 4 Series Chipset Serial KT Controller
   vendor: Intel Corporation
   physical id: 3.3
   bus info: pci@:00:03.3
   version: 03
   width: 32 bits
   clock: 66MHz
   capabilities: pm msi 16550 bus_master cap_list
   configuration: driver=serial latency=0
   resources: irq:17 ioport:ecb8(size=8) memory:fe6d8000-fe6d8fff
  *-network
   description: Ethernet interface
   product: 82567LM-3 Gigabit Network Connection
   vendor: Intel Corporation
   physical id: 19
   bus info: pci@:00:19.0
   logical name: enp0s25
   version: 02

[Touch-packages] [Bug 1720010] [NEW] can't log into Gnome - terminal or Unity work fine

2017-09-27 Thread Jurgen Gaeremyn

Public bug reported:

When launching my computer, I get the login screen. On entering my
password, I get a small flicker of the screen and am not logged in. I
can log in using the terminal (Alt-F2).

Inspection of /var/log/auth.log suggests that interface, member and some
other data are not correctly transmitted from the login manager to
systemd-logind.

After installing Unity, I can log into unity.

When reading /var/log/auth.log, I see these lines:

Sep 27 20:48:32 bigmomma dbus[764]: [system] Rejected send message, 2 matched 
rules; type="error", sender=":1.0" (uid=0 pid=739 
comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error 
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" 
destination=":1.24" (uid=121 pid=948 comm="/usr/bin/gnome-shell ")
Sep 27 20:48:32 bigmomma dbus[764]: message repeated 18 times: [ [system] 
Rejected send message, 2 matched rules; type="error", sender=":1.0" (uid=0 
pid=739 comm="/lib/systemd/systemd-logind ") interface="(unset)" 
member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" 
requested_reply="0" destination=":1.24" (uid=121 pid=948 
comm="/usr/bin/gnome-shell ")]
Sep 27 21:17:01 bigmomma CRON[3642]: pam_unix(cron:session): session opened for 
user root by (uid=0)
Sep 27 21:17:01 bigmomma CRON[3642]: pam_unix(cron:session): session closed for 
user root
Sep 27 22:17:01 bigmomma CRON[3686]: pam_unix(cron:session): session opened for 
user root by (uid=0)
Sep 27 22:17:01 bigmomma CRON[3686]: pam_unix(cron:session): session closed for 
user root
Sep 27 22:40:25 bigmomma dbus[764]: [system] Rejected send message, 2 matched 
rules; type="error", sender=":1.0" (uid=0 pid=739 
comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error 
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" 
destination=":1.24" (uid=121 pid=948 comm="/usr/bin/gnome-shell ")
Sep 27 22:40:25 bigmomma dbus[764]: message repeated 18 times: [ [system] 
Rejected send message, 2 matched rules; type="error", sender=":1.0" (uid=0 
pid=739 comm="/lib/systemd/systemd-logind ") interface="(unset)" 
member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" 
requested_reply="0" destination=":1.24" (uid=121 pid=948 
comm="/usr/bin/gnome-shell ")]
Sep 27 22:40:36 bigmomma gdm-password]: pam_unix(gdm-password:session): session 
opened for user jurgen by (uid=0)
Sep 27 22:40:36 bigmomma systemd-logind[739]: New session 10 of user jurgen.
Sep 27 22:40:36 bigmomma dbus[764]: [system] Rejected send message, 2 matched 
rules; type="error", sender=":1.0" (uid=0 pid=739 
comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error 
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" 
destination=":1.104" (uid=1000 pid=3735 comm="/usr/lib/xorg/Xorg vt4 -displayfd 
3 -auth /run/use")
Sep 27 22:40:37 bigmomma dbus[764]: [system] Rejected send message, 2 matched 
rules; type="error", sender=":1.0" (uid=0 pid=739 
comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error 
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" 
destination=":1.104" (uid=1000 pid=3735 comm="/usr/lib/xorg/Xorg vt4 -displayfd 
3 -auth /run/use")
Sep 27 22:40:37 bigmomma dbus[764]: [system] Rejected send message, 2 matched 
rules; type="error", sender=":1.0" (uid=0 pid=739 
comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error 
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" 
destination=":1.104" (uid=1000 pid=3735 comm="/usr/lib/xorg/Xorg vt4 -displayfd 
3 -auth /run/use")
Sep 27 22:40:37 bigmomma dbus[764]: [system] Rejected send message, 2 matched 
rules; type="error", sender=":1.0" (uid=0 pid=739 
comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error 
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" 
destination=":1.104" (uid=1000 pid=3735 comm="/usr/lib/xorg/Xorg vt4 -displayfd 
3 -auth /run/use")
Sep 27 22:40:37 bigmomma dbus[764]: [system] Rejected send message, 2 matched 
rules; type="error", sender=":1.0" (uid=0 pid=739 
comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error 
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" 
destination=":1.104" (uid=1000 pid=3735 comm="/usr/lib/xorg/Xorg vt4 -displayfd 
3 -auth /run/use")
Sep 27 22:40:37 bigmomma dbus[764]: [system] Rejected send message, 2 matched 
rules; type="error", sender=":1.0" (uid=0 pid=739 
comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error 
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" 
destination=":1.104" (uid=1000 pid=3735 comm="/usr/lib/xorg/Xorg vt4 -displayfd 
3 -auth /run/use")
Sep 27 22:40:37 bigmomma dbus[764]: [system] Rejected send message, 2 matched 
rules; type="error", sender=":1.0" (uid=0 pid=739 
comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error

[Touch-packages] [Bug 1709500] Re: [UIFe] Headerbar buttons that are highlighted/coloured in Adwaita are not coloured at all in Ambiance.

2017-09-27 Thread Didier Roche

Please find attach one of those actions, see the top green button.

** Summary changed:

- Headerbar buttons that are highlighted/coloured in Adwaita are not coloured 
at all in Ambiance.
+ [UIFe] Headerbar buttons that are highlighted/coloured in Adwaita are not 
coloured at all in Ambiance.

** Attachment added: "default-suggested-action.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1709500/+attachment/4957867/+files/default-suggested-action.png

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

Title:
  [UIFe] Headerbar buttons that are highlighted/coloured in Adwaita are
  not coloured at all in Ambiance.

Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in ubuntu-themes source package in Artful:
  Confirmed

Bug description:
  Using Ambiance on artful, the "action buttons" used in GtkHeaderBar
  are using a color similar to bar background which makes them not stand
  out. One example is the file-roller extract dialog, when using Adwaita
  the "extract" button is blue which make it an obvious click target,
  that's not the case under our themes

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

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

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

2017-09-27 Thread Eric Desrochers

** Also affects: systemd (Ubuntu Trusty)
   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/1718966

Title:
  Cannot install snaps on Ubuntu 14.04 with /var on its own partition

Status in snapd:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  New

Bug description:
  Installing snaps is not possible on Ubuntu 14.04 when having /var on
  its own partition, whether its LVM or not.

  The issue is with the core snap being unable to mount:

  The error with /var isolated and using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  The error with /var isolated but without using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service
 failed to load: No such file or directory. See system logs and 'systemctl 
status 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service'
 for details.
  )

  The same error happens if I try to install the hello-world snap (with
  LVM in this example):

  root@ubuntu:~# snap install hello-world
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  I cannot reproduce the issue in Ubuntu 16.04.

  I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image
  which doesn't isolate /var on its own partition. I tried adding a
  secondary disk to that cloud image VM and create a dummy VG and LV,
  but couldn't reproduce the issue.

  Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with
  only a / partition and swap.

  
  Steps to reproduce:
  ===

  # Install Ubuntu 14.04 in KVM (I used the 14.04.4 server iso) and
  configure /, /var and swap on their own partitions (with LVM or not,
  the issue happens in both situations).

  root@ubuntu:~# lvs
  LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
  rootvol vg00 -wi-ao--- 3.72g 
  swap vg00 -wi-ao--- 3.72g 
  varvol vg00 -wi-ao--- 3.72g 

  root@ubuntu:~# df -h
  Filesystem   Size  Used Avail Use% Mounted on
  udev 484M  4.0K  484M   1% /dev
  tmpfs100M  988K   99M   1% /run
  /dev/dm-03.7G  1.7G  1.8G  49% /
  none 4.0K 0  4.0K   0% /sys/fs/cgroup
  none 5.0M 0  5.0M   0% /run/lock
  none 497M 0  497M   0% /run/shm
  none 100M 0  100M   0% /run/user
  /dev/mapper/vg00-varvol  3.7G  716M  2.8G  21% /var

  
  # Upgrade system, install snapd and reboot

  root@ubuntu:~# apt update
  root@ubuntu:~# apt upgrade -y
  root@ubuntu:~# apt install -y snapd
  root@ubuntu:~# reboot

  
  # After reboot, check kernel version and try to install the 
canonical-livepatch snap:

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  root@ubuntu:~# snap list
  No snaps are installed yet. Try "snap install hello-world".

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

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

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

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

** Tags removed: rls-aa-incoming

** Also affects: xorg (Ubuntu Artful)
   Importance: High
   Status: Confirmed

** Also affects: xubuntu-meta (Ubuntu Artful)
   Importance: Undecided
   Status: Fix Released

** Changed in: xorg (Ubuntu Artful)
 Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)

-- 
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 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/+source/xorg/+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 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

2017-09-27 Thread Doug McMahon

It should then be added to the release notes.

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

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

Status in gdm3 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

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

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

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

2017-09-27 Thread Rafael David Tinoco

I was also able to reproduce this, here are my notes for now:

## /etc/fstab

LABEL=LVROOT / ext4 errors=remount-ro 0 1
LABEL=LVVAR /var ext4 defaults 0 1
LABEL=TESTE /teste ext4 defaults 0 1

Right after boot:

inaddy@trustylivepatch:~$ systemctl list-units --all | grep fsck
systemd-...el-LVVAR.service error  inactive dead
systemd-fsck@dev-disk-by\x2dlabel-LVVAR.service
systemd-...el-TESTE.service error  inactive dead
systemd-fsck@dev-disk-by\x2dlabel-TESTE.service

This indicates that UPSTART is the one mounting the block devices, NOT
SYSTEMD using its mount units. SNAPS are mounting the SQUASH filesystems
using SYSTEMD UNITS, despite UPSTART scripts.

It is likely that this wasn't noticed, on systems mounting "/" only,
because the "-.mount" SYSTEMD UNIT doesn't depend on "systemd-
fsck@.service" unit, it depends only on "systemd-fsck-root.service", non
existent in TRUSTY's SYSTEMD version. Probably this made SYSTEMD to act
like no error existed.

For SYSTEMD mount units to work, it is needed that no fsck unit error
exists - like when having /var or any other mounting besides root
filesystem - allowing all SYSTEMD units created by snappy to work.

Comparing default setups for TRUSTY and ZESTY:


## TRUSTY

$ dpkg -L systemd | grep fsck
/lib/systemd/systemd-fsck

$ systemctl list-units --all | grep fsck
systemd-...el-LVVAR.service error  inactive dead
systemd-fsck@dev-disk-by\x2dlabel-LVVAR.service
systemd-...el-TESTE.service error  inactive dead
systemd-fsck@dev-disk-by\x2dlabel-TESTE.service

$ systemctl list-units --all | grep mount
-.mountloaded active   mounted /
teste.mountloaded active   mounted /teste
var.mount  loaded active   mounted /var
umount.target  loaded inactive deadUnmount All Filesystems

## ZESTY

$ dpkg -L systemd | grep fsck
/lib/systemd/system/systemd-fsck-root.service
/lib/systemd/system/systemd-fsck@.service
/lib/systemd/system/systemd-fsckd.service
/lib/systemd/system/systemd-fsckd.socket
/lib/systemd/systemd-fsck
/lib/systemd/systemd-fsckd

$ systemctl list-unit-files | grep fsck
systemd-fsck-root.service   static
systemd-fsck@.service   static
systemd-fsck@dev-disk-by\x2dlabel-TESTE.service static
systemd-fsckd.service   static
systemd-fsckd.socketstatic

$ systemctl list-unit-files | grep mount
-.mount   generated
home-inaddy-work.mountgenerated
mnt.mount static
mountall.service  masked
umountfs.service  masked
umountroot.servicemasked
umount.target static


SYSTEMD in TRUSTY was treated differently for FSCK. TRUSTY's version
contains systemd-fsck but not systemd-fsckd, the daemon responsible for
consolidating all fsck information for SYSTEMD journal. It is also clear
that TRUSTY did not include any unit file for systemd-fsck@.service,
that might still be considered for the automatically generated mount
unit files.

You can reproduce this by trying to use TRUSTY SYSTEMD mount units:


## TRUSTY

$ mount /teste

$ mount | grep teste
/dev/sdb2 on /teste type ext4 (rw)

$ systemctl status teste.mount
teste.mount - /teste
   Loaded: loaded (/etc/fstab)
   Active: active (mounted) since Wed 2017-09-27 17:27:21 BRT; 10s ago
Where: /teste
 What: /dev/sdb2
  Process: 1754 ExecUnmount=/bin/umount /teste (code=exited, status=0/SUCCESS)

$ systemctl stop teste.mount

$ systemctl status teste.mount
teste.mount - /teste
   Loaded: loaded (/etc/fstab)
   Active: inactive (dead) since Wed 2017-09-27 17:27:33 BRT; 2s ago
Where: /teste
 What: /dev/disk/by-label/TESTE
  Process: 1778 ExecUnmount=/bin/umount /teste (code=exited, status=0/SUCCESS)

$ mount | grep teste

$ systemctl start teste.mount
Failed to issue method call: Unit 
systemd-fsck@dev-disk-by\x2dlabel-TESTE.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-disk-by\x2dlabel-TESTE.service' for details.


Also, in TRUSTY, SYSTEMD creates the mount units based on /etc/fstab
entries, just like the recent SYSTEMD does, but on them THERE IS NO
setting for fsck dependencies (Requires/After), and, still, it appears
to be considering those fsck dependencies when you try to mount a
".mount" unit, based on errors I showed above for "systemctl start
XXX.mount".


## TRUSTY

$ cat var.mount

# Automatically generated by systemd-fstab-generator

[Unit]
SourcePath=/etc/fstab
DefaultDependencies=no
After=local-fs-pre.target
Conflicts=umount.target
Before=umount.target
Before=local-fs.target

[Mount]
What=/dev/disk/by-label/LVVAR
Where=/var
Type=ext4
FsckPassNo=1

## ZESTY

$ systemctl edit --full mnt.mount
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=local-fs.target

Re: [Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.

2017-09-27 Thread Balint Reczey

On Wed, Sep 27, 2017 at 2:42 PM, Julian Andres Klode
 wrote:
> Hmm, I thought we would not do that anymore, and packages get marked as
> manual when removing a meta package, but I might be missing something.

I ran this on zesty, but if meta packages are handled differently then
I could imagine a similar
case when meta packages are not involved.

-- 
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 is unable to 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:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in gnome-software source package in Artful:
  New
Status in unattended-upgrades source package in Artful:
  New
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 1709500] Re: Headerbar buttons that are highlighted/coloured in Adwaita are not coloured at all in Ambiance.

** Tags removed: rls-aa-incoming

** Also affects: ubuntu-themes (Ubuntu Artful)
   Importance: High
   Status: Confirmed

** Changed in: ubuntu-themes (Ubuntu Artful)
 Assignee: (unassigned) => Didier Roche (didrocks)

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

Title:
  Headerbar buttons that are highlighted/coloured in Adwaita are not
  coloured at all in Ambiance.

Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in ubuntu-themes source package in Artful:
  Confirmed

Bug description:
  Using Ambiance on artful, the "action buttons" used in GtkHeaderBar
  are using a color similar to bar background which makes them not stand
  out. One example is the file-roller extract dialog, when using Adwaita
  the "extract" button is blue which make it an obvious click target,
  that's not the case under our themes

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

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

[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

We're not going to get this fixed this cycle.  It will be looked at in
the BB cycle.


** Tags removed: rls-aa-incoming
** Tags added: rls-aa-notfixing rls-bb-incoming

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

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

Status in gdm3 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

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

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

[Touch-packages] [Bug 1713186] Re: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-09-27 Thread Phillip Susi

You have broken third party init scripts installed ( "K01.depend.boot"
for example ).  You will need to fix or remove them.


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

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

Title:
  package util-linux 2.29-1ubuntu2.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Aug 25 21:35:55 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-06-29 (423 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: util-linux
  Title: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-08-26 (0 days ago)

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

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

[Touch-packages] [Bug 1719934] Re: Missing fonts in list of languages

** Branch linked: lp:~jibel/ubuntu-seeds/platform.artful

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

Title:
  Missing fonts in list of languages

Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  There is a font missing on the ISO and one of the language is shown as
  unicode characters (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 11:22:24 2017
  InstallationDate: Installed on 2013-09-03 (1484 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  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/1719934/+subscriptions

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

[Touch-packages] [Bug 1715062] Re: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

This bug was fixed in the package python-defaults - 2.7.14-2ubuntu1

---
python-defaults (2.7.14-2ubuntu1) artful; urgency=medium

  * pycompile, pyclean, pyversions: Use python2 as the shebang to guard
against people fiddling around with the python symlink or having a
python3 installed as python in /usr/local. LP: #1715062.
  * Rename the idle package to idle2. idle is now built for python3.

 -- Matthias Klose   Sat, 23 Sep 2017 10:18:14 +0200

** Changed in: python-defaults (Ubuntu)
   Status: New => Fix Released

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

Title:
  package python-six 1.10.0-3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in python-defaults package in Ubuntu:
  Fix Released

Bug description:
  kflkt

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-six 1.10.0-3
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Sep  5 06:44:23 2017
  Dependencies:
   
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-08-03 (32 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: six
  Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719982] [NEW] please add a way to enable debug symbols

Public bug reported:

Hi,
add-apt-repository is already doing so much for ppa's adding sources as well as 
adding keys.
If one wants to enable debug symbols usually people follow wiki pages, but it 
would be much better than following some wiki pages.

Essentially integrate [1] into add-apt-repository.

[1]: https://wiki.ubuntu.com/Debug%20Symbol%20Packages

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  please add a way to enable debug symbols

Status in software-properties package in Ubuntu:
  New

Bug description:
  Hi,
  add-apt-repository is already doing so much for ppa's adding sources as well 
as adding keys.
  If one wants to enable debug symbols usually people follow wiki pages, but it 
would be much better than following some wiki pages.

  Essentially integrate [1] into add-apt-repository.

  [1]: https://wiki.ubuntu.com/Debug%20Symbol%20Packages

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

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

[Touch-packages] [Bug 1718717] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

2017-09-27 Thread Till Kamppeter

Principally this kind of problem got already fixed and should not occur
again with the cups-daemon 2.2.4-7 package or newer. It is possible that
perhaps your /usr/sbin/cupsd file got somehow overwritten by an older
version.

So please try at first the following:

sudo apt install --reinstall cups-daemon

Then reboot the system and observe whether this makes the problem going
away.

Please report back here.

** Bug watch added: github.com/apple/cups/issues #5128
   https://github.com/apple/cups/issues/5128

** Also affects: cups via
   https://github.com/apple/cups/issues/5128
   Importance: Unknown
   Status: Unknown

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

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  after updates of cups-filter and reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 21 17:43:42 2017
  ExecutablePath: /usr/sbin/cupsd
  Lpstat:
   device for HP-LaserJet-4200: hp:/net/hp_LaserJet_4200?ip=192.168.10.21
   device for PDF: cups-pdf:/
  MachineType: Dell Inc. OptiPlex 960
  Papersize: a4
  PpdFiles:
   PDF: Generic CUPS-PDF Printer (w/ options)
   HP-LaserJet-4200: HP LaserJet 4200 Series Postscript (recommended)
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f32dc0c7954 : cmpq   
$0x0,(%rdi)
   PC (0x7f32dc0c7954) ok
   source "$0x0" ok
   destination "(%rdi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: Upgraded to artful on 2017-09-19 (2 days ago)
  UserGroups:
   
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0Y958C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0Y958C:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1719983] [NEW] please add a way to enable proposed

Public bug reported:

Hi,
add-apt-repository is already doing so much for ppa's it would be great if 
there would be a nice and consistent cli way through the same tool to enable 
proposed.

Sure there are UI ways to enable, but on a server that usually isn't an
option.

That would be much better than following some wiki pages.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  please add a way to enable proposed

Status in software-properties package in Ubuntu:
  New

Bug description:
  Hi,
  add-apt-repository is already doing so much for ppa's it would be great if 
there would be a nice and consistent cli way through the same tool to enable 
proposed.

  Sure there are UI ways to enable, but on a server that usually isn't
  an option.

  That would be much better than following some wiki pages.

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

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

[Touch-packages] [Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

2017-09-27 Thread Till Kamppeter

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

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

Title:
  CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  It appears that the cups-browsed service as of Xenial (version
  1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests
  for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected
  conditions and regardless of a presence or lack of Canon printer
  devices on the network.

  This is manifested by enabling UFW, and observing multicast requests being 
blocked that are sent from the host machine's network IPv4 or IPv6 address to 
the multicast address, e.g.
  [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24

  IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00
  PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24

  Users have observed that the requests can be reproduced when any USB device 
is plugged/unplugged into the computer, regardless of whether the device has 
anything to do with printing:
  https://twitter.com/gertvdijk/status/621790755758178304
  https://bugs.kali.org/view.php?id=3094

  Just Googling "udp 8612", shows are a large number of results on different 
websites of people who have observed this behaviour in firewall and traffic 
logs, and have noticed that it may contribute to network slowdown and latency:
  https://askubuntu.com/questions/867739/what-is-this-traffic/867786
  
https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets

  https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends 
disabling the cups-browsed service to stop these requests:
  systemctl stop cups-browsed.service
  systemctl disable cups-browsed.service

  There are probably two things to address here:
  1. Connecting any USB device should not cause these requests unless the 
device is actually a printer or directly related to printing.
  2. Requests independent of connecting USB devices should be rate limited to a 
degree and/or should be dependent on the actual presence of a Canon printer 
configured on the network.

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

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

[Touch-packages] [Bug 1637034] Re: Ubuntu Mate 16.04 mouse inputs not handled correctly on multi gpu system

2017-09-27 Thread Sebastian Ramacher

Sounds like a Qt issue (similar to #1637020).

** Package changed: vlc (Ubuntu) => qtbase-opensource-src (Ubuntu)

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

Title:
  Ubuntu Mate 16.04 mouse inputs not handled correctly on multi gpu
  system

Status in ubuntu-mate:
  Invalid
Status in dolphin package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  
My mouse inputs aren't being handled properly by a few but not all 
applications in Ubuntu 16.04 using the Mate desktop.  The problem occurs on my 
system that has 3 gpus, 5 monitor setup with compiz, accelerated graphics, and 
xinerama enabled.  I'm using the Nvidia 361 drivers.  I do not have these 
problems on my laptop, a single monitor setup with compiz and accelerated 
graphics enabled.

Applications like the Caja file manager handles all the mouse inputs
  correctly, but the Dolphin file manager doesn't.  In Dolphin, I can
  mouse click the menu items just fine, but any sub-menu mouse inputs
  are not registered.  Also in Dolphin, none of the mouse inputs are
  recognized while clicking on any of the files/folders/places but I can
  still use the mouse to scroll the file list window.

Other applications that exhibit this odd mouse behavior are VLC and
  SMPlayer (see https://bugs.launchpad.net/ubuntu-mate/+bug/1637020 for
  a bug with VLC that I filed that I believe has a similar root cause).
  Other applications that I've used that don't exhibit this behavior are
  firefox, chromium, virtual box kaffeine, tvtime...  actually, all the
  other programs I've tried don't have this problem.  I'll update the
  list of problem applications as I come across them.  My *guess* is
  that the common denominator between these problem applications is that
  they use the same graphical tool kit and that there is a flaw in that
  tool kit's implementation that affects multi-gpu systems.

If you want, I can record my desktop to demonstrate the problem.

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

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

[Touch-packages] [Bug 1637020] Re: Ubuntu 16.04 Mate vlc info boxes appear on wrong monitor

2017-09-27 Thread Sebastian Ramacher

The pop up is handled by Qt, so reassigning there.

** Package changed: vlc (Ubuntu) => qtbase-opensource-src (Ubuntu)

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

Title:
  Ubuntu 16.04 Mate vlc info boxes appear on wrong monitor

Status in ubuntu-mate:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  
On a multi-monitor Ubuntu 16.04 system the VLC pop up info boxes appear on 
the wrong monitor - see attached screen shot.  5 monitor, 3 gpu, compiz (with 
accelerated graphis), xinerama - two monitors are clones, two other monitors 
are rotated.  As you can tell from the description and attached screen shot 
this is an unusual monitor set up, so I would not be surprised that this issue 
hasn't been seen before.  I'm rather excited as this is the first Ubuntu/Mate 
desktop multi-monitor set up that I've gotten to work with compiz and 
accelerated graphics (I should say that Mate is the only desktop environment 
that I got working with multi-gpu/monitors and compiz/accelerated graphics) and 
I've only encountered minor bugs like this.

As you can see from the attached screen shot, the mouse is hovering
  over the OpenGL GLX box in the VLC preferences window (bottom, center
  monitor).  The pop up info box appears on the upper section of the
  left most monitor.  If I were to move the VLC preference window, the
  info pop up box offset would be the same.  For example, if I move the
  preference window 100 pixels to the right, the info pop up box would
  also appear 100 pixels to the right of its previous position.

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

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

[Touch-packages] [Bug 1719934] Re: Missing font in list of languages

2017-09-27 Thread Jean-Baptiste Lallement

The following fonts are missing from the ISO:
fonts-knda
fonts-telu

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

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

** Package changed: ubiquity (Ubuntu) => ubuntu-meta (Ubuntu)

** Summary changed:

- Missing font in list of languages
+ Missing fonts in list of languages

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

Title:
  Missing fonts in list of languages

Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  There is a font missing on the ISO and one of the language is shown as
  unicode characters (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 11:22:24 2017
  InstallationDate: Installed on 2013-09-03 (1484 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  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/1719934/+subscriptions

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

[Touch-packages] [Bug 1637034] [NEW] Ubuntu Mate 16.04 mouse inputs not handled correctly on multi gpu system

You have been subscribed to a public bug:


  My mouse inputs aren't being handled properly by a few but not all 
applications in Ubuntu 16.04 using the Mate desktop.  The problem occurs on my 
system that has 3 gpus, 5 monitor setup with compiz, accelerated graphics, and 
xinerama enabled.  I'm using the Nvidia 361 drivers.  I do not have these 
problems on my laptop, a single monitor setup with compiz and accelerated 
graphics enabled.

  Applications like the Caja file manager handles all the mouse inputs
correctly, but the Dolphin file manager doesn't.  In Dolphin, I can
mouse click the menu items just fine, but any sub-menu mouse inputs are
not registered.  Also in Dolphin, none of the mouse inputs are
recognized while clicking on any of the files/folders/places but I can
still use the mouse to scroll the file list window.

  Other applications that exhibit this odd mouse behavior are VLC and
SMPlayer (see https://bugs.launchpad.net/ubuntu-mate/+bug/1637020 for a
bug with VLC that I filed that I believe has a similar root cause).
Other applications that I've used that don't exhibit this behavior are
firefox, chromium, virtual box kaffeine, tvtime...  actually, all the
other programs I've tried don't have this problem.  I'll update the list
of problem applications as I come across them.  My *guess* is that the
common denominator between these problem applications is that they use
the same graphical tool kit and that there is a flaw in that tool kit's
implementation that affects multi-gpu systems.

  If you want, I can record my desktop to demonstrate the problem.

** Affects: ubuntu-mate
 Importance: Undecided
 Status: Invalid

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

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Ubuntu Mate 16.04 mouse inputs not handled correctly on multi gpu system
https://bugs.launchpad.net/bugs/1637034
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtbase-opensource-src 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 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.

2017-09-27 Thread Julian Andres Klode

Hmm, I thought we would not do that anymore, and packages get marked as
manual when removing a meta package, but I might be missing something.

-- 
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 is unable to 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:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in gnome-software source package in Artful:
  New
Status in unattended-upgrades source package in Artful:
  New
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 1637020] [NEW] Ubuntu 16.04 Mate vlc info boxes appear on wrong monitor

You have been subscribed to a public bug:


  On a multi-monitor Ubuntu 16.04 system the VLC pop up info boxes appear on 
the wrong monitor - see attached screen shot.  5 monitor, 3 gpu, compiz (with 
accelerated graphis), xinerama - two monitors are clones, two other monitors 
are rotated.  As you can tell from the description and attached screen shot 
this is an unusual monitor set up, so I would not be surprised that this issue 
hasn't been seen before.  I'm rather excited as this is the first Ubuntu/Mate 
desktop multi-monitor set up that I've gotten to work with compiz and 
accelerated graphics (I should say that Mate is the only desktop environment 
that I got working with multi-gpu/monitors and compiz/accelerated graphics) and 
I've only encountered minor bugs like this.

  As you can see from the attached screen shot, the mouse is hovering
over the OpenGL GLX box in the VLC preferences window (bottom, center
monitor).  The pop up info box appears on the upper section of the left
most monitor.  If I were to move the VLC preference window, the info pop
up box offset would be the same.  For example, if I move the preference
window 100 pixels to the right, the info pop up box would also appear
100 pixels to the right of its previous position.

** Affects: ubuntu-mate
 Importance: Undecided
 Status: Invalid

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Ubuntu 16.04 Mate vlc info boxes appear on wrong monitor
https://bugs.launchpad.net/bugs/1637020
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtbase-opensource-src 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 1719934] [NEW] Missing font in list of languages

You have been subscribed to a public bug:

There is a font missing on the ISO and one of the language is shown as
unicode characters (cf screenshot)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 27 11:22:24 2017
InstallationDate: Installed on 2013-09-03 (1484 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: amd64 apport-bug artful rls-aa-incoming wayland-session
-- 
Missing font in list of languages
https://bugs.launchpad.net/bugs/1719934
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-meta 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

Re: [Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.

2017-09-27 Thread Balint Reczey

On Wed, Sep 27, 2017 at 1:49 PM, Brian Murray  wrote:
> @Balint re "@Jarno: IMO Unattended-Upgrade::Remove-Unused-Dependencies
> is already a risky option and I don't recommend enabling it because it
> may remove packages which are not used according the to package-
> dependency chain but which users rely on using software that is not
> packaged."
>
> Could you give me an example of how people would install dependencies
> for software that is not package that would also set the
> "is_auto_removable" flag in the apt cache to True? I can't think of a
> situation like this.

I had the opposite situation in my mind. People would remove packages
which are not auto removable, like ubuntu-desktop (for example because
something ubuntu-desktop depends on is acting badly) and then many
package in ubuntu-desktop's dependency change become auto removable:

$ sudo apt-get remove ubuntu-desktop
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  a11y-profile-manager-indicator activity-log-manager adium-theme-ubuntu
  aisleriot app-install-data-partner apturl apturl-common baobab bluez-cups
...
  xorg
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  ubuntu-desktop
0 upgraded, 0 newly installed, 1 to remove and 7 not upgraded.
After this operation, 46,1 kB disk space will be freed.
Do you want to continue? [Y/n]

It is a simpler problematic situation than the one I originally mentioned, u-u
would remove software which is probably in use, no additional software is
broken.

-- 
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 is unable to 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:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in gnome-software source package in Artful:
  New
Status in unattended-upgrades source package in Artful:
  New
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 1718717] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

2017-09-27 Thread Till Kamppeter

** Information type changed from Private to Public

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in cups package in Ubuntu:
  New

Bug description:
  after updates of cups-filter and reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 21 17:43:42 2017
  ExecutablePath: /usr/sbin/cupsd
  Lpstat:
   device for HP-LaserJet-4200: hp:/net/hp_LaserJet_4200?ip=192.168.10.21
   device for PDF: cups-pdf:/
  MachineType: Dell Inc. OptiPlex 960
  Papersize: a4
  PpdFiles:
   PDF: Generic CUPS-PDF Printer (w/ options)
   HP-LaserJet-4200: HP LaserJet 4200 Series Postscript (recommended)
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f32dc0c7954 : cmpq   
$0x0,(%rdi)
   PC (0x7f32dc0c7954) ok
   source "$0x0" ok
   destination "(%rdi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: Upgraded to artful on 2017-09-19 (2 days ago)
  UserGroups:
   
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0Y958C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0Y958C:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1582950] Re: broken apport hook: TypeError: a bytes-like object is required, not 'str'

2017-09-27 Thread Jean-Baptiste Lallement

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

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

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

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)

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

Title:
  broken apport hook: TypeError: a bytes-like object is required, not
  'str'

Status in apport package in Ubuntu:
  Triaged
Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  The apport hook for ubiquity appears broken. (Ignore the Wnck error,
  that's bug 1580412).

  $ ubuntu-bug ubiquity
  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
  dpkg-query: no packages found matching ubiquity
  ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 61, in 
add_info
  if 'Buffer I/O error on device' in syslog:
  TypeError: a bytes-like object is required, not 'str'

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 17 17:31:33 2016
  InstallationDate: Installed on 2012-10-18 (1307 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: ubiquity
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (17 days ago)

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

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

[Touch-packages] [Bug 1719355] Re: Switcher widget background goes outside its border

2017-09-27 Thread Carlo Lobrano

Hi Laney, do you think this solution is acceptable?

** Attachment added: "ubuntu-theme-switchers.png"
   
https://bugs.launchpad.net/ubuntu-themes/+bug/1719355/+attachment/4957782/+files/ubuntu-theme-switchers.png

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

Title:
  Switcher widget background goes outside its border

Status in Ubuntu theme:
  Triaged
Status in Ubuntu UX:
  New
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  In both Ambiance and Radiance themes, the switcher background is
  visible outside the widget border when inside a headerbar.

  
  See picture from Gnome Control Settings -> Search

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

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

[Touch-packages] [Bug 1582950] Re: broken apport hook: TypeError: a bytes-like object is required, not 'str'

** Branch linked: lp:~jibel/ubuntu/artful/apport/lp1582950_ubiquity_hook

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

Title:
  broken apport hook: TypeError: a bytes-like object is required, not
  'str'

Status in apport package in Ubuntu:
  Triaged
Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  The apport hook for ubiquity appears broken. (Ignore the Wnck error,
  that's bug 1580412).

  $ ubuntu-bug ubiquity
  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
  dpkg-query: no packages found matching ubiquity
  ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 61, in 
add_info
  if 'Buffer I/O error on device' in syslog:
  TypeError: a bytes-like object is required, not 'str'

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 17 17:31:33 2016
  InstallationDate: Installed on 2012-10-18 (1307 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: ubiquity
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (17 days ago)

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

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

[Touch-packages] [Bug 1719959] Re: eglibc 2.19 leaks memory on getaddrinfo

2017-09-27 Thread Florian Weimer

Looks like this issue

  https://sourceware.org/bugzilla/show_bug.cgi?id=21336#c16

Quoting:

The announcement of CVE-2015-7547 said:

“
- Always malloc the second response buffer if needed.

  - Requires fix for sourceware bug 16574 to avoid memory leak.
commit d668061994a7486a3ba9c7d5e7882d85a2883707
commit ab09bf616ad527b249aca5f2a4956fd526f0712f
”



Coincidentally, this regression originally delayed the disclosure of
CVE-2015-7547.  The upstream glibc 2.19 branch already had the fix for
bug 16574 when CVE-2015-7547 was fixed, but our downstream 2.12 and 2.17
branches still needed it.

If you have you own resolv backports, you should really try to get a
valgrind-clean pass with the external resolv test suite:



** Bug watch added: Sourceware.org Bugzilla #21336
   https://sourceware.org/bugzilla/show_bug.cgi?id=21336

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2015-7547

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

Title:
  eglibc 2.19 leaks memory on getaddrinfo

Status in eglibc package in Ubuntu:
  New

Bug description:
  eglibc 2.19-0ubuntu6.13 is leaking memory when getaddrinfo is called
  with a bad address.

  Ubuntu version: 14.04.5 LTS

  We're using Travis CI to do our CI. https://travis-ci.org/curl/curl-
  fuzzer/builds/279417251 exhibits a memory leak when attempting to do a
  lookup on the fqdn "t.."

  I've done a bit of investigation - the memory is allocated here:

  Direct leak of 65536 byte(s) in 1 object(s) allocated from:
  #0 0x4be69c in __interceptor_malloc 
/home/development/llvm/3.9.0/final/llvm.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:64:3
  #1 0x7513bd05 in send_dg 
/build/eglibc-SvCtMH/eglibc-2.19/resolv/res_send.c:1369
  #2 0x7513bd05 in __libc_res_nsend 
/build/eglibc-SvCtMH/eglibc-2.19/resolv/res_send.c:576

  
  Backtrace at point of allocation is:

  (gdb) bt
  #0  __libc_res_nsend (statp=statp@entry=0x702ffdb8, 
buf=buf@entry=0x702fc360 "\t:\001", buflen=19, 
buf2=buf2@entry=0x702fc374 "\371%\001", buflen2=buflen2@entry=19,
  ans=ans@entry=0x702fcf70 "\t:\201\203", anssiz=anssiz@entry=2048, 
ansp=ansp@entry=0x702fd7e0, ansp2=ansp2@entry=0x702fd7f0, 
nansp2=nansp2@entry=0x702fd7a0,
  resplen2=resplen2@entry=0x702fd7b0, 
ansp2_malloced=ansp2_malloced@entry=0x702fd7c0) at res_send.c:580
  #1  0x75138e2c in __GI___libc_res_nquery 
(statp=statp@entry=0x702ffdb8, name=0x702fcaf0 "t.", 
class=class@entry=1, type=type@entry=62321, answer=answer@entry=0x702fcf70 
"\t:\201\203",
  anslen=anslen@entry=2048, answerp=answerp@entry=0x702fd7e0, 
answerp2=answerp2@entry=0x702fd7f0, 
nanswerp2=nanswerp2@entry=0x702fd7a0, 
resplen2=resplen2@entry=0x702fd7b0,
  answerp2_malloced=answerp2_malloced@entry=0x702fd7c0) at 
res_query.c:227
  #2  0x75139863 in __libc_res_nquerydomain (domain=0x0, 
answerp2_malloced=0x702fd7c0, resplen2=0x702fd7b0, 
nanswerp2=0x702fd7a0, answerp2=0x702fd7f0, answerp=0x702fd7e0, 
anslen=2048,
  answer=0x702fcf70 "\t:\201\203", type=62321, class=1, 
name=0x60323f28 "t..", statp=0x702ffdb8) at res_query.c:591
  #3  __GI___libc_res_nsearch (statp=0x702ffdb8, 
name=name@entry=0x60323f28 "t..", class=class@entry=1, 
type=type@entry=62321, answer=answer@entry=0x702fcf70 "\t:\201\203", 
anslen=anslen@entry=2048,
  answerp=answerp@entry=0x702fd7e0, 
answerp2=answerp2@entry=0x702fd7f0, 
nanswerp2=nanswerp2@entry=0x702fd7a0, 
resplen2=resplen2@entry=0x702fd7b0,
  answerp2_malloced=answerp2_malloced@entry=0x702fd7c0) at 
res_query.c:381
  #4  0x7fffef6f0c73 in _nss_dns_gethostbyname4_r 
(name=name@entry=0x60323f28 "t..", pat=pat@entry=0x702fde00, 
buffer=buffer@entry=0x702fd890 "\177", buflen=buflen@entry=1064,
  errnop=errnop@entry=0x702fddd0, herrnop=herrnop@entry=0x702fde30, 
ttlp=ttlp@entry=0x0) at nss_dns/dns-host.c:315
  #5  0x7595a636 in gaih_inet (name=, 
name@entry=0x60323f28 "t..", service=, 
req=req@entry=0x60d0cfb8, pai=pai@entry=0x702fdf40, 
naddrs=naddrs@entry=0x702fdf30)
  at ../sysdeps/posix/getaddrinfo.c:858
  #6  0x7595d93d in __GI_getaddrinfo (name=0x60323f28 "t..", 
service=0x702fec60 "80", hints=0x60d0cfb8, pai=0x702fe9a0) at 
../sysdeps/posix/getaddrinfo.c:2414
  #7  0x00449825 in __interceptor_getaddrinfo () at 
/home/development/llvm/3.9.0/final/llvm.src/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:2169
  #8  0x0051dbe5 in curl_dogetaddrinfo (hostname=0x60323f28 "t..", 
service=0x702fec60 "80", hints=0x60d0cfb8, result=0x702fe9a0,

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.

@Balint re "@Jarno: IMO Unattended-Upgrade::Remove-Unused-Dependencies
is already a risky option and I don't recommend enabling it because it
may remove packages which are not used according the to package-
dependency chain but which users rely on using software that is not
packaged."

Could you give me an example of how people would install dependencies
for software that is not package that would also set the
"is_auto_removable" flag in the apt cache to True? I can't think of a
situation like this.

-- 
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 is unable to 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:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in gnome-software source package in Artful:
  New
Status in unattended-upgrades source package in Artful:
  New
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 is unable to automatically remove packages that become unused in conjunction with updating by other software.

The get_auto_removable function in unattended-ugprades just checks to
see if the package has the "is_auto_removable" flag set. So setting
"Unattended-Upgrade::Remove-Unused-Dependencies" to "true" will produce
the same outcome as using "sudo apt autoremove" e.g.:

bdmurray@clean-xenial-amd64:~$ sudo apt autoremove
[sudo] password for bdmurray:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  libllvm3.8 libmircommon5 libsnapd-glib1 linux-headers-4.4.0-31 
linux-headers-4.4.0-31-generic linux-image-4.4.0-31-generic
  linux-image-extra-4.4.0-31-generic snap-confine snapd-login-service 
ubuntu-core-launcher

bdmurray@clean-xenial-amd64:~$ sudo unattended-upgrade --dry-run
/usr/bin/dpkg --status-fd 9 --force-depends --remove libllvm3.8:amd64 
libmircommon5:amd64 snapd-login-service:amd64 libsnapd-glib1:amd64 
linux-headers-4.4.0-31-generic:amd64 linux-headers-4.4.0-31:all 
linux-image-extra-4.4.0-31-generic:amd64 linux-image-4.4.0-31-generic:amd64 
snap-confine:amd64 ubuntu-core-launcher:amd64
/usr/bin/dpkg --status-fd 11 --configure --pending

So I think the question here is whether or not we think it is safe to
run autoremovals without user interaction.

-- 
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 is unable to 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:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in gnome-software source package in Artful:
  New
Status in unattended-upgrades source package in Artful:
  New
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 1719963] [NEW] package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 139 hibakóddal kilépett

2017-09-27 Thread László Attila

Public bug reported:

 Applicatin crashes on login

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.5-2ubuntu0.1
Uname: Linux 4.13.4-041304-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Sep 27 09:34:46 2017
ErrorMessage: telepítve post-installation parancsfájl alfolyamat 139 hibakóddal 
kilépett
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
telepítve post-installation parancsfájl alfolyamat 139 hibakóddal kilépett
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shared-mime-info (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 shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1719963

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade:
  telepítve post-installation parancsfájl alfolyamat 139 hibakóddal
  kilépett

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
   Applicatin crashes on login

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2ubuntu0.1
  Uname: Linux 4.13.4-041304-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Sep 27 09:34:46 2017
  ErrorMessage: telepítve post-installation parancsfájl alfolyamat 139 
hibakóddal kilépett
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
telepítve post-installation parancsfájl alfolyamat 139 hibakóddal kilépett
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1719963/+subscriptions

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

[Touch-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation

2017-09-27 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in console-setup package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cuase]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - system reset.
  00 zIPL ..
  "

  They start to occur when the software gets installed:

  "Select and install software ... 10% can't open /dev/tty4: No such
  device or address"

  And only stop with the final system reboot at the end of the
  installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+subscriptions

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

[Touch-packages] [Bug 1661329] Re: Wifi password not taken into account if not entered rapidly

2017-09-27 Thread rogue-spectre

Maybe ;)… it seems that they also report in bug #1650835 a problem of
timing but did not make mistakes typing the password the first time.
Maybe not a duplicate… but obviously it seems that the problems might be
linked

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

Title:
  Wifi password not taken into account if not entered rapidly

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  We install ubuntu/mint to numerous people and we got multiple
  reports that the wifi password was not taken into account. We managed
  to reproduce it by

  1 - Select your wifi network
  2 - Enter a fake password (Just to simulate a user error not entering well 
his wifi password)
  3 - Obviously here we cannot connect, so we wait
  4 - Password is asked a second time, and we enter it without error but we 
take our time to do so ( or wait some time after ). By taking our time we 
simulate people who are not fluent with their keyboard.
  5 - Wait to connect
  6 - Password is asked a third time.
  7 - Here if we go into the properties of the wifi (Applet > Modify > Modify) 
and check the password… the first fake password is still there

  Nice day

  It might be a double of this bug
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1219171

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

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

[Touch-packages] [Bug 1719959] [NEW] eglibc 2.19 leaks memory on getaddrinfo

2017-09-27 Thread Max Dymond

Public bug reported:

eglibc 2.19-0ubuntu6.13 is leaking memory when getaddrinfo is called
with a bad address.

Ubuntu version: 14.04.5 LTS

We're using Travis CI to do our CI. https://travis-ci.org/curl/curl-
fuzzer/builds/279417251 exhibits a memory leak when attempting to do a
lookup on the fqdn "t.."

I've done a bit of investigation - the memory is allocated here:

Direct leak of 65536 byte(s) in 1 object(s) allocated from:
#0 0x4be69c in __interceptor_malloc 
/home/development/llvm/3.9.0/final/llvm.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:64:3
#1 0x7513bd05 in send_dg 
/build/eglibc-SvCtMH/eglibc-2.19/resolv/res_send.c:1369
#2 0x7513bd05 in __libc_res_nsend 
/build/eglibc-SvCtMH/eglibc-2.19/resolv/res_send.c:576


Backtrace at point of allocation is:

(gdb) bt
#0  __libc_res_nsend (statp=statp@entry=0x702ffdb8, 
buf=buf@entry=0x702fc360 "\t:\001", buflen=19, 
buf2=buf2@entry=0x702fc374 "\371%\001", buflen2=buflen2@entry=19,
ans=ans@entry=0x702fcf70 "\t:\201\203", anssiz=anssiz@entry=2048, 
ansp=ansp@entry=0x702fd7e0, ansp2=ansp2@entry=0x702fd7f0, 
nansp2=nansp2@entry=0x702fd7a0,
resplen2=resplen2@entry=0x702fd7b0, 
ansp2_malloced=ansp2_malloced@entry=0x702fd7c0) at res_send.c:580
#1  0x75138e2c in __GI___libc_res_nquery 
(statp=statp@entry=0x702ffdb8, name=0x702fcaf0 "t.", 
class=class@entry=1, type=type@entry=62321, answer=answer@entry=0x702fcf70 
"\t:\201\203",
anslen=anslen@entry=2048, answerp=answerp@entry=0x702fd7e0, 
answerp2=answerp2@entry=0x702fd7f0, 
nanswerp2=nanswerp2@entry=0x702fd7a0, 
resplen2=resplen2@entry=0x702fd7b0,
answerp2_malloced=answerp2_malloced@entry=0x702fd7c0) at res_query.c:227
#2  0x75139863 in __libc_res_nquerydomain (domain=0x0, 
answerp2_malloced=0x702fd7c0, resplen2=0x702fd7b0, 
nanswerp2=0x702fd7a0, answerp2=0x702fd7f0, answerp=0x702fd7e0, 
anslen=2048,
answer=0x702fcf70 "\t:\201\203", type=62321, class=1, 
name=0x60323f28 "t..", statp=0x702ffdb8) at res_query.c:591
#3  __GI___libc_res_nsearch (statp=0x702ffdb8, 
name=name@entry=0x60323f28 "t..", class=class@entry=1, 
type=type@entry=62321, answer=answer@entry=0x702fcf70 "\t:\201\203", 
anslen=anslen@entry=2048,
answerp=answerp@entry=0x702fd7e0, 
answerp2=answerp2@entry=0x702fd7f0, 
nanswerp2=nanswerp2@entry=0x702fd7a0, 
resplen2=resplen2@entry=0x702fd7b0,
answerp2_malloced=answerp2_malloced@entry=0x702fd7c0) at res_query.c:381
#4  0x7fffef6f0c73 in _nss_dns_gethostbyname4_r 
(name=name@entry=0x60323f28 "t..", pat=pat@entry=0x702fde00, 
buffer=buffer@entry=0x702fd890 "\177", buflen=buflen@entry=1064,
errnop=errnop@entry=0x702fddd0, herrnop=herrnop@entry=0x702fde30, 
ttlp=ttlp@entry=0x0) at nss_dns/dns-host.c:315
#5  0x7595a636 in gaih_inet (name=, 
name@entry=0x60323f28 "t..", service=, 
req=req@entry=0x60d0cfb8, pai=pai@entry=0x702fdf40, 
naddrs=naddrs@entry=0x702fdf30)
at ../sysdeps/posix/getaddrinfo.c:858
#6  0x7595d93d in __GI_getaddrinfo (name=0x60323f28 "t..", 
service=0x702fec60 "80", hints=0x60d0cfb8, pai=0x702fe9a0) at 
../sysdeps/posix/getaddrinfo.c:2414
#7  0x00449825 in __interceptor_getaddrinfo () at 
/home/development/llvm/3.9.0/final/llvm.src/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:2169
#8  0x0051dbe5 in curl_dogetaddrinfo (hostname=0x60323f28 "t..", 
service=0x702fec60 "80", hints=0x60d0cfb8, result=0x702fe9a0, 
line=124, source=0x6c3f60 <.str> "curl_addrinfo.c")
at curl_addrinfo.c:575
#9  0x0051cf81 in Curl_getaddrinfo_ex (nodename=0x60323f28 "t..", 
servname=0x702fec60 "80", hints=0x60d0cfb8, result=0x60d0cfb0) at 
curl_addrinfo.c:124
#10 0x005275f7 in getaddrinfo_thread (arg=0x60d0cf90) at 
asyn-thread.c:279
#11 0x0062e71a in curl_thread_create_thunk (arg=0x60323e98) at 
curl_threads.c:57
#12 0x76897184 in start_thread (arg=0x702ff700) at 
pthread_create.c:312
#13 0x75987ffd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Let me know if any further diagnostics would be helpful. It's 100%
reproducible on Travis.

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

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

Title:
  eglibc 2.19 leaks memory on getaddrinfo

Status in eglibc package in Ubuntu:
  New

Bug description:
  eglibc 2.19-0ubuntu6.13 is leaking memory when getaddrinfo is called
  with a bad address.

  Ubuntu version: 14.04.5 LTS

  We're using Travis CI to do our CI. https://travis-ci.org/curl/curl-
  fuzzer/builds/279417251 exhibits a memory leak when attempting to do a
  lookup on the

[Touch-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation

2017-09-27 Thread bugproxy

--- Comment From heinz-werner_se...@de.ibm.com 2017-09-27 12:20 EDT---
Will be covered by original Launchpad bug

** Tags added: architecture-s39064 bugnameltc-159373 severity-high
targetmilestone-inin1710

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in console-setup package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cuase]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - system reset.
  00 zIPL ..
  "

  They start to occur when the software gets installed:

  "Select and install software ... 10% can't open /dev/tty4: No such
  device or address"

  And only stop with the final system reboot at the end of the
  installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+subscriptions

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

[Touch-packages] [Bug 1719935] Re: It would be great to get a stacktrace on apparmor "events" - maybe add a tracepoint

2017-09-27 Thread Christian Boltz

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

** Tags added: aa-feature

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

Title:
  It would be great to get a stacktrace on apparmor "events" - maybe add
  a tracepoint

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,
  as just discussed it would be a great help to add a tracepoint(s) at 
intersting spots like the DENY message.
  If that is a common place give it an argument for the message so people cna 
filter on it.
  If these are different places add them as multiple tracepoints.

  Then people could easily with perf do the tracing and get all they
  need (backtraces, but also much more if needed).

  We all kind of agreed so this is mostly to track so I get a ping once
  you do something on it.

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

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

[Touch-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation

2017-09-27 Thread Frank Heimes

Reverse proxy initiated ...

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => bugproxy (bugproxy)

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in console-setup package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cuase]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - system reset.
  00 zIPL ..
  "

  They start to occur when the software gets installed:

  "Select and install software ... 10% can't open /dev/tty4: No such
  device or address"

  And only stop with the final system reboot at the end of the
  installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+subscriptions

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

[Touch-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation

2017-09-27 Thread Dimitri John Ledkov

/dev/tty1 file exists on s390x ubuntu, however, one cannot open that
file doing that results in ENXIO.

console-setup is an architecture independent package which tries to
detect and configure all consoles. Ideally, I do not want to encode if
`uname -p` is s390x or some such to filter-out and skip tty[0-9].

Imho, if /dev/tty[0-9] devices do not exist, why does kernel create such
files? Can it be escalated to IBM linux team to not have those files at
all? E.g. make a upstream kernel patch to not create these devices.
Maybe I am crazy, I don't understand things - e.g. is it possible to
somehow get a working /dev/tty1?

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in console-setup package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cuase]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - system reset.
  00 zIPL ..
  "

  They start to occur when the software gets installed:

  "Select and install software ... 10% can't open /dev/tty4: No such
  device or address"

  And only stop with the final system reboot at the end of the
  installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+subscriptions

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

[Touch-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation

2017-09-27 Thread Dimitri John Ledkov

** No longer affects: console-setup (Ubuntu Xenial)

** No longer affects: console-setup (Ubuntu Zesty)

** No longer affects: console-setup (Ubuntu Artful)

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

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

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

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in console-setup package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cuase]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - system reset.
  00 zIPL ..
  "

  They start to occur when the software gets installed:

  "Select and install software ... 10% can't open /dev/tty4: No such
  device or address"

  And only stop with the final system reboot at the end of the
  installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+subscriptions

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

[Touch-packages] [Bug 1707929] Re: [FFe] Revert blacklisting of Indic layouts

2017-09-27 Thread Gunnar Hjalmarsson

To the release team: This would be a simple change: We could just add
the Debian level patch which moves the Indic language back from
"extras".

** Summary changed:

- Revert blacklisting of Indic layouts
+ [FFe] Revert blacklisting of Indic layouts

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

Title:
  [FFe] Revert blacklisting of Indic layouts

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Triaged
Status in xkeyboard-config package in Debian:
  Fix Released

Bug description:
  In xkeyboard-config 2.19-1 several Indic keyboard layouts were moved
  to "extras".

  https://cgit.freedesktop.org/xkeyboard-config/commit/?id=913af7

  The measure has been criticized and has been reverted afterwards at
  both freedesktop.org and Debian. We should make sure it's reverted in
  Ubuntu 17.10 as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1707929/+subscriptions

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

[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

2017-09-27 Thread Colin Law

@prefec2 that sounds like a different bug. This one is not intermittent.
If the workaround in comment #6 does not fix it for you then I suggest
filing a new bug.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

2017-09-27 Thread Reiner Jung

** Attachment added: "File containing my present journal log, with multiple 
on/off toggles."
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712283/+attachment/4957729/+files/a

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Touch-packages] [Bug 1719935] [NEW] It would be great to get a stacktrace on apparmor "events" - maybe add a tracepoint

Public bug reported:

Hi,
as just discussed it would be a great help to add a tracepoint(s) at intersting 
spots like the DENY message.
If that is a common place give it an argument for the message so people cna 
filter on it.
If these are different places add them as multiple tracepoints.

Then people could easily with perf do the tracing and get all they need
(backtraces, but also much more if needed).

We all kind of agreed so this is mostly to track so I get a ping once
you do something on it.

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

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

Title:
  It would be great to get a stacktrace on apparmor "events" - maybe add
  a tracepoint

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,
  as just discussed it would be a great help to add a tracepoint(s) at 
intersting spots like the DENY message.
  If that is a common place give it an argument for the message so people cna 
filter on it.
  If these are different places add them as multiple tracepoints.

  Then people could easily with perf do the tracing and get all they
  need (backtraces, but also much more if needed).

  We all kind of agreed so this is mostly to track so I get a ping once
  you do something on it.

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

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

[Touch-packages] [Bug 1719936] [NEW] It would be great to get a stacktrace on apparmor "events" - maybe add a tracepoint

Public bug reported:

Hi,
as just discussed it would be a great help to add a tracepoint(s) at intersting 
spots like the DENY message.
If that is a common place give it an argument for the message so people cna 
filter on it.
If these are different places add them as multiple tracepoints.

Then people could easily with perf do the tracing and get all they need
(backtraces, but also much more if needed).

We all kind of agreed so this is mostly to track so I get a ping once
you do something on it.

** Affects: apparmor (Ubuntu)
 Importance: Low
 Status: Confirmed

** Changed in: apparmor (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  It would be great to get a stacktrace on apparmor "events" - maybe add
  a tracepoint

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  as just discussed it would be a great help to add a tracepoint(s) at 
intersting spots like the DENY message.
  If that is a common place give it an argument for the message so people cna 
filter on it.
  If these are different places add them as multiple tracepoints.

  Then people could easily with perf do the tracing and get all they
  need (backtraces, but also much more if needed).

  We all kind of agreed so this is mostly to track so I get a ping once
  you do something on it.

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

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

[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

2017-09-27 Thread Reiner Jung

I have the same issue. A couple of month ago we had a similar issue, which 
could be fixed by "downgrading" the resolver setup for systemd. However, the 
issue returned a couple of days ago.
In general networking works after start up, but stops after a random time 
period. When I "turn off" the connection and then turn it on again, it works 
again for some time before it breaks down again. 

This only affects DNS, as media streams and running connections are not
affected. The time interval range from 1-2 minutes up to an hour.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2017-09-27 Thread Graham Bosworth

It's been a while, but the interface does not fail when I want it to.
My script has been enhanced with more diagnostics, which have not given
any answers. I have seen that iptables is empty, so I think that
D.H.C.P. or U.D.P. is not hitting a DROP.

But here's something that strikes me as very odd - I now have three
network interfaces on the computer, for the purposes of testing, but
only the wired one, eth0, was active and enabled. The address was lost
again as usual, but manually starting "dhclient" on ANOTHER interface
brought "eth0" back up with the address that had previously been
associated with a wireless interface.

There is a bit of a history attached. Now I am waiting for the network
to be lost again to see what else I can learn.

** Attachment added: "boing.txt"

https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+attachment/4957719/+files/boing.txt

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

Title:
Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed

Bug description:
For some reason, if I leave my Ubuntu VM up for a prolonged period of
time the machine will lose connection to the network. ip addr shows
that the nic port no longer has an address and an examination of the
syslog shows this:

May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record
for 10.0.2.15 on enp0s3.
May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast
group on interface enp0s3.IPv4 with address 10.0.2.15.
May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no
longer relevant for mDNS.

for no known reason.

The only reliable way to get the network to come back (that I have
found) is a full reboot.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri May 27 15:11:34 2016
InstallationDate: Installed on 2015-10-22 (218 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: avahi
UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

2017-09-27 Thread Dr. Thomas Orgis

Can we get any reaction from Ubuntu on this? Is the needed reworking of
the initrd about to happen for the LTS or is this a WONTFIX and root-on-
Intel-Matrix-RAID is simply not supported? It is clear what has to
happen to make things work again with systemd and mdadm/mdmon. Will it
happen?

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio, but to no avail.

  Linux

[Touch-packages] [Bug 1350821] Re: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_key_press()

2017-09-27 Thread reg

@Marco... 
Thanks for the info on the fix manual-install, but on my system 14.04 nothing 
has changed, bug still alive and well.

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

Title:
  unity-panel-service crashed with SIGSEGV in
  ido_calendar_menu_item_key_press()

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Trusty:
  Fix Released

Bug description:
  
  [Impact]
  Unity panel service crashes when opening the Calendar menu

  [Test Case]
  There's not a way to reproduce this systemically. Just open frequently the 
calendar menu, but this crash can happen or not.

  [Regression Potential]
  None, the code change consists only on protecting against a null pointer 
(recorded in the stacktraces here), so it's just pretty safe.

  
  ProblemType: CrashDistroRelease: Ubuntu 14.10
  Package: unity-services 7.3.0+14.10.20140711-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.5-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul 31 13:53:14 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.12, 3.16.0-5-generic, x86_64: installed
   virtualbox, 4.3.12, 3.16.0-6-generic, x86_64: installed
  ExecutablePath: /usr/lib/unity/unity-panel-service
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2013-12-22 (221 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221)
  MachineType: LENOVO 429149G
  ProcCmdline: /usr/lib/unity/unity-panel-service
  ProcEnviron:
   PATH=(custom, user)
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic 
root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7ffbbaf3b766:mov0x10(%rdx),%ecx
   PC (0x7ffbbaf3b766) ok
   source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo
  dmi.bios.date: 05/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET46WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429149G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429149G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Jul 30 18:55:05 2014
  xserver.configfile: default
  xserver.errors:
   intel: Failed to load module "dri3" (module does not exist, 0)
   intel: Failed to load module "present" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu8

To

[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

2017-09-27 Thread Sebastien Bacher

** Tags removed: rls-as-incoming
** Tags added: rls-aa-incoming

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

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

Status in gdm3 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

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

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

[Touch-packages] [Bug 1719765] Re: Evolution can't add new data(contact, appointment) to nextcloud

2017-09-27 Thread Bug Watch Updater

** Changed in: gnome-online-accounts
   Status: Unknown => Confirmed

** Changed in: gnome-online-accounts
   Importance: Unknown => Medium

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

Title:
  Evolution can't add new data(contact, appointment)  to nextcloud

Status in gnome-online-accounts:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Evolution is not able to add new data eg. new contacts, new
  appointments to nextcloud. Whenn trying I get the following error
  message: "... 415 (Unsupported Media Type):
  Sabre\DAV\Exception\UnsupportedMediaType ...". Synchronizing from
  nextcloud server to client works as expected.

  I'm using Ubuntu 17.10 and on the server side Ubuntu 16.04 + Nextcloud
  snap is used.

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

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

[Touch-packages] [Bug 1719765] Re: Evolution can't add new data(contact, appointment) to nextcloud

2017-09-27 Thread Sebastien Bacher

thanks

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Triaged

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

Title:
  Evolution can't add new data(contact, appointment)  to nextcloud

Status in gnome-online-accounts:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Evolution is not able to add new data eg. new contacts, new
  appointments to nextcloud. Whenn trying I get the following error
  message: "... 415 (Unsupported Media Type):
  Sabre\DAV\Exception\UnsupportedMediaType ...". Synchronizing from
  nextcloud server to client works as expected.

  I'm using Ubuntu 17.10 and on the server side Ubuntu 16.04 + Nextcloud
  snap is used.

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

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

[Touch-packages] [Bug 1719720] Re: [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127

2017-09-27 Thread Frank Heimes

** Changed in: ubuntu-power-systems
   Status: New => Triaged

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

Title:
  [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with
  exit code 127

Status in The Ubuntu-power-systems project:
  Triaged
Status in coreutils package in Ubuntu:
  Triaged

Bug description:
  ---Problem Description---
  Currently syslog is getting flooded with below log messages ..
  Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch 
/run/run.vpdd
  update' failed with exit code 127.

  This is on UBuntu 17.10 latest build.. 
   
  ---uname output---
  Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ZZ-L 

  ---Steps to Reproduce---
   I have seen these messages logged more often when we do any hotplug 
operations.. ex. cpu hotplug..

  Ok. .this is the continuation of LTC #144627 / Launchpad #1682774.

  As suggested in that bug, we did change udev script to create
  temporary file under /run and that patch is available in ubuntu 17.10.

  Looks like this is udev script issue. If I modify systemd-udevd like
  below it works fine.

  I've limited udev knowledge. I don't know if you have any other better
  solution to this issue.

  root@ltc-boston123:/lib/systemd/system# diff -Naurp  
systemd-udevd.service.org systemd-udevd.service
  --- systemd-udevd.service.org 2017-09-26 04:37:47.090057318 -0500
  +++ systemd-udevd.service 2017-09-26 04:37:55.381739372 -0500
  @@ -25,7 +25,7 @@ KillMode=mixed
   WatchdogSec=3min
   TasksMax=infinity
   MountFlags=slave
  -MemoryDenyWriteExecute=yes
  +#MemoryDenyWriteExecute=yes
   RestrictRealtime=yes
   RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
   SystemCallArchitectures=native

  
  -Vasant

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1719720/+subscriptions

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

[Touch-packages] [Bug 1719765] Re: Evolution can't add new data(contact, appointment) to nextcloud

2017-09-27 Thread nehrka

I filed a bug according this issue:
https://bugzilla.gnome.org/show_bug.cgi?id=788239

** Bug watch added: GNOME Bug Tracker #788239
   https://bugzilla.gnome.org/show_bug.cgi?id=788239

** Also affects: gnome-online-accounts via
   https://bugzilla.gnome.org/show_bug.cgi?id=788239
   Importance: Unknown
   Status: Unknown

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

Title:
  Evolution can't add new data(contact, appointment)  to nextcloud

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Evolution is not able to add new data eg. new contacts, new
  appointments to nextcloud. Whenn trying I get the following error
  message: "... 415 (Unsupported Media Type):
  Sabre\DAV\Exception\UnsupportedMediaType ...". Synchronizing from
  nextcloud server to client works as expected.

  I'm using Ubuntu 17.10 and on the server side Ubuntu 16.04 + Nextcloud
  snap is used.

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

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

[Touch-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

2017-09-27 Thread bugproxy

** Tags removed: severity-high
** Tags added: severity-medium

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+subscriptions

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

[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

2017-09-27 Thread Doug McMahon

Just to note: I do get proper shutdowns from tty1 (has to be done before
attempting gui shutdown

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

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

Status in gdm3 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

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

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

[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"