[Touch-packages] [Bug 1727174] Re: ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection ip:7fb85293d253 sp:7ffeecf73800 error:0 in libX11.so.6.3.0[7fb8528a0000+134000]

[Sebastien Bacher]

what desktop environment/session do you use?

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

Title:
  ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection
  ip:7fb85293d253 sp:7ffeecf73800 error:0 in
  libX11.so.6.3.0[7fb8528a+134000]

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  uname -a
  Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 
19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  read-config
  SCHEMA: org.freedesktop.ibus.general
dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', 
'/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
use-system-keyboard-layout: true
embed-preedit-text: true
enable-by-default: false
use-global-engine: false
use-xmodmap: true
switcher-delay-time: 400
version: '1.5.14'
engines-order: ['libpinyin']
preload-engines: ['libpinyin', 'xkb:us::eng']
xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 
'jp(kana)', 'mal', 'mkd', 'ru', 'ua']
  SCHEMA: org.freedesktop.ibus.general.hotkey
next-engine: ['Alt+Shift_L']
disable-unconditional: @as []
enable-unconditional: @as []
trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 
'Hangul', 'Alt+Release+Alt_R']
previous-engine: @as []
prev-engine: @as []
next-engine-in-menu: ['Alt+Shift_L']
triggers: ['space']
  SCHEMA: org.freedesktop.ibus.panel
x: -1
property-icon-delay-time: 500
y: -1
lookup-table-orientation: 1
show: 2
xkb-icon-rgba: '#415099'
auto-hide-timeout: 1
show-im-name: false
follow-input-cursor-when-always-shown: false
custom-font: 'Sans 10'
show-icon-on-systray: true
use-custom-font: false

  ibus engine
  xkb:us::eng

  ps -ef|grep ibus
  gdm   1969  1647  0 12:42 tty1 00:00:00 ibus-daemon --xim --panel 
disable
  gdm   1972  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf
  gdm   1975 1  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  gdm   2046  1969  0 12:42 tty1 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   2516  2433  0 12:42 tty2 00:00:02 ibus-daemon --xim --panel 
disable
  hdzhong   3966  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf
  hdzhong   3968 1  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  hdzhong   3984  2516  0 12:53 tty2 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   4198  3939  0 12:58 pts/100:00:00 grep --color=auto ibus

  dpkg:

  ii  ibus 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - core
  ii  ibus-anthy   1.5.9-2  amd64anthy 
engine for IBus
  ii  ibus-clutter:amd64   0.0+git20090728.a936bacf-5.1 amd64ibus 
input method framework for clutter
  ii  ibus-gtk:amd64   1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+2 support
  ii  ibus-gtk3:amd64  1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+3 support
  ii  ibus-libpinyin   1.7.3-2  amd64
Intelligent Pinyin engine based on libpinyin for IBus
  ii  ibus-qt4 1.3.3-1  amd64
qt-immodule for ibus (QT4) (plugin)
  ii  ibus-sunpinyin   2.0.3-5build3amd64
sunpinyin engine for ibus
  ii  ibus-table   1.9.14-3 all  table 
engine for IBus
  ii  ibus-table-wubi  1.8.2-2  all  
ibus-table input method: Wubi
  ii  ibus-wayland 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - Wayland support
  ii  libibus-1.0-5:amd64   1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- shared library
  ii  libibus-1.0-dev:amd64 1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- development file
  ii  libibus-qt1   1.3.3-1 amd64qt-immodule for ibus 
(QT4) (library)

  
  execute command: "ibus-daemon -rdx" won't fixed the issue.

  and no system tray in the topbar.

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

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

[Touch-packages] [Bug 1727174] Re: ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection ip:7fb85293d253 sp:7ffeecf73800 error:0 in libX11.so.6.3.0[7fb8528a0000+134000]

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

** Package changed: linux (Ubuntu) => ibus (Ubuntu)

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

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

Title:
  ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection
  ip:7fb85293d253 sp:7ffeecf73800 error:0 in
  libX11.so.6.3.0[7fb8528a+134000]

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  uname -a
  Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 
19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  read-config
  SCHEMA: org.freedesktop.ibus.general
dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', 
'/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
use-system-keyboard-layout: true
embed-preedit-text: true
enable-by-default: false
use-global-engine: false
use-xmodmap: true
switcher-delay-time: 400
version: '1.5.14'
engines-order: ['libpinyin']
preload-engines: ['libpinyin', 'xkb:us::eng']
xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 
'jp(kana)', 'mal', 'mkd', 'ru', 'ua']
  SCHEMA: org.freedesktop.ibus.general.hotkey
next-engine: ['Alt+Shift_L']
disable-unconditional: @as []
enable-unconditional: @as []
trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 
'Hangul', 'Alt+Release+Alt_R']
previous-engine: @as []
prev-engine: @as []
next-engine-in-menu: ['Alt+Shift_L']
triggers: ['space']
  SCHEMA: org.freedesktop.ibus.panel
x: -1
property-icon-delay-time: 500
y: -1
lookup-table-orientation: 1
show: 2
xkb-icon-rgba: '#415099'
auto-hide-timeout: 1
show-im-name: false
follow-input-cursor-when-always-shown: false
custom-font: 'Sans 10'
show-icon-on-systray: true
use-custom-font: false

  ibus engine
  xkb:us::eng

  ps -ef|grep ibus
  gdm   1969  1647  0 12:42 tty1 00:00:00 ibus-daemon --xim --panel 
disable
  gdm   1972  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf
  gdm   1975 1  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  gdm   2046  1969  0 12:42 tty1 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   2516  2433  0 12:42 tty2 00:00:02 ibus-daemon --xim --panel 
disable
  hdzhong   3966  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf
  hdzhong   3968 1  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  hdzhong   3984  2516  0 12:53 tty2 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   4198  3939  0 12:58 pts/100:00:00 grep --color=auto ibus

  dpkg:

  ii  ibus 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - core
  ii  ibus-anthy   1.5.9-2  amd64anthy 
engine for IBus
  ii  ibus-clutter:amd64   0.0+git20090728.a936bacf-5.1 amd64ibus 
input method framework for clutter
  ii  ibus-gtk:amd64   1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+2 support
  ii  ibus-gtk3:amd64  1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+3 support
  ii  ibus-libpinyin   1.7.3-2  amd64
Intelligent Pinyin engine based on libpinyin for IBus
  ii  ibus-qt4 1.3.3-1  amd64
qt-immodule for ibus (QT4) (plugin)
  ii  ibus-sunpinyin   2.0.3-5build3amd64
sunpinyin engine for ibus
  ii  ibus-table   1.9.14-3 all  table 
engine for IBus
  ii  ibus-table-wubi  1.8.2-2  all  
ibus-table input method: Wubi
  ii  ibus-wayland 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - Wayland support
  ii  libibus-1.0-5:amd64   1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- shared library
  ii  libibus-1.0-dev:amd64 1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- development file
  ii  libibus-qt1   1.3.3-1 amd64qt-immodule for ibus 
(QT4) (library)

  
  execute command: "ibus-daemon -rdx" won't fixed the issue.

  and no system tray in the topbar.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1725641] Re: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Botched upgrade from 17.04 to 17.10, the bug reporter came up after I
  finally managed to login.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  AptOrdering:
   libdb5.3:amd64: Configure
   multiarch-support:amd64: Configure
   libobs0:amd64: Install
   obs-plugins:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Oct 21 10:13:28 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-03-23 (2037 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
disabled  enabled  enabled

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

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

[Touch-packages] [Bug 1727174] [NEW] ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection ip:7fb85293d253 sp:7ffeecf73800 error:0 in libX11.so.6.3.0[7fb8528a0000+134000]

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

uname -a
Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 
19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


lsb_release -a
LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful

read-config
SCHEMA: org.freedesktop.ibus.general
  dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', 
'/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
  use-system-keyboard-layout: true
  embed-preedit-text: true
  enable-by-default: false
  use-global-engine: false
  use-xmodmap: true
  switcher-delay-time: 400
  version: '1.5.14'
  engines-order: ['libpinyin']
  preload-engines: ['libpinyin', 'xkb:us::eng']
  xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 'jp(kana)', 
'mal', 'mkd', 'ru', 'ua']
SCHEMA: org.freedesktop.ibus.general.hotkey
  next-engine: ['Alt+Shift_L']
  disable-unconditional: @as []
  enable-unconditional: @as []
  trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 
'Hangul', 'Alt+Release+Alt_R']
  previous-engine: @as []
  prev-engine: @as []
  next-engine-in-menu: ['Alt+Shift_L']
  triggers: ['space']
SCHEMA: org.freedesktop.ibus.panel
  x: -1
  property-icon-delay-time: 500
  y: -1
  lookup-table-orientation: 1
  show: 2
  xkb-icon-rgba: '#415099'
  auto-hide-timeout: 1
  show-im-name: false
  follow-input-cursor-when-always-shown: false
  custom-font: 'Sans 10'
  show-icon-on-systray: true
  use-custom-font: false

ibus engine
xkb:us::eng

ps -ef|grep ibus
gdm   1969  1647  0 12:42 tty1 00:00:00 ibus-daemon --xim --panel 
disable
gdm   1972  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf
gdm   1975 1  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
gdm   2046  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-engine-simple
hdzhong   2516  2433  0 12:42 tty2 00:00:02 ibus-daemon --xim --panel 
disable
hdzhong   3966  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf
hdzhong   3968 1  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
hdzhong   3984  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-engine-simple
hdzhong   4198  3939  0 12:58 pts/100:00:00 grep --color=auto ibus

dpkg:

ii  ibus 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - core
ii  ibus-anthy   1.5.9-2  amd64anthy 
engine for IBus
ii  ibus-clutter:amd64   0.0+git20090728.a936bacf-5.1 amd64ibus 
input method framework for clutter
ii  ibus-gtk:amd64   1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+2 support
ii  ibus-gtk3:amd64  1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+3 support
ii  ibus-libpinyin   1.7.3-2  amd64
Intelligent Pinyin engine based on libpinyin for IBus
ii  ibus-qt4 1.3.3-1  amd64
qt-immodule for ibus (QT4) (plugin)
ii  ibus-sunpinyin   2.0.3-5build3amd64
sunpinyin engine for ibus
ii  ibus-table   1.9.14-3 all  table 
engine for IBus
ii  ibus-table-wubi  1.8.2-2  all  
ibus-table input method: Wubi
ii  ibus-wayland 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - Wayland support
ii  libibus-1.0-5:amd64   1.5.14-2ubuntu1 amd64Intelligent Input Bus - 
shared library
ii  libibus-1.0-dev:amd64 1.5.14-2ubuntu1 amd64Intelligent Input Bus - 
development file
ii  libibus-qt1   1.3.3-1 amd64qt-immodule for ibus 
(QT4) (library)


execute command: "ibus-daemon -rdx" won't fixed the issue.

and no system tray in the topbar.

** Affects: ibus (Ubuntu)
 Importance: High
 Status: Incomplete


** Tags: artful ibus ibus-ui-gtk3
-- 
ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection 
ip:7fb85293d253 sp:7ffeecf73800 error:0 in libX11.so.6.3.0[7fb8528a+134000]
https://bugs.launchpad.net/bugs/1727174
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ibus 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 1727147] Re: [Dell Inspiron 20 - 3064] [Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter] [168c:0042] The bluetooth detection is gone with kernel 4.10.0-38-generic on z

[Daniel van Vugt]

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

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

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

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

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

  hciconfig did not output anything.

  More information:

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

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

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

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Sebastien Bacher]

The corresponding GNOME bug has been marked fixed in 
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=02d56ec87

that commit is in the 17.10 version, if that doesn't work then it's
another issue or the upstream report should be reopened

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu Artful)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu Zesty)
   Importance: Undecided => High

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

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

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

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

[Taihsiang Ho]

zesty + 4.10.0-35.39 kernel +  bluez (5.43-0ubuntu1.1)
could not reproduce this issue.

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

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

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

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

  hciconfig did not output anything.

  More information:

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

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

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

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

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

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

[Taihsiang Ho]

zesty + 4.10.0-35.39 kernel + bluez (5.43-0ubuntu1.1)
could not reproduce this issue according to history test records.

Maybe my hardware has issues. Checking.

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

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

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

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

  hciconfig did not output anything.

  More information:

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

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

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

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

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

