date:20171009

This bug was fixed in the package xkeyboard-config - 2.19-1.1ubuntu1

---
xkeyboard-config (2.19-1.1ubuntu1) artful; urgency=medium

  * Merge with Debian (LP: #1707929), remaining changes:
- control, rules, xkb-data-i18n.install, xkb-data.install: Split out
  xkb-data-i18n to be used by console-setup.
- xkb-data.postinst: Remove the xkb cache to make sure it gets
  regenerated.
- debian/patches/elfdalian-kb-layout.diff

xkeyboard-config (2.19-1.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Revert blacklisting of Indic layouts (Closes: #865316)

 -- Gunnar Hjalmarsson   Mon, 02 Oct 2017 21:46:00
+0200

** Changed in: xkeyboard-config (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [FFe] Revert blacklisting of Indic layouts

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

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

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

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

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

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

[Touch-packages] [Bug 1722151] Re: Incorrect syntax when writing to ~/.pam_environment

2017-10-09 Thread Gunnar Hjalmarsson

Thanks for clarifying, Olivier. Fix uploaded to the artful queue.

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

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

Status in accountsservice package in Ubuntu:
  Fix Committed

Bug description:
  While investigating bug #1662031, I found out that /usr/share
  /language-tools/save-to-pam-env writes to ~/.pam_environment using an
  incorrect syntax: "VARIABLE=value" on each line. The expected syntax
  is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: accountsservice 0.6.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 06:57:17 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (463 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago)

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

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

Re: [Touch-packages] [Bug 1722300] Re: Boot times since artful upgrade have increased 4 fold

2017-10-09 Thread Chris Gregan

Fixed by multiple apt-get update calls. Seems the networking bug in systemd
was preventing me from getting the updated version that fixed the
networking issue.

On Mon, Oct 9, 2017 at 2:31 PM, Dimitri John Ledkov 
wrote:

> Please reboot?
>
> /me goes to fix all ubuntu mirrors in the world
>
> does it work now? cool.
>
> http://www.commitstrip.com/en/2015/02/17/have-you-tried-turning-it-off-
> and-on-again/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1722300
>
> Title:
>   Boot times since artful upgrade have increased 4 fold
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/
> 1722300/+subscriptions
>

-- 
Chris Gregan
Quality Assurance Manager
Field Engineering/CPE
cgre...@irc.canonical.com

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

Title:
  Boot times since artful upgrade have increased 4 fold

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  systemd:
Installed: 234-2ubuntu10

  I'm seeing a much longer bot time in Artful than I did in Zesty. 
Systemd-analyze blame indicates that systemd is at the root of this issue.

  hris@Thermia:~$ sudo systemd-analyze blame
2min 541ms lxd-containers.service
2min 213ms systemd-networkd-wait-online.service
6.260s NetworkManager-wait-online.service
4.342s plymouth-quit-wait.service
1.108s fwupd.service
 838ms lxd.service
 690ms snapd.service
 567ms dev-mapper-ubuntu\x2d\x2dvg\x2droot.device
 374ms dev-loop8.device
 353ms dev-loop9.device
 340ms dev-loop10.device
 312ms dev-loop4.device

  Syslog shows:
  chris@Thermia:~$ cat /var/log/syslog | grep 
systemd-networkd-wait-online.service
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  chris@Thermia:~$ ubuntu-bug

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

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

[Touch-packages] [Bug 1722397] [NEW] idle doesn't run in 17.10

2017-10-09 Thread Serhiy Storchaka

Public bug reported:

In 17.10 the idle package (v. 3.6.3-0ubuntu1) depends on Python 3.6. But
the /usr/bin/idle script contains the code that doesn't work in Python
3.6.

$ idle
Traceback (most recent call last):
  File "/usr/bin/idle", line 3, in 
from idlelib.PyShell import main
ModuleNotFoundError: No module named 'idlelib.PyShell'

In Python 3.6 the PyShell module was renamed to pyshell (see
https://bugs.python.org/issue24225).

/usr/bin/idle-python3.6 from the idle-python3.6 package works correctly.

Maybe make /usr/bin/idle just a link to /usr/bin/idle-python3.6?

If you want /usr/bin/idle always run the default python3 and don't
depent of future changes in the idlelib Python package, you can make it
a shell script:

#! /bin/sh
exec /usr/bin/python3 -m idlelib

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  idle doesn't run in 17.10

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  In 17.10 the idle package (v. 3.6.3-0ubuntu1) depends on Python 3.6.
  But the /usr/bin/idle script contains the code that doesn't work in
  Python 3.6.

  $ idle
  Traceback (most recent call last):
File "/usr/bin/idle", line 3, in 
  from idlelib.PyShell import main
  ModuleNotFoundError: No module named 'idlelib.PyShell'

  In Python 3.6 the PyShell module was renamed to pyshell (see
  https://bugs.python.org/issue24225).

  /usr/bin/idle-python3.6 from the idle-python3.6 package works
  correctly.

  Maybe make /usr/bin/idle just a link to /usr/bin/idle-python3.6?

  If you want /usr/bin/idle always run the default python3 and don't
  depent of future changes in the idlelib Python package, you can make
  it a shell script:

  #! /bin/sh
  exec /usr/bin/python3 -m idlelib

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

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

[Touch-packages] [Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

2017-10-09 Thread uklas

** Changed in: unity-settings-daemon (Ubuntu)
 Assignee: (unassigned) => uklas (uklasius)

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

Status in Upower:
  Unknown
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  SRU TEST CASE (upower)
  --
  On affected machines, unity-settings-daemon crashes immediately on login, as 
due to a kernel bug upowerd takes a very long time to start. With the fixed 
package the crash is fixed. Power status information will still be wrong, but 
at least theme, hotkeys, and all other unity-settings-daemon functionality will 
work.

  This can be synthetically tested with:

     DBUS_SYSTEM_BUS_ADDRESS=foo upower --dump

  With the current xenial version this causes a segfault, while with the
  fix you get a proper error message.

  Fix: https://cgit.freedesktop.org/upower/commit/?id=932a6a39e3
 https://cgit.freedesktop.org/upower/commit/?id=4e83fabac
  (The second one is not crucial, but provides a much better failure mode for 
the "upower" CLI tool).

  Regression potential: This changes the core behaviour of libupower.
  The patch is carefully written to be backwards compatible to the
  extent possible, but changing the behaviour is necessary to fix this
  bug (see commit log for details). Thus clients such as unity-control-
  center, unity-settings-daemon, or mate-power-manager should be tested
  as part of the verification.

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1721821] Re: sddm freezes 50 seconds before KDE Plasma starts

2017-10-09 Thread vmagnin

The problem seem to be a "timed out" problem with NetworkManager
1.8.4-1ubuntu1, not sddm.

** Package changed: sddm (Ubuntu) => network-manager (Ubuntu)

** Summary changed:

- sddm freezes 50 seconds before KDE Plasma starts
+ Kubuntu 17.10 freezes 50 seconds before KDE Plasma starts

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

Title:
  Kubuntu 17.10 freezes 50 seconds before KDE Plasma starts

Status in network-manager package in Ubuntu:
  New

Bug description:
  I upgraded my Kubuntu 17.04 to 17.10 four days ago.

  My PC is booting fast: ~10 seconds to see the greeter. But when I
  connect to my Plasma session, the greeter is staying ~50 seconds at
  screen, before Plasma is starting (in ~10 more seconds). There was no
  problem before upgrading to Kubuntu 17.10.

  I connected to a terminal session just after having entered my
  password in the greeter, and I launched the htop command: all I can
  say is that there is no cpu eating process. The cpu is nearly idle
  during these 50 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: sddm 0.14.0-4ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Fri Oct  6 18:13:42 2017
  InstallationDate: Installed on 2012-07-31 (1893 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  SourcePackage: sddm 0.14.0-4ubuntu1
  UpgradeStatus: Upgraded to artful on 2017-10-02 (3 days ago)

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

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

[Touch-packages] [Bug 1721821] [NEW] sddm freezes 50 seconds before KDE Plasma starts

You have been subscribed to a public bug:

I upgraded my Kubuntu 17.04 to 17.10 four days ago.

My PC is booting fast: ~10 seconds to see the greeter. But when I
connect to my Plasma session, the greeter is staying ~50 seconds at
screen, before Plasma is starting (in ~10 more seconds). There was no
problem before upgrading to Kubuntu 17.10.

I connected to a terminal session just after having entered my password
in the greeter, and I launched the htop command: all I can say is that
there is no cpu eating process. The cpu is nearly idle during these 50
seconds.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: sddm 0.14.0-4ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic i686
ApportVersion: 2.20.7-0ubuntu2
Architecture: i386
CurrentDesktop: KDE
Date: Fri Oct  6 18:13:42 2017
InstallationDate: Installed on 2012-07-31 (1893 days ago)
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
SourcePackage: sddm 0.14.0-4ubuntu1
UpgradeStatus: Upgraded to artful on 2017-10-02 (3 days ago)

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug artful i386
-- 
sddm freezes 50 seconds before KDE Plasma starts
https://bugs.launchpad.net/bugs/1721821
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager 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 1302546] Re: gtk drawing area - missing or incorrect expose or draw event

2017-10-09 Thread Bug Watch Updater

** Changed in: gtk
   Status: New => Fix Released

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

Title:
  gtk drawing area - missing or incorrect expose or draw event

Status in GTK+:
  Fix Released
Status in LiVES:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Application is Fotoxx 14.04. A GTK notebook is used with tabs
  containing drawing areas inside scrolled windows. The program works on
  Ubuntu 13.10 and earlier (GTK 3.8) and fails on Ubuntu 14.04 beta (as
  of April 4) (GTK 3.10).

  When the notebook tab is changed the new tab's drawing area is not
  updated (Fotoxx gallery page). Some prior data is present and the rest
  is background color only. Clicking elsewhere and then clicking the
  window title bar (unfocus and refocus the app) causes the tab to
  update correctly. Removing the default "double buffered" attribute
  from the drawing area widget after it is created makes everything work
  correctly on Ubuntu 14.04. However on earlier Ubuntu releases the
  background is not updated and is filled with data from the previous
  tab.

  This seems to be a problem with missing "draw" events or events with
  incorrect update regions. I have verified that draw events are not
  sent when the tab is switched but are sent when the window acquires
  focus.

  The GTK bug tracking system seems to have related bugs but I cannot be
  sure (too much technical jargon for my knowledge of GTK internals). I
  did not file a report there because the expected knowledge of
  internals is missing. The bug may be fixed in GTK 3.12.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgtk-3-0 3.10.7-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 13:28:59 2014
  InstallationDate: Installed on 2014-03-28 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1722300] Re: Boot times since artful upgrade have increased 4 fold

Please reboot?

/me goes to fix all ubuntu mirrors in the world

does it work now? cool.

http://www.commitstrip.com/en/2015/02/17/have-you-tried-turning-it-off-
and-on-again/

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

Title:
  Boot times since artful upgrade have increased 4 fold

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  systemd:
Installed: 234-2ubuntu10

  
  I'm seeing a much longer bot time in Artful than I did in Zesty. 
Systemd-analyze blame indicates that systemd is at the root of this issue.

  hris@Thermia:~$ sudo systemd-analyze blame
2min 541ms lxd-containers.service
2min 213ms systemd-networkd-wait-online.service
6.260s NetworkManager-wait-online.service
4.342s plymouth-quit-wait.service
1.108s fwupd.service
 838ms lxd.service
 690ms snapd.service
 567ms dev-mapper-ubuntu\x2d\x2dvg\x2droot.device
 374ms dev-loop8.device
 353ms dev-loop9.device
 340ms dev-loop10.device
 312ms dev-loop4.device

  Syslog shows:
  chris@Thermia:~$ cat /var/log/syslog | grep 
systemd-networkd-wait-online.service
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  chris@Thermia:~$ ubuntu-bug

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

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

[Touch-packages] [Bug 1714803] Re: Search list in resolv.conf breaks resolving for that domain

Hm.

So my local WiFi router is setup to send 'surgut.co.uk' domain. And I
can resolve 'blog.surgut.co.uk' and 'surgut.co.uk' via both `systemd-
resolve [blog.]surgut.so.uk` and `getent ahosts [blog.]surgut.co.uk`.

I think i really need to see all of the settings for systemd can you
attach a tarball of:

/run/systemd/*
/etc/systemd/resolved.conf*

?

/me really should extend the apport hooks to include those things.

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

Title:
  Search list in resolv.conf breaks resolving for that domain

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.04
  systemd 232-21ubuntu5

  Adding a domain to the search list in /etc/resolv.conf breaks
  resolving for that domain. Not only does the search list not get used
  as expected, but host names in the domain cannot be resolved by
  systemd-resolved at all.

  I just ran into this after upgrading from ubuntu 16.04 to 17.04 which
  enabled systemd-resolved. I have for a long time used resolveconf to
  add a 'search my-domain'-line to my /etc/resolv.conf.

  
  Example of expected behaviour. With Googles DNS server (8.8.8.8) and 
ubuntu.com in the search list in /etc/resolv.conf. Both dig and systemd-resolve 
can resolve www.ubuntu.com and www:

  $ cat /etc/resolv.conf 
  nameserver 8.8.8.8
  search ubuntu.com
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55037
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   501 IN  A   91.189.89.115
  
  $ dig +search +nostat +nocmd www
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25772
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   382 IN  A   91.189.89.103
  
  $ systemd-resolve www.ubuntu.com
  www.ubuntu.com: 91.189.89.115
  
  -- Information acquired via protocol DNS in 2.7ms.
  -- Data is authenticated: no
  $ systemd-resolve www
  www: 91.189.90.59
   (www.ubuntu.com)
  
  -- Information acquired via protocol DNS in 3.8ms.
  -- Data is authenticated: no

  Ubuntu 17.04 default config, with the systemd-resolved name server in
  /etc/resolv.conf and no search list. www.ubuntu.com can still be
  resolved correctly:

  $ cat /etc/resolv.conf
  nameserver 127.0.0.53
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64646
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   482 IN  A   91.189.89.110
  $ systemd-resolve www.ubuntu.com
  www.ubuntu.com: 91.189.90.58
  
  -- Information acquired via protocol DNS in 18.2ms.
  -- Data is authenticated: no

  Broken behaviour, using the systemd-resolved name server and specify
  ubuntu.com in search list. Resolving fails for www.ubuntu.com and www,
  both using dig (DNS) and using sytemd-resolve:

  $ cat /etc/resolv.conf
  nameserver 127.0.0.53
  search ubuntu.com
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 4
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  $ dig +search +nostat +nocmd www
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 50588
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  $ systemd-resolve www.ubuntu.com
  www.ubuntu.com: resolve call failed: No appropriate name servers or 
networks for name found
  $ systemd-resolve www
  www: resolve call failed: All attempts to contact name servers or 
networks failed

To manage notifications about this bug go to:

[Touch-packages] [Bug 1721839] Re: Services asked for by UDEV do not get triggered

** Tags added: rls-aa-incoming

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

Title:
  Services asked for by UDEV do not get triggered

Status in systemd package in Ubuntu:
  New

Bug description:
  The packages system-config-printer-udev and ippusbxd are installed,
  having the following UDEV rule files:

  /lib/udev/rules.d/70-printers.rules

  --
  # Low-level USB device add trigger
  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="udev-configure-printer", 
TAG+="systemd", PROGRAM="/bin/systemd-escape 
--template=udev-configure-printer@.service %p", ENV{SYSTEMD_WANTS}+="%c"
  # Low-level USB device remove trigger
  ACTION=="remove", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p"
  --

  /lib/udev/rules.d/55-ippusbxd.rules

  --
  # ippusbxd udev rules file

  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device" 
ENV{ID_USB_INTERFACES}=="*:070104:*", OWNER="root", GROUP="lp", MODE="0664", 
PROGRAM="/bin/systemd-escape --template=ippusbxd@.service 
$env{BUSNUM}:$env{DEVNUM}", ENV{SYSTEMD_WANTS}+="%c"
  --

  If I turn on an appropriate printer (USB, supporting IPP-over-USB,
  here the HP DeskJet 2540) I get in the output of "udevadm monitor
  --environment"

  --
  UDEV  [17527.514150] add  /devices/pci:00/:00:14.0/usb2/2-2 (usb)
  ACTION=add
  BUSNUM=002
  DEVNAME=/dev/bus/usb/002/033
  DEVNUM=033
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2
  DEVTYPE=usb_device
  DRIVER=usb
  ID_BUS=usb
  ID_MODEL=Deskjet_2540_series
  ID_MODEL_ENC=Deskjet\x202540\x20series
  ID_MODEL_ID=c211
  ID_REVISION=0100
  ID_SERIAL=HP_Deskjet_2540_series_BR54BFB02C05XK
  ID_SERIAL_SHORT=BR54BFB02C05XK
  ID_USB_INTERFACES=:ffcc00:070104:070102:ff0401:
  ID_VENDOR=HP
  ID_VENDOR_ENC=HP
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  ID_VENDOR_ID=03f0
  MAJOR=189
  MINOR=160
  PRODUCT=3f0/c211/100
  SEQNUM=9891
  SUBSYSTEM=usb
  SYSTEMD_WANTS=ippusbxd@002:033.service 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service 
printer.target
  TAGS=:udev-configure-printer:systemd:
  TYPE=0/0/0
  USEC_INITIALIZED=17527513940

  UDEV  [17527.517724] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
  .MM_USBIFNUM=00
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0
  DEVTYPE=usb_interface
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=255/204/0
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFiscCCip00in00
  PRODUCT=3f0/c211/100
  SEQNUM=9892
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527517478

  UDEV  [17527.522565] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2 (usb)
  .MM_USBIFNUM=02
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2
  DEVTYPE=usb_interface
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=255/4/1
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFisc04ip01in02
  PRODUCT=3f0/c211/100
  SEQNUM=9895
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527522332

  UDEV  [17527.523761] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1 (usb)
  .MM_USBIFNUM=01
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1
  DEVTYPE=usb_interface
  DRIVER=usblp
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=7/1/2
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00ic07isc01ip02in01
  PRODUCT=3f0/c211/100
  SEQNUM=9893
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527523500

  UDEV  [17527.527275] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1 (usbmisc)
  .MM_USBIFNUM=01
  ACTION=add
  DEVNAME=/dev/usb/lp1
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1
  MAJOR=180
  MINOR=1
  SEQNUM=9894
  SUBSYSTEM=usbmisc
  USEC_INITIALIZED=17527527175
  --

  Here one can see that the UDEV rules files are correct, leading to the
  correct systemd services being requested

  SYSTEMD_WANTS=ippusbxd@002:033.service udev-configure-printer
  @-devices-pci:00-:00:14.0-usb2-2\x2d2.service printer.target

  but neither the service ippusbxd@002:033.service nor the service udev-
  configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service
  get started (note that I have put the .service file for ippusbxd in
  place by "sudo cp /usr/share/doc/ippusbxd/examples/ippusbxd@.service
  /lib/systemd/system/").

  I can start each of these services manually though:

  sudo systemctl start 'udev-configure-printer@-devices-
  pci:00-:00:14.0-usb2-2\x2d2.service'

  sudo systemctl start ippusbxd@002:033.service

  In each case ippusbxd gets started for this printer and a print queue
  auto-created.

  What I expect is that the services get automatically started (and that
  worked in 17.04) so that after plugging in an USB

[Touch-packages] [Bug 1722319] Re: Totem Player not working correctly on 17.10 Beta 2

2017-10-09 Thread corrado venturini

I have the same problem on MOST video, but sometime totem works, apparently 
random: the same video sometimes is displayed, but a minute later i have a 
black screen. Sometimes i have also another problem, totem is unable to create 
a screenshot: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248 both 
problems with x11 and wayland.
corrado@corrado-beta-4ott:~$ inxi -GxxIS
System:Host: corrado-beta-4ott Kernel: 4.13.0-12-generic x86_64
   bits: 64 gcc: 7.2.0
   Desktop: Gnome 3.26.1 (Gtk 3.22.21-0ubuntu1) dm: gdm3
   Distro: Ubuntu Artful Aardvark (development branch)
Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0 chip-ID: 8086:5912
   Display Server: x11 (X.Org 1.19.3 ) driver: i915
   Resolution: 1920x1080@60.00hz
   OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
   version: 4.5 Mesa 17.2.2 (compat-v: 3.0) Direct Render: Yes
Info:  Processes: 236 Uptime: 35 min Memory: 1225.7/7684.1MB
   Init: systemd v: 234 runlevel: 5 Gcc sys: N/A
   Client: Shell (bash 4.4.121 running in gnome-terminal-) inxi: 2.3.37 
corrado@corrado-beta-4ott:~$

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

Title:
  Totem Player not working correctly on 17.10 Beta 2

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 17.10 Beta 2 on my laptop - Dell
  Inspiron N4110, Intel Sandybridge Mobile Graphics, Intel® Core™
  i3-2350M CPU @ 2.30GHz × 4, 6GB of RAM.  If I try to play ANY video on
  the Totem movie player (the default GNOME player), I get sound and
  subtitles but no picture. VLC works just fine. This did not happen on
  my previous 14.04 install on the same laptop. Is this a beta OS bug or
  just a bad media player?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.3-1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 08:31:37 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-10-06 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  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.
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1722319/+subscriptions

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

[Touch-packages] [Bug 1722319] Re: Totem Player not working correctly on 17.10 Beta 2

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

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Totem Player not working correctly on 17.10 Beta 2

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 17.10 Beta 2 on my laptop - Dell
  Inspiron N4110, Intel Sandybridge Mobile Graphics, Intel® Core™
  i3-2350M CPU @ 2.30GHz × 4, 6GB of RAM.  If I try to play ANY video on
  the Totem movie player (the default GNOME player), I get sound and
  subtitles but no picture. VLC works just fine. This did not happen on
  my previous 14.04 install on the same laptop. Is this a beta OS bug or
  just a bad media player?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.3-1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 08:31:37 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-10-06 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  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.
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1722319/+subscriptions

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

[Touch-packages] [Bug 1722300] Re: Boot times since artful upgrade have increased 4 fold

2017-10-09 Thread Chris Gregan

@Dimitri
234-2ubunbtu10 us the only one available in the current artful archive.

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

Title:
  Boot times since artful upgrade have increased 4 fold

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  systemd:
Installed: 234-2ubuntu10

  
  I'm seeing a much longer bot time in Artful than I did in Zesty. 
Systemd-analyze blame indicates that systemd is at the root of this issue.

  hris@Thermia:~$ sudo systemd-analyze blame
2min 541ms lxd-containers.service
2min 213ms systemd-networkd-wait-online.service
6.260s NetworkManager-wait-online.service
4.342s plymouth-quit-wait.service
1.108s fwupd.service
 838ms lxd.service
 690ms snapd.service
 567ms dev-mapper-ubuntu\x2d\x2dvg\x2droot.device
 374ms dev-loop8.device
 353ms dev-loop9.device
 340ms dev-loop10.device
 312ms dev-loop4.device

  Syslog shows:
  chris@Thermia:~$ cat /var/log/syslog | grep 
systemd-networkd-wait-online.service
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  chris@Thermia:~$ ubuntu-bug

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

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

[Touch-packages] [Bug 1722355] [NEW] Despite power/display settings on never, screen turns off

2017-10-09 Thread Steve

Public bug reported:

Running 17.10 64bit on Syx/MSI 16Gb desktop with Geforce GTX950 on
Samsung monitor.  When left unattended, screen blanks after a few
minutes, as if it was set to.  Wakes with no issues, but sometimes i
find that it has logged me out.  I have triple-checked all settings and
see no problem there.  Problem began a few days ago after a recent
update.  Thanks

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-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  384.90  Tue Sep 19 19:17:35 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu2)
.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.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  9 12:57:46 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2957]
InstallationDate: Installed on 2017-04-07 (184 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
MachineType: MSI MS-7673
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-12-generic 
root=UUID=7aaf85cc-4052-49d5-ba13-4e3a8c8ff17d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.28B6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P67A-C43 (MS-7673)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.28B6:bd08/31/2011:svnMSI:pnMS-7673:pvr1.0:rvnMSI:rnP67A-C43(MS-7673):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7673
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
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
xserver.bootTime: Mon Oct  9 12:44:58 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech Unifying Device. Wireless PID:4016 MOUSE, id 8
 inputLogitech M215 2nd Gen MOUSE, id 9
 inputLogitech Unifying Device. Wireless PID:4016 KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu7

** 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/1722355

Title:
  Despite power/display settings on never, screen turns off

Status in xorg package in Ubuntu:
  New

Bug description:
  Running 17.10 64bit on Syx/MSI 16Gb desktop with Geforce GTX950 on
  Samsung monitor.  When left unattended, screen blanks after a few
  minutes, as if it was set to.  Wakes with no issues, but sometimes i
  find that it has logged me out.  I have triple-checked all settings
  and see no problem there.  Problem began a few days ago after a recent
  update.  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic

[Touch-packages] [Bug 1722353] Re: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta

2017-10-09 Thread DJ Dallas

Filed against Xorg due to selection limitations of apport. Mutter is the
best guess of responsible application/package.

** Package changed: xorg (Ubuntu) => mutter (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/1722353

Title:
Screen blanking and/or screen lock crashes gnome-shell user session on
wayland - Ubuntu 17.10 beta

Status in mutter package in Ubuntu:
New

Bug description:
Filed against Xorg due to selection limitations of apport. Mutter is
the best guess of responsible application/package.

Automatic (timed) screen blanking (or manually locking the desktop)
causes the wayland gnome-shell session to crash and drop to user login
prompt. The monitor fades the background to black (but oddly the mouse
cursor does not fade). The monitor blanks and goes into signal search
and then power saving mode. Almost immediately the monitor switches
back on, displaying the login prompt (note login and not unlock as
would be expected). Thereafter the screen stays on indefinitely
without further attempts to blank or power-save.

Ubuntu artful 17.10 beta. Dell monitor at 1920x1080x60hz using hdmi
connected to nvidia card with nouveau drivers on wayland session. Xorg
session seems to work as expected.

/var/crash is empty and manually running Apport and reproducing crash
does not produce a crash report, as Apport crashes with the user
session. Have included Apport output, though I had to select xorg from
limited options in app and this is clearly technically incorrect (xorg
session works fine).

Have attached an exported log file of screen blanking causing the
crash. Blanking probably starts at about the 16:04:22 entry, and the
actual crash seems to happen at 16:04:35.

...
16:04:35 gnome-session-b: WARNING: Application 'org.gnome.Shell.desktop'
killed by signal 6
16:04:35 gnome-shell: Fatal server error:
16:04:35 update-notifier: Error reading events from display: Broken pipe
16:04:35 gnome-shell:
mutter:ERROR:backends/meta-monitor-manager.c:2267:meta_monitor_manager_get_logical_monitor_from_number:
assertion failed: ((unsigned int) number < g_list_length
(manager->logical_monitors))
16:04:28 gnome-software: no app for changed ubuntu-appindicat...@ubuntu.com
16:04:22 gnome-shell: Some code accessed the property 'Client' on the module
'dbusMenu'. That property was defined with 'let' or 'const' inside the module.
This was previously supported, but is not correct according to the ES6
standard. Any symbols to be exported from a module must be defined with 'var'.
The property access will work as previously for the time being, but please fix
your code anyway.
...

Crash of gnome-shell can be avoided by changing "Settings - Power -
Power Savings - Blank screen" to "never", and never attempting to lock
the desktop. Alternatively logging in to a Xorg session seems to avoid
crashes.

Bug may be related to
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721577 but
circumstances leading to crash are completely different.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
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
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 9 17:47:51 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00
[VGA controller])
Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 730] [1043:84f5]
InstallationDate: Installed on 2017-10-08 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: PINNACLE MICRO PROLINE DQ57TM
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed
root=UUID=805df197-93bb-4468-8ac9-c1611d91bbbf ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: TMIBX10H.86A.0050.2011.1207.1134
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DQ57TM
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE70931-402
dmi.chassis.type: 3
dmi.chassis.version: UATX
dmi.modalias:
dmi:bvnIntelCorp.:bvrTMIBX10H.86A.0050.2011.1207.1134:bd12/07/2011:svnPINNACLEMICRO:pnPROLINEDQ57TM:pvr:rvnIntelCorporation:rnDQ57TM:rvrAAE70931-402:cvn:ct3:cvrUATX:
dmi.product.name: PROLINE DQ57TM
dmi.sys.vendor: PINNACLE MICRO
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:

[Touch-packages] [Bug 1722353] [NEW] Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta

2017-10-09 Thread DJ Dallas

Public bug reported:

Filed against Xorg due to selection limitations of apport. Mutter is the
best guess of responsible application/package.

Automatic (timed) screen blanking (or manually locking the desktop)
causes the wayland gnome-shell session to crash and drop to user login
prompt. The monitor fades the background to black (but oddly the mouse
cursor does not fade). The monitor blanks and goes into signal search
and then power saving mode. Almost immediately the monitor switches back
on, displaying the login prompt (note login and not unlock as would be
expected). Thereafter the screen stays on indefinitely without further
attempts to blank or power-save.

Ubuntu artful 17.10 beta. Dell monitor at 1920x1080x60hz using hdmi
connected to nvidia card with nouveau drivers on wayland session. Xorg
session seems to work as expected.

/var/crash is empty and manually running Apport and reproducing crash
does not produce a crash report, as Apport crashes with the user
session. Have included Apport output, though I had to select xorg from
limited options in app and this is clearly technically incorrect (xorg
session works fine).

Have attached an exported log file of screen blanking causing the crash.
Blanking probably starts at about the 16:04:22 entry, and the actual
crash seems to happen at 16:04:35.

...
16:04:35 gnome-session-b: WARNING: Application 'org.gnome.Shell.desktop' killed 
by signal 6
16:04:35 gnome-shell: Fatal server error:
16:04:35 update-notifier: Error reading events from display: Broken pipe
16:04:35 gnome-shell: 
mutter:ERROR:backends/meta-monitor-manager.c:2267:meta_monitor_manager_get_logical_monitor_from_number:
 assertion failed: ((unsigned int) number < g_list_length 
(manager->logical_monitors))
16:04:28 gnome-software: no app for changed ubuntu-appindicat...@ubuntu.com
16:04:22 gnome-shell: Some code accessed the property 'Client' on the module 
'dbusMenu'. That property was defined with 'let' or 'const' inside the module. 
This was previously supported, but is not correct according to the ES6 
standard. Any symbols to be exported from a module must be defined with 'var'. 
The property access will work as previously for the time being, but please fix 
your code anyway.
...

Crash of gnome-shell can be avoided by changing "Settings - Power -
Power Savings - Blank screen" to "never", and never attempting to lock
the desktop. Alternatively logging in to a Xorg session seems to avoid
crashes.

Bug may be related to
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721577 but
circumstances leading to crash are completely different.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
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
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  9 17:47:51 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 730] [1043:84f5]
InstallationDate: Installed on 2017-10-08 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: PINNACLE MICRO PROLINE DQ57TM
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=805df197-93bb-4468-8ac9-c1611d91bbbf ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: TMIBX10H.86A.0050.2011.1207.1134
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DQ57TM
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE70931-402
dmi.chassis.type: 3
dmi.chassis.version: UATX
dmi.modalias: 
dmi:bvnIntelCorp.:bvrTMIBX10H.86A.0050.2011.1207.1134:bd12/07/2011:svnPINNACLEMICRO:pnPROLINEDQ57TM:pvr:rvnIntelCorporation:rnDQ57TM:rvrAAE70931-402:cvn:ct3:cvrUATX:
dmi.product.name: PROLINE DQ57TM
dmi.sys.vendor: PINNACLE MICRO
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.3-1ubuntu7
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: mutter (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "log of gnome-shell crash at approx 16:04:35"

[Touch-packages] [Bug 1712433] Re: man page typo

2017-10-09 Thread Liam Ryan

Pull request created upstream - https://github.com/karelzak/util-
linux/pull/519

** Changed in: util-linux (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  man page typo

Status in util-linux package in Ubuntu:
  In Progress

Bug description:
  man mount contains the following section:

  Note  that mount is very strict about non-root users and all paths specified 
on command line are verified before fstab is
     parsed or a helper program is executed. It's strogly recommended to 
use a valid mountpoint to specify filesystem,  other‐
     wise mount may fail. For example it's bad idea to use NFS or CIFS 
source on command line.

  The word 'strogly' should be 'strongly'

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: mount 2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Aug 23 07:48:32 2017
  InstallationDate: Installed on 2017-03-23 (152 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-08-13 (9 days ago)

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

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

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

Hello Robin, or anyone else affected,

Accepted dkms into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu11.5 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

Status in dkms package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

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

  Note:  Filling up the /boot partition causes updates to fail.

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

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

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

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

Hello Robin, or anyone else affected,

Accepted dkms into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.3-3ubuntu1.2 in
a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. 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!

** Tags removed: verification-failed-zesty
** Tags added: verification-needed-zesty

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

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

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

Status in dkms package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

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

  Note:  Filling up the /boot partition causes updates to fail.

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

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

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

[Touch-packages] [Bug 1714803] Re: Search list in resolv.conf breaks resolving for that domain

2017-10-09 Thread Matthias Fratz

I can confirm that the underlying bug still exists in today's artful
nightly CD.

I wasn't able to get a search path to stick in /etc/resolv.conf, but
setting Domains=ubuntu.com in /etc/systemd/resolved.conf triggers the
same bug: It breaks resolution for ubuntu.com and www.ubuntu.com (and
probably all other subdomains as well), and www doesn't resolve either.
nslookup reports SERVFAIL; systemd-resolve reports "No appropriate name
servers or networks for name found".

Testing this on my 17.04, I enabled systemd-resolved logging. The output
for "affected" domains (ie. ones named in the search path) listed
"LLMNR"; for other domains it listed "LLMNR" and "DNS" strategies. I
will try to reproduce this in the artful VM and will hopefully be able
to post the debugging output tomorrow.

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

Title:
  Search list in resolv.conf breaks resolving for that domain

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.04
  systemd 232-21ubuntu5

  Adding a domain to the search list in /etc/resolv.conf breaks
  resolving for that domain. Not only does the search list not get used
  as expected, but host names in the domain cannot be resolved by
  systemd-resolved at all.

  I just ran into this after upgrading from ubuntu 16.04 to 17.04 which
  enabled systemd-resolved. I have for a long time used resolveconf to
  add a 'search my-domain'-line to my /etc/resolv.conf.

  
  Example of expected behaviour. With Googles DNS server (8.8.8.8) and 
ubuntu.com in the search list in /etc/resolv.conf. Both dig and systemd-resolve 
can resolve www.ubuntu.com and www:

  $ cat /etc/resolv.conf 
  nameserver 8.8.8.8
  search ubuntu.com
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55037
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   501 IN  A   91.189.89.115
  
  $ dig +search +nostat +nocmd www
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25772
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   382 IN  A   91.189.89.103
  
  $ systemd-resolve www.ubuntu.com
  www.ubuntu.com: 91.189.89.115
  
  -- Information acquired via protocol DNS in 2.7ms.
  -- Data is authenticated: no
  $ systemd-resolve www
  www: 91.189.90.59
   (www.ubuntu.com)
  
  -- Information acquired via protocol DNS in 3.8ms.
  -- Data is authenticated: no

  Ubuntu 17.04 default config, with the systemd-resolved name server in
  /etc/resolv.conf and no search list. www.ubuntu.com can still be
  resolved correctly:

  $ cat /etc/resolv.conf
  nameserver 127.0.0.53
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64646
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   482 IN  A   91.189.89.110
  $ systemd-resolve www.ubuntu.com
  www.ubuntu.com: 91.189.90.58
  
  -- Information acquired via protocol DNS in 18.2ms.
  -- Data is authenticated: no

  Broken behaviour, using the systemd-resolved name server and specify
  ubuntu.com in search list. Resolving fails for www.ubuntu.com and www,
  both using dig (DNS) and using sytemd-resolve:

  $ cat /etc/resolv.conf
  nameserver 127.0.0.53
  search ubuntu.com
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 4
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  $ dig +search +nostat +nocmd www
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 50588
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A

[Touch-packages] [Bug 1721839] Re: Services asked for by UDEV do not get triggered

Some discussion with xnox on IRC helped me to get to a possible cause of
the problem:

journalctl -u udev-configure-printer@-devices-
pci:00-:00:14.0-usb2-2x2d2.service > journalctl-u.txt

gives (file redirection prevents trimming ;lines to terminal width):

--
-- Logs begin at Mon 2017-10-09 09:07:44 -03, end at Mon 2017-10-09 12:17:45 
-03. --
Oct 09 11:29:17 till-x1carbon systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:14.0-usb2-2x2d2)...
Oct 09 11:29:17 till-x1carbon udev-configure-printer[23296]: add 
/devices/pci:00/:00:14.0/usb2/2x2d2
Oct 09 11:29:17 till-x1carbon udev-configure-printer[23296]: unable to access 
/sys/devices/pci:00/:00:14.0/usb2/2x2d2
Oct 09 11:29:17 till-x1carbon systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2x2d2.service: 
Control process exited, code=exited status=1
Oct 09 11:29:17 till-x1carbon systemd[1]: Failed to start Automatic 
USB/Bluetooth printer setup (-devices-pci:00-:00:14.0-usb2-2x2d2).
Oct 09 11:29:17 till-x1carbon systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2x2d2.service: 
Unit entered failed state.
Oct 09 11:29:17 till-x1carbon systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2x2d2.service: 
Failed with result 'exit-code'.
--

The directory which needs to get accessed by udev-configure-printer is:
/sys/devices/pci:00/:00:14.0/usb2/2-2, note that the second last
character is a dash. UDEV/systemd(?) inserts for the %i in the second
line of the /lib/systemd/system/udev-configure-printer@.service file:
-devices-pci:00-:00:14.0-usb2-2x2d2, replacing each slash by a
dash and the original dash by "x2d" (should it not be "\x2d"? Not sure
what gets inserted for the %I in the ExecStart line, but udev-configure-
printer ends up with a /sys/devices/pci:00/:00:14.0/usb2/2x2d2
which it does not find as the "x2d" is not turned back into a dash.

This worked in 17.04 so it is a regression.

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

Title:
  Services asked for by UDEV do not get triggered

Status in systemd package in Ubuntu:
  New

Bug description:
  The packages system-config-printer-udev and ippusbxd are installed,
  having the following UDEV rule files:

  /lib/udev/rules.d/70-printers.rules

  --
  # Low-level USB device add trigger
  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="udev-configure-printer", 
TAG+="systemd", PROGRAM="/bin/systemd-escape 
--template=udev-configure-printer@.service %p", ENV{SYSTEMD_WANTS}+="%c"
  # Low-level USB device remove trigger
  ACTION=="remove", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p"
  --

  /lib/udev/rules.d/55-ippusbxd.rules

  --
  # ippusbxd udev rules file

  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device" 
ENV{ID_USB_INTERFACES}=="*:070104:*", OWNER="root", GROUP="lp", MODE="0664", 
PROGRAM="/bin/systemd-escape --template=ippusbxd@.service 
$env{BUSNUM}:$env{DEVNUM}", ENV{SYSTEMD_WANTS}+="%c"
  --

  If I turn on an appropriate printer (USB, supporting IPP-over-USB,
  here the HP DeskJet 2540) I get in the output of "udevadm monitor
  --environment"

  --
  UDEV  [17527.514150] add  /devices/pci:00/:00:14.0/usb2/2-2 (usb)
  ACTION=add
  BUSNUM=002
  DEVNAME=/dev/bus/usb/002/033
  DEVNUM=033
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2
  DEVTYPE=usb_device
  DRIVER=usb
  ID_BUS=usb
  ID_MODEL=Deskjet_2540_series
  ID_MODEL_ENC=Deskjet\x202540\x20series
  ID_MODEL_ID=c211
  ID_REVISION=0100
  ID_SERIAL=HP_Deskjet_2540_series_BR54BFB02C05XK
  ID_SERIAL_SHORT=BR54BFB02C05XK
  ID_USB_INTERFACES=:ffcc00:070104:070102:ff0401:
  ID_VENDOR=HP
  ID_VENDOR_ENC=HP
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  ID_VENDOR_ID=03f0
  MAJOR=189
  MINOR=160
  PRODUCT=3f0/c211/100
  SEQNUM=9891
  SUBSYSTEM=usb
  SYSTEMD_WANTS=ippusbxd@002:033.service 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service 
printer.target
  TAGS=:udev-configure-printer:systemd:
  TYPE=0/0/0
  USEC_INITIALIZED=17527513940

  UDEV  [17527.517724] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
  .MM_USBIFNUM=00
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0
  DEVTYPE=usb_interface
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=255/204/0
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFiscCCip00in00
  PRODUCT=3f0/c211/100
  SEQNUM=9892
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527517478

  UDEV  [17527.522565] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2 (usb)
  .MM_USBIFNUM=02
  ACTION=add

[Touch-packages] [Bug 1722300] Re: Boot times since artful upgrade have increased 4 fold

please upgrade before reporting bugs

234-2ubuntu10 is out of date. Please try again with 234-2ubuntu12

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

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

Title:
  Boot times since artful upgrade have increased 4 fold

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  systemd:
Installed: 234-2ubuntu10

  
  I'm seeing a much longer bot time in Artful than I did in Zesty. 
Systemd-analyze blame indicates that systemd is at the root of this issue.

  hris@Thermia:~$ sudo systemd-analyze blame
2min 541ms lxd-containers.service
2min 213ms systemd-networkd-wait-online.service
6.260s NetworkManager-wait-online.service
4.342s plymouth-quit-wait.service
1.108s fwupd.service
 838ms lxd.service
 690ms snapd.service
 567ms dev-mapper-ubuntu\x2d\x2dvg\x2droot.device
 374ms dev-loop8.device
 353ms dev-loop9.device
 340ms dev-loop10.device
 312ms dev-loop4.device

  Syslog shows:
  chris@Thermia:~$ cat /var/log/syslog | grep 
systemd-networkd-wait-online.service
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  chris@Thermia:~$ ubuntu-bug

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

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

[Touch-packages] [Bug 1722329] Re: package isc-dhcp-client 4.2.4-7ubuntu12.10 failed to install/upgrade: cannot compute MD5 hash for file '/etc/apparmor.d/sbin.dhclient': failed to read (Input/output

2017-10-09 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: isc-dhcp (Ubuntu)
   Importance: Undecided => Low

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Invalid

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

Title:
  package isc-dhcp-client 4.2.4-7ubuntu12.10 failed to install/upgrade:
  cannot compute MD5 hash for file '/etc/apparmor.d/sbin.dhclient':
  failed to read (Input/output error)

Status in isc-dhcp package in Ubuntu:
  Invalid

Bug description:
  errors noticed at start up

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: isc-dhcp-client 4.2.4-7ubuntu12.10
  ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Wed Oct  4 19:02:12 2017
  DuplicateSignature: package:isc-dhcp-client:4.2.4-7ubuntu12.10:cannot compute 
MD5 hash for file '/etc/apparmor.d/sbin.dhclient': failed to read (Input/output 
error)
  ErrorMessage: cannot compute MD5 hash for file 
'/etc/apparmor.d/sbin.dhclient': failed to read (Input/output error)
  InstallationDate: Installed on 2016-04-19 (538 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-client 4.2.4-7ubuntu12.10 failed to install/upgrade: 
cannot compute MD5 hash for file '/etc/apparmor.d/sbin.dhclient': failed to 
read (Input/output error)
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.sbin.dhclient: [inaccessible: [Errno 5] 
Input/output error]

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

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

[Touch-packages] [Bug 1722313] Re: [SRU][xenial] Add "--with-audit" config option so that the hwclock command creates an audit record when the hardware clock is altered.

Comment #3 Should have read "Common Criteria EAL2 hwclock testcase".

** Description changed:

  [IMPACT]
  There is a requirement for Common Criteria EAL2 certification that changes to 
the system's hardware clock be audited/monitored. In Ubuntu the hwclock command 
can be used to alter the system's hardware clock. Thus this event needs to be 
audited for EAL2. The hwclock command within util-linux has the ability to 
create an audit event when the system's hardware clock is altered, but this 
ability is enabled via the --with-audit config option. This option is currently 
not enabled.
  
- Only the hwclock and the login commands within util-linux package use this 
--with-audit config option to enable auditing. However, it appears the login 
command is not built nor shipped in util-linux. Ubuntu uses the login command 
from shadow instead. Thus, only hwclock command would be affected by this 
change. The change would enable (1) call to audit_open to create a netlink 
socket descritor. (2) generate an audit entry when system hardware clock 
altered. The entry will be logged into the /var/log/audit/audit.log IF auditd 
is installed and running.
-  
+ Only the hwclock and the login commands within util-linux package use
+ this --with-audit config option to enable auditing. However, it appears
+ the login command is not built nor shipped in util-linux. Ubuntu uses
+ the login command from shadow instead. Thus, only hwclock command would
+ be affected by this change. The change would enable (1) call to
+ audit_open to create a netlink socket descritor. (2) generate an audit
+ entry when system hardware clock altered. The entry will be logged into
+ the /var/log/audit/audit.log IF auditd is installed and running.
+ 
  [TEST]
  
  This has been tested on both P8 and amd64 architectures. With the patch
  all the Common Criteria testcases pass for hwclock. Before this patch,
  the functional part of the testcase passed, but the check for the
- triggered audit records would fail.
+ triggered audit records would fail. Attached the Common Criteria
+ testcase below.
+ 
+ Also, the util-linux package has testcases that get run during the
+ build. All of these pass. Pointer to build log below.
  
  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

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

Title:
  [SRU][xenial] Add "--with-audit" config option so that the hwclock
  command creates an audit record when the hardware clock is altered.

Status in util-linux package in Ubuntu:
  New

Bug description:
  [IMPACT]
  There is a requirement for Common Criteria EAL2 certification that changes to 
the system's hardware clock be audited/monitored. In Ubuntu the hwclock command 
can be used to alter the system's hardware clock. Thus this event needs to be 
audited for EAL2. The hwclock command within util-linux has the ability to 
create an audit event when the system's hardware clock is altered, but this 
ability is enabled via the --with-audit config option. This option is currently 
not enabled.

  Only the hwclock and the login commands within util-linux package use
  this --with-audit config option to enable auditing. However, it
  appears the login command is not built nor shipped in util-linux.
  Ubuntu uses the login command from shadow instead. Thus, only hwclock
  command would be affected by this change. The change would enable (1)
  call to audit_open to create a netlink socket descritor. (2) generate
  an audit entry when system hardware clock altered. The entry will be
  logged into the /var/log/audit/audit.log IF auditd is installed and
  running.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

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

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

[Touch-packages] [Bug 1709823] Update Released

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

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

Title:
  Installation of libgles1-mesa (12.0.6-0ubuntu0.16.04.1) failed

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Installation of libgles1-mesa (12.0.6-0ubuntu0.16.04.1) on Ubuntu 16.04 LTS 
failed - it needs the package libglapi-mesa (12.0.6-0buntu0.16.04.1), which 
does not exist. The current version of libglapi-mesa is 17.0.7-0ubuntu0.16.04.1 
(xenial-updates), which does not support the installation of libgles1-mesa.

  [Test case]
  Try to install the package from 
  
https://01.org/linuxgraphics/downloads/intel-graphics-update-tool-linux-os-v2.0.2

  [Regression potential]
  none, it just adds a dummy package to fix broken/unnecessary dependencies in 
3rd party packages

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

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

[Touch-packages] [Bug 1722313] Re: [SRU][xenial] Add "--with-audit" config option so that the hwclock command creates an audit record when the hardware clock is altered.

** Attachment added: "EAL hwclock testcase"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+attachment/4966040/+files/test_hwclock.bash

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

Title:
  [SRU][xenial] Add "--with-audit" config option so that the hwclock
  command creates an audit record when the hardware clock is altered.

Status in util-linux package in Ubuntu:
  New

Bug description:
  [IMPACT]
  There is a requirement for Common Criteria EAL2 certification that changes to 
the system's hardware clock be audited/monitored. In Ubuntu the hwclock command 
can be used to alter the system's hardware clock. Thus this event needs to be 
audited for EAL2. The hwclock command within util-linux has the ability to 
create an audit event when the system's hardware clock is altered, but this 
ability is enabled via the --with-audit config option. This option is currently 
not enabled.

  Only the hwclock and the login commands within util-linux package use
  this --with-audit config option to enable auditing. However, it
  appears the login command is not built nor shipped in util-linux.
  Ubuntu uses the login command from shadow instead. Thus, only hwclock
  command would be affected by this change. The change would enable (1)
  call to audit_open to create a netlink socket descritor. (2) generate
  an audit entry when system hardware clock altered. The entry will be
  logged into the /var/log/audit/audit.log IF auditd is installed and
  running.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

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

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

[Touch-packages] [Bug 1696686] Update Released

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

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

Title:
  ld: Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to
  PLT entry

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Released

Bug description:
  SRU acceptance criteria:
   - the package builds
   - the newly added tests pass, no regressions to previous builds
   - needs only testing on armhf, no other changes.

  Original bug report:

  When linking large applications, we sometimes see this error. This is
  affecting the LLVM ARM buildbots.

  The issue was fixed upstream:
  https://sourceware.org/bugzilla/show_bug.cgi?id=20608

  Could you please backport it to Xenial?

  I have applied the patch on top of binutils_2.26.1.orig.tar.gz + 
binutils_2.26.1-1ubuntu1~16.04.3.diff.gz as found here:
  https://packages.ubuntu.com/xenial-updates/binutils-arm-linux-gnueabihf

  It applies cleanly (except the ChangeLog) and passes make check.

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

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

[Touch-packages] [Bug 1709823] Re: Installation of libgles1-mesa (12.0.6-0ubuntu0.16.04.1) failed

This bug was fixed in the package mesa - 17.0.7-0ubuntu0.16.04.2

---
mesa (17.0.7-0ubuntu0.16.04.2) xenial; urgency=medium

  * control: Add a transitional package for libgles1-mesa. (LP:
#1709823)

 -- Timo Aaltonen   Fri, 11 Aug 2017 00:51:18 +0300

** Changed in: mesa (Ubuntu Xenial)
   Status: Confirmed => Fix Released

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

Title:
  Installation of libgles1-mesa (12.0.6-0ubuntu0.16.04.1) failed

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Installation of libgles1-mesa (12.0.6-0ubuntu0.16.04.1) on Ubuntu 16.04 LTS 
failed - it needs the package libglapi-mesa (12.0.6-0buntu0.16.04.1), which 
does not exist. The current version of libglapi-mesa is 17.0.7-0ubuntu0.16.04.1 
(xenial-updates), which does not support the installation of libgles1-mesa.

  [Test case]
  Try to install the package from 
  
https://01.org/linuxgraphics/downloads/intel-graphics-update-tool-linux-os-v2.0.2

  [Regression potential]
  none, it just adds a dummy package to fix broken/unnecessary dependencies in 
3rd party packages

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

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

[Touch-packages] [Bug 1696686] Re: ld: Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to PLT entry

This bug was fixed in the package binutils - 2.26.1-1ubuntu1~16.04.5

---
binutils (2.26.1-1ubuntu1~16.04.5) xenial-proposed; urgency=medium

  * SRU: LP: #1696686.
  * Fix PR ld/20608: Relocation truncated to fit: R_ARM_THM_JUMP24 for
relocation to PLT entry.

 -- Matthias Klose   Mon, 21 Aug 2017 16:24:14 +0200

** Changed in: binutils (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  ld: Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to
  PLT entry

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Released

Bug description:
  SRU acceptance criteria:
   - the package builds
   - the newly added tests pass, no regressions to previous builds
   - needs only testing on armhf, no other changes.

  Original bug report:

  When linking large applications, we sometimes see this error. This is
  affecting the LLVM ARM buildbots.

  The issue was fixed upstream:
  https://sourceware.org/bugzilla/show_bug.cgi?id=20608

  Could you please backport it to Xenial?

  I have applied the patch on top of binutils_2.26.1.orig.tar.gz + 
binutils_2.26.1-1ubuntu1~16.04.3.diff.gz as found here:
  https://packages.ubuntu.com/xenial-updates/binutils-arm-linux-gnueabihf

  It applies cleanly (except the ChangeLog) and passes make check.

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

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

[Touch-packages] [Bug 1722313] Re: [SRU][xenial] Add "--with-audit" config option so that the hwclock command creates an audit record when the hardware clock is altered.

build log and tests run
https://launchpad.net/~j-latten/+archive/ubuntu/joyppa/+build/13375821

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

Title:
  [SRU][xenial] Add "--with-audit" config option so that the hwclock
  command creates an audit record when the hardware clock is altered.

Status in util-linux package in Ubuntu:
  New

Bug description:
  [IMPACT]
  There is a requirement for Common Criteria EAL2 certification that changes to 
the system's hardware clock be audited/monitored. In Ubuntu the hwclock command 
can be used to alter the system's hardware clock. Thus this event needs to be 
audited for EAL2. The hwclock command within util-linux has the ability to 
create an audit event when the system's hardware clock is altered, but this 
ability is enabled via the --with-audit config option. This option is currently 
not enabled.

  Only the hwclock and the login commands within util-linux package use this 
--with-audit config option to enable auditing. However, it appears the login 
command is not built nor shipped in util-linux. Ubuntu uses the login command 
from shadow instead. Thus, only hwclock command would be affected by this 
change. The change would enable (1) call to audit_open to create a netlink 
socket descritor. (2) generate an audit entry when system hardware clock 
altered. The entry will be logged into the /var/log/audit/audit.log IF auditd 
is installed and running.
   
  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

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

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

[Touch-packages] [Bug 1722329] Re: package isc-dhcp-client 4.2.4-7ubuntu12.10 failed to install/upgrade: cannot compute MD5 hash for file '/etc/apparmor.d/sbin.dhclient': failed to read (Input/output

2017-10-09 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package isc-dhcp-client 4.2.4-7ubuntu12.10 failed to install/upgrade:
  cannot compute MD5 hash for file '/etc/apparmor.d/sbin.dhclient':
  failed to read (Input/output error)

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  errors noticed at start up

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: isc-dhcp-client 4.2.4-7ubuntu12.10
  ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Wed Oct  4 19:02:12 2017
  DuplicateSignature: package:isc-dhcp-client:4.2.4-7ubuntu12.10:cannot compute 
MD5 hash for file '/etc/apparmor.d/sbin.dhclient': failed to read (Input/output 
error)
  ErrorMessage: cannot compute MD5 hash for file 
'/etc/apparmor.d/sbin.dhclient': failed to read (Input/output error)
  InstallationDate: Installed on 2016-04-19 (538 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-client 4.2.4-7ubuntu12.10 failed to install/upgrade: 
cannot compute MD5 hash for file '/etc/apparmor.d/sbin.dhclient': failed to 
read (Input/output error)
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.sbin.dhclient: [inaccessible: [Errno 5] 
Input/output error]

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

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

[Touch-packages] [Bug 1371250] Re: LightDM fails to switch to greeter on logout if allow-user-switching=false

2017-10-09 Thread Charles Wright

Hello,

I'm using multiseat under ubuntu lts 16.04

I found a description of what is happening here:
https://lists.launchpad.net/ubuntu-multiseat/msg00505.html

In short, seat-1 lock/switch user doesn't work and generates tons of
error logs

[+763003.64s] DEBUG: Launching process 27821: /usr/bin/X :1 -s seat-1 :2 
-config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 
-nolisten tcp
[+763003.69s] DEBUG: Launching process 27822: /usr/bin/X :1 -s seat-1 :2 
-config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 
-nolisten tcp
[+763003.74s] DEBUG: Launching process 27823: /usr/bin/X :1 -s seat-1 :2 
-config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 
-nolisten tcp
[+763003.79s] DEBUG: Launching process 27824: /usr/bin/X :1 -s seat-1 :2 
-config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 
-nolisten tcp
[+763003.84s] DEBUG: Launching process 27825: /usr/bin/X :1 -s seat-1 :2 
-config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 
-nolisten tcp


I configured allow-user-switching=false so that my logs won't fill up.

[Seat:seat-1]
xserver-command=/usr/bin/X :1 -s seat-1
xserver-config=/etc/X11/xorg.conf.nvidia
# This kept constant respawn of X from filling up logs, but only allows one 
login - greeter fails to start
allow-user-switching=false

Now what happens, just as reported in this bug is that I can start
lightdm, and someone can login once to seat-1, but once they log out
there is no greeter respawned.

I think this bug should be updated to include Xenial as well.

Anyways I'm sure multiseat is a rare thing but I wanted someone to know
it matters to me.

I'm so close to having it work!

Is there anything else I can try to work around?

I see the question above:

"Should we adopt the following solution for this bug?"

I vote yes to that.

Thanks.

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

Title:
  LightDM fails to switch to greeter on logout if allow-user-
  switching=false

Status in Light Display Manager:
  Triaged
Status in Light Display Manager 1.10 series:
  Triaged
Status in Light Display Manager 1.12 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Utopic:
  Won't Fix

Bug description:
  In my multiseat system, if I logout on a non-seat0 seat (which has
  allow-user-switching=false by default), lightdm fails to start a
  greeter on that seat:

  DEBUG: Seat: Display server stopped
  DEBUG: Seat: Active display server stopped, starting greeter
  DEBUG: Seat: Stopping; failed to start a greeter
  DEBUG: Seat: Stopping
  DEBUG: Seat: Stopped

  I guess the problem is related to seat_switch_to_greeter() calls in
  session_stopped or display_server_stopped callbacks in seat.c. Switch
  to greeter should be always allowed on logout.

  NOTE: This was observed in LightDM 1.10.2 on Ubuntu 14.04, but I guess
  it also happens on trunk series.

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

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

[Touch-packages] [Bug 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

This bug was fixed in the package initramfs-tools - 0.103ubuntu4.8

---
initramfs-tools (0.103ubuntu4.8) trusty; urgency=medium

  * hook-functions: handle lvm-on-nvme case.
(LP: #1718055)

 -- Dan Streetman   Tue, 19 Sep 2017
11:03:43 -0400

** Changed in: initramfs-tools (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  update-initramfs fails for MODULES=dep when root is on LVM wich uses
  nvme device

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Fix Released

Bug description:
  [impact]

  On a trusty system, if using MODULES=dep with lvm-on-nvme then update-
  initramfs fails to rebuild the initramfs.  This prevents using
  MODULES=dep for building an initramfs on trusty, with a rootfs that
  uses lvm on nvme.

  [test case]

  install a system where the rootfs uses a LVM logical volume that is
  located on a physical volume on a NVMe drive.  Edit the /etc
  /initramfs-tools/initramfs.conf file and change the MODULES line to
  MODULES=dep and save the file.  Then run sudo update-initramfs -u
  which will fail with:

  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic
  mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry
  mkinitramfs: workaround is MODULES=most
  mkinitramfs: Error please report the bug
  update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1.

  [regression potential]

  This changes initramfs creation for rootfs that are on nvme or lvm, so
  has the potential to break it for any system with its rootfs on either
  or both of those.  It is likely to only break initramfs creation, not
  system booting.

  About the autopkgtest failure, explanation can be found here: 
  
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718055/comments/9

  [other info]

  related to bug 1532146

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

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

[Touch-packages] [Bug 1722313] Re: [SRU][xenial] Add "--with-audit" config option so that the hwclock command creates an audit record when the hardware clock is altered.

** Description changed:

[IMPACT]
There is a requirement for Common Criteria EAL2 certification that changes to
the system's hardware clock be audited/monitored. In Ubuntu the hwclock command
can be used to alter the system's hardware clock. Thus this event needs to be
audited for EAL2. The hwclock command within util-linux has the ability to
create an audit event when the system's hardware clock is altered, but this
ability is enabled via the --with-audit config option. This option is currently
not enabled.

- Only the hwclock and the login commands within util-linux package use
- this --with-audit config option to enable auditing. However, it appears
- the login command is not built nor shipped in util-linux. Ubuntu uses
- the login command from shadow instead. Thus, only hwclock command would
- be affected by this change. The change would enable (1) call to
- audit_open to create a netlink socket descritor. (2) generate an audit
- entry when system hardware clock altered. The entry will be logged into
- the /var/log/audit/audit.log IF auditd is installed and running.
-
- [FIX]
-
+ Only the hwclock and the login commands within util-linux package use this
--with-audit config option to enable auditing. However, it appears the login
command is not built nor shipped in util-linux. Ubuntu uses the login command
from shadow instead. Thus, only hwclock command would be affected by this
change. The change would enable (1) call to audit_open to create a netlink
socket descritor. (2) generate an audit entry when system hardware clock
altered. The entry will be logged into the /var/log/audit/audit.log IF auditd
is installed and running.
+
[TEST]

This has been tested on both P8 and amd64 architectures. With the patch
all the Common Criteria testcases pass for hwclock. Before this patch,
the functional part of the testcase passed, but the check for the
triggered audit records would fail.

[REGRESSION POTENTIAL]
The regression potential for this should be small. This change does not take
away from any current functionality. It just adds the ability to generate an
audit entry when system hardware clock is altered.

** Attachment added: "debdiff of version 3.3 and 3.4~joyppa2"

https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+attachment/4966026/+files/debdiff.out

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

Title:
[SRU][xenial] Add "--with-audit" config option so that the hwclock
command creates an audit record when the hardware clock is altered.

Status in util-linux package in Ubuntu:
New

Bug description:
[IMPACT]
There is a requirement for Common Criteria EAL2 certification that changes to
the system's hardware clock be audited/monitored. In Ubuntu the hwclock command
can be used to alter the system's hardware clock. Thus this event needs to be
audited for EAL2. The hwclock command within util-linux has the ability to
create an audit event when the system's hardware clock is altered, but this
ability is enabled via the --with-audit config option. This option is currently
not enabled.

Only the hwclock and the login commands within util-linux package use this
--with-audit config option to enable auditing. However, it appears the login
command is not built nor shipped in util-linux. Ubuntu uses the login command
from shadow instead. Thus, only hwclock command would be affected by this
change. The change would enable (1) call to audit_open to create a netlink
socket descritor. (2) generate an audit entry when system hardware clock
altered. The entry will be logged into the /var/log/audit/audit.log IF auditd
is installed and running.

[TEST]

This has been tested on both P8 and amd64 architectures. With the
patch all the Common Criteria testcases pass for hwclock. Before this
patch, the functional part of the testcase passed, but the check for
the triggered audit records would fail.

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

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

[Touch-packages] [Bug 1722329] [NEW] package isc-dhcp-client 4.2.4-7ubuntu12.10 failed to install/upgrade: cannot compute MD5 hash for file '/etc/apparmor.d/sbin.dhclient': failed to read (Input/outpu

2017-10-09 Thread aaron

Public bug reported:

errors noticed at start up

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: isc-dhcp-client 4.2.4-7ubuntu12.10
ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
Date: Wed Oct  4 19:02:12 2017
DuplicateSignature: package:isc-dhcp-client:4.2.4-7ubuntu12.10:cannot compute 
MD5 hash for file '/etc/apparmor.d/sbin.dhclient': failed to read (Input/output 
error)
ErrorMessage: cannot compute MD5 hash for file '/etc/apparmor.d/sbin.dhclient': 
failed to read (Input/output error)
InstallationDate: Installed on 2016-04-19 (538 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: isc-dhcp
Title: package isc-dhcp-client 4.2.4-7ubuntu12.10 failed to install/upgrade: 
cannot compute MD5 hash for file '/etc/apparmor.d/sbin.dhclient': failed to 
read (Input/output error)
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.sbin.dhclient: [inaccessible: [Errno 5] 
Input/output error]

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package isc-dhcp-client 4.2.4-7ubuntu12.10 failed to install/upgrade:
  cannot compute MD5 hash for file '/etc/apparmor.d/sbin.dhclient':
  failed to read (Input/output error)

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  errors noticed at start up

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: isc-dhcp-client 4.2.4-7ubuntu12.10
  ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Wed Oct  4 19:02:12 2017
  DuplicateSignature: package:isc-dhcp-client:4.2.4-7ubuntu12.10:cannot compute 
MD5 hash for file '/etc/apparmor.d/sbin.dhclient': failed to read (Input/output 
error)
  ErrorMessage: cannot compute MD5 hash for file 
'/etc/apparmor.d/sbin.dhclient': failed to read (Input/output error)
  InstallationDate: Installed on 2016-04-19 (538 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-client 4.2.4-7ubuntu12.10 failed to install/upgrade: 
cannot compute MD5 hash for file '/etc/apparmor.d/sbin.dhclient': failed to 
read (Input/output error)
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.sbin.dhclient: [inaccessible: [Errno 5] 
Input/output error]

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

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

[Touch-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

I see there are some nplan regressions for this upload. I looked at them
briefly and I see that the nplan testsuite is in terrible shape and
tends to just fail a lot, so they're probably are unrelated, but could
the uploader please take a look and double-confirm? I can then release
this fix to -updates.

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Incomplete
Status in wpa package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in ubiquity source package in Xenial:
  Confirmed
Status in wpa source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Users booting from OEM setup may find that their wireless device is "not 
ready" as per NetworkManager, because wpasupplicant is not running. This is 
because the steps taken to start in OEM prepare, before moving to the real 
system runs systemctl isolate, and wpasupplicant gets caught in the crossfire.

  
  [Test case]
  * Steps to reproduce:
  1. Install in OEM mode
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  
  [Regression potential]
  The following are examples of possible regression scenarios from this stable 
update:
  - Failure to get the wireless device ready at session start
  - Driver loading issues for the wireless devices
  - Failure to complete OEM preparation steps, due to the oem user remaining 
connected while it's being removed by the last steps of the OEM preparation 
process.

  
  [Background information]
  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

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

[Touch-packages] [Bug 1718055] Update Released

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

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

Title:
  update-initramfs fails for MODULES=dep when root is on LVM wich uses
  nvme device

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Fix Released

Bug description:
  [impact]

  On a trusty system, if using MODULES=dep with lvm-on-nvme then update-
  initramfs fails to rebuild the initramfs.  This prevents using
  MODULES=dep for building an initramfs on trusty, with a rootfs that
  uses lvm on nvme.

  [test case]

  install a system where the rootfs uses a LVM logical volume that is
  located on a physical volume on a NVMe drive.  Edit the /etc
  /initramfs-tools/initramfs.conf file and change the MODULES line to
  MODULES=dep and save the file.  Then run sudo update-initramfs -u
  which will fail with:

  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic
  mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry
  mkinitramfs: workaround is MODULES=most
  mkinitramfs: Error please report the bug
  update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1.

  [regression potential]

  This changes initramfs creation for rootfs that are on nvme or lvm, so
  has the potential to break it for any system with its rootfs on either
  or both of those.  It is likely to only break initramfs creation, not
  system booting.

  About the autopkgtest failure, explanation can be found here: 
  
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718055/comments/9

  [other info]

  related to bug 1532146

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

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

2017-10-09 Thread Doug Smythies

Paul wrote:

> I am using Linux 4.14-rc3+.

O.K. that is/was really important information.

While I have been calling this a kernel regression, it might be that a
great number of apparmor profiles need to be updated to accommodate the
new security stuff that was introduced in kernel 4.14-rc2 (it missed
-rc1 due to some issues, and it is not normal to include such major
changes in anything other than -rc1). i.e. It might be that this is a
non-backwards compatible kernel change.

Anyway, I know nothing about this area of the kernel, and will step back
now.

To be able to proceed with my own work, I have compiled kernel 4.14-rc3
(and now 4.14-rc4) with apparmor disabled.

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

Title:
  apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"

Status in apparmor package in Ubuntu:
  New

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 1718717] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

2017-10-09 Thread Markward Kufleitner

This Bug came again just after shutdown, reboot and logging in to
cinnamon.

Any hints, what's wrong with my system?

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

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

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

Bug description:
  after updates of cups-filter and reboot

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

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

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

[Touch-packages] [Bug 1722313] [NEW] [SRU][xenial] Add "--with-audit" config option so that the hwclock command creates an audit record when the hardware clock is altered.

Public bug reported:

[IMPACT]
There is a requirement for Common Criteria EAL2 certification that changes to 
the system's hardware clock be audited/monitored. In Ubuntu the hwclock command 
can be used to alter the system's hardware clock. Thus this event needs to be 
audited for EAL2. The hwclock command within util-linux has the ability to 
create an audit event when the system's hardware clock is altered, but this 
ability is enabled via the --with-audit config option. This option is currently 
not enabled.

Only the hwclock and the login commands within util-linux package use
this --with-audit config option to enable auditing. However, it appears
the login command is not built nor shipped in util-linux. Ubuntu uses
the login command from shadow instead. Thus, only hwclock command would
be affected by this change. The change would enable (1) call to
audit_open to create a netlink socket descritor. (2) generate an audit
entry when system hardware clock altered. The entry will be logged into
the /var/log/audit/audit.log IF auditd is installed and running.

[FIX]

[TEST]

This has been tested on both P8 and amd64 architectures. With the patch
all the Common Criteria testcases pass for hwclock. Before this patch,
the functional part of the testcase passed, but the check for the
triggered audit records would fail.

[REGRESSION POTENTIAL]
The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

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

** Summary changed:

- Add "--with-audit" config option so that the hwclock command creates audit 
records when it is used to alter the hardware clock.
+ [SRU][xenial] Add "--with-audit" config option so that the hwclock command 
creates an audit record when the hardware clock is altered.

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

Title:
  [SRU][xenial] Add "--with-audit" config option so that the hwclock
  command creates an audit record when the hardware clock is altered.

Status in util-linux package in Ubuntu:
  New

Bug description:
  [IMPACT]
  There is a requirement for Common Criteria EAL2 certification that changes to 
the system's hardware clock be audited/monitored. In Ubuntu the hwclock command 
can be used to alter the system's hardware clock. Thus this event needs to be 
audited for EAL2. The hwclock command within util-linux has the ability to 
create an audit event when the system's hardware clock is altered, but this 
ability is enabled via the --with-audit config option. This option is currently 
not enabled.

  Only the hwclock and the login commands within util-linux package use
  this --with-audit config option to enable auditing. However, it
  appears the login command is not built nor shipped in util-linux.
  Ubuntu uses the login command from shadow instead. Thus, only hwclock
  command would be affected by this change. The change would enable (1)
  call to audit_open to create a netlink socket descritor. (2) generate
  an audit entry when system hardware clock altered. The entry will be
  logged into the /var/log/audit/audit.log IF auditd is installed and
  running.

  [FIX]

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

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

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

[Touch-packages] [Bug 1722319] [NEW] Totem Player not working correctly on 17.10 Beta 2

2017-10-09 Thread James Daube

Public bug reported:

I did a fresh install of Ubuntu 17.10 Beta 2 on my laptop - Dell
Inspiron N4110, Intel Sandybridge Mobile Graphics, Intel® Core™ i3-2350M
CPU @ 2.30GHz × 4, 6GB of RAM.  If I try to play ANY video on the Totem
movie player (the default GNOME player), I get sound and subtitles but
no picture. VLC works just fine. This did not happen on my previous
14.04 install on the same laptop. Is this a beta OS bug or just a bad
media player?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libgstreamer1.0-0 1.12.3-1
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
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  9 08:31:37 2017
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-10-06 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
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.
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Totem Player not working correctly on 17.10 Beta 2

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  I did a fresh install of Ubuntu 17.10 Beta 2 on my laptop - Dell
  Inspiron N4110, Intel Sandybridge Mobile Graphics, Intel® Core™
  i3-2350M CPU @ 2.30GHz × 4, 6GB of RAM.  If I try to play ANY video on
  the Totem movie player (the default GNOME player), I get sound and
  subtitles but no picture. VLC works just fine. This did not happen on
  my previous 14.04 install on the same laptop. Is this a beta OS bug or
  just a bad media player?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.3-1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 08:31:37 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-10-06 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  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.
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1722319/+subscriptions

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

[Touch-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo

2017-10-09 Thread Dik

The all dmesg's/lspci's of users must be analyzed, but I think, its
Intel 3945ABG specific bug (iwl3945)

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1569269] Re: CUPS incorrectly reports 'waste-receptacle-full'

2017-10-09 Thread Emerson Prado

I am having this problem with a LAN printer (corporate environment):

Printer: Ricoh MP 501
Kernel: 3.16.0-4-amd64
Distro: Linux Mint Debian Edition v. 2 (Betsy) - Binary compatible to Debian 8.9
Cups version: 1.7.5-11+deb

I'm puzzled to see the cups version is higher than the fixed one.
Regression or different issue?

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

Title:
  CUPS incorrectly reports 'waste-receptacle-full'

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When I try to print a test page on my Ricoh Aficio MP C3502 I get an
  error message saying "Printer 'ricoh':'waste-receptacle-full'".

  However, my colleagues are able to use the printer normally on Fedora
  and Windows.

  After investigation, I realised that the problem was reported
  previously here: https://bugzilla.redhat.com/show_bug.cgi?id=1193105
  and fixed in the version cups_1.7.5. I could not find this bug being
  reported on Ubuntu bug track.

  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Linux work 4.2.0-35-generic #40~14.04.1-Ubuntu SMP Fri Mar 18 16:37:35 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
  cups:
Installed: 1.7.2-0ubuntu1.7
Candidate: 1.7.2-0ubuntu1.7

  Expected behaviour:
  Remove the incorrect error message when trying to print a page.

  What happened:
  The error message shows up when it should not.

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

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

[Touch-packages] [Bug 1714596] Re: PDF images are blank

2017-10-09 Thread Leonidas S. Barbosa

Ok, I could reproduce seems that it has some regression in libpoppler-
glib8. If you downgrade only this .deb for (https://launchpad.net
/~ubuntu-security/+archive/ubuntu/ppa/+build/13046914/+files/libpoppler-
glib8_0.48.0-2ubuntu2.1_amd64.deb) things will works fine.

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  In Progress

Bug description:
  1. Download a PDFs with images such as - 
  
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  
http://www.hopkinsmedicine.org/human_resources/_docs/employee_handbook_non-union_non-represented.pdf
  http://humanservices.arkansas.gov/dccece/classroom_docs/carseatsafety.pdf

  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

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

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

2017-10-09 Thread Paul Menzel

Dear Doug,


Thank you for your reply.

On 10/06/17 21:16, Doug Smythies wrote:
> Which kernel are you using?

I am using Linux 4.14-rc3+.

> On my development 17.10 Desktop, I get the same as you but only for mainline
> kernels 4.14-rc2 and 4.14-rc3. Earlier kernels, including mainline 4.14-rc1 > 
> seem to be fine with respect to this issue.

I don’t know, when it started. The problem wasn’t there with Linux 4.13. 
So, your observation seems plausible.


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"

Status in apparmor package in Ubuntu:
  New

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 1722300] [NEW] Boot times since artful upgrade have increased 4 fold

2017-10-09 Thread Chris Gregan

Public bug reported:

systemd:
  Installed: 234-2ubuntu10


I'm seeing a much longer bot time in Artful than I did in Zesty. 
Systemd-analyze blame indicates that systemd is at the root of this issue.

hris@Thermia:~$ sudo systemd-analyze blame
  2min 541ms lxd-containers.service
  2min 213ms systemd-networkd-wait-online.service
  6.260s NetworkManager-wait-online.service
  4.342s plymouth-quit-wait.service
  1.108s fwupd.service
   838ms lxd.service
   690ms snapd.service
   567ms dev-mapper-ubuntu\x2d\x2dvg\x2droot.device
   374ms dev-loop8.device
   353ms dev-loop9.device
   340ms dev-loop10.device
   312ms dev-loop4.device

Syslog shows:
chris@Thermia:~$ cat /var/log/syslog | grep systemd-networkd-wait-online.service
Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: Main 
process exited, code=exited, status=1/FAILURE
Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: Unit 
entered failed state.
Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: Main 
process exited, code=exited, status=1/FAILURE
Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: Unit 
entered failed state.
Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: Main 
process exited, code=exited, status=1/FAILURE
Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: Unit 
entered failed state.
Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: Main 
process exited, code=exited, status=1/FAILURE
Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: Unit 
entered failed state.
Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
chris@Thermia:~$ ubuntu-bug

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

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

Title:
  Boot times since artful upgrade have increased 4 fold

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd:
Installed: 234-2ubuntu10

  
  I'm seeing a much longer bot time in Artful than I did in Zesty. 
Systemd-analyze blame indicates that systemd is at the root of this issue.

  hris@Thermia:~$ sudo systemd-analyze blame
2min 541ms lxd-containers.service
2min 213ms systemd-networkd-wait-online.service
6.260s NetworkManager-wait-online.service
4.342s plymouth-quit-wait.service
1.108s fwupd.service
 838ms lxd.service
 690ms snapd.service
 567ms dev-mapper-ubuntu\x2d\x2dvg\x2droot.device
 374ms dev-loop8.device
 353ms dev-loop9.device
 340ms dev-loop10.device
 312ms dev-loop4.device

  Syslog shows:
  chris@Thermia:~$ cat /var/log/syslog | grep 
systemd-networkd-wait-online.service
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  8 13:04:45 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  8 16:32:34 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Unit entered failed state.
  Oct  9 08:32:12 Thermia systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  chris@Thermia:~$ ubuntu-bug

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

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

[Touch-packages] [Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown

2017-10-09 Thread Pasquale Pompeo

Hi, I can confirm this bug affects my notepad too. System hangs on
shutdown/reboot with the "A stop job for network-manager and wpa
supplicant is running" message.

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

Title:
  can't disable wi-fi and system hangs on shutdown

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  If I try to turn off wi-fi the system freezes for few seconds and after that 
internet is not working and I can't open settings anymore, even if the wi-fi 
tray icon still shows a connection.
  When I shutdown the system it says that "A stop job for network-manager and 
wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension 
doesn't work neither.
  Everything was working just fine on 17.10 daily builds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 23:18:01 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-22 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  IpRoute:
   default via 192.168.1.254 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp2s0  ethernet  unavailable  /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.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown

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

Title:
  can't disable wi-fi and system hangs on shutdown

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  If I try to turn off wi-fi the system freezes for few seconds and after that 
internet is not working and I can't open settings anymore, even if the wi-fi 
tray icon still shows a connection.
  When I shutdown the system it says that "A stop job for network-manager and 
wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension 
doesn't work neither.
  Everything was working just fine on 17.10 daily builds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 23:18:01 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-22 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  IpRoute:
   default via 192.168.1.254 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp2s0  ethernet  unavailable  /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.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1722297] [NEW] package systemd 232-21ubuntu5 failed to install/upgrade: package systemd is not ready for configuration cannot configure (current status 'half-installed')

2017-10-09 Thread Everett Haley

Public bug reported:

will not let me update anything

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: systemd 232-21ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Mon Oct  9 10:49:13 2017
DpkgHistoryLog:
 Start-Date: 2017-10-09  10:49:12
 Commandline: apt-get install -f
 Install: linux-image-extra-4.10.0-35-generic:amd64 (4.10.0-35.39, automatic), 
linux-image-4.10.0-26-generic:amd64 (4.10.0-26.30, automatic), 
linux-headers-4.10.0-35-generic:amd64 (4.10.0-35.39, automatic), 
linux-headers-4.10.0-35:amd64 (4.10.0-35.39, automatic), 
linux-image-4.10.0-35-generic:amd64 (4.10.0-35.39, automatic)
 Upgrade: linux-headers-generic:amd64 (4.10.0.26.28, 4.10.0.35.35), 
linux-image-generic:amd64 (4.10.0.26.28, 4.10.0.35.35), linux-generic:amd64 
(4.10.0.26.28, 4.10.0.35.35)
DpkgTerminalLog:
 dpkg: error processing package systemd (--configure):
  package systemd is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package systemd is not ready for configuration  cannot configure 
(current status 'half-installed')
InstallationDate: Installed on 2017-04-19 (172 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 003: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 7741
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: systemd
Title: package systemd 232-21ubuntu5 failed to install/upgrade: package systemd 
is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/21/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.12
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire 7741
dmi.board.vendor: Acer
dmi.board.version: V1.12
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.12
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.12:bd06/21/2010:svnAcer:pnAspire7741:pvrV1.12:rvnAcer:rnAspire7741:rvrV1.12:cvnAcer:ct10:cvrV1.12:
dmi.product.name: Aspire 7741
dmi.product.version: V1.12
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-package zesty

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

Title:
  package systemd 232-21ubuntu5 failed to install/upgrade: package
  systemd is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in systemd package in Ubuntu:
  New

Bug description:
  will not let me update anything

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon Oct  9 10:49:13 2017
  DpkgHistoryLog:
   Start-Date: 2017-10-09  10:49:12
   Commandline: apt-get install -f
   Install: linux-image-extra-4.10.0-35-generic:amd64 (4.10.0-35.39, 
automatic), linux-image-4.10.0-26-generic:amd64 (4.10.0-26.30, automatic), 
linux-headers-4.10.0-35-generic:amd64 (4.10.0-35.39, automatic), 
linux-headers-4.10.0-35:amd64 (4.10.0-35.39, automatic), 
linux-image-4.10.0-35-generic:amd64 (4.10.0-35.39, automatic)
   Upgrade: linux-headers-generic:amd64 (4.10.0.26.28, 4.10.0.35.35), 
linux-image-generic:amd64 (4.10.0.26.28, 4.10.0.35.35), linux-generic:amd64 
(4.10.0.26.28, 4.10.0.35.35)
  DpkgTerminalLog:
   dpkg: error processing package systemd (--configure):
package systemd is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package systemd is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-04-19 (172 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 003: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire

[Touch-packages] [Bug 1722283] Re: gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-packages/PyKDE4/init.py: No module named 'DLFCN'

2017-10-09 Thread Apport retracing service

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

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 #1708947, 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

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

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

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

** This bug has been marked a duplicate of bug 1708947
   gdebi-kde crashed with ModuleNotFoundError in 
/usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN'

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

Title:
  gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-
  packages/PyKDE4/__init__.py: No module named 'DLFCN'

Status in gdebi package in Ubuntu:
  New

Bug description:
  Gdebi will not show up in "open with other application" context. using
  Gnome Desktop on Ubuntu 17.10.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gdebi-kde 0.9.5.7+nmu1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 10:15:40 2017
  ExecutablePath: /usr/share/gdebi/gdebi-kde
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-kde
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu1
  PythonArgs: ['/usr/bin/gdebi-kde']
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  SourcePackage: gdebi
  Title: gdebi-kde crashed with ModuleNotFoundError in 
/usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN'
  UpgradeStatus: Upgraded to artful on 2017-10-03 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.

2017-10-09 Thread Florian Weimer

I filed a glibc bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=22273

However, I do not know if that bug is the root cause of the issue
reported here.

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

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

Title:
  cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368:
  __spawnix: Assertion `ec >= 0' failed.

Status in CUPS:
  New
Status in cups package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Confirmed

Bug description:
  1. Error: Package/cups-daemon2.2.4-7 (mutilated)
  2. compiz-core/tmp/apport_core_q_vnqis (corrupted)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: 
Assertion `ec >= 0' failed.
  Date: Fri Sep 22 22:16:18 2017
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2017-05-27 (118 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=el_GR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: 
__spawnix: Assertion `ec >= 0' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-K D3
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  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/cups/+bug/1719004/+subscriptions

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

[Touch-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo

2017-10-09 Thread Kai-Heng Feng

Does this happen to all iwlegacy users, or just some?
We probably need to implement some device matching mechanism in NM.

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1714596] Re: PDF images are blank

2017-10-09 Thread Sebastien Bacher

Right, let's upload a build with --enable-libopenjpeg=unmaintained for
this cycle and try to get the external library promoted next cycle

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

** Changed in: poppler (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  In Progress

Bug description:
  1. Download a PDFs with images such as - 
  
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  
http://www.hopkinsmedicine.org/human_resources/_docs/employee_handbook_non-union_non-represented.pdf
  http://humanservices.arkansas.gov/dccece/classroom_docs/carseatsafety.pdf

  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

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

[Touch-packages] [Bug 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.

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

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

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

Title:
  cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368:
  __spawnix: Assertion `ec >= 0' failed.

Status in CUPS:
  New
Status in cups package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Confirmed

Bug description:
  1. Error: Package/cups-daemon2.2.4-7 (mutilated)
  2. compiz-core/tmp/apport_core_q_vnqis (corrupted)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: 
Assertion `ec >= 0' failed.
  Date: Fri Sep 22 22:16:18 2017
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2017-05-27 (118 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=el_GR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: 
__spawnix: Assertion `ec >= 0' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-K D3
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  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/cups/+bug/1719004/+subscriptions

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

[Touch-packages] [Bug 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.

** Information type changed from Private to Public

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

** Changed in: cups (Ubuntu)
   Importance: Medium => High

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

Title:
  cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368:
  __spawnix: Assertion `ec >= 0' failed.

Status in CUPS:
  New
Status in cups package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Confirmed

Bug description:
  1. Error: Package/cups-daemon2.2.4-7 (mutilated)
  2. compiz-core/tmp/apport_core_q_vnqis (corrupted)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: 
Assertion `ec >= 0' failed.
  Date: Fri Sep 22 22:16:18 2017
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2017-05-27 (118 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=el_GR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: 
__spawnix: Assertion `ec >= 0' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-K D3
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  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/cups/+bug/1719004/+subscriptions

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

[Touch-packages] [Bug 1722178] Re: /usr/sbin/cupsd:cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.

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

** This bug has been marked a duplicate of bug 1719004
   cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: 
__spawnix: Assertion `ec >= 0' failed.

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

Title:
  /usr/sbin/cupsd:cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368:
  __spawnix: Assertion `ec >= 0' failed.

Status in cups package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups.  This problem was most recently seen with package version 2.2.4-7ubuntu2, 
the problem page at 
https://errors.ubuntu.com/problem/4fd1bde6959ac4c338d3ac6e9c2bcbbf78361e9f 
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/ubuntu/+source/cups/+bug/1722178/+subscriptions

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

[Touch-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo

2017-10-09 Thread Dik

So, it seems, that not all folk became the solution from
bugzilla.kernel.org. The bug is resolved since 05/2017

It's a firmware issue, that will not be fixed. The workaround is to
disable the Power Save mode of the device.

For further info, please read:
https://bugzilla.kernel.org/show_bug.cgi?id=93041

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1714596] Re: PDF images are blank

2017-10-09 Thread Leonidas S. Barbosa

I don't think poppler is the issue here, I've tested this in artful
with: evince 3.24.1-ubuntu2 and libpoppler68 0.57.0-2ubuntu2 and
couldn't reproduce this issue. https://imgur.com/a/YyDZD

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  1. Download a PDFs with images such as - 
  
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  
http://www.hopkinsmedicine.org/human_resources/_docs/employee_handbook_non-union_non-represented.pdf
  http://humanservices.arkansas.gov/dccece/classroom_docs/carseatsafety.pdf

  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

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

[Touch-packages] [Bug 1720331] Re: Whoopsie continually relaunching

2017-10-09 Thread James Henstridge

So I think I've got things sorted out by (a) switching to call
SetReportCrashes async to avoid blocking the UI, and (b) not calling
SetReportCrashes if we're asked to set it to the current (cached) value
of the property.

I've noticed that if whoopsie-preferences exits while the privacy panel
is open, I get a bit of a bounce when toggling the switch next.  This
seems to be due to whoopsie-preferences sending out a stray change
notification signal on start up:

method call time=1507538340.672978 sender=:1.1499 -> 
destination=com.ubuntu.WhoopsiePreferences serial=30 
path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; 
member=SetReportCrashes
   boolean false
signal time=1507538340.756225 sender=:1.1507 -> destination=(null 
destination) serial=9 path=/com/ubuntu/WhoopsiePreferences; 
interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
   string "com.ubuntu.WhoopsiePreferences"
   array [
  dict entry(
 string "ReportMetrics"
 variant boolean true
  )
  dict entry(
 string "ReportCrashes"
 variant boolean true
  )
   ]
   array [
   ]
method call time=1507538340.756590 sender=:1.1499 -> destination=:1.1507 
serial=31 path=/com/ubuntu/WhoopsiePreferences; 
interface=org.freedesktop.DBus.Properties; member=GetAll
   string "com.ubuntu.WhoopsiePreferences"
method call time=1507538340.757395 sender=:1.1499 -> 
destination=com.ubuntu.WhoopsiePreferences serial=32 
path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; 
member=SetReportCrashes
   boolean true
signal time=1507538341.034321 sender=:1.1507 -> destination=(null 
destination) serial=14 path=/com/ubuntu/WhoopsiePreferences; 
interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
   string "com.ubuntu.WhoopsiePreferences"
   array [
  dict entry(
 string "ReportCrashes"
 variant boolean false
  )
   ]
   array [
   ]
method call time=1507538341.035076 sender=:1.1499 -> destination=:1.1507 
serial=33 path=/com/ubuntu/WhoopsiePreferences; 
interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes
   boolean false

So essentially whoopsie-preferences is sending out an unsolicited
PropertiesChanged signal on startup with the initial values before
processing the SetReportCrashes method call.  Then gnome-control-center
responds by trying to match the switch state leading to the bounce.

So I guess I'll have to dive into the whoopsie-preferences code to see
if I can silence the stray signal.

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

Title:
  Whoopsie continually relaunching

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in whoopsie package in Ubuntu:
  Invalid

Bug description:
  Today for the first time, and coincidentally looking for a different
  setting, I went to the Settings->Privacy dialogue. I was also
  (coincidentally for a different reason, relating to #1720149) already
  tailing /var/log/syslog to a terminal.

  Immediately on opening that dialogue, the syslog tail flooded with
  whoopsie continually relaunching, causing enough work to raise the fan
  speeds. This is a representative section from towards the end of me
  letting it, before I killed the service, with some necessary
  viciousness. Specifically

  systemctl stop whoopsie
  (didn't stop it)
  systemctl disable whoopsie
  (didn't stop it)
  (find pid for whoopsie's root process and kill it)
  (that stopped it)

  Also for good measure ensured the automatic bug reporting option in
  the privacy settings dialog was set to manual, which I think was done
  anyway when I disabled whoopsie, though the dialog wasn't on top at
  the time for me to be sure. It had been set to automatic when I first
  opened the dialog.

  Snippet from syslog attached. It was just repeating this continually
  for several minutes before I stopped it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: whoopsie 0.2.58
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashReports:
   664:1000:119:0:2017-09-25 18:16:58.760134901 +0100:2017-09-25 
18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.upload
   640:1000:119:102847031:2017-09-27 20:28:45.352315425 +0100:2017-09-28 
09:02:32.195212507 +0100:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:119:34020328:2017-09-25 18:16:57.656132936 +0100:2017-09-25 
18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.crash
   600:111:119:0:2017-09-25 18:16:59.348145502

[Touch-packages] [Bug 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu

2017-10-09 Thread Pilot6

This DKMS package was never supposed to work on any other kernel but the
4.4.

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

Title:
  Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Since some Versions of Linux Kernel and Ubuntu Releases this problem
  exists.

  I am now running ubuntu 16.04 prerelease and still have the same
  problem.

  Bluetooth does not work with the atheros device on  msi gt 72 2qd
  notebook.

  WORKAROUND FOR [0CF3:3004] DEVICE ONLY with kernel 4.4:

  sudo apt install dkms
  wget 
https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542743-dkms_0.1_all.deb
  sudo dpkg -i btusb-lp1542743-dkms_0.1_all.deb

  FOR KERNEL 4.8 A WORKAROUND DKMS DEB IS

  https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files
  /btusb-lp1542743-dkms_0.2~4.8_all.deb

  dmesg | grep Bluetooth:
  [2.655360] Bluetooth: Core ver 2.21
  [2.655373] Bluetooth: HCI device and connection manager initialized
  [2.655377] Bluetooth: HCI socket layer initialized
  [2.655379] Bluetooth: L2CAP socket layer initialized
  [2.655385] Bluetooth: SCO socket layer initialized
  [6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.612794] Bluetooth: BNEP filters: protocol multicast
  [6.612798] Bluetooth: BNEP socket layer initialized
  [9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
  [9.016882] Bluetooth: Loading patch file failed

  hwinfo | grep Bluetooth:
  <6>[6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    <6>[6.612794] Bluetooth: BNEP filters: protocol multicast
    <6>[6.612798] Bluetooth: BNEP socket layer initialized
    <3>[9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
    <3>[9.016882] Bluetooth: Loading patch file failed
  60: USB 00.0: 11500 Bluetooth Device
    Model: "Atheros AR3012 Bluetooth 4.0"
    Device: usb 0x3004 "AR3012 Bluetooth 4.0"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.36-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  7 00:38:04 2016
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2015-10-24 (105 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. GT72 2QD
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=f7880b23-39b5-423a-bdbf-62b111783450 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-02-02 (4 days ago)
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10I
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10I:bd12/19/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QD:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QD
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:

  rfkill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no

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

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

[Touch-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo

2017-10-09 Thread Gabor Simon

The same here, "Error sending C_SCAN: enqueue_hcmd failed" and "BSM
uCode verification failed at addr" and all the other niceties, for this
good ol' piece of hw that have been working flawlessly under other OSes,
so it's definitely a sw issue.

I don't really hope for getting a solution, but anyway, won't hurt to
mention.

Additionally, if you let me comment on the issue policy here:

* this bug has been reported more than 2.5 years ago
* it affects several Ubuntu versions
* it affects a lot of users (more than 54, just not everybody registers for 
adding a 'meetoo')
* it makes the OS virtually unusable (i know, still can ping localhost, hooray)
* nobody has taken any steps to solve it, *not even asking a fine question*
* the ticket hasn't even been assigned to anyone
* and its importance is still 'LOW'

That last word 'LOW', my dear Sirs, is the exact quality of the support
here, not because of the lack of success solving the problem, but
because not even being interested in trying to.

Since this OS is free, I got exactly the worth for my money, so I don't 
complain,
but whenever I'll happen to need *paid* support for some company IT business, 
hell sure that it won't be Canonical whom I'll contact in the first 100 place.

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1722151] Re: Incorrect syntax when writing to ~/.pam_environment

2017-10-09 Thread Olivier Tilloy

This is misleading. The syntax for envfile is "VARIABLE=value" pairs,
whereas the syntax for user_envfile is that of pam_env.conf ("VARIABLE
[DEFAULT=[value]] [OVERRIDE=[value]]"). The documentation leaves to be
desired in that regard, but reading the code confirms that the two files
are parsed and interpreted in different manners.

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  While investigating bug #1662031, I found out that /usr/share
  /language-tools/save-to-pam-env writes to ~/.pam_environment using an
  incorrect syntax: "VARIABLE=value" on each line. The expected syntax
  is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: accountsservice 0.6.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 06:57:17 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (463 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago)

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

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

[Touch-packages] [Bug 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu

2017-10-09 Thread Adam Ryczkowski

The patch doesn't work for the 4.13 kernel from mainline ppa:

$ cat /var/lib/dkms/btusb-lp1542743/0.2~4.8/build/make.log
DKMS make.log for btusb-lp1542743-0.2~4.8 for kernel 4.13.0-041300-generic 
(x86_64)
pon, 9 paź 2017, 13:00:15 CEST
make: Entering directory '/usr/src/linux-headers-4.13.0-041300-generic'
  AR  /var/lib/dkms/btusb-lp1542743/0.2~4.8/build/built-in.o
  CC [M]  /var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.o
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c: In function 
‘inject_cmd_complete’:
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c:1825:2: warning: 
dereferencing ‘void *’ pointer
  *skb_put(skb, 1) = 0x00;
  ^
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c:1825:2: error: invalid use 
of void expression
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c: In function 
‘alloc_diag_urb’:
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c:2697:2: warning: 
dereferencing ‘void *’ pointer
  *skb_put(skb, 1) = 0xf0;
  ^
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c:2697:2: error: invalid use 
of void expression
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c:2698:2: warning: 
dereferencing ‘void *’ pointer
  *skb_put(skb, 1) = enable;
  ^
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c:2698:2: error: invalid use 
of void expression
scripts/Makefile.build:308: recipe for target 
'/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.o' failed
make[1]: *** [/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.o] Error 1
Makefile:1512: recipe for target 
'_module_/var/lib/dkms/btusb-lp1542743/0.2~4.8/build' failed
make: *** [_module_/var/lib/dkms/btusb-lp1542743/0.2~4.8/build] Error 2
make: Leaving directory '/usr/src/linux-headers-4.13.0-041300-generic'

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

Title:
  Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Since some Versions of Linux Kernel and Ubuntu Releases this problem
  exists.

  I am now running ubuntu 16.04 prerelease and still have the same
  problem.

  Bluetooth does not work with the atheros device on  msi gt 72 2qd
  notebook.

  WORKAROUND FOR [0CF3:3004] DEVICE ONLY with kernel 4.4:

  sudo apt install dkms
  wget 
https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542743-dkms_0.1_all.deb
  sudo dpkg -i btusb-lp1542743-dkms_0.1_all.deb

  FOR KERNEL 4.8 A WORKAROUND DKMS DEB IS

  https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files
  /btusb-lp1542743-dkms_0.2~4.8_all.deb

  dmesg | grep Bluetooth:
  [2.655360] Bluetooth: Core ver 2.21
  [2.655373] Bluetooth: HCI device and connection manager initialized
  [2.655377] Bluetooth: HCI socket layer initialized
  [2.655379] Bluetooth: L2CAP socket layer initialized
  [2.655385] Bluetooth: SCO socket layer initialized
  [6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.612794] Bluetooth: BNEP filters: protocol multicast
  [6.612798] Bluetooth: BNEP socket layer initialized
  [9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
  [9.016882] Bluetooth: Loading patch file failed

  hwinfo | grep Bluetooth:
  <6>[6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    <6>[6.612794] Bluetooth: BNEP filters: protocol multicast
    <6>[6.612798] Bluetooth: BNEP socket layer initialized
    <3>[9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
    <3>[9.016882] Bluetooth: Loading patch file failed
  60: USB 00.0: 11500 Bluetooth Device
    Model: "Atheros AR3012 Bluetooth 4.0"
    Device: usb 0x3004 "AR3012 Bluetooth 4.0"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.36-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  7 00:38:04 2016
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2015-10-24 (105 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. GT72 2QD
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=f7880b23-39b5-423a-bdbf-62b111783450 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-02-02 (4 days ago)
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10I
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10

[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  New

Bug description:
  Hi there, 
  we found a replicable issue that involves the Ubuntu Core networking and 
causes complete loss of connectivity. 
  We run a custom board with ubuntu core: the architecure is amrhf.
  We replicated this issue with an official Ubuntu Core image on a Raspberry 
Pi: other platform was been tested.
  It shows that it is a snap core problem which interests networkd: we use the 
default network stack based on networkd + netplan.

  Below steps to replicate the issue.

  1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes).
  2)Boot the board and wait for get an ip from dhcp server
  3)Before the lease expires, set a reservation for a different ip address

  Depending on lease duration before the lease expires( for 10 minute we have 2 
minutes before ), networkd configure the new address in addition to the 
previous one.
  When the lease expire both ip address ( the prevoius and the new one ) 
disappear from the interested network interface.
  Depending on lease duration before the second lease expires ( for 10 minure 
we have 2 minutes before ) networkd configure only the new ip address on the 
network interface and the ping toward an outside host work properly.

  During the test the dhcp server records correctly leases and their
  duration.

  We check directly from console the network interface setting with the
  tool ip, checking continuously the value for ip address and valid_lft
  fields for the interested network interface.

  Please note that if the ip address setting are the same between leases
  the problem doesn’t jump out.

  Please note that if the ip address setting are different between lease
  the problem jumps out and it is very bad:

  Typically the lease time on consumer router are about some day, then a
  board that change ip between lease loses the network connectivity for
  some day without a direct action.

  Please, after a confirmation from your side of the issue, could you
  fix the problem or escalate the issue at the upstream project?

  We are available for further testing.

  Below syslog annotated with ip address state:

  
  Oct  4 09:48:06 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:49:36 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:49:25 localhost systemd-timesyncd[996]: Network configuration 
changed, trying to establish connection.
  Oct  4 09:49:26 localhost systemd-timesyncd[996]: Synchronized to time server 
91.189.89.199:123 (ntp.ubuntu.com).
  Oct  4 09:49:26 localhost systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Oct  4 09:49:26 localhost systemd[1]: Started Update resolvconf for networkd 
DNS.
  Oct  4 09:49:37 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:51:07 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:51:09 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:52:39 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:52:40 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:54:10 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:54:11 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:55:41 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:54:23 localhost systemd-timesyncd[996]: Network configuration 
changed, trying to establish connection.
  Oct  4 09:54:23 localhost systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Oct  4 09:54:23 localhost systemd-timesyncd[996]: Synchronized to time server 
91.189.89.199:123 (ntp.ubuntu.com).
  Oct  4 09:54:23 localhost systemd[1]: Started Update resolvconf for networkd 
DNS.
  Oct  4 09:55:43 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:57:13 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:57:14 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 09:58:44 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 09:58:46 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4 10:00:16 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Oct  4 10:00:17 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Wed Oct  4

[Touch-packages] [Bug 1720754] Re: rhythmbox doesn't show up headerbar in ubuntu session

** Branch linked: lp:~ubuntu-desktop/gnome-session/ubuntu

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

Title:
  rhythmbox doesn't show up headerbar in ubuntu session

Status in glib2.0 package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New

Bug description:
  No headerbar plugin extension enabled despite for it being the default
  in rhythmbox. This is due to the per-session override not working for
  the way rhythmbox access the value.

  We need to reset it as well for people who already installed the beta
  or before and upgrading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1720754/+subscriptions

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

[Touch-packages] [Bug 1722151] Re: Incorrect syntax when writing to ~/.pam_environment

2017-10-09 Thread Gunnar Hjalmarsson

Hmm.. I just noticed this in "man pam_env":

"By default rules for (un)setting of variables is taken from the config
file /etc/security/pam_env.conf if no other file is specified.

This module can also parse a file with simple KEY=VAL pairs on separate
lines (/etc/environment by default)."

Doesn't that mean that the simple "KEY=VAL" syntax is documented after
all?

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  While investigating bug #1662031, I found out that /usr/share
  /language-tools/save-to-pam-env writes to ~/.pam_environment using an
  incorrect syntax: "VARIABLE=value" on each line. The expected syntax
  is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: accountsservice 0.6.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 06:57:17 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (463 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago)

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

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

[Touch-packages] [Bug 1718890] Re: name resolution stops working

2017-10-09 Thread Wolf Rogner

To make clear the bearing of this:

systemd-resolved stops working on EVERY machine here after 5 minutes.

the DNS server has not been down since April

A Macintosh running macOS High Sierra installed for comparison can
resolve and connect to internal resources in every case where Ubuntu
looses connection.

And a last one: internally, my domain uses .internal as domain name. I
want to keep this separate from my official domains.

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

Title:
name resolution stops working

Status in systemd package in Ubuntu:
New

Bug description:
System: Ubuntu 17.10 beta
DNS server hosts an internal and an external domain (the internal is used for
internal purposes).

Name resolution works for a while. Every now and then, the name resolution
stops working.
This issue was reported in 17.04 but no suggestion for resolv has worked.

In 17.10 the symptoms are the same, the duration till it happens are
longer (about 1.5 days).

restarting systemd-resolved solves the issue temporarily. However,
this should not be required at all.

Happens on a fresh install

Setup:

DNS serves rsb.at and rsb.intern
Server www.rsb.at can be reached even when internal resolution fails.
Seems that the internal DNS server (the first in the line) is not queried
first.
If so, an rsb.intern address will not be found.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu10
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 22 11:05:57 2017
InstallationDate: Installed on 2017-09-05 (16 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
Lsusb:
Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro12,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2017
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0167.B33.1706181928
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
mtime.conffile..etc.systemd.resolved.conf: 2017-09-06T23:14:52.682864

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

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

[Touch-packages] [Bug 1718890] Re: name resolution stops working

2017-10-09 Thread Wolf Rogner

Just found this article
https://github.com/systemd/systemd/issues/5755

Following the argument, systemd-resolved resolves DNS names on the
assumption that all configured DNS servers are equal.

diego-treitos and others argue that in small/medium sized companies, DNS
configuration will have an external DNS server configured and conveyed
via DHCP.

This is the case here as well.

This has not posed a problem before systemd-resolved was adopted. But
when a resolver insists on treating the fallback equally and keeping the
connection till the next fallback, internal DNS resolution is not
possible any more.

It breaks known and established configurations.

I have to accept that RFCs actually lend to the interpretation of
poettering.

In this case (as he is reluctant to adapt his softwares behaviour to
previously known standards) there need to be a quick way to eliminate
systemd-resolver from the system.

I for one need the old behaviour with a primary DNS (internal, it
resolved private addresses as well) and a secondary DNS (external, which
only resolved external / official addresses) as a fallback.

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

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

Title:
name resolution stops working

Status in systemd package in Ubuntu:
New

Bug description:
System: Ubuntu 17.10 beta
DNS server hosts an internal and an external domain (the internal is used for
internal purposes).

Name resolution works for a while. Every now and then, the name resolution
stops working.
This issue was reported in 17.04 but no suggestion for resolv has worked.

In 17.10 the symptoms are the same, the duration till it happens are
longer (about 1.5 days).

restarting systemd-resolved solves the issue temporarily. However,
this should not be required at all.

Happens on a fresh install

Setup:

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

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

[Touch-packages] [Bug 1722193] [NEW] very slow

2017-10-09 Thread chitra

Public bug reported:

Hi,
I am simply a user. Nothing more that I know. This program is going slow these 
days. Do not know why?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Oct  9 14:59:51 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3978]
InstallationDate: Installed on 2016-08-09 (426 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20237
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic.efi.signed 
root=UUID=06512fc0-2431-4471-a15b-992ab0d72fd5 ro plymouth:debug=1=1=1 quiet 
splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/23/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 79CN46WW(V3.05)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G410
dmi.modalias: 
dmi:bvnLENOVO:bvr79CN46WW(V3.05):bd12/23/2013:svnLENOVO:pn20237:pvrLenovoG410:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG410:
dmi.product.name: 20237
dmi.product.version: Lenovo G410
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Oct  9 11:06:58 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   17740 
 vendor SEC
xserver.version: 2:1.18.4-0ubuntu0.4

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


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

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

Title:
  very slow

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,
  I am simply a user. Nothing more that I know. This program is going slow 
these days. Do not know why?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct  9 14:59:51 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3978]
  InstallationDate: Installed on 2016-08-09 (426 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20237
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic.efi.signed 
root=UUID=06512fc0-2431-4471-a15b-992ab0d72fd5 ro plymouth:debug=1=1=1 quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79CN46WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version:

[Touch-packages] [Bug 1714596] Re: PDF images are blank

2017-10-09 Thread Nick Moffitt

This bug makes the PDF viewer all but useless in artful.  Can we hope to
see a bug fix before release?

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  1. Download a PDFs with images such as - 
  
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  
http://www.hopkinsmedicine.org/human_resources/_docs/employee_handbook_non-union_non-represented.pdf
  http://humanservices.arkansas.gov/dccece/classroom_docs/carseatsafety.pdf

  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

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

[Touch-packages] [Bug 977750] Re: package-data-downloader crashed with ValueError in command(): invalid literal for int() with base 10: ''

2017-10-09 Thread snoop foo

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

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

Title:
  package-data-downloader crashed with ValueError in command(): invalid
  literal for int() with base 10: ''

Status in Debconf:
  New
Status in debconf package in Ubuntu:
  New

Bug description:
  "as usual", crash message appearing at logon

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: update-notifier-common 0.119ubuntu5
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 10 07:53:20 2012
  ExecutablePath: /usr/lib/update-notifier/package-data-downloader
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120316)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/lib/update-notifier/package-data-downloader
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   SHELL=/bin/sh
  PythonArgs: ['/usr/lib/update-notifier/package-data-downloader']
  SourcePackage: update-notifier
  Title: package-data-downloader crashed with ValueError in command(): invalid 
literal for int() with base 10: ''
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1722151] Re: Incorrect syntax when writing to ~/.pam_environment

2017-10-09 Thread Olivier Tilloy

When adding the "debug" parameter to the invokation of pam_env in
/etc/pam.d/gdm-password, I'm seeing the following in journalctl:

oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
pam_putenv("PATH=/usr/local/sbin:/usr/local/bin:/usr/
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
pam_putenv("LANG=en_US.UTF-8")
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
pam_putenv("LC_NUMERIC=es_ES.UTF-8")
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
pam_putenv("LC_TIME=es_ES.UTF-8")
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
pam_putenv("LC_MONETARY=es_ES.UTF-8")
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
pam_putenv("LC_PAPER=es_ES.UTF-8")
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
pam_putenv("LC_NAME=es_ES.UTF-8")
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
pam_putenv("LC_ADDRESS=es_ES.UTF-8")
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
pam_putenv("LC_TELEPHONE=es_ES.UTF-8")
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
pam_putenv("LC_MEASUREMENT=es_ES.UTF-8")
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
pam_putenv("LC_IDENTIFICATION=es_ES.UTF-8")
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
pam_putenv("LANGUAGE=en_US")
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
remove variable "LANGUAGE=fr_FR:en_GB:en"
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
remove variable "LANG=fr_FR.UTF-8"
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
remove variable "LC_NUMERIC=es_ES.UTF-8"
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
remove variable "LC_TIME=es_ES.UTF-8"
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
remove variable "LC_MONETARY=es_ES.UTF-8"
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
remove variable "LC_PAPER=es_ES.UTF-8"
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
remove variable "LC_NAME=es_ES.UTF-8"
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
remove variable "LC_ADDRESS=es_ES.UTF-8"
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
remove variable "LC_TELEPHONE=es_ES.UTF-8"
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
remove variable "LC_MEASUREMENT=es_ES.UTF-8"
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
remove variable "LC_IDENTIFICATION=es_ES.UTF-8"
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session): 
remove variable "PAPERSIZE=a4"
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_unix(gdm-password:session): 
session opened for user ubuntu by (uid=0)

The code for the _undefine_var() function in pam-env.c 
(https://github.com/linux-pam/linux-pam/blob/master/modules/pam_env/pam_env.c#L738)
 calls pam_putenv(pamh, var->name), and this happens to work because var->name 
== "NAME=value", which is the first token on the line.
This is working, but really by accident, and if in the future pam's parser for 
conf files becomes stricter, this will cease to work. I think we should 
consider complying better with the documented way of setting variable values 
(and we should update the documentation, too).

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  While investigating bug #1662031, I found out that /usr/share
  /language-tools/save-to-pam-env writes to ~/.pam_environment using an
  incorrect syntax: "VARIABLE=value" on each line. The expected syntax
  is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: accountsservice 0.6.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 06:57:17 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (463 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago)

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

-- 
Mailing

[Touch-packages] [Bug 1722178] [NEW] /usr/sbin/cupsd:cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.

2017-10-09 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups.  This problem was most recently seen with package version 2.2.4-7ubuntu2, 
the problem page at 
https://errors.ubuntu.com/problem/4fd1bde6959ac4c338d3ac6e9c2bcbbf78361e9f 
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/.

** Affects: cups (Ubuntu)
 Importance: High
 Assignee: Till Kamppeter (till-kamppeter)
 Status: New


** Tags: artful kylin-17.10

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

Title:
  /usr/sbin/cupsd:cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368:
  __spawnix: Assertion `ec >= 0' failed.

Status in cups package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups.  This problem was most recently seen with package version 2.2.4-7ubuntu2, 
the problem page at 
https://errors.ubuntu.com/problem/4fd1bde6959ac4c338d3ac6e9c2bcbbf78361e9f 
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/ubuntu/+source/cups/+bug/1722178/+subscriptions

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

[Touch-packages] [Bug 1722178] Re: /usr/sbin/cupsd:cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.

2017-10-09 Thread Sebastien Bacher

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

** Changed in: cups (Ubuntu)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  /usr/sbin/cupsd:cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368:
  __spawnix: Assertion `ec >= 0' failed.

Status in cups package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups.  This problem was most recently seen with package version 2.2.4-7ubuntu2, 
the problem page at 
https://errors.ubuntu.com/problem/4fd1bde6959ac4c338d3ac6e9c2bcbbf78361e9f 
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/ubuntu/+source/cups/+bug/1722178/+subscriptions

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

[Touch-packages] [Bug 1720861] Re: package python-minimal 2.7.13-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1