[Touch-packages] [Bug 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

[KEVIN KENNY]

Upgraded to 17.10. Uninstalled and reinstalled openssh-client, openssh-
server (including loading a fresh /usr/etc/ssh directory).

Still fails.

I attach the output of:
sudo strace -f -e trace=socket /usr/sbin/sshd -d 2>&1 | tee sshd.result.txt

All the other configuration is as before.

What other information can I get for you so as not to just get this
issue closed again?

I've downloaded source, but of course it configures to run from
/usr/local. What are the correct flags for ./configure to get it to
build the way Ubuntu builds it and install to the Ubuntu paths?
Alternatively, where can I find out how to run the daemon from
/usr/local/sbin instead of /usr/sbin? (That would allow me to configure
the extra debugging information requested in the second comment.)

** Attachment added: "Output of strace - showing the 'socket' call in the child 
process."
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+attachment/4993455/+files/sshd.result.txt

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

Title:
  openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Status in openssh package in Ubuntu:
  New

Bug description:
  The 'sshd' process gets 'authentication failure' and refuses to allow
  any login.

  dmesg indicates that the problem is SIGSYS on a call to 'socket'
  (syscall #41, signal #31).

  On a hunch, I decided to test whether the problem is related to
  'seccomp' and changed /etc/ssh/sshd_config from the default

  # UsePrivilegeSeparation sandbox

  to the former standard value

  UsePrivilegeSeparation yes

  and logins started to work again.

  Obviously, I'd like to have the additional protection that sandboxing
  would give me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: openssh-server 1:7.4p1-10
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 12 21:06:20 2017
  InstallationDate: Installed on 2017-04-08 (35 days ago)
  InstallationMedia:
   
  SourcePackage: openssh
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago)

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

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

[Touch-packages] [Bug 1690497] Re: package liblocale-gettext-perl 1.07-3build1 failed to install/upgrade: pre-dependency problem - not installing liblocale-gettext-perl

[Launchpad Bug Tracker]

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

** Changed in: liblocale-gettext-perl (Ubuntu)
   Status: New => Confirmed

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

Title:
  package liblocale-gettext-perl 1.07-3build1 failed to install/upgrade:
  pre-dependency problem - not installing liblocale-gettext-perl

Status in liblocale-gettext-perl package in Ubuntu:
  Confirmed

Bug description:
  when i am using Ubuntu ...my laptop hangs ...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: liblocale-gettext-perl 1.07-3build1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  Date: Sat May 13 08:47:11 2017
  ErrorMessage: pre-dependency problem - not installing liblocale-gettext-perl
  InstallationDate: Installed on 2016-12-13 (150 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: liblocale-gettext-perl
  Title: package liblocale-gettext-perl 1.07-3build1 failed to install/upgrade: 
pre-dependency problem - not installing liblocale-gettext-perl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

[KEVIN KENNY]

Oh, another note: changing the UsePrivilegeSeparation setting no longer
works. It reports that the setting is deprecated and ignores it. This
leaves me without a workaround.

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

Title:
  openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Status in openssh package in Ubuntu:
  New

Bug description:
  The 'sshd' process gets 'authentication failure' and refuses to allow
  any login.

  dmesg indicates that the problem is SIGSYS on a call to 'socket'
  (syscall #41, signal #31).

  On a hunch, I decided to test whether the problem is related to
  'seccomp' and changed /etc/ssh/sshd_config from the default

  # UsePrivilegeSeparation sandbox

  to the former standard value

  UsePrivilegeSeparation yes

  and logins started to work again.

  Obviously, I'd like to have the additional protection that sandboxing
  would give me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: openssh-server 1:7.4p1-10
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 12 21:06:20 2017
  InstallationDate: Installed on 2017-04-08 (35 days ago)
  InstallationMedia:
   
  SourcePackage: openssh
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago)

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

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

[Touch-packages] [Bug 1727160] Re: alt-tabbing out of a fullscreen game and back in causes the game to not come back fullscreen

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

Title:
  alt-tabbing out of a fullscreen game and back in causes the game to
  not come back fullscreen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Launch any game full screen on steam (Civ5 is a good example) and alt-
  tab.  When you alt-tab back to the game it will not be full screen,
  but windowed and slightly down and right from where it should be.
  Some applications have alt-enter to switch from windowed to fullscreen
  and toggling that will work (0 AD) is a good example.  Most do not.

  Ubuntu 17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 00:06:36 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:119e]
  InstallationDate: Installed on 2017-10-19 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Alienware Aurora-R4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2013
  dmi.bios.vendor: Alienware
  dmi.bios.version: A11
  dmi.board.name: 07JNH0
  dmi.board.vendor: Alienware
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00:
  dmi.product.family: 0
  dmi.product.name: Aurora-R4
  dmi.product.version: 00
  dmi.sys.vendor: Alienware
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1727160] [NEW] alt-tabbing out of a fullscreen game and back in causes the game to not come back fullscreen

[Steve Barcomb]

Public bug reported:

Launch any game full screen on steam (Civ5 is a good example) and alt-
tab.  When you alt-tab back to the game it will not be full screen, but
windowed and slightly down and right from where it should be.  Some
applications have alt-enter to switch from windowed to fullscreen and
toggling that will work (0 AD) is a good example.  Most do not.

Ubuntu 17.10

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 25 00:06:36 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
 nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:119e]
InstallationDate: Installed on 2017-10-19 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Alienware Aurora-R4
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2013
dmi.bios.vendor: Alienware
dmi.bios.version: A11
dmi.board.name: 07JNH0
dmi.board.vendor: Alienware
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Alienware
dmi.chassis.version: 00
dmi.modalias: 
dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00:
dmi.product.family: 0
dmi.product.name: Aurora-R4
dmi.product.version: 00
dmi.sys.vendor: Alienware
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu

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

Title:
  alt-tabbing out of a fullscreen game and back in causes the game to
  not come back fullscreen

Status in xorg package in Ubuntu:
  New

Bug description:
  Launch any game full screen on steam (Civ5 is a good example) and alt-
  tab.  When you alt-tab back to the game it will not be full screen,
  but windowed and slightly down and right from where it should be.
  Some applications have alt-enter to switch from windowed to fullscreen
  and toggling that will work (0 AD) is a good example.  Most do not.

  Ubuntu 17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  

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

[Daniel van Vugt]

Are you saying it has never worked with any kernel?

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

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

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

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

  hciconfig did not output anything.

  More information:

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

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

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

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

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

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

[Daniel van Vugt]

Otherwise, what was the last kernel that did work?

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

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

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

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

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

  hciconfig did not output anything.

  More information:

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

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

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

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

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

[Touch-packages] [Bug 1727158] [NEW] lscpu shows incorrect instantaneous CPU MHz value

[David Oswald]

Public bug reported:

Ubuntu 17.10:

lscpu has the following fields of interest to this report:

Model name:  Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz

CPU MHz: 3499.996
CPU max MHz: 5900.
CPU min MHz: 1600.

The CPU MHz field is incorrect:  At idle it never shows down-step, and
at full load, it never shows the CPU's boost frequency (which should be
up to about 4.6GHz on my system).

This was working correctly under Ubuntu 17.04, showing the full range
between 1600 and 4600.  But with Ubuntu 17.10 it remains constantly at
the CPU's design spec of 3499.996.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: util-linux 2.30.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 24 22:00:02 2017
InstallationDate: Installed on 2017-09-01 (53 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

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

Title:
  lscpu shows incorrect instantaneous CPU MHz value

Status in util-linux package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10:

  lscpu has the following fields of interest to this report:

  Model name:  Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz

  CPU MHz: 3499.996
  CPU max MHz: 5900.
  CPU min MHz: 1600.

  The CPU MHz field is incorrect:  At idle it never shows down-step, and
  at full load, it never shows the CPU's boost frequency (which should
  be up to about 4.6GHz on my system).

  This was working correctly under Ubuntu 17.04, showing the full range
  between 1600 and 4600.  But with Ubuntu 17.10 it remains constantly at
  the CPU's design spec of 3499.996.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: util-linux 2.30.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 22:00:02 2017
  InstallationDate: Installed on 2017-09-01 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)

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

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

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

[Taihsiang Ho]

Hi Daniel, thanks for your comments.

I noted this issue initially with proposed zesty (bluez 5.43-0ubuntu1.1
and 4.10.0-38-generic kernel), and filed this report on zesty with
ubuntu-bug.

And then I recalled when I was playing around with proposed xenail
(bluez 5.37-0ubuntu5.1 and 4.4.0-98.121 kernel) and it seems that I had
the same issue. I need to go back to confirm my memory.

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

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

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

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

  hciconfig did not output anything.

  More information:

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

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

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

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

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

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

[Taihsiang Ho]

Tried with the previous kernels on zesty with the same stack. Still
could not find bluetooth.




ubuntu@201606-22459:~$ uname -a
Linux 201606-22459 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@201606-22459:~$ hciconfig
ubuntu@201606-22459:~$ lsmod | grep ath
ath10k_pci 45056  0
ath10k_core   344064  1 ath10k_pci
ath28672  1 ath10k_core
mac80211  782336  1 ath10k_core
cfg80211  602112  3 mac80211,ath,ath10k_core
ubuntu@201606-22459:~$ dpkg -l bluez
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version 
ArchitectureDescription
+++-=-===-===-===
ii  bluez 5.43-0ubuntu1.1 
amd64   Bluetooth tools and daemons
ubuntu@201606-22459:~$

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

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

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

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

  hciconfig did not output anything.

  More information:

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

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

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

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Ricardo]

This bug still exists in Ubuntu 17.10 (ProtonVPN). In distros as Arch, Manjaro 
and Fedora it never happened. Is this going to 18.04 LTS as well?! Why no one 
cares?

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

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

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

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

[Daniel van Vugt]

Sounds like bluez 5.37 might not understand something about kernel 4.10,
but I can't find any obvious explanation in git...

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

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

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

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

  hciconfig did not output anything.

  More information:

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

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

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

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

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

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

[Daniel van Vugt]

Ignore that comment #5. I thought you were on 16.04 but this is 17.04 so
that's bluez 5.43 and kernel 4.10 has been there since the beginning.

** Tags added: regression-proposed

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

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

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

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

  hciconfig did not output anything.

  More information:

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

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

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

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

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

[Touch-packages] [Bug 1659727] Re: Xorg freeze - blank screen - Enlightenment + nvidia driver

[Paul Higgins]

Doing the upgrade to E21 on the original system finally fixed the
problem there...

Sorry I forgot to log the results...

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

Title:
  Xorg freeze - blank screen - Enlightenment + nvidia driver

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I helped my friend Roger setup five systems running ubuntu with boinc
  running in the background for the Einstein@home project.  One has a
  AMD Phenom 9950 CPU, and the others have AMD FX-8320E, FX-8150,
  FX-8350, and FX-8370 CPUs.  All have the X64 version of ubuntu
  installed. In an effort to speed up processing, we install NVidia GTX
  1060 graphics cards in three of them.

  We added the nvidia-367 kernel driver to two systems that were already
  upgraded to 16.04 LTS (they use Lightdm and Unity with Xorg).  They
  now use the GPU for one of the processes without problems.

  This problem system (with the FX-8150 CPU) was originally using Ubuntu
  Precise Pangolin and running Enlightenment instead of Unity.  It was
  using Trusty when we installed the new graphics card.  It still used
  the Nouveau video driver.  I had problems installing the NVidia kernel
  driver on that, so I gave up and used the 'do-release-upgrade' script
  to do the upgrade to 16.04.1 LTS (Xenial).  Everything seemed OK until
  I added the NVidia driver to the system.  Now, after every reboot the
  display goes thru the text boot sequence, and flashes briefly when
  loading X, but then the screen goes blank until rebooting again.

  Fortunately, I found I could open a ssh session (or use scp to copy
  files) to the system.  The NVidia GPU is being used by one of the
  BOINC jobs, even with the blank screen on the console!

  After a lot of horsing around, I moved the file failsafe-x.conf from
  /etc/init to /root, so I could try various hacks to get the display to
  work.  It took me a long time to find the error message in file
  /home/roger/.xsession-errors.  It says:

openConnection: connect: No such file or directory
cannot connect to brltty at :0
main init win: 1920x1080 for 1d4
screen region screen 0x6e4140: 0 0   1920x1080
CRI: modules/evas/engines/gl_x11/evas_engine.c:2511 eng_image_native_set() 
eina_log_print() unknown domain -1, original message format 'GLX Pixmap create 
fail'
action halt 3
action reboot 3
action suspend 3
action hibernate 3

  The 5th line (starting with 'CRI') led me to the efl source package
  associated with enlightenment, (which I installed in /usr/src).  It
  seems to have source for a number of DLLs for e17.  I found the line
  from the message in file:
  '/usr/src/efl-1.8.6/src/modules/evas/engines/gl_x11/evas_engine.c'.

  I don't know how to proceed from here.  I assume the apport-bug job
  gave most of the system state information.  Is there a way to look at
  the various X processes that are running?  Please advise..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Jan 26 22:54:02 2017
  DistUpgraded: 2017-01-16 22:52:51,433 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 3.13.0-107-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-59-generic, x86_64: installed
   nvidia-367, 367.57, 4.4.0-59-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard: NVIDIA Corporation Device [10de:1c03] (rev a1) (prog-if 00 [VGA 
controller])
  InstallationDate: Installed on 2012-07-09 (1662 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
 

[Touch-packages] [Bug 1727147] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** 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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1727147

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

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

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

  hciconfig did not output anything.

  More information:

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

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

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

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

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

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

[Taihsiang Ho]

duplicate https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1727148

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

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

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

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

  hciconfig did not output anything.

  More information:

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

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

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

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

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

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

[Taihsiang Ho]

Looks like this affects proposed kernel of xenial 4.4.0-98.121. Needs to
confirm this later.

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

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

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

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

  hciconfig did not output anything.

  More information:

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

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

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

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

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

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

[Taihsiang Ho]

Public bug reported:

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

hciconfig did not output anything.

More information:

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


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

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

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: 201606-22459 amd64 apport-bug package-from-proposed taipei-lab zesty

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

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

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

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

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

  hciconfig did not output anything.

  More information:

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

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

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

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

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

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

[Taihsiang Ho]

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

Public bug reported:

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

hciconfig did not output anything.

More information:

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

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

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

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

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


** Tags: 201606-22459 amd64 apport-bug taipei-lab zesty

** This bug has been marked a duplicate of bug 1727147
   [Dell Inspiron 20 - 3064] [Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter] [168c:0042] The bluetooth detection is gone with kernel 
4.10.0-38-generic on zesty

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

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

Status in bluez package in Ubuntu:
  New

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

  hciconfig did not output anything.

  More information:

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

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

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

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

To manage notifications about this bug go to:

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Eric Carroll]

Reinstalling the ca-certificates did not work for me.

Only removing dbus-user-session works around the problem for me.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Eric Carroll]

Also, openrazer & polychromatic no longer have the dependency on dbus-
user-session. Thanks to the maintainers of these packages.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1693992] Re: gdm-session-worker crashed with SIGABRT - "assertion failed: (manager->priv->accounts_proxy != NULL)" in load_users()

[Daniel van Vugt]

** Summary changed:

- gdm-session-worker crashed with SIGABRT in g_assertion_message() from 
g_assertion_message_expr() from load_users() from load_idle()
+ gdm-session-worker crashed with SIGABRT - "assertion failed: 
(manager->priv->accounts_proxy != NULL)" in load_users()

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

Title:
  gdm-session-worker crashed with SIGABRT - "assertion failed:
  (manager->priv->accounts_proxy != NULL)" in load_users()

Status in Ubuntu GNOME:
  New
Status in accountsservice package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed

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

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

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

[Touch-packages] [Bug 1726929] Re: pulseaudio crashed with SIGABRT in __GI_____strtof128_l_internal()

[Daniel van Vugt]

** Information type changed from Private to Public

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

Title:
  pulseaudio crashed with SIGABRT in __GI_strtof128_l_internal()

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  In sound panel, the analog output keeps appearing/disappearing for a
  minute or so. Then this crash occurs.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   henklaak    F...m firefox
   /dev/snd/controlC0:  henklaak    F firefox
henklaak   6370 F alsamixer
   /dev/snd/timer:  henklaak    f firefox
  CrashCounter: 1
  CurrentDesktop: Unity:Unity7
  Date: Tue Oct 24 18:07:04 2017
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-04-25 (547 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_sink_input_finish_move () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so
   pa_sink_move_all_finish () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   pa_card_set_profile () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so
   ?? () from /usr/lib/pulse-10.0/modules/module-switch-on-port-available.so
  Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
  UpgradeStatus: Upgraded to artful on 2017-10-19 (4 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  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.:bvr1708:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1726924] Re: bluetoothd assert failure: *** Error in `/usr/lib/bluetooth/bluetoothd': free(): invalid pointer: 0x00005650785cc410 ***

[Daniel van Vugt]

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

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


** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1689438
   bluetoothd crashed with SIGABRT in free(): invalid pointer

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

Title:
  bluetoothd assert failure: *** Error in
  `/usr/lib/bluetooth/bluetoothd': free(): invalid pointer:
  0x5650785cc410 ***

Status in bluez package in Ubuntu:
  New

Bug description:
  I have no idea

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/lib/bluetooth/bluetoothd': free(): 
invalid pointer: 0x5650785cc410 ***
  Date: Tue Oct 24 18:07:36 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2016-10-17 (372 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Vostro 3558ti
  ProcCmdline: /usr/lib/bluetooth/bluetoothd
  ProcEnviron:
   LANG=te_IN.UTF-8
   LANGUAGE=te
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=040c776f-fb00-4448-8637-127b4bc5af29 ro quiet splash 
i915.enable_rc6=0 vt.handoff=7
  Signal: 6
  SourcePackage: bluez
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ff531c144e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7ff531c10e6e "free(): invalid 
pointer", ptr=, ar_ptr=) at malloc.c:5425
   _int_free (av=0x7ff531e46c20 , p=, have_lock=0) 
at malloc.c:4174
   __GI___libc_free (mem=) at malloc.c:3144
   g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: bluetoothd assert failure: *** Error in 
`/usr/lib/bluetooth/bluetoothd': free(): invalid pointer: 0x5650785cc410 ***
  UpgradeStatus: Upgraded to artful on 2017-10-22 (2 days ago)
  UserGroups:
   
  dmi.bios.date: 10/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 05JF1T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd10/15/2015:svnDellInc.:pnVostro3558ti:pvr01:rvnDellInc.:rn05JF1T:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 3558ti
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 78:0C:B8:A9:23:41  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:129530 acl:2421 sco:0 events:13376 errors:0
TX bytes:12751608 acl:12962 sco:0 commands:330 errors:0

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

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

[Touch-packages] [Bug 1726850] Re: gnome-shell crashed with SIGSEGV

[Daniel van Vugt]

** Information type changed from Private to Public

** Summary changed:

- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in image_get_buffers()

** Summary changed:

- gnome-shell crashed with SIGSEGV in image_get_buffers()
+ gnome-shell crashed with SIGSEGV in image_get_buffers() from 
intel_update_image_buffers()

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

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

** Summary changed:

- gnome-shell crashed with SIGSEGV in image_get_buffers() from 
intel_update_image_buffers()
+ gnome-shell crashed with SIGSEGV in image_get_buffers() from 
intel_update_image_buffers() [i965]

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

Title:
  gnome-shell crashed with SIGSEGV in image_get_buffers() from
  intel_update_image_buffers() [i965]

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  This bug was collected by Apport and so I don't know all the details.
  I just installed Ubuntu 17.10 and I have had problems with all my
  programs being closed (it looks as if the computer had been rebooted)
  after the screen had been locked. I then changed from Wayland to Xorg,
  just before this bug was reported, but I am uncertain if the bug
  report pertains to this problem, or if the bug was for the Wayland or
  Xorg state. I'm happy to provide more information, I just need to know
  what to look for.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Oct 23 14:06:31 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-23 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fb3f4c56233:mov0x200(%rax),%rax
   PC (0x7fb3f4c56233) ok
   source "0x200(%rax)" (0x706e692f7665662f) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgbm.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[tenaciousd]

it doesn't work on ubuntu 17.10

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition

[Harvey Houston]

I have seen where this stays on top of the list when running `top` in a 
terminal. As a temporary workaround, use this link to solve your problems. Run 
each line of the script box in a terminal:
https://askubuntu.com/questions/346211/tracker-store-and-tracker-miner-fs-eating-up-my-cpu-on-every-startup#348692

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

Title:
  tracker-store uses 100% cpu and fills all the disk space in home
  partition

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I recently noticed that several tracker related programs were using
  100% cpu on my system and in particular tracker-store filled up
  completely all the available disk space in my home partition.

  I rerun tracker-preferences to make sure that indexing would not
  proceed if less than 20% of free space is available, but it seems that
  tracker-store ignores it.  After I noticed that I had left only 44Kb
  free on the home partition,  I deleted the cache from another program
  and I noticed that tracker-store filled up again the disk space that I
  freed few minutes before.

  This is the content of my .cache/tracker/ directory:
  totale 772068
  -rw-r--r-- 1 eclipse eclipse  3072 2011-06-26 22:56 contents.db
  -rw-r--r-- 1 eclipse eclipse11 2012-01-04 21:24 db-locale.txt
  -rw-r--r-- 1 eclipse eclipse 2 2011-12-12 04:02 db-version.txt
  -rw-r--r-- 1 eclipse eclipse  3072 2010-12-05 21:29 email-contents.db
  -rw-r--r-- 1 eclipse eclipse  3072 2009-05-06 19:16 email-fulltext.db
  -rw-r--r-- 1 eclipse eclipse   2359292 2011-06-26 22:54 email-index.db
  -rw-r--r-- 1 eclipse eclipse 34816 2010-12-05 21:29 email-meta.db
  -rw-r--r-- 1 eclipse eclipse  17062912 2011-06-26 19:30 file-contents.db
  -rw-r--r-- 1 eclipse eclipse  15014912 2010-01-12 20:26 file-fulltext.db
  -rw-r--r-- 1 eclipse eclipse  75609207 2011-06-26 22:54 file-index.db
  -rw-r--r-- 1 eclipse eclipse  37027840 2011-06-26 19:31 file-meta.db
  -rw--- 1 eclipse eclipse   1180048 2009-05-05 22:57 file-update-index.db
  -rw-r--r-- 1 eclipse eclipse  28376064 2011-10-20 09:34 fulltext.db
  -rw-r--r-- 1 eclipse eclipse  1024 2012-01-04 21:24 meta.db
  -rw-r--r-- 1 eclipse eclipse   4653056 2012-01-04 21:26 meta.db-shm
  -rw-r--r-- 1 eclipse eclipse 608064304 2012-01-04 21:26 meta.db-wal
  -rw-r--r-- 1 eclipse eclipse11 2011-12-12 04:02 
miner-applications-locale.txt
  -rw-r--r-- 1 eclipse eclipse345110 2012-01-04 21:24 ontologies.gvdb

  and this is  how much space I have left on my home partition after I KILLED 
the tracker-store process:
  /dev/sda8  31G   30G  418M  99% /home
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  Package: tracker 0.10.24-1build2
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=it_IT:it:en_GB:en
   PATH=(custom, user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric
  Uname: Linux 3.0.0-14-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-20 (76 days ago)
  UserGroups: adm admin audio cdrom dip fuse lpadmin plugdev polkituser 
pulse-access sambashare src video

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

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

[Touch-packages] [Bug 1721578] Re: Firefox

[Paul White]

** Package changed: xorg (Ubuntu) => firefox (Ubuntu)

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

Title:
  Firefox

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox does not work properly

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Oct  5 18:38:01 2017
  DistUpgraded: 2017-07-12 16:05:47,505 DEBUG icon theme changed, re-reading
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF104 [GeForce GTX 460] [1043:835d]
  InstallationDate: Installed on 2017-07-10 (87 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=fi
   PATH=(custom, no user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-07-12 (85 days ago)
  dmi.bios.date: 10/24/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0815
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0815:bd10/24/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Thu Oct  5 16:54:59 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.1
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1727100] Re: systemd-udevd crashed with SIGABRT in __libc_open64()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-udevd crashed with SIGABRT in __libc_open64()

Status in systemd package in Ubuntu:
  New

Bug description:
  Not sure what happened, Ubuntu prompted me to report this bug, no
  other symptom. Apologies if that's a duplicate, the potential
  duplicates proposed by launchpad didn't match.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 23 13:27:16 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2017-10-19 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ZBook 15 G2
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=9b0a43d1-1be9-4e7d-8884-b4fa8ff898b2 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_open64 (file=0x560100f4b160 "/dev/sdb", oflag=657408) at 
../sysdeps/unix/sysv/linux/open64.c:46
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __libc_open64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/23/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.12
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.10
  dmi.chassis.asset.tag: MBARI-1983
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM70Ver.01.12:bd09/23/2015:svnHewlett-Packard:pnHPZBook15G2:pvrA3009DD10303:rvnHewlett-Packard:rn2253:rvrKBCVersion03.10:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP ZBook 15 G2
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1727104] Re: systemd-udevd crashed with SIGABRT in __libc_open64()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-udevd crashed with SIGABRT in __libc_open64()

Status in systemd package in Ubuntu:
  New

Bug description:
  Sorry, I really can't provide any info, I just know that this dialog
  came up about a system error. I don't know anything about systemd

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 24 19:44:44 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2016-12-04 (324 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_open64 (file=0x557c5748a2e0 "/dev/sdc", oflag=657408) at 
../sysdeps/unix/sysv/linux/open64.c:46
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __libc_open64()
  UpgradeStatus: Upgraded to artful on 2017-10-21 (3 days ago)
  UserGroups:
   
  dmi.bios.vendor: Intel Corp.
  dmi.board.vendor: Intel corporation

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

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

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

[John Johansen]

@Paul,

sorry no. At least not unless you are doing some very specific pinning
of the kernel features abi as I suggested as a solution in #19.

You will need the userspace fix in the ppa until ubuntu can land an SRU
of either patch r3700 or a full SRU of the current maintenance releases.
With the userspace fix ubuntu policy should just work under the 4.14-rcX
kernels

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

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

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

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

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

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

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

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

[Seth Arnold]

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

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

Title:
  ufw does not start automatically at boot

Status in ufw package in Ubuntu:
  New

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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

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

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

[Matt Caswell]

Hi Seth,

This is what I get:

matt@matt-laptop:~$ sudo ufw status
Status: inactive
matt@matt-laptop:~$ journalctl -u ufw.service
-- Logs begin at Tue 2017-10-24 22:48:54 BST, end at Wed 2017-10-25 00:03:54 
BST. --
Oct 24 22:48:54 matt-laptop systemd[1]: Started Uncomplicated firewall.
matt@matt-laptop:~$ systemctl status ufw
● ufw.service - Uncomplicated firewall
   Loaded: loaded (/lib/systemd/system/ufw.service; enabled; vendor preset: 
enabled)
   Active: active (exited) since Tue 2017-10-24 22:48:54 BST; 1h 15min ago
 Docs: man:ufw(8)
  Process: 443 ExecStart=/lib/ufw/ufw-init start quiet (code=exited, 
status=0/SUCCESS)
 Main PID: 443 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
   CGroup: /system.slice/ufw.service

Oct 24 22:48:54 matt-laptop systemd[1]: Started Uncomplicated firewall.
Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable.

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

Title:
  ufw does not start automatically at boot

Status in ufw package in Ubuntu:
  Incomplete

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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

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

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

[Seth Arnold]

Hi Matt, can you give the output of:

systemctl status ufw

and

journalctl -u ufw.service

Thanks

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

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

Title:
  ufw does not start automatically at boot

Status in ufw package in Ubuntu:
  Incomplete

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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

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

[Touch-packages] [Bug 1021975] Re: gzip --rsyncable not rsyncable

[Bug Watch Updater]

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

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

Title:
  gzip --rsyncable not rsyncable

Status in gzip package in Ubuntu:
  Incomplete
Status in gzip package in Debian:
  Fix Released

Bug description:
  i use gzip --rsyncable to compress postgresql 9 db dumps for rsyncing
  from an east-coast colo to a west-coast colo.  the dumps are always
  changing in small ways so this compression speeds up the rsync by
  quite a bit.  both the following tests are with a large text dump file
  on both sides, the local is newer than the remote.

  a gzip 1.3.12 (with
  
http://archive.ubuntu.com/ubuntu/pool/main/g/gzip/gzip_1.3.12-9ubuntu1.diff.gz)
  session ends with the usual infodump like this:

  rj@fudge:~$ rsync -Pvazl latest-linux-pg9.gz rj@cake:
  Password:
  sending incremental file list
  latest-linux-pg9.gz
1857354904 100%2.77MB/s0:10:39 (xfer#1, to-check=0/1)

  sent 310747861 bytes  received 301381 bytes  456418.55 bytes/sec
  total size is 1857354904  speedup is 5.97

  but with the ubuntu server LTS gzip 1.4 i'm getting little or no
  speedup:

  rj@fudge:~$ rsync -Pvazl latest-linux-pg9.gz rj@cake: 
  Password:
  sending incremental file list
  latest-linux-pg9.gz
1802447002 100%  634.16kB/s0:46:15 (xfer#1, to-check=0/1)

  sent 1739614120 bytes  received 297265 bytes  617318.21 bytes/sec
  total size is 1802447002  speedup is 1.04

  i haven't taken a look at the code or data to suggest the difference,
  but the result is noticeable.  basically, not super-critical because i
  can build previous versions with previous-version patches, but i
  figured i should report it.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gzip 1.4-1ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Fri Jul  6 21:21:29 2012
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gzip
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1724013] Re: mount does not correctly process x-* options

[DaytonaJohn]

After further investigation, it turns out that mount is actually
handling the options correctly and passing the options (with x-* options
removed) to mount.cifs. The problem is that mount.cifs ignores those
passed options if the user running the mount command is not root, and
just grabs the options from fstab without removing the x-* options. So
the problem is actually in mount.cifs that it does not correctly handle
x-* options (and probably doesn't handle "comment=" options correctly
either).

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

Title:
  mount does not correctly process x-* options

Status in util-linux package in Ubuntu:
  New

Bug description:
  According to the mount(8) man page:

  All options prefixed with "x-" are interpreted as comments or as
  userspace application-specific options.  These options are not stored
  in  the  mtab  file,  nor  sent  to  the mount.type helpers nor to the
  mount(2) system call.  The suggested format is x-appname.option (e.g.
  x-systemd.automount).

  However, adding any such option to cifs entry, such as "x-test.opt"
  (other than x-systemd.automount) results in:

  mount error(22): Invalid argument
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  No options starting with "x-" should be passed to mount.cifs, so the
  mount should succeed.

  Running Ubuntu 16.04.3 LTS
  mount package installed is 2.27.1-6ubuntu3.3

  This error always happens when such an option is specified. Here is an 
example fstab line that causes this failure:
  //192.168.1.3/Public/mnt/mybookcifs   
noauto,x-test.opt,rw,users,noperm,guest,soft,cache=none,sec=none  0  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mount 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 16 12:29:40 2017
  InstallationDate: Installed on 2016-04-22 (542 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1322854] Re: [4389W1B, Conexant CX20585, Speaker, Internal] Sound works for a while, then breaks

[Huseyin]

Hi, just re-installed Ubuntu 16.04.3, no audio from my speakers at all
on my Thinkpad W510. Please find attached Alsa Info document. In case of
more information needed, please contact me. Thank you.

** Attachment added: "Alsa Info from Thinkpad W510"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1322854/+attachment/4992893/+files/Alsa-Info

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

Title:
  [4389W1B, Conexant CX20585, Speaker, Internal] Sound works for a
  while, then breaks

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Today sound from speakers suddenly stopped while I was playing music.
  The problem persists reboot. Headphones work fine. When I dual-boot
  Windows on the same machine, there is no problem with the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ke 2142 F pulseaudio
   /dev/snd/controlC0:  ke 2142 F pulseaudio
ke 2726 F alsamixer
   /dev/snd/pcmC0D0p:   ke 2142 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Sat May 24 16:22:22 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-05-16 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ke 2142 F pulseaudio
   /dev/snd/controlC0:  ke 2142 F pulseaudio
ke 2726 F alsamixer
   /dev/snd/pcmC0D0p:   ke 2142 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [4389W1B, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET84WW (1.45 )
  dmi.board.name: 4389W1B
  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:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4389W1B:pvrThinkPadW510:rvnLENOVO:rn4389W1B:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4389W1B
  dmi.product.version: ThinkPad W510
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1726803] Re: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Steve Langasek]

It appears this is normal that the nvidia packages will upgrade to pull
in a newer version as a dependency.  This means we need to special-case
nvidia in /var/lib/dkms/nvidia-* to avoid triggering errors in
unattended upgrades.

** Package changed: unattended-upgrades (Ubuntu) => shim-signed (Ubuntu)

** Changed in: shim-signed (Ubuntu)
   Importance: Undecided => High

** Changed in: shim-signed (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in shim-signed package in Ubuntu:
  Triaged

Bug description:
  Occurred a minute after logging in

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .proc.sys.kernel.moksbstate_disabled: 0
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Oct 24 11:35:53 2017
  EFITables:
   Oct 24 11:33:04 paddy-laptop kernel: efi: EFI v2.40 by American Megatrends
   Oct 24 11:33:04 paddy-laptop kernel: efi:  ACPI=0x7866  ACPI 
2.0=0x7866  SMBIOS=0xf  SMBIOS 3.0=0xf0020  ESRT=0x79360598 
   Oct 24 11:33:04 paddy-laptop kernel: esrt: Reserving ESRT space from 
0x79360598 to 0x793605d0.
   Oct 24 11:33:04 paddy-laptop kernel: Secure boot enabled
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-09-11 (42 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SecureBoot: 6   0   0   0   1
  SourcePackage: shim-signed
  Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1726968] Re: mail.log stopped working - rsyslog package

[Seth Arnold]

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

** Changed in: rsyslog (Ubuntu)
   Status: New => Invalid

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

Title:
  mail.log stopped working - rsyslog package

Status in rsyslog package in Ubuntu:
  Invalid

Bug description:
  mail.log is not registering any activity. Attempted to reinstall
  rsyslog, change owner status on /var/log, change file permissions but
  nothing has worked so far. I want to be able to have a 'mail.log' file
  that logs things again. Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rsyslog 8.16.0-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 24 15:25:13 2017
  InstallationDate: Installed on 2017-07-22 (94 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 367211] Re: sed -i destroys symlink

[Aditya Gnaneshwar]

can we have a similar option for a hard link file?

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

Title:
  sed -i destroys symlink

Status in sed package in Ubuntu:
  Fix Released

Bug description:
  When using 'sed -i' on a symlink the symlink gets destroyed.
  Observe:

  % ls -l myfile symlink
  -rw-rw-r-- 1 miekg miekg 12 Apr 26 10:53 myfile
  lrwxrwxrwx 1 miekg miekg  6 Apr 26 10:53 symlink -> myfile

  # do an edit
  % sed -i 's/hello//' symlink

  % ls -l myfile symlink
  -rw-rw-r-- 1 miekg miekg 12 Apr 26 10:53 myfile
  -rw-rw-r-- 1 miekg miekg  7 Apr 26 10:54 symlink

  And gone is your symlink.

  This either a feature or a bug :)

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

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

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

[Bug Watch Updater]

** Changed in: backintime
   Status: Unknown => Fix Released

** Changed in: backintime
   Importance: Unknown => High

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

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

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

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

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

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

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

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

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

  
  


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

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

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

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

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

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

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

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

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

[Touch-packages] [Bug 1666676] Re: Install tracker by default

[Jeremy Bicha]

** Description changed:

- For Nautilus' built-in search to not be very slow, Nautilus needs to use
- tracker for search.
+ Benefits
+ 
+ 
+ 1. It speeds up searching for files in the Files app.
+ 
+ 2. It enables full-text search in the Files app. In other words, you can
+ look for files that contain specific words, instead of searching just by
+ filename.
+ 
+ 3. It allows the Batch Rename feature in the Files app able to rename
+ based on file metadata. For instance, you can use the Artist name for
+ properly tagged music files as part of the new file name.
+ 
+ Other Info
+ --
+ You can customize the folders it indexes from Settings > Search > gear button.
+ 
+ Original Bug Report
+ ===
+ For Nautilus' built-in search to not be very slow, Nautilus needs to use 
tracker for search.
  
  This is especially important since it's being seriously proposed for
  Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted
  the removal of that feature by Nautilus years ago. (LP: #181)
  
  To not cripple Ubuntu GNOME, it was previously decided to let Nautilus
  build against tracker but not use that functionality on Unity. See this
  patch:
  
  https://bazaar.launchpad.net/~ubuntu-
  
desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch
  
  This bug is requesting that patch be dropped and the extra tracker
  components be allowed into main and installed by default in Unity.

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

Title:
  Install tracker by default

Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Benefits
  

  1. It speeds up searching for files in the Files app.

  2. It enables full-text search in the Files app. In other words, you
  can look for files that contain specific words, instead of searching
  just by filename.

  3. It allows the Batch Rename feature in the Files app able to rename
  based on file metadata. For instance, you can use the Artist name for
  properly tagged music files as part of the new file name.

  Other Info
  --
  You can customize the folders it indexes from Settings > Search > gear button.

  Original Bug Report
  ===
  For Nautilus' built-in search to not be very slow, Nautilus needs to use 
tracker for search.

  This is especially important since it's being seriously proposed for
  Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted
  the removal of that feature by Nautilus years ago. (LP: #181)

  To not cripple Ubuntu GNOME, it was previously decided to let Nautilus
  build against tracker but not use that functionality on Unity. See
  this patch:

  https://bazaar.launchpad.net/~ubuntu-
  
desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch

  This bug is requesting that patch be dropped and the extra tracker
  components be allowed into main and installed by default in Unity.

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

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

[Touch-packages] [Bug 1726803] Re: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Launchpad Bug Tracker]

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Occurred a minute after logging in

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .proc.sys.kernel.moksbstate_disabled: 0
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Oct 24 11:35:53 2017
  EFITables:
   Oct 24 11:33:04 paddy-laptop kernel: efi: EFI v2.40 by American Megatrends
   Oct 24 11:33:04 paddy-laptop kernel: efi:  ACPI=0x7866  ACPI 
2.0=0x7866  SMBIOS=0xf  SMBIOS 3.0=0xf0020  ESRT=0x79360598 
   Oct 24 11:33:04 paddy-laptop kernel: esrt: Reserving ESRT space from 
0x79360598 to 0x793605d0.
   Oct 24 11:33:04 paddy-laptop kernel: Secure boot enabled
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-09-11 (42 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SecureBoot: 6   0   0   0   1
  SourcePackage: shim-signed
  Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1726757] Re: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Steve Langasek]

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

** Package changed: shim-signed (Ubuntu) => unattended-upgrades (Ubuntu)

** This bug has been marked a duplicate of bug 1726803
   package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1

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

Title:
  package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  When I start the computer, it come out the bug (or error I don't
  know).

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .proc.sys.kernel.moksbstate_disabled: 0
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Oct 24 06:28:31 2017
  EFITables:
   Oct 24 16:29:21 AceT kernel: efi: EFI v2.50 by Lenovo
   Oct 24 16:29:21 AceT kernel: efi:  SMBIOS=0x7ba44000  SMBIOS 3.0=0x7ba42000  
ACPI=0x7befe000  ACPI 2.0=0x7befe014  ESRT=0x7aea5000 
   Oct 24 16:29:21 AceT kernel: esrt: Reserving ESRT space from 
0x7aea5000 to 0x7aea5060.
   Oct 24 16:29:21 AceT kernel: Secure boot enabled
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-15 (162 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SecureBoot: 6   0   0   0   1
  SourcePackage: shim-signed
  Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1727072] Re: do-release-upgrade to 17.10 fails on Windows 10 17017

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1725333
   do-release-upgrade broke WSL

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

Title:
  do-release-upgrade to 17.10 fails on Windows 10 17017

Status in bash package in Ubuntu:
  New

Bug description:
  This is easily reproducible - install Ubuntu from the store, upgrade
  to 17.04 (succeeds), then upgrade again to 17.10 (fails)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bash 4.4-2ubuntu1.1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Oct 24 18:04:02 2017
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  DuplicateSignature:
   package:bash:4.4-2ubuntu1.1
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)

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

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

[Touch-packages] [Bug 1726757] [NEW] package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit statu

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I start the computer, it come out the bug (or error I don't know).

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Oct 24 06:28:31 2017
EFITables:
 Oct 24 16:29:21 AceT kernel: efi: EFI v2.50 by Lenovo
 Oct 24 16:29:21 AceT kernel: efi:  SMBIOS=0x7ba44000  SMBIOS 3.0=0x7ba42000  
ACPI=0x7befe000  ACPI 2.0=0x7befe014  ESRT=0x7aea5000 
 Oct 24 16:29:21 AceT kernel: esrt: Reserving ESRT space from 
0x7aea5000 to 0x7aea5060.
 Oct 24 16:29:21 AceT kernel: Secure boot enabled
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-05-15 (162 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SecureBoot: 6   0   0   0   1
SourcePackage: shim-signed
Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial
-- 
package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
https://bugs.launchpad.net/bugs/1726757
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to unattended-upgrades 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 1727072] [NEW] do-release-upgrade to 17.10 fails on Windows 10 17017

[Corey Frenette]

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

Public bug reported:

This is easily reproducible - install Ubuntu from the store, upgrade to
17.04 (succeeds), then upgrade again to 17.10 (fails)

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: bash 4.4-2ubuntu1.1
ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
Uname: Linux 4.4.0-43-Microsoft x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Tue Oct 24 18:04:02 2017
Dmesg:
 
DpkgTerminalLog:
 Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
 preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 
0' failed.
 dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
  subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
DuplicateSignature:
 package:bash:4.4-2ubuntu1.1
 Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
 preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 
0' failed.
 dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
  subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: bash
Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)

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


** Tags: amd64 apport-package artful uec-images

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

Title:
  do-release-upgrade to 17.10 fails on Windows 10 17017

Status in bash package in Ubuntu:
  New

Bug description:
  This is easily reproducible - install Ubuntu from the store, upgrade
  to 17.04 (succeeds), then upgrade again to 17.10 (fails)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bash 4.4-2ubuntu1.1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Oct 24 18:04:02 2017
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  DuplicateSignature:
   package:bash:4.4-2ubuntu1.1
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)

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

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

[Touch-packages] [Bug 1726093] Re: ubuntu-desktop: Install gir1.2-gmenu-3.0 by default

[Jeremy Bicha]

** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged => In Progress

** Description changed:

  Impact
  ==
  Ubuntu doesn't install particular files ( gir1.2-gmenu-3.0 ) that are needed 
by several popular GNOME Shell extensions.
  
  Test Case
  =
  Install the update to Ubuntu 17.10.
  Open the Ubuntu Software app.
  Search for Arc Menu
  Install it.
  There should be an A menu in the top left of the screen.
  
  Other Info
  ==
  Debian-based distros are somewhat unique in that they split gir files into 
separate packages. This is normally not a problem since .deb packages should 
simply depend on the packages they need. It is a bit of a problem for GNOME 
Shell extensions distributed through extensions.gnome.org since they can't 
depend on system packages except as a comment in the extension description that 
may or may be read even if it is mentioned.
  
  Specifically, there are several extensions that add a traditional
  applications menu to GNOME Shell. These usually need gir1.2-gmenu-3.0.
  
  This wasn't noticed much before because both Debian GNOME and Ubuntu
  GNOME installed the gnome-shell-extensions package by default which
  depends on gir1.2-gmenu-3.0.
  
  Now though, it just feels to users like Ubuntu is broken. I've read
  comments that think that Ubuntu is intentionally trying to make it
  difficult to use these app menu extensions.
+ 
+ Approved at the Ubuntu Desktop meeting (discussion continues until 15:09)
+ https://irclogs.ubuntu.com/2017/10/24/%23ubuntu-desktop.html#t14:44

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

Title:
  ubuntu-desktop: Install gir1.2-gmenu-3.0 by default

Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  Impact
  ==
  Ubuntu doesn't install particular files ( gir1.2-gmenu-3.0 ) that are needed 
by several popular GNOME Shell extensions.

  Test Case
  =
  Install the update to Ubuntu 17.10.
  Open the Ubuntu Software app.
  Search for Arc Menu
  Install it.
  There should be an A menu in the top left of the screen.

  Other Info
  ==
  Debian-based distros are somewhat unique in that they split gir files into 
separate packages. This is normally not a problem since .deb packages should 
simply depend on the packages they need. It is a bit of a problem for GNOME 
Shell extensions distributed through extensions.gnome.org since they can't 
depend on system packages except as a comment in the extension description that 
may or may be read even if it is mentioned.

  Specifically, there are several extensions that add a traditional
  applications menu to GNOME Shell. These usually need gir1.2-gmenu-3.0.

  This wasn't noticed much before because both Debian GNOME and Ubuntu
  GNOME installed the gnome-shell-extensions package by default which
  depends on gir1.2-gmenu-3.0.

  Now though, it just feels to users like Ubuntu is broken. I've read
  comments that think that Ubuntu is intentionally trying to make it
  difficult to use these app menu extensions.

  Approved at the Ubuntu Desktop meeting (discussion continues until 15:09)
  https://irclogs.ubuntu.com/2017/10/24/%23ubuntu-desktop.html#t14:44

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

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

[Touch-packages] [Bug 1726960] Re: Installation of network-manager-config-connectivity-ubuntu fails when installing ubuntu-desktop task from mini.iso

[Thomas Ward]

Sebastien:

Yeah, it complains because when it tries to execute its postinstall
tasks, the Network Manager service isn't yet started.

My suggestion would be to test if the service is actually in a 'running'
state or not before trying to install, and if not, attempt to start the
service.  That's probably just a handful of lines in the postinst file,
but that's the exact error, it fails to configure proper in its
postinstallation tasks because the service wasn't running and it
couldn't connect to it.

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

Title:
  Installation of network-manager-config-connectivity-ubuntu fails when
  installing ubuntu-desktop task from mini.iso

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Installation of this package as part of the Ubuntu Desktop task fails
  if being executed from the mini.iso after installation.  This is due
  to teh Network Manager service not running when it tries to install
  itself.

  This seems like it might be related to
  https://bugs.launchpad.net/ubuntu/+source/network-manager-
  applet/+bug/1726958 in some way, as they both happened on a 17.10
  installation installed from the mini.iso and the command line (no GUI
  initially).

  This issue does *not* happen with the Ubuntu Desktop ISOs.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:17:34 2017
  IpRoute:
   default via 192.168.226.2 dev ens33 proto dhcp src 192.168.226.131 metric 
100 
   192.168.226.0/24 dev ens33 proto kernel scope link src 192.168.226.131 
   192.168.226.2 dev ens33 proto dhcp scope link src 192.168.226.131 metric 100
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   ens33   ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --   
   ----   
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4disconnected  started  unknown   enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1726960] Re: Installation of network-manager-config-connectivity-ubuntu fails when installing ubuntu-desktop task from mini.iso

[Thomas Ward]

Note that if you manually start the network manager service and then do
`apt-get install -f` or `sudo dpkg-reconfigure network-manager-config-
connectivity-ubuntu`, it appears to work.  So something in the apt
ordering is not starting network manager once it's been installed, so a
`sudo apt-get install ubuntu-desktop^` call as per the wiki to emulate
the tasksel task itself post-install of the system will fail only on
that package.

This assumes of course one's starting from a barebones mini.iso
installation, and hasn't done any custom configuration.

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

Title:
  Installation of network-manager-config-connectivity-ubuntu fails when
  installing ubuntu-desktop task from mini.iso

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Installation of this package as part of the Ubuntu Desktop task fails
  if being executed from the mini.iso after installation.  This is due
  to teh Network Manager service not running when it tries to install
  itself.

  This seems like it might be related to
  https://bugs.launchpad.net/ubuntu/+source/network-manager-
  applet/+bug/1726958 in some way, as they both happened on a 17.10
  installation installed from the mini.iso and the command line (no GUI
  initially).

  This issue does *not* happen with the Ubuntu Desktop ISOs.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:17:34 2017
  IpRoute:
   default via 192.168.226.2 dev ens33 proto dhcp src 192.168.226.131 metric 
100 
   192.168.226.0/24 dev ens33 proto kernel scope link src 192.168.226.131 
   192.168.226.2 dev ens33 proto dhcp scope link src 192.168.226.131 metric 100
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   ens33   ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --   
   ----   
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4disconnected  started  unknown   enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

[Isak Asp]

Bose QC 35 pairs nice with 17.10, but experience a lot of lag and
jitter.

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

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

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

[Touch-packages] [Bug 1726504] Re: Was there a change of RemoveIPC semantics in Ubuntu 17.10?

[Renardo]

:I just wrote “Oracle-ignorant” but I think the correct expression is
“Oracle-agnostic”. Sorry. Foreign languages have always been my problem.

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

Title:
  Was there a change of RemoveIPC semantics in Ubuntu 17.10?

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  A few days ago I upgraded my Ubuntu 17.04 to 17.10. Afterwards I found
  that my Oracle XE would no longer start. alert_XE.log said things like

  ORA-27300: OS system dependent operation:semctl failed with status: 22
  ORA-27301: OS failure message: Invalid argument
  ORA-27302: failure occurred at: sskgpwrm1
  ORA-27157: OS post/wait facility removed
  ORA-27300: OS system dependent operation:semop failed with status: 43
  ORA-27301: OS failure message: Identifier removed
  ORA-27302: failure occurred at: sskgpwwait1

  I found that /etc/systemd/logind.conf had the RemoveIPC line commented
  out. When I set RemoveIPC=no (the default is “yes”) and rebooted
  Linux, Oracle XE started fine, as it had before the upgrade. So I
  assume the 17.10 upgrade somehow made a change to the RemoveIPC
  semantics.

  As I found that my previous installation also had a commented
  RemoveRPC it looks like Ubuntu 17.10 changed the default value from
  “no” to “yes”, and so breaks the Oracle XE installation. In this case
  I consider this behavior problematic, it should at least produce a
  clear warning during upgrade.

  If the default value did not change I have no explanation of the
  phenomenon.

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

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

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

[Norbert]

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

** Also affects: backintime via
   https://bugzilla.gnome.org/show_bug.cgi?id=776437
   Importance: Unknown
   Status: Unknown

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

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

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

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

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

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

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

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

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

  
  


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

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

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 

[Touch-packages] [Bug 1726960] Re: Installation of network-manager-config-connectivity-ubuntu fails when installing ubuntu-desktop task from mini.iso

[Sebastien Bacher]

Thank you for your bug report, could you give details on the error you
get?

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

Title:
  Installation of network-manager-config-connectivity-ubuntu fails when
  installing ubuntu-desktop task from mini.iso

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Installation of this package as part of the Ubuntu Desktop task fails
  if being executed from the mini.iso after installation.  This is due
  to teh Network Manager service not running when it tries to install
  itself.

  This seems like it might be related to
  https://bugs.launchpad.net/ubuntu/+source/network-manager-
  applet/+bug/1726958 in some way, as they both happened on a 17.10
  installation installed from the mini.iso and the command line (no GUI
  initially).

  This issue does *not* happen with the Ubuntu Desktop ISOs.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:17:34 2017
  IpRoute:
   default via 192.168.226.2 dev ens33 proto dhcp src 192.168.226.131 metric 
100 
   192.168.226.0/24 dev ens33 proto kernel scope link src 192.168.226.131 
   192.168.226.2 dev ens33 proto dhcp scope link src 192.168.226.131 metric 100
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   ens33   ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --   
   ----   
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4disconnected  started  unknown   enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1727043] Re: random screen rotation of laptop disply when using additional screen.

[Springnuts]

Grateful if an admin could correct my typo in the heading.

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

Title:
  random screen rotation of laptop disply when using additional screen.

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm on 17.10.  One screen - the laptop screen - rotates at random,
  typically when a video is playing, but not, I think always.  It
  rotates 180 degrees and stays upside down.  Mouse movememnts are
  reversed (ie correct for  the orientation of the screen).

  I tried

  gsettings set org.gnome.settings-daemon.plugins.orientation active
  false

  following a thread here https://askubuntu.com/questions/968169/screen-
  randomly-rotates-on-ubuntu-17-10/968284

  but it doesn't stop the behaviour.

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

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

[Touch-packages] [Bug 1727043] [NEW] random screen rotation of laptop disply when using additional screen.

[Springnuts]

Public bug reported:

I'm on 17.10.  One screen - the laptop screen - rotates at random,
typically when a video is playing, but not, I think always.  It rotates
180 degrees and stays upside down.  Mouse movememnts are reversed (ie
correct for  the orientation of the screen).

I tried

gsettings set org.gnome.settings-daemon.plugins.orientation active false

following a thread here https://askubuntu.com/questions/968169/screen-
randomly-rotates-on-ubuntu-17-10/968284

but it doesn't stop the behaviour.

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

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

Title:
  random screen rotation of laptop disply when using additional screen.

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm on 17.10.  One screen - the laptop screen - rotates at random,
  typically when a video is playing, but not, I think always.  It
  rotates 180 degrees and stays upside down.  Mouse movememnts are
  reversed (ie correct for  the orientation of the screen).

  I tried

  gsettings set org.gnome.settings-daemon.plugins.orientation active
  false

  following a thread here https://askubuntu.com/questions/968169/screen-
  randomly-rotates-on-ubuntu-17-10/968284

  but it doesn't stop the behaviour.

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

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

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

[Andreas Hasenack]

I meant in the ssh localhost test case that you showed. But still, even
in the remote case, the "X server" would be your local machine and the X
api calls from matlab would be routed to your local X server (wayland or
xorg) through the ssh connection.

So, just to clarify, matlab works on your localhost when ssh is not
used? I.e., just opening a terminal and running "matlab" followed by the
plot command?

And if you repeat the above but first do a "ssh -X localhost", i.e., the
DISPLAY variable is something other than just ":0", then it doesn't
work?

Both scenarios above stay the same regardless if you are using wayland
or xorg in Ubuntu Artful?

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

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

Status in openssh package in Ubuntu:
  Incomplete

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

  REPRODUCE THE BUG:

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

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

  2. Launch matlab
  $ matlab &

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

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

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

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

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

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

[Markus Birth]

Confirmed on a hp Spectre x360 13-4104ng.

On battery power, the system DOESN'T boot up.

With the charger connected, the system boots up just fine.


See https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458 for my 
apport logs.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Andrea Azzarone]

Hi all, there's already a proposed fix for gtk+ upstream. I'm preparing a
distro patch to SRU the issue.

On 24 Oct 2017 19:11, "gloonie"  wrote:

> Ditto here. I added a Google account also. This was after a fresh
> install.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1720400
>
> Title:
>   /usr/bin/gnome-control-
>   center:11:update_buffers:image_get_buffers:intel_
> update_image_buffers:intel_update_renderbuffers:intel_prepare_render
>
> Status in GTK+:
>   Confirmed
> Status in gnome-control-center package in Ubuntu:
>   In Progress
> Status in gtk+3.0 package in Ubuntu:
>   In Progress
>
> Bug description:
>   The Ubuntu Error Tracker has been receiving reports about a problem
> regarding gnome-control-center.  This problem was most recently seen with
> package version 1:3.26.0-0ubuntu3, the problem page at
> https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a
> contains more details, including versions of packages affected, stacktrace
> or traceback, and individual crash reports.
>   If you do not have access to the Ubuntu Error Tracker and are a software
> developer, you can request it at http://forms.canonical.com/reports/.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gtk/+bug/1720400/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=gtk; status=Confirmed; importance=Medium;
> assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-control-center;
> component=main; status=In Progress; importance=High; assignee=
> andrea.azzar...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=gtk+3.0; component=main;
> status=In Progress; importance=High; assignee=andrea.azzarone@
> canonical.com;
> Launchpad-Bug-Tags: artful zesty
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: alvinc azzar1 gloonie gonzo-dark janitor
> oliver-gerhardt pjsingh5000 whoopsie-daisy-bug-bridge
> Launchpad-Bug-Reporter: errors.ubuntu.com bug bridge
> (whoopsie-daisy-bug-bridge)
> Launchpad-Bug-Modifier: gloonie (gloonie)
> Launchpad-Message-Rationale: Assignee
> Launchpad-Message-For: azzar1
>

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

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

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

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

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

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

[Touch-packages] [Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful

[Markus Birth]

Yes, this seems to be a duplicate of your bug.

On battery power, the system DOESN'T boot up.

With the charger connected, the system boots up just fine.

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

Title:
  System unbootable with root fs mounted ro after update to systemd
  234-2ubuntu12 (from 234-2ubuntu10) on artful

Status in systemd package in Ubuntu:
  New

Bug description:
  After not touching my notebook since 30th September (where I did the
  dist-upgrade to artful and installed all available updates), I did all
  available updates today (20th October) and the system didn't boot
  after that.

  The last message I see is "Reached target Bluetooth". Before that,
  there are several failed services. GDM doesn't come up.

  After logging in on tty2, I saw that the root partition was mounted
  read-only. Inspecting the messages of e.g. systemd-resolved shows that
  it didn't start because of the read-only filesystem. After remounting
  it fw, I was able to restart the daemons and could also start GDM and
  login fine.

  My fstab shows:

  UUID=a936dbe9-5ab5-4272-aaae-d22030824373 /   ext4
  errors=remount-ro 0   1

  
  The UUID is correct as "mount / -o remount,rw" works fine. Booting with the 
previous kernel doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 20 21:46:36 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-26 (451 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago)
  dmi.bios.date: 09/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81A1
  dmi.board.vendor: HP
  dmi.board.version: 33.76
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1725455] Re: Login screen invisible / UI hanging when both 4K monitors connected via Displayport MST (docking station)

[Nicolas Ramoudt]

** Summary changed:

- UI login invisible / UI hanging when Dual 4K monitor via Displayport MST is 
connected (Lenovo Ultra Dock)
+ Login screen invisible / UI hanging when both 4K monitors connected via 
Displayport MST (docking station)

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

Title:
  Login screen invisible / UI hanging when both 4K monitors connected
  via Displayport MST (docking station)

Status in xorg package in Ubuntu:
  New

Bug description:
  I am experiencing serious issues after upgrading to Ubuntu 17.10
  (coming from 17.04 with Gnome, kernel 4.13).

  I have 2 x 4K (Asus PB279Q) monitors, connected to a Lenovo Ultra Dock
  (containing 2 x Displayport  via MST), where the Lenovo T550 is
  connected onto it.  Both monitors were working perfectly fine at 30Hz
  simultaneously in an extended desktop, 4K resolution in my old setup
  with Gnome for over half a year (since kernel 4.10 blink issues on 4K
  were solved, i used this setup since then).

  However after upgrading to 17.10 using the new Gnome interface:
  When the laptop is connected to the Lenovo Ultra Dock (to work on both 
monitors), the system is hanging and becoming unresponsive.  The mouse pointer 
is freezing and the only way is to do a hard-reboot.  I have checked the 
monitor settings, it's displayed at 60Hz when active, and it appears I am never 
able to use both monitors simultaneously.  When I get 1 monitor working 
(disconnecting the 2nd monitor from the MST port), after rebooting it works 
fine.  I tried to put settings of the 4K manually on 30Hz, reconnecting, but 
the system hangs again.  I have tried several combinations.  It results in a 
blank (purple) screen and hanging mouse (see attachment).

  I tried also with the installation-iso to run a fresh 17.10 and tried
  the same, the symptoms are similar.  I suspect that must be an issue
  with the Displayport MST on dual 4K setups in the new 17.10.

  When I connect 1 x 4K monitor to the rear displayport of the Lenovo
  Ultra Dock (there are 2 for MST on the rear, so I disconnected the
  other) *and* when I connect the other 4K monitor on the separate
  displayport of the T550 itself instead, it works 100% fine!

  Shortly: based on my knowledge that must definitely be some issue with
  the MST displayport functionality itself, that is unable to
  recognize/identify both 4K monitors when connected to the dock's both
  displayport connections?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.13.4-041304-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 21:10:50 2017
  DistUpgraded: 2017-10-19 21:54:53,162 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2225]
 Subsystem: Lenovo GM108M [GeForce 940M] [17aa:2225]
  InstallationDate: Installed on 2017-04-16 (186 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20CKCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.4-041304-generic 
root=UUID=9fcc7f4c-35c0-4297-9c98-4dac9acee798 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET42W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CKCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CKCTO1WW
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  

[Touch-packages] [Bug 1727039] [NEW] Xorg crash

[Daniel C Aragao]

Public bug reported:

I got some messages in logs program.

Message:
"CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erro ao chamar 
StartServiceByName para org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1"


Message: 
"Unrecoverable failure in required component org.gnome.Shell.desktop"

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
BootLog:
 
CompositorRunning: None
CurrentDesktop: GNOME
Date: Tue Oct 24 16:32:43 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755]
InstallationDate: Installed on 2017-10-19 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P06RCX.075.160311.JJ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP370E4K-KW3BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW3BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.family: SAMSUNG ATIV
dmi.product.name: 370E4K
dmi.product.version: P06RCX
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  I got some messages in logs program.

  Message:
  "CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erro ao chamar 
StartServiceByName para org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1"

  
  Message: 
  "Unrecoverable failure in required component org.gnome.Shell.desktop"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 24 16:32:43 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755]
  InstallationDate: Installed on 2017-10-19 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RCX.075.160311.JJ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP370E4K-KW3BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240
  

[Touch-packages] [Bug 1726647] Re: crash reports still sent to LP on artful

[Brian Murray]

verification done on artful:

Setting up apport (2.20.7-0ubuntu3.1) ...
Installing new version of config file /etc/apport/crashdb.conf ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for hicolor-icon-theme (0.17-1) ...
[ 12:18PM 10296 ]  [ bdmurray@impulse:~ ]
 $ cat /etc/apport/crashdb.conf
# map crash database names to CrashDatabase implementations and URLs

default = 'ubuntu'

def get_oem_project():
'''Determine OEM project name from Distribution Channel Descriptor

Return None if it cannot be determined or does not exist.
'''
try:
dcd = open('/var/lib/ubuntu_dist_channel').read()
if dcd.startswith('canonical-oem-'):
return dcd.split('-')[2]
except IOError:
return None

databases = {
'ubuntu': {
'impl': 'launchpad',
'problem_types': ['Bug', 'Package'],
'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
'distro': 'ubuntu',
'escalation_tag': 'bugpattern-needed',
'escalated_tag': 'bugpattern-written',
},


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

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

Title:
  crash reports still sent to LP on artful

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Artful:
  Fix Committed

Bug description:
  /etc/apport/crashdb.conf was not modified to stop sending crash
  reports to Launchpad for Ubuntu 17.10, since it was released they
  should only be going to errors.ubuntu.com.

  The problem_types field needs to change to ['Bug', 'Package'].

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 17:43:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1741 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[thomas duriez]

Dear Andreas,

It was tried in all three modes. 
Furthermore how do I enforce Xorg when I log from another machine (in my case a 
windows running Xming) to this one ?
I suspect once I connect through ssh with X11 forwarding, the session is Xorg.  

Thanks for your time.

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

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

Status in openssh package in Ubuntu:
  Incomplete

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

  REPRODUCE THE BUG:

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

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

  2. Launch matlab
  $ matlab &

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

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

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

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

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

[Touch-packages] [Bug 1726504] Re: Was there a change of RemoveIPC semantics in Ubuntu 17.10?

[Renardo]

Thanks, Dimitri John Ledkov, for your kind interest in my report and for
your remarks. It's not so easy to experiment with my system during
(European) daytime, I need it to make a living.

I had not seen bug 1671760 before (the number is somehow reminiscent of
the Beagle Boys, isn't it?); I now looked at it but fail to see anything
familiar. Sorry.

I now did what I maybe should have done before – check for
reproducibility. Unfortunately it is not a problem at all. When I
comment out the “RemoveIPC=no” in /etc/systemd/logind.conf and reboot
Linux, Oracle XE fails. When I restore the entry and reboot, Oracle XE
works. Just logging out and in again does not change anything.

I have no backups of the /etc directory but I have a second PC which has
not been updated to Ubuntu 17.10 (so the name is “artful”, thanks, but I
never remember such names). The “RemoveIPC” line is commented out there
as well, which confirms your assumption that nothing was changed on
upgrade. But Oracle had no problems running on this machine. And I doubt
that upgrading to Ubuntu 17.10 did in any way touch Oracle XE; certainly
Ubuntu is not supposed to know anything about Oracle (on the contrary,
to be Oracle-ignorant).

In my /var/log/apt/ directory there are term.log and history.log files.
I suppose they are not of much help. It looks like the question is not
so much “why did Oracle stop working” but “why did it work before.”

If it's evident that the treatment of RemoveIPC did not change between
Zesty and Artful I can live with the changed RemoveIPC and would agree
to close the 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/1726504

Title:
  Was there a change of RemoveIPC semantics in Ubuntu 17.10?

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  A few days ago I upgraded my Ubuntu 17.04 to 17.10. Afterwards I found
  that my Oracle XE would no longer start. alert_XE.log said things like

  ORA-27300: OS system dependent operation:semctl failed with status: 22
  ORA-27301: OS failure message: Invalid argument
  ORA-27302: failure occurred at: sskgpwrm1
  ORA-27157: OS post/wait facility removed
  ORA-27300: OS system dependent operation:semop failed with status: 43
  ORA-27301: OS failure message: Identifier removed
  ORA-27302: failure occurred at: sskgpwwait1

  I found that /etc/systemd/logind.conf had the RemoveIPC line commented
  out. When I set RemoveIPC=no (the default is “yes”) and rebooted
  Linux, Oracle XE started fine, as it had before the upgrade. So I
  assume the 17.10 upgrade somehow made a change to the RemoveIPC
  semantics.

  As I found that my previous installation also had a commented
  RemoveRPC it looks like Ubuntu 17.10 changed the default value from
  “no” to “yes”, and so breaks the Oracle XE installation. In this case
  I consider this behavior problematic, it should at least produce a
  clear warning during upgrade.

  If the default value did not change I have no explanation of the
  phenomenon.

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

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

[Touch-packages] [Bug 1726803] Re: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Steve Langasek]

I'm surprised to see that your nvidia stack is being switched as part of
an unattended upgrade.  Reassigning to the unattended-upgrades package
for further investigation.

In order to fix the particular upgrade failure, you should run 'sudo apt
-f install' from a terminal.  Note that you must complete the process of
disabling SecureBoot, which requires a reboot, in order to use the
nvidia driver on a SecureBoot-enabled system.

** Package changed: shim-signed (Ubuntu) => unattended-upgrades (Ubuntu)

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

Title:
  package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Occurred a minute after logging in

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .proc.sys.kernel.moksbstate_disabled: 0
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Oct 24 11:35:53 2017
  EFITables:
   Oct 24 11:33:04 paddy-laptop kernel: efi: EFI v2.40 by American Megatrends
   Oct 24 11:33:04 paddy-laptop kernel: efi:  ACPI=0x7866  ACPI 
2.0=0x7866  SMBIOS=0xf  SMBIOS 3.0=0xf0020  ESRT=0x79360598 
   Oct 24 11:33:04 paddy-laptop kernel: esrt: Reserving ESRT space from 
0x79360598 to 0x793605d0.
   Oct 24 11:33:04 paddy-laptop kernel: Secure boot enabled
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-09-11 (42 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SecureBoot: 6   0   0   0   1
  SourcePackage: shim-signed
  Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1726803] [NEW] package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit statu

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Occurred a minute after logging in

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Oct 24 11:35:53 2017
EFITables:
 Oct 24 11:33:04 paddy-laptop kernel: efi: EFI v2.40 by American Megatrends
 Oct 24 11:33:04 paddy-laptop kernel: efi:  ACPI=0x7866  ACPI 
2.0=0x7866  SMBIOS=0xf  SMBIOS 3.0=0xf0020  ESRT=0x79360598 
 Oct 24 11:33:04 paddy-laptop kernel: esrt: Reserving ESRT space from 
0x79360598 to 0x793605d0.
 Oct 24 11:33:04 paddy-laptop kernel: Secure boot enabled
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-09-11 (42 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SecureBoot: 6   0   0   0   1
SourcePackage: shim-signed
Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial
-- 
package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
https://bugs.launchpad.net/bugs/1726803
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to unattended-upgrades 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 1726647] Re: crash reports still sent to LP on artful

[Steve Langasek]

Hello Brian, or anyone else affected,

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

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

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

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

** Changed in: apport (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  crash reports still sent to LP on artful

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Artful:
  Fix Committed

Bug description:
  /etc/apport/crashdb.conf was not modified to stop sending crash
  reports to Launchpad for Ubuntu 17.10, since it was released they
  should only be going to errors.ubuntu.com.

  The problem_types field needs to change to ['Bug', 'Package'].

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 17:43:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1741 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Andreas Hasenack]

Are you using Wayland? If yes, can you try with plain Xorg? To switch to
xorg, logout, and on the login screen, after clicking on your name, you
will see a small gear icon. Click that to select xorg, and then continue
with the login.

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

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

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

Status in openssh package in Ubuntu:
  Incomplete

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

  REPRODUCE THE BUG:

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

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

  2. Launch matlab
  $ matlab &

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

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

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

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

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

[Touch-packages] [Bug 1726965] Re: lsb_release crashed with SIGSEGV

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  lsb_release crashed with SIGSEGV

Status in lsb package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: lsb-release 9.20160110ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 24 17:33:36 2017
  ExecutablePath: /usr/bin/lsb_release
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 -Es /usr/bin/lsb_release -c -s
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x4aeca8:  subq   $0x1,(%rdi)
   PC (0x004aeca8) ok
   source "$0x1" ok
   destination "(%rdi)" (0x7f8509de7530) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: lsb
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: lsb_release crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1726973] Re: dpkg-preconfigure crashed with SIGSEGV in Perl_sv_clear()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  dpkg-preconfigure crashed with SIGSEGV in Perl_sv_clear()

Status in debconf package in Ubuntu:
  New

Bug description:
  

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: debconf 1.5.63
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Oct 24 17:39:55 2017
  ExecutablePath: /usr/sbin/dpkg-preconfigure
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterpreterPath: /usr/bin/perl
  PackageArchitecture: all
  ProcCmdline: /usr/bin/perl -w /usr/sbin/dpkg-preconfigure --apt
  SegvAnalysis:
   Segfault happened at: 0x56250468e50a :   movzbl 
(%rsi),%edx
   PC (0x56250468e50a) ok
   source "(%rsi)" (0x566505cfd9c1) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: debconf
  StacktraceTop:
   Perl_sv_clear ()
   Perl_sv_free2 ()
   ?? ()
   Perl_sv_clean_objs ()
   perl_destruct ()
  Title: dpkg-preconfigure crashed with SIGSEGV in Perl_sv_clear()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1726975] Re: dpkg-preconfigure crashed with SIGSEGV in Perl_sv_clear()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  dpkg-preconfigure crashed with SIGSEGV in Perl_sv_clear()

Status in debconf package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: debconf 1.5.63
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Oct 24 17:39:55 2017
  ExecutablePath: /usr/sbin/dpkg-preconfigure
  ExecutableTimestamp: 1499822627
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterpreterPath: /usr/bin/perl
  PackageArchitecture: all
  ProcCmdline: /usr/bin/perl -w /usr/sbin/dpkg-preconfigure --apt
  ProcCwd: /home/adnan
  SegvAnalysis:
   Segfault happened at: 0x56250468e50a :   movzbl 
(%rsi),%edx
   PC (0x56250468e50a) ok
   source "(%rsi)" (0x566505cfd9c1) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: debconf
  StacktraceTop:
   Perl_sv_clear ()
   Perl_sv_free2 ()
   ?? ()
   Perl_sv_clean_objs ()
   perl_destruct ()
  Title: dpkg-preconfigure crashed with SIGSEGV in Perl_sv_clear()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1495276] Re: cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free: Assertion `*_head == _item' failed.

[Steve Langasek]

This bug was asserted fixed in 2.2.4-4, but I just had a crash with
2.2.4-7ubuntu2 in Ubuntu 17.10 that was reported to be a duplicate of
this issue.

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

** Changed in: cups (Ubuntu)
 Assignee: VOIRIN ERIC (evoirin-9) => (unassigned)

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

Title:
  cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free:
  Assertion `*_head == _item' failed.

Status in cups package in Ubuntu:
  Triaged

Bug description:
  This crash just appeared during startup.
  Lots of CUPS updates and errors lately.
   Printer and scanner have worked mostly one way or the other using different 
apps.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: cups-daemon 2.1.0-1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AssertionMessage: cupsd: entrygroup.c:245: avahi_entry_group_free: Assertion 
`*_head == _item' failed.
  CrashCounter: 1
  Date: Sat Sep 12 22:57:48 2015
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2015-01-29 (226 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat:
   device for Brother-DCP-7065DN: 
dnssd://Brother%20DCP-7065DN._pdl-datastream._tcp.local/
   device for Brother-DCP-7065DN-2: 
dnssd://Brother%20DCP-7065DN._pdl-datastream._tcp.local/
   device for david@david-Lenovo-H535: 
dnssd://Brother%20DCP-7065DN._pdl-datastream._tcp.local/
   device for PDF: cups-pdf:/
  MachineType: LENOVO 10117
  Papersize: letter
  PpdFiles:
   david@david-Lenovo-H535: Brother DCP-7065DN, using brlaser v3
   PDF: Generic CUPS-PDF Printer
   Brother-DCP-7065DN-2: Brother DCP-7065DN, using brlaser v3
   Brother-DCP-7065DN: Brother DCP-7065DN, using brlaser v3
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=94709fac-8bfa-41bf-8d29-24abdd9f77cc ro drm.debug=0xe plymouth:debug
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=94709fac-8bfa-41bf-8d29-24abdd9f77cc ro drm.debug=0xe plymouth:debug
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __assert_fail_base (fmt=0x7fed6ded1028 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fed6e80d132 "*_head == _item", 
file=file@entry=0x7fed6e80d117 "entrygroup.c", line=line@entry=245, 
function=function@entry=0x7fed6e80d3b0 "avahi_entry_group_free") at assert.c:92
   __GI___assert_fail (assertion=0x7fed6e80d132 "*_head == _item", 
file=0x7fed6e80d117 "entrygroup.c", line=245, function=0x7fed6e80d3b0 
"avahi_entry_group_free") at assert.c:101
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
  Title: cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free: 
Assertion `*_head == _item' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I7KT31AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 STD
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrI7KT31AUS:bd11/05/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STD:cvnLENOVO:ct3:cvr:
  dmi.product.name: 10117
  dmi.product.version: Lenovo H535
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-04-16T18:25:57

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

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

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

[Launchpad Bug Tracker]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  When the user purged laptop-mode-tools the system 

[Touch-packages] [Bug 1631631] Re: Trivial bug in man documentation: forgotten --strip-unneeded option in objcopy SYNOPSIS

[Launchpad Bug Tracker]

** Branch linked: lp:~lkocia/binutils/stripunneeded_manpage

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

Title:
  Trivial bug in man documentation: forgotten --strip-unneeded option in
  objcopy SYNOPSIS

Status in One Hundred Papercuts:
  Confirmed
Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  In the man page of "objcopy" the "--strip-unneeded" option:
  - is described in OPTIONS section;
  - but is forgotten in SYNOPSIS section (don't confuse with 
"--strip-unneeded-symbol=" and "--strip-unneeded-symbols=", which aren't 
forgotten).

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

  $ apt-cache policy binutils
  binutils:
Installed: 2.26.1-1ubuntu1~16.04.3
Candidate: 2.26.1-1ubuntu1~16.04.3
Version table:
   *** 2.26.1-1ubuntu1~16.04.3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.26-8ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I expected SYNOPSIS and OPTIONS sections of the man page of "objcopy"
  to be consistent.

  Option "--strip-unneeded" present in OPTIONS section, is absent in
  SYNOPSIS section.

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

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

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

[Launchpad Bug Tracker]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  When the user purged laptop-mode-tools the 

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

[Nikhil Verma]

Is there an official solution yet? BTW https://askubuntu.com/a/968309/
seemed to help me out.

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

Title:
  systemd-resolved using 100% CPU

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

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

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

  strace output:

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

  journalctl output:

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

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

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

[Touch-packages] [Bug 1726818] Dependencies.txt

[Scott Moser]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1726818/+attachment/4992312/+files/Dependencies.txt

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

Title:
  vagrant artful64 box filesystem too small

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After building a new vagrant instance using the ubuntu/artful64 box
  (v20171023.1.0), the size of the filesystem seems to be much too
  small. Here's the output of `df -h` on the newly built instance:

  vagrant@ubuntu-artful:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev991M 0  991M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   2.2G  2.1G   85M  97% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  182G   28G  87% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  For comparison, here is the same from the latest zesty64 box:

  ubuntu@ubuntu-zesty:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev992M 0  992M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   9.7G  2.5G  7.3G  26% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  183G   28G  88% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  With artful64, the size of /dev/sda1 is reported as 2.2G, which results in 
97% of disk usage immediately after building, even though the disk size is 10G, 
as reported by the fdisk:

  
  vagrant@ubuntu-artful:~$ sudo fdisk -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x4ad77c39

  Device Boot Start  End  Sectors Size Id Type
  /dev/sda1  * 2048 20971486 20969439  10G 83 Linux

  
  Disk /dev/sdb: 10 MiB, 10485760 bytes, 20480 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes

  
  Almost any additional installation results in a "No space left on device" 
error.

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

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

[Touch-packages] [Bug 1726818] ProcCpuinfoMinimal.txt

[Scott Moser]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1726818/+attachment/4992313/+files/ProcCpuinfoMinimal.txt

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

** No longer affects: e2fsprogs (Ubuntu)

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

Title:
  vagrant artful64 box filesystem too small

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After building a new vagrant instance using the ubuntu/artful64 box
  (v20171023.1.0), the size of the filesystem seems to be much too
  small. Here's the output of `df -h` on the newly built instance:

  vagrant@ubuntu-artful:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev991M 0  991M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   2.2G  2.1G   85M  97% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  182G   28G  87% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  For comparison, here is the same from the latest zesty64 box:

  ubuntu@ubuntu-zesty:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev992M 0  992M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   9.7G  2.5G  7.3G  26% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  183G   28G  88% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  With artful64, the size of /dev/sda1 is reported as 2.2G, which results in 
97% of disk usage immediately after building, even though the disk size is 10G, 
as reported by the fdisk:

  
  vagrant@ubuntu-artful:~$ sudo fdisk -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x4ad77c39

  Device Boot Start  End  Sectors Size Id Type
  /dev/sda1  * 2048 20971486 20969439  10G 83 Linux

  
  Disk /dev/sdb: 10 MiB, 10485760 bytes, 20480 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes

  
  Almost any additional installation results in a "No space left on device" 
error.

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

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

[Touch-packages] [Bug 1726818] apport information

[Scott Moser]

ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
DistroRelease: Ubuntu 17.10
Ec2AMI: ami-02da
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
Package: linux
PackageArchitecture: amd64
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Tags:  artful ec2-images
Uname: Linux 4.13.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
_MarkForUpload: True

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

Title:
  vagrant artful64 box filesystem too small

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After building a new vagrant instance using the ubuntu/artful64 box
  (v20171023.1.0), the size of the filesystem seems to be much too
  small. Here's the output of `df -h` on the newly built instance:

  vagrant@ubuntu-artful:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev991M 0  991M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   2.2G  2.1G   85M  97% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  182G   28G  87% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  For comparison, here is the same from the latest zesty64 box:

  ubuntu@ubuntu-zesty:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev992M 0  992M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   9.7G  2.5G  7.3G  26% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  183G   28G  88% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  With artful64, the size of /dev/sda1 is reported as 2.2G, which results in 
97% of disk usage immediately after building, even though the disk size is 10G, 
as reported by the fdisk:

  
  vagrant@ubuntu-artful:~$ sudo fdisk -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x4ad77c39

  Device Boot Start  End  Sectors Size Id Type
  /dev/sda1  * 2048 20971486 20969439  10G 83 Linux

  
  Disk /dev/sdb: 10 MiB, 10485760 bytes, 20480 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes

  
  Almost any additional installation results in a "No space left on device" 
error.

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

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

[Touch-packages] [Bug 1726818] Re: vagrant artful64 box filesystem too small

[Scott Moser]

So the/some interesting points of dmesg.log:

[0.00] random: get_random_bytes called from start_kernel+0x42/0x4e1 
with crng_init=0
[0.00] Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 
7.2.0 (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
(Ubuntu 4.13.0-16.19-generic 4.13.4)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] XSAVE consistency problem, dumping leaves
[0.00] [ cut here ]
[0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-XO_uEE/linux-4.13.0/arch/x86/kernel/fpu/xstate.c:596 
fpu__init_system_xstate+0x437/0x7f0
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.13.0-16-generic 
#19-Ubuntu
[0.00] task: 8ec10480 task.stack: 8ec0
[0.00] RIP: 0010:fpu__init_system_xstate+0x437/0x7f0
[0.00] RSP: :8ec03d88 EFLAGS: 00010082 ORIG_RAX: 

[0.00] RAX: 0029 RBX: 000a RCX: 8ec5fcc8
[0.00] RDX:  RSI: 0096 RDI: 0047
[0.00] RBP: 8ec03de8 R08: 6f63204556415358 R09: 0007
[0.00] R10: 8ee5b7c0 R11:  R12: 0340
[0.00] R13: 0440 R14: 8ec03da8 R15: 0100
[0.00] FS:  () GS:8ee7f000() 
knlGS:
[0.00] CS:  0010 DS:  ES:  CR0: 80050033
[0.00] CR2: 8808a000 CR3: 06113000 CR4: 000406a0
[0.00] Call Trace:
[0.00]  ? get_cpu_cap+0x2a3/0x370
[0.00]  ? msr_clear_bit+0x3a/0xa0
[0.00]  fpu__init_system+0x1fb/0x248
[0.00]  early_cpu_init+0x145/0x14c
[0.00]  ? 0x8de0
[0.00]  setup_arch+0xbf/0xcd4
[0.00]  ? printk+0x52/0x6e
[0.00]  ? early_idt_handler_array+0x120/0x120
[0.00]  start_kernel+0xab/0x4e1
[0.00]  ? early_idt_handler_array+0x120/0x120
[0.00]  x86_64_start_reservations+0x24/0x26
[0.00]  x86_64_start_kernel+0x13e/0x161
[0.00]  secondary_startup_64+0x9f/0x9f
[0.00] Code: 0f 85 42 fd ff ff 44 3b 25 44 e9 22 00 74 2c 80 3d 32 8e 
f6 ff 00 75 15 48 c7 c7 68 f3 a8 8e c6 05 22 8e f6 ff 01 e8 cf 6f 03 ff <0f> ff 
83 3d f5 be d7 ff 00 74 05 e8 eb b4 f8 fe 48 8b 35 47 ed 
[0.00] ---[ end trace 97d576cdb74ee0b3 ]---
[0.00] CPUID[0d, 00]: eax=0007 ebx=0440 ecx=0440 
edx=
...
[   23.952218] ioc0: LSI53C1030 A0: Capabilities={Initiator}
[   24.340974] scsi host2: ioc0: LSI53C1030 A0, FwRev=h, Ports=1, 
MaxQ=256, IRQ=20
[   24.720543] scsi 2:0:0:0: Direct-Access VBOX HARDDISK 1.0  
PQ: 0 ANSI: 5
[   25.360635] scsi target2:0:0: Beginning Domain Validation
[   25.760433] floppy0: no floppy controllers found
[   25.760450] floppy0: floppy_shutdown: timeout handler died.  
[   25.765456] scsi target2:0:0: Domain Validation skipping write tests
[   25.765457] scsi target2:0:0: Ending Domain Validation
[   25.765489] scsi target2:0:0: asynchronous
[   28.065202] scsi 2:0:1:0: Direct-Access VBOX HARDDISK 1.0  
PQ: 0 ANSI: 5
[   28.274132] scsi target2:0:1: Beginning Domain Validation
[   28.380210] scsi target2:0:1: Domain Validation skipping write tests
[   28.860360] scsi target2:0:1: Ending Domain Validation
[   28.905875] scsi target2:0:1: asynchronous
[   28.956489] sd 2:0:0:0: [sda] 20971520 512-byte logical blocks: (10.7 
GB/10.0 GiB)
[   28.964136] sd 2:0:0:0: Attached scsi generic sg0 type 0
[   28.964514] sd 2:0:1:0: Attached scsi generic sg1 type 0
[   29.421363] sd 2:0:0:0: [sda] Write Protect is off
[   29.561592] sd 2:0:0:0: [sda] Mode Sense: 04 00 10 00
[   29.561653] sd 2:0:1:0: [sdb] 20480 512-byte logical blocks: (10.5 MB/10.0 
MiB)
[   29.757147] sd 2:0:0:0: [sda] Incomplete mode parameter data
[   29.757166] sd 2:0:1:0: [sdb] Write Protect is off
[   29.757167] sd 2:0:1:0: [sdb] Mode Sense: 04 00 10 00
[   29.757249] sd 2:0:1:0: [sdb] Incomplete mode parameter data
[   29.757249] sd 2:0:1:0: [sdb] Assuming drive cache: write through
[   29.758166] sd 2:0:1:0: [sdb] Attached SCSI disk
[   31.908285] sd 2:0:0:0: [sda] Assuming drive cache: write through
[   32.441340]  sda: sda1
[   32.597115] sd 2:0:0:0: [sda] Attached SCSI disk
...
[   36.033180] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: 
(null)
...
[   40.452364] EXT4-fs (sda1): re-mounted. Opts: (null)
...
[   60.954983] EXT4-fs (sda1): resizing filesystem from 576000 to 2621179 blocks
[   60.955487] EXT4-fs (sda1): resized filesystem to 2621179
[   61.010337] VFS: brelse: Trying to free free buffer
[   

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

[Paul Menzel]

Dear Christian,


Am 24.10.2017 um 19:14 schrieb Christian Boltz:
>> ... apparmor="DENIED" operation="create" ... family="unix"
> sock_type="stream"
> 
> With the pinned-down feature set, you probably "lost" support for unix
> rules.

Sorry, I have no clue about the internals. I just use what’s shipped in 
Ubuntu 16.04.

> In theory, apparmor_parser will downgrade those rules to "network unix,"
> - but in practise a bug in apparmor_parser prevented it. This bug was
> fixed in the point releases some days ago.

Just a note, that the no regression policy of Linux actually demands 
that the latest Linux kernel also works with buggy user space software.

> Can you please test with the latest apparmor_parser? "Latest" means
> 2.11.1, 2.10.3 or 2.9.5 - or, if you want to test only the bugfix, apply
> the patch from bzr trunk r3700 - http://bazaar.launchpad.net/~apparmor-
> dev/apparmor/master/revision/3700

The system is an up-to-date Ubuntu 16.04 installation. So that should be 
already installed? I can check tomorrow.


Kind regards,

Paul

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

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

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

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

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

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

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

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

[Chad Smith]

Just tested on artful both above and below the prompt choice threshold
of 10 and bug reporting works.  Input of "9" for single digits
choices versus "13" for multi-digit choices both work now for
choice prompts with long lists. Short choice list prompts retain their
single character responses.

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

Title:
  apport question will not accept multi-character responses

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1725980] Re: package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall

[Andreas Hasenack]

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

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

Title:
  package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-
  4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad
  inconsistent state; you should  reinstall it before attempting
  configuration

Status in heimdal package in Ubuntu:
  Incomplete

Bug description:
  not updated

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Sun Oct 22 09:37:53 2017
  DuplicateSignature:
   package:libheimntlm0-heimdal:i386:1.7~git20150920+dfsg-4ubuntu1.16.04.1
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libheimntlm0-heimdal:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-03-06 (229 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: heimdal
  Title: package libheimntlm0-heimdal:i386 
1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[TJ]

** Also affects: laptop-mode-tools
   Importance: Undecided
   Status: New

** No longer affects: laptop-mode-tools

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

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

** Description changed:

  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.
  
  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.
  
  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.
  
  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.
  
  From the start-up logs (with "systemd.log_level=debug") we see the ext4
  driver report a remount operation not once but five times.
  
  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  
  Those last five appear to be carrying options generated by laptop-mode-
  tools.
  
  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.
  
  We see several reports of "read-only file-system":
  
  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system
  
  We also see several problems with systemd's connection to Dbus:
  
  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connected
  
  When the user purged laptop-mode-tools the system starts successfully on
  battery.
  
  The user installed a fresh instance of 17.10 on a 2nd M2 SSD. When
  laptop-mode-tools was added to that instance it 

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

[TJ]

** Attachment added: "Photo of startup console messages"
   
https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+attachment/4991895/+files/IMAG2881.jpg

** Description changed:

  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.
  
  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.
  
  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.
  
  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.
  
  From the start-up logs (with "systemd.log_level=debug") we see the ext4
  driver report a remount operation not once but five times.
  
  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  
  Those last five appear to be carrying options generated by laptop-mode-
  tools.
  
  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.
  
  We see several reports of "read-only file-system":
  
  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system
  
  We also see several problems with systemd's connection to Dbus:
  
  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connected
  
  When the user purged laptop-mode-tools the system starts successfully on
  battery.
  
  The user installed a fresh instance of 17.10 on a 2nd M2 SSD. When
  laptop-mode-tools was added to that instance it also exhibited the
  failure.
+ 
+ # apt-cache rdepends laptop-mode-tools
+ laptop-mode-tools
+ Reverse Depends:
+   systemd
+   tlp
+   powertop-1.13
+   powertop
+ 
+ # apt-cache depends systemd
+ 

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

[TJ]

systemd-resolved.service and systemd.hostnamed.service show up pretty
clearly on the startup console as having problems and their logs show
repeated entries of the form:

-- Logs begin at Mon 2017-10-23 13:01:36 EDT, end at Mon 2017-10-23 13:05:52 
EDT. --
Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
Oct 23 13:01:38 T450s systemd[1]: Failed to start Network Name Resolution.
Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Unit entered failed 
state.
Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Failed with result 
'resources'.
Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Service has no 
hold-off time, scheduling restart.
Oct 23 13:01:38 T450s systemd[1]: Stopped Network Name Resolution.
Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system


-- Logs begin at Mon 2017-10-23 13:01:36 EDT, end at Mon 2017-10-23 13:06:20 
EDT. --
Oct 23 13:01:38 T450s systemd[1]: systemd-hostnamed.service: Failed to run 
'start' task: Read-only file system
Oct 23 13:01:38 T450s systemd[1]: Failed to start Hostname Service.
Oct 23 13:01:38 T450s systemd[1]: systemd-hostnamed.service: Unit entered 
failed state.
Oct 23 13:01:38 T450s systemd[1]: systemd-hostnamed.service: Failed with result 
'resources'.

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

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

Status in laptop-mode-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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

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

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send 

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

[TJ]

The systemd/dbus issues are possibly related to the partial fix detailed
in

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1591411

However, there are 2 upstream DBus bugs/fixes and I believe one of them
isn't in 17.10's DBus at present:

"unix fd in-flight counting broken" 
https://bugs.freedesktop.org/show_bug.cgi?id=95263
" _dbus_timeout_set_enabled doesn't reset timeout ticking" 
https://bugs.freedesktop.org/show_bug.cgi?id=95619#c10

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

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

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

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

Status in laptop-mode-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1726960] Re: Installation of network-manager-config-connectivity-ubuntu fails when installing ubuntu-desktop task from mini.iso

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Installation of network-manager-config-connectivity-ubuntu fails when
  installing ubuntu-desktop task from mini.iso

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Installation of this package as part of the Ubuntu Desktop task fails
  if being executed from the mini.iso after installation.  This is due
  to teh Network Manager service not running when it tries to install
  itself.

  This seems like it might be related to
  https://bugs.launchpad.net/ubuntu/+source/network-manager-
  applet/+bug/1726958 in some way, as they both happened on a 17.10
  installation installed from the mini.iso and the command line (no GUI
  initially).

  This issue does *not* happen with the Ubuntu Desktop ISOs.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:17:34 2017
  IpRoute:
   default via 192.168.226.2 dev ens33 proto dhcp src 192.168.226.131 metric 
100 
   192.168.226.0/24 dev ens33 proto kernel scope link src 192.168.226.131 
   192.168.226.2 dev ens33 proto dhcp scope link src 192.168.226.131 metric 100
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   ens33   ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --   
   ----   
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4disconnected  started  unknown   enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful

[TJ]

May be related to
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1591411

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

Title:
  System unbootable with root fs mounted ro after update to systemd
  234-2ubuntu12 (from 234-2ubuntu10) on artful

Status in systemd package in Ubuntu:
  New

Bug description:
  After not touching my notebook since 30th September (where I did the
  dist-upgrade to artful and installed all available updates), I did all
  available updates today (20th October) and the system didn't boot
  after that.

  The last message I see is "Reached target Bluetooth". Before that,
  there are several failed services. GDM doesn't come up.

  After logging in on tty2, I saw that the root partition was mounted
  read-only. Inspecting the messages of e.g. systemd-resolved shows that
  it didn't start because of the read-only filesystem. After remounting
  it fw, I was able to restart the daemons and could also start GDM and
  login fine.

  My fstab shows:

  UUID=a936dbe9-5ab5-4272-aaae-d22030824373 /   ext4
  errors=remount-ro 0   1

  
  The UUID is correct as "mount / -o remount,rw" works fine. Booting with the 
previous kernel doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 20 21:46:36 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-26 (451 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago)
  dmi.bios.date: 09/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81A1
  dmi.board.vendor: HP
  dmi.board.version: 33.76
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful

[TJ]

Sorry, wrong link! may be related to
https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930

The other link is related to the problems systemd<>dbus encounter where
"Transport endpoint is not connected" messages are reported because
systemd cannot talk to its client services through Dbus.

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

Title:
  System unbootable with root fs mounted ro after update to systemd
  234-2ubuntu12 (from 234-2ubuntu10) on artful

Status in systemd package in Ubuntu:
  New

Bug description:
  After not touching my notebook since 30th September (where I did the
  dist-upgrade to artful and installed all available updates), I did all
  available updates today (20th October) and the system didn't boot
  after that.

  The last message I see is "Reached target Bluetooth". Before that,
  there are several failed services. GDM doesn't come up.

  After logging in on tty2, I saw that the root partition was mounted
  read-only. Inspecting the messages of e.g. systemd-resolved shows that
  it didn't start because of the read-only filesystem. After remounting
  it fw, I was able to restart the daemons and could also start GDM and
  login fine.

  My fstab shows:

  UUID=a936dbe9-5ab5-4272-aaae-d22030824373 /   ext4
  errors=remount-ro 0   1

  
  The UUID is correct as "mount / -o remount,rw" works fine. Booting with the 
previous kernel doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 20 21:46:36 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-26 (451 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago)
  dmi.bios.date: 09/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81A1
  dmi.board.vendor: HP
  dmi.board.version: 33.76
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1726960] [NEW] Installation of network-manager-config-connectivity-ubuntu fails when installing ubuntu-desktop task from mini.iso

[Thomas Ward]

Public bug reported:

Installation of this package as part of the Ubuntu Desktop task fails if
being executed from the mini.iso after installation.  This is due to teh
Network Manager service not running when it tries to install itself.

This seems like it might be related to
https://bugs.launchpad.net/ubuntu/+source/network-manager-
applet/+bug/1726958 in some way, as they both happened on a 17.10
installation installed from the mini.iso and the command line (no GUI
initially).

This issue does *not* happen with the Ubuntu Desktop ISOs.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 24 13:17:34 2017
IpRoute:
 default via 192.168.226.2 dev ens33 proto dhcp src 192.168.226.131 metric 100 
 192.168.226.0/24 dev ens33 proto kernel scope link src 192.168.226.131 
 192.168.226.2 dev ens33 proto dhcp scope link src 192.168.226.131 metric 100
IwConfig:
 ens33 no wireless extensions.
 
 lono wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
 ens33   ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
 running  1.8.4disconnected  started  unknown   enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: Confirmed


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

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

Title:
  Installation of network-manager-config-connectivity-ubuntu fails when
  installing ubuntu-desktop task from mini.iso

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Installation of this package as part of the Ubuntu Desktop task fails
  if being executed from the mini.iso after installation.  This is due
  to teh Network Manager service not running when it tries to install
  itself.

  This seems like it might be related to
  https://bugs.launchpad.net/ubuntu/+source/network-manager-
  applet/+bug/1726958 in some way, as they both happened on a 17.10
  installation installed from the mini.iso and the command line (no GUI
  initially).

  This issue does *not* happen with the Ubuntu Desktop ISOs.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:17:34 2017
  IpRoute:
   default via 192.168.226.2 dev ens33 proto dhcp src 192.168.226.131 metric 
100 
   192.168.226.0/24 dev ens33 proto kernel scope link src 192.168.226.131 
   192.168.226.2 dev ens33 proto dhcp scope link src 192.168.226.131 metric 100
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   ens33   ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --   
   ----   
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4disconnected  started  unknown