date:20190322

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

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

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

Title:
  package udev 239-7ubuntu10.6 failed to install/upgrade: installed udev
  package post-installation script subprocess returned error exit status
  1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  udev failed to upgrade during the upgrade from 18.04.1 LTS to 18.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.6
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CustomUdevRuleFiles: 70-snap.core.rules 70-snap.vlc.rules 
70-snap.spotify.rules 70-snap.brave.rules
  Date: Sun Feb  3 15:49:53 2019
  DuplicateSignature:
   package:udev:239-7ubuntu10.6
   Installing new version of config file /etc/udev/udev.conf ...
   The group `kvm' already exists and is not a system group. Exiting.
   dpkg: error processing package udev (--configure):
installed udev package post-installation script subprocess returned error 
exit status 1
  ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-07-29 (189 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS13 9333
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: systemd
  Title: package udev 239-7ubuntu10.6 failed to install/upgrade: installed udev 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to cosmic on 2019-02-03 (0 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment

2019-03-22 Thread Bug Watch Updater

** Changed in: policykit-1
   Status: Unknown => New

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in policykit-1 package in Ubuntu:
  New

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions

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

[Touch-packages] [Bug 1820953] Re: 19.04 hidden wifi - unable to connect to network following 18.10's page

The documentation is wrong. There are three dots in the Wi-Fi settings
menu near the close, minimize, maximize buttons. If you click that the
"Connect to Hidden network" option is revealed.

** Package changed: wireless-tools (Ubuntu) => ubuntu-docs

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

Title:
  19.04 hidden wifi - unable to connect to network following 18.10's
  page

Status in Ubuntu Documentation:
  New

Bug description:
  Ubuntu 19.04 QA-test (daily live)
  Note: this is not a software issue.

  When it comes to wifi - I'm equal to an idiot.

  I tried to follow 
https://help.ubuntu.com/stable/ubuntu-help/net-wireless-hidden.html.en
  but I could not find any "Connect to Hidden Wifi" option following 
instructions.

  I did this first on a sony ultrabook & failed, now on a thinkpad sl510.
  Problem I believe is either 19.04 doesn't match docs, or idiot-at-keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wireless-tools 30~pre9-13ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 20 06:36:54 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190318)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wireless-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1810840] Re: whoopsie can't remember "always report" setting

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

** This bug has been marked a duplicate of bug 1809247
   SetReportCrashes to true dbus call failed

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

Title:
  whoopsie can't remember "always report" setting

Status in whoopsie-preferences package in Ubuntu:
  Confirmed

Bug description:
  After ticking the checkbox for whoopsie to automatically always send
  crash reports, I get the following error dialog (screenshot attached):

  *Can't remember send report status settings*
  Saving crash report state failed. Can't set auto or never reporting mode.
  Command '['/usr/bin/gdbus', 'call', '-y', '-d', 
'com.ubuntu.WhoopsiePreferences', '-o', '/com/ubuntu/WhoopsiePreferences', 
'-m', 'com.ubuntu.WhoopsiePreferences.SetReportCrashes', 'true']' returned
  non-zero exit status 1.

  I'm pretty sure this error happens because whoopsie-preferences was not 
installed; afterwards I installed whoopsie-preferences and manually ran in a 
terminal:
  $ /usr/bin/gdbus call -y -d com.ubuntu.WhoopsiePreferences -o 
/com/ubuntu/WhoopsiePreferences -m 
com.ubuntu.WhoopsiePreferences.SetReportCrashes true

  and got a return value of () but no errors or warnings.

  This computer was freshly-installed with Xubuntu 18.04 less than 2
  weeks ago... I've kept a record of everything I changed since then,
  and I've only removed five packages (sgt-puzzles, gnome-sudoku, gnome-
  mines, pidgin, mousepad).  If whoopsie-preferences is not included in
  a fresh install of (X)ubuntu, then perhaps it should be; in any case,
  if it isn't installed then the checkbox for making crash reporting
  automatic should not be visible.

  
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  $ apt-cache policy whoopsie
  whoopsie:
Installed: 0.2.62
Candidate: 0.2.62
Version table:
   *** 0.2.62 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy whoopsie-preferences 
  whoopsie-preferences:
Installed: (none)
Candidate: 0.19
Version table:
   0.19 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Touch-packages] [Bug 1821364] Re: xfce4 install on Ubuntu 18.04 has no polkit agent

2019-03-22 Thread Seth Arnold

** Package changed: dbus (Ubuntu) => xfce4 (Ubuntu)

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

Title:
  xfce4 install on Ubuntu 18.04 has no polkit agent

Status in xfce4 package in Ubuntu:
  New

Bug description:
  The problem was evident as en error message when trying run 'Language
  Support' (gnome-language-selector) after install. (This was the
  advised way to get the Atom spell-checker working).

  Error described here: https://askubuntu.com/questions/1031319
  /language-support-in-18-04-not-working-org-freedesktop-policykiterror-
  failed/1127862#1127862

  It occurred on a fresh install of Ubuntu 18.04 after installing xfce4.

  No PolicyKit Authentication Agent was installed - or at least not one
  that xfce seemed to recognise.

  I solved the problem by installing one:

  $ sudo apt install policykit-1-gnome

  That installed the package: /usr/lib/policykit-1-gnome/polkit-gnome-
  authentication-agent-1.

  It seemed to update the autostart list.

  Though there is such a thing as 'xfce-polkit' and 'xfce-polkit-git', I
  could not see them on my machine and Debian [reports][3], in it's
  account of the package policykit-1-gnome, that xfce still uses the
  gnome polkit agent:

  "This implementation was originally designed for GNOME 2, but most
  GNOME-based desktop environments, including GNOME 3, GNOME Flashback,
  and MATE, have their own built-in PolicyKit agents and no longer use
  this one. The remaining users of this implementation are Cinnamon,
  XFCE and Unity."

  (https://packages.debian.org/sid/policykit-1-gnome)

  It is worth noting that the terminal emulator that comes default in
  Ubuntu and is still default after installing xfce (gnome terminal)
  would not run polkit-gnome-authentication-agent-1 after install. I
  understand it may have been necessary, perhaps ironically, to run it
  an an xterm. I didn't attempt this. But all was well after restart.

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

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

[Touch-packages] [Bug 1821415] [NEW] pkexec fails in a non-graphical environment

Public bug reported:

The plymouth apport source package hooks wants to gather log files as
the root user and apport provides a policy kit policy for collecting
that information. This works fine in a graphical environment but not in
a non-graphical one.

ubuntu@disco:~$ ubuntu-bug plymouth

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
Authentication is required to collect system information for this problem report
Authenticating as: Ubuntu (ubuntu)
Password: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
 AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.

Subsequently, bug reports from servers will contain less information.

** Affects: policykit-1
 Importance: Unknown
 Status: Unknown

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: cosmic disco rls-dd-incoming

** Bug watch added: gitlab.freedesktop.org/polkit/polkit/issues #17
   https://gitlab.freedesktop.org/polkit/polkit/issues/17

** Also affects: policykit-1 via
   https://gitlab.freedesktop.org/polkit/polkit/issues/17
   Importance: Unknown
   Status: Unknown

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  Unknown
Status in policykit-1 package in Ubuntu:
  New

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions

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

[Touch-packages] [Bug 1819728] Re: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18)

The bionic version of this systemd update was used on an Ubuntu 18.04
system that ran the full spread test suite (>300 tests). There are
hundreds of mount units created, started, stopped and a bunch of system
services created and removed and tons of daemon-reloads. No systemd
related issues where found.

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

Title:
  Please backport "fix race between daemon-reload and other commands
  #8803" to 16.04 (for UC16) and 18.04 (for UC18)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  On Ubuntu Core we recently hit the a race in daemon-reload and systemctl 
twice. This race is fixed in systemd upstream: "fix race between daemon-reload 
and other commands #8803" and a subsequent fix in "PR#11121".

  Note that this is a general problem in systemd with daemon-reload and
  systemctl commands, we just happen to hit it more often on Ubuntu Core
  but the test-case below explodes just fine on a normal Ubuntu release
  like 16.04 or 18.04 (not on 18.10+ as its fixed there).

  [TEST CASE]
  To reproduce its enough to run:

  for i in $(seq 50); do
    systemctl daemon-reload &
    systemctl start ssh &
  done

  This will result in "systemctl start ssh" hanging in ppoll. With the
  patch applied the hangs go away.

  [REGRESSION POTENTIAL]
  Medium/High, this change is already in the systemd upstream and in use disco 
and later but the backport required some manual resolving of conflicts the code 
because changed between 229,237 and the fixed code in 240. Its also
  not fully clear if the fix relies on the new systemd "coldplug" functionality 
that was added in more recent git revisions.

  The upstream fix is https://github.com/systemd/systemd/pull/8803 and
  https://github.com/systemd/systemd/pull/11121

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

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

[Touch-packages] [Bug 1821101] Re: unattended-upgrades: Fall back to adjusting more packages' candidates when a package from an allowed origin can't be marked to install/upgrade

This bug was fixed in the package unattended-upgrades - 1.10ubuntu2

---
unattended-upgrades (1.10ubuntu2) disco; urgency=medium

  * Compare apt.package.Version objects and not the versions' string
representation. (LP: #1820888)
This prevented adjusting candidates when the strings sorted differently.
Also extend tests to catch issue.
  * Fall back to adjusting more packages' candidates
when a package from an allowed origin can't be marked to install/upgrade.
(LP: #1821101)
  * Skip sending email when no package had to be installed, upgraded or removed
(LP: #1821103) (Closes: #924554)

 -- Balint Reczey   Fri, 22 Mar 2019 20:42:08 +0100

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

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

Title:
  unattended-upgrades: Fall back to adjusting more packages' candidates
  when a package from an allowed origin can't be marked to
  install/upgrade

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  .

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

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

[Touch-packages] [Bug 1820888] Re: unattended-upgrades may hold back upgrades due to comparing package versions by their string representation

This bug was fixed in the package unattended-upgrades - 1.10ubuntu2

---
unattended-upgrades (1.10ubuntu2) disco; urgency=medium

  * Compare apt.package.Version objects and not the versions' string
representation. (LP: #1820888)
This prevented adjusting candidates when the strings sorted differently.
Also extend tests to catch issue.
  * Fall back to adjusting more packages' candidates
when a package from an allowed origin can't be marked to install/upgrade.
(LP: #1821101)
  * Skip sending email when no package had to be installed, upgraded or removed
(LP: #1821103) (Closes: #924554)

 -- Balint Reczey   Fri, 22 Mar 2019 20:42:08 +0100

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

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

Title:
  unattended-upgrades may hold back upgrades due to comparing package
  versions by their string representation

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  This is part of the reason why the autopkgtes installing all security updates 
is failing for cosmic with 1.10ubuntu1:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz
  ...
  Checking: libnss-systemd ([])
  pkg libsystemd0 not in allowed origin
  sanity check failed
  ...

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

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

[Touch-packages] [Bug 1821103] Re: [SRU] Skip sending email when no package had to be installed, upgraded or removed

This bug was fixed in the package unattended-upgrades - 1.10ubuntu2

---
unattended-upgrades (1.10ubuntu2) disco; urgency=medium

  * Compare apt.package.Version objects and not the versions' string
representation. (LP: #1820888)
This prevented adjusting candidates when the strings sorted differently.
Also extend tests to catch issue.
  * Fall back to adjusting more packages' candidates
when a package from an allowed origin can't be marked to install/upgrade.
(LP: #1821101)
  * Skip sending email when no package had to be installed, upgraded or removed
(LP: #1821103) (Closes: #924554)

 -- Balint Reczey   Fri, 22 Mar 2019 20:42:08 +0100

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

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

Title:
  [SRU] Skip sending email when no package had to be installed, upgraded
  or removed

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Committed

Bug description:
  .

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

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

[Touch-packages] [Bug 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication

2019-03-22 Thread Till Kamppeter

By the way, if there is one SRU package to fix several separately
reported bugs, each of these bugs should link to the others, so that a
single bug cannot cause the removal of the SRU even if it gets verified
in the other bugs. Or the SRU package needs one "master bug" where the
verification gets handled.

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

Title:
  NetworkManager does not support AES-encrypted private keys for WPA
  802.1x authentication

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Selecting AES-{192,256}-CBC keys to connect isn't working

  * Test case

  1. Start with a working (cleartext or DES-3) private key/cert for a network.  
Set up a connection and verify that everything works.
  2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in 
working-key.pem -out aes-key.pem -aes256" (the output should have a line 
starting with "DEK-Info: AES-256-CBC,")
  3. Delete the settings for the test network and attempt to reconnect using 
the new key. 

  That should work

  * Regression potential

  That's new code for an extra type of keys, it shouldn't impact
  existing options

  --

  NetworkManager does not appear to support private keys encrypted with
  AES.  At the very least, it will not validate such a key in nm-util
  when setting up a WPA 802.1x TLS wifi connection.

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

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

[Touch-packages] [Bug 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication

2019-03-22 Thread Till Kamppeter

The SRU bug 1809132 has the same proposed package as this one and it got
marked verified after three months without complaints and also after
some testing by me and in agreement with Ken VanDine, Will Cooke,
Olivier Tilloy.

So at least the new network-manager version should not cause any
regressions.

So I mark this bug as verified, too and remove the removal-candidate
tag.

Feel free to mark this bug as duplicate of bug 1809132 or as Invalid,
but please DO NOT remove the network-manager 1.10.14-0ubuntu1 package as
it is already a verified SRU for bug 1809132.

** Tags removed: removal-candidate verification-needed 
verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  NetworkManager does not support AES-encrypted private keys for WPA
  802.1x authentication

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Selecting AES-{192,256}-CBC keys to connect isn't working

  * Test case

  1. Start with a working (cleartext or DES-3) private key/cert for a network.  
Set up a connection and verify that everything works.
  2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in 
working-key.pem -out aes-key.pem -aes256" (the output should have a line 
starting with "DEK-Info: AES-256-CBC,")
  3. Delete the settings for the test network and attempt to reconnect using 
the new key. 

  That should work

  * Regression potential

  That's new code for an extra type of keys, it shouldn't impact
  existing options

  --

  NetworkManager does not appear to support private keys encrypted with
  AES.  At the very least, it will not validate such a key in nm-util
  when setting up a WPA 802.1x TLS wifi connection.

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

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

[Touch-packages] [Bug 1495580] Re: chfn needs to learn about the --extrausers argument and use libnss-extrausers files when set

** Also affects: shadow (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: shadow (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  chfn needs to learn about the --extrausers argument and use libnss-
  extrausers files when set

Status in Snappy:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Confirmed
Status in shadow source package in Bionic:
  Fix Released

Bug description:
  as seen in bug 1492327, adduser now works for creating users in the
  extrausers db but when it tries to update the GECOS field at the end
  of adding a user (interactively and noninteractively) chfn falls over
  ...

  chfn needs similar patches to the other shadow binaries that recently
  got extrausers support.

  TEST CASE:
  - create a user "foo" on an Ubuntu Core system
  - run "chfn --extrausers -f some-name foo" on an Ubuntu Core system

  REGRESSION POTENTIAL:
  - low: this requires the new (and optional) --extrausers switch to change 
anything.

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

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

[Touch-packages] [Bug 1819969] Re: gdb-multiarch does not include RISC-V architecture

** Tags added: rls-dd-incoming

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

Title:
  gdb-multiarch does not include RISC-V architecture

Status in gdb package in Ubuntu:
  New

Bug description:
  This issue was recently fixed in Debian, but seems to have not been
  pulled into Ubuntu: https://salsa.debian.org/gdb-
  team/gdb/commit/e59e4e54af0fbe9086c40ab80a1000d5c50c7175

  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  gdb-multiarch:
Installed: 8.2.90-0ubuntu1
Candidate: 8.2.90-0ubuntu1
Version table:
   *** 8.2.90-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 794757] Re: Mysterious "System program problem detected" prompt

** Changed in: update-notifier (Ubuntu)
 Assignee: Evan (ev) => (unassigned)

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

** Tags added: rls-ee-incoming

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

Title:
  Mysterious "System program problem detected" prompt

Status in apport package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apport

  A unsolicited, untitled window recently appeared that contained only
  the following text:

  System program problem detected
  Do you want to report the problem now?

  [ Cancel ] [ Report problem... ]

  There are two problems with this:

  1) I have no idea what "system program problem" this is referring to,
  so I have no way of knowing yet whether or not I want to report it. My
  only rational option is to choose "Cancel."

  2) I have no indication of what program is generating this prompt.
  Since it reappeared again later, though, I gave in to curiosity and
  clicked "Report problem," hoping that it might reveal more information
  about the "system program problem." Instead of more information,
  however, I was presented with a password prompt. I am NOT going to
  grant administrative privileges to an unidentified program. Once
  again, my only rational option is to choose "Cancel."

  Users at Ask Ubuntu [1] helped me identify the mystery prompt as
  belonging to Apport.

  Apport needs to identify itself before requesting elevated privileges.

  [1] http://askubuntu.com/questions/47675/why-should-i-trust-this

  

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: apport 1.20.1-0ubuntu5
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  ApportLog:
   ERROR: apport (pid 13522) Tue Jun  7 10:13:17 2011: called for pid 12778, 
signal 11
   ERROR: apport (pid 13522) Tue Jun  7 10:13:17 2011: executable: 
/usr/bin/Xorg (command line "/usr/bin/X :0 -auth /var/run/lightdm/authority/0 
-nolisten tcp vt2")
   ERROR: apport (pid 13522) Tue Jun  7 10:13:18 2011: wrote report 
/var/crash/_usr_bin_Xorg.0.crash
  Architecture: amd64
  CrashReports:
   600:1000:1000:546955:2011-06-07 11:51:12.50130 -0700:2011-06-07 
11:51:13.50130 -0700:/var/crash/_usr_bin_update-notifier.1000.crash
   600:0:0:635299:2011-06-07 10:13:18.563455402 -0700:2011-06-07 
10:13:17.292818549 -0700:/var/crash/_usr_bin_Xorg.0.crash
   600:1000:1000:232476:2011-06-05 21:03:36.352573000 -0700:2011-06-05 
21:03:37.352573000 
-0700:/var/crash/_usr_lib_telepathy_telepathy-salut.1000.crash
  Date: Wed Jun  8 13:30:15 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1495580] Re: chfn needs to learn about the --extrausers argument and use libnss-extrausers files when set

** Description changed:

  as seen in bug 1492327, adduser now works for creating users in the
  extrausers db but when it tries to update the GECOS field at the end of
  adding a user (interactively and noninteractively) chfn falls over ...
  
  chfn needs similar patches to the other shadow binaries that recently
  got extrausers support.
+ 
+ REGRESSION POTENTIAL:
+ - low: this requires the new (and optional) --extrausers switch to change 
anything.

** Description changed:

  as seen in bug 1492327, adduser now works for creating users in the
  extrausers db but when it tries to update the GECOS field at the end of
  adding a user (interactively and noninteractively) chfn falls over ...
  
  chfn needs similar patches to the other shadow binaries that recently
  got extrausers support.
  
+ TEST CASE:
+ - create a user "foo" on an Ubuntu Core system
+ - run "chfn --extrausers -f some-name foo" on an Ubuntu Core system
+ 
  REGRESSION POTENTIAL:
  - low: this requires the new (and optional) --extrausers switch to change 
anything.

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

Title:
  chfn needs to learn about the --extrausers argument and use libnss-
  extrausers files when set

Status in Snappy:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Confirmed
Status in shadow source package in Bionic:
  Fix Released

Bug description:
  as seen in bug 1492327, adduser now works for creating users in the
  extrausers db but when it tries to update the GECOS field at the end
  of adding a user (interactively and noninteractively) chfn falls over
  ...

  chfn needs similar patches to the other shadow binaries that recently
  got extrausers support.

  TEST CASE:
  - create a user "foo" on an Ubuntu Core system
  - run "chfn --extrausers -f some-name foo" on an Ubuntu Core system

  REGRESSION POTENTIAL:
  - low: this requires the new (and optional) --extrausers switch to change 
anything.

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

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

[Touch-packages] [Bug 1659534] Re: userdel doesn't supports extrausers

2019-03-22 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  userdel doesn't supports extrausers

Status in Snappy:
  In Progress
Status in shadow package in Ubuntu:
  In Progress
Status in shadow source package in Xenial:
  In Progress
Status in shadow source package in Bionic:
  In Progress

Bug description:
  TEST CASE:
  - run userdel --extrausers foo on a ubuntu core system

  REGRESSION POTENTIAL:
  - low, this option will only take effect when "userdel --extrauser" is used.

  On an Ubuntu Core system is impossible to delete an user from the
  extrausers db:

  root@localhost:/# userdel --extrausers alice
  userdel: unrecognized option '--extrausers'

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

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

[Touch-packages] [Bug 1799118] Re: executing ubuntu-bug gives warnings

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

** This bug has been marked a duplicate of bug 1805653
   launching firefox from terminal reveals Gtk-WARNING

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

Title:
  executing ubuntu-bug gives warnings

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When I use ubuntu-bug I get the following errors.

  robert@ASUS-A88XM-A:~/Desktop$ ubuntu-bug linux

  (apport-gtk:581): Gtk-WARNING **: 01:00:16.903: Theme parsing error:
  gtk-widgets.css:3135:13: 'max-width' is not a valid property name

  (apport-gtk:581): Gtk-WARNING **: 01:00:16.904: Theme parsing error: 
gtk-widgets.css:3136:14: 'max-height' is not a valid property name
  robert@ASUS-A88XM-A:~/Desktop$ 
  (google-chrome-stable:1222): Gtk-WARNING **: 01:00:33.982: Theme parsing 
error: gtk-widgets.css:3135:13: 'max-width' is not a valid property name

  (google-chrome-stable:1222): Gtk-WARNING **: 01:00:33.982: Theme parsing 
error: gtk-widgets.css:3136:14: 'max-height' is not a valid property name
  Created new window in existing browser session.

  Ubuntu MATE 18.04 totally crashed (I had to reinstall 18.04 just to
  boot). Since I was going to have to reinstall everything, I thought to
  check and see if 18.04 was the latest. It isn't, so I decided to try
  18.10 before reinstalling everything. Unfortunately, its still very
  buggy. Both the Software Botique and the Software app are buggy. With
  the Software app down, I can't even try to load Eclipse - which is in
  the 18.04 Software app.

  When I try to report bugs with ubuntu-bug, I get yet more bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 3464 F pulseaudio
   /dev/snd/controlC0:  robert 3464 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Oct 22 01:00:17 2018
  InstallationDate: Installed on 2018-10-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=7057e77c-c1e8-4bf5-9810-7609aceb50a0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1819969] Re: gdb-multiarch does not include RISC-V architecture

2019-03-22 Thread Ubuntu Foundations Team Bug Bot

The attachment "patch.diff" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  gdb-multiarch does not include RISC-V architecture

Status in gdb package in Ubuntu:
  New

Bug description:
  This issue was recently fixed in Debian, but seems to have not been
  pulled into Ubuntu: https://salsa.debian.org/gdb-
  team/gdb/commit/e59e4e54af0fbe9086c40ab80a1000d5c50c7175

  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  gdb-multiarch:
Installed: 8.2.90-0ubuntu1
Candidate: 8.2.90-0ubuntu1
Version table:
   *** 8.2.90-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations

** Tags added: rls-ee-incoming

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

Title:
  the WifiSyslog apport hook (used in firefox/tb) includes SSID
  informations

Status in apport package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I apport-bug certain packages such as firefox for example, it
  uploads the WifiSyslog.txt file.

  The WifiSyslog may contain a list of all system connections enumerated
  in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has
  ever connected to that are found in the system-connections. This is a
  serious privacy risk and completely unnecessary information for most
  bug reports.

  Should either remove WifiSyslog as a requirement for packages that
  don't need it (should I report this to
  https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact
  information that may contain usernames and SSIDs from the log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.4
  ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 
-0400:2018-11-01 19:17:30.982295751 
-0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 11:24:20 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (50 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago)

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

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

[Touch-packages] [Bug 1819969] Re: gdb-multiarch does not include RISC-V architecture

2019-03-22 Thread Jonathan Behrens

As per http://packaging.ubuntu.com/html/fixing-a-bug.html, I'm directly
including a patch. I've tested this locally and confirmed that these
changes enable debugging RISC-V programs running inside very recent
versions of QEMU. As noted before, it has also already been applied to
the Debian version of the package.

** Patch added: "patch.diff"
   
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1819969/+attachment/5248684/+files/patch.diff

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

Title:
  gdb-multiarch does not include RISC-V architecture

Status in gdb package in Ubuntu:
  New

Bug description:
  This issue was recently fixed in Debian, but seems to have not been
  pulled into Ubuntu: https://salsa.debian.org/gdb-
  team/gdb/commit/e59e4e54af0fbe9086c40ab80a1000d5c50c7175

  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  gdb-multiarch:
Installed: 8.2.90-0ubuntu1
Candidate: 8.2.90-0ubuntu1
Version table:
   *** 8.2.90-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1070006] Re: Mobile Broadband Fails to Configure on Ubuntu-Gnome (ZTE MF622)

2019-03-22 Thread Rolf Leggewie

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Mobile Broadband Fails to Configure on Ubuntu-Gnome (ZTE MF622)

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in modemmanager package in Ubuntu:
  Invalid
Status in network-manager package in Fedora:
  Fix Released

Bug description:
  The modem (ZTE MF622) is recognised and 'Mobile Broadband' can be
  enabled.  The network is shown ('3' in the UK) and has signal strength
  bars (2 for me). However, the modem doesn't connect.

  Ubuntu Desktop displays a Mobile Broadband Connection dialog/wiz

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

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

[Touch-packages] [Bug 1818564] Re: directory permission sanity checks

** Tags added: rls-ee-incoming

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

Title:
  directory permission sanity checks

Status in apport package in Ubuntu:
  New

Bug description:
  Hello, we've received a surprising number of bug reports that include
  lines from ufw's sanity checks on / permissions are incorrect; it's
  been a recurring feature of systemd-tmpfiles bug reports as well.

  I think apport should include a similar report if / /etc /lib /usr
  /tmp etc have incorrect user, group, or permissions.

  Thanks

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

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

[Touch-packages] [Bug 438520] Re: Right Alt key is always selected under "key to choose 3rd level"

2019-03-22 Thread Rolf Leggewie

what is the status here? Anything left to be done for bionic or later?

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

Title:
  Right Alt key is always selected under "key to choose 3rd level"

Status in console-setup package in Ubuntu:
  Expired
Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: gnome-control-center

  On a fresh install of Karmic, under the keyboard layout options, the
  right Alt key is selected under "Key to Choose 3rd Level". I'm not
  even sure what the 3rd level is, as I've never needed this setting
  before. On Jaunty, there is nothing set under this option. As a result
  on Karmic, this breaks the right Alt key. For example right Alt+F2
  doesn't do anything. But when you try to uncheck this option, it
  doesn't remember the setting. The next time you open the layout
  options, it's checked again. There seems to be no way to uncheck this
  option.

  What should happen
  1. Open System > Preferences > Keyboard
  2. Go to the Layouts tab
  3. Click Layout Options
  4. Expand Key to Choose 3rd Level
  5. Uncheck Right Alt
  5. Close the Layout Options window
  6. Reopen Layout Options
  7. Nothing should be checked under Key to Choose 3rd Level

  What happens instead
  Right Alt is still selected after unchecking it, closing the Layout Options 
window and reopening it.

  ProblemType: Bug
  Architecture: i386
  Date: Tue Sep 29 00:08:29 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: gnome-control-center 1:2.28.0-0ubuntu2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
  SourcePackage: gnome-control-center
  Uname: Linux 2.6.31-11-generic i686

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

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

[Touch-packages] [Bug 1820770] Re: when printing from the internet at Wikipedia the 8 page document only printed pages 2, 3, 4 and did not print 1, 5, 6, 7 and 8.

2019-03-22 Thread Shane Horton

Thanks for your reply.  I had used chrome browser to print the article and the 
preview did not show the break in but showed the document in entirety.  I just 
used foxfire and the document printed in entirety but with two more pages due 
to larger font, which is fine really, so I guess I will start using Firefox 
more for the the things that chrome won't do as it is becoming clearer that 
Firefox seems more versatile at this time than chrome (which I've been using 
since streaming Netflix was made possible years ago). Anyhow TMI, 
Thx!

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

Title:
  when printing from the internet at Wikipedia the 8 page document only
  printed pages 2,3,4 and did not print 1,5,6,7 and 8.

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Other random internet pages do not print at all.  The printer is a
  Brother HL-L2305W.  I have been to brother and installed the driver
  package from them with the same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.3
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 16:18:36 2019
  InstallationDate: Installed on 2018-12-25 (83 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat:
   device for HL-L2305-2: usb://Brother/HL-L2305%20series?serial=U63934M4N615987
   device for HLL2305: usb://Brother/HL-L2305%20series?serial=U63934M4N615987
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HLL2305.ppd', 
'/etc/cups/ppd/HL-L2305-2.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HLL2305.ppd: Permission denied
   grep: /etc/cups/ppd/HL-L2305-2.ppd: Permission denied
  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.15.0-46-generic 
root=UUID=15257050-0864-47a7-8179-fe818fbcbe2f ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.37
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1693
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 14.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.37:bd01/16/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1693:rvrKBCVersion14.16:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 05931120461620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 984390] Re: $PATH is taken from login.defs not /etc/environment

This is "fixed" in disco - the "su" binary does no longer comes from
"shadow" here but from util-linux. And there this bug does not exist.

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

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

Title:
  $PATH is taken from login.defs not /etc/environment

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Precise:
  Won't Fix
Status in shadow source package in Xenial:
  New
Status in shadow source package in Bionic:
  New

Bug description:
  $PATH isn't sourced from /etc/environment, instead the version in
  /etc/login.defs is used.  (The example below comes from a precise install.)

  | james@panlong:~$ echo $PATH
  | /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$ cat /etc/environment
  | 
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
  | buildd@panlong:~$ grep PATH /etc/login.defs
  | # Three items must be defined:  MAIL_DIR, ENV_SUPATH, and ENV_PATH.
  | # *REQUIRED*  The default PATH settings, for superuser and normal users.
  | ENV_SUPATH  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  | ENV_PATH
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | #CRACKLIB_DICTPATH
  | buildd@panlong:~$ sudo sed -i -e "s#^ENV_PATH.*#ENV_PATH
PATH=/wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games#" 
/etc/login.defs
  | buildd@panlong:~$ logout
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$

  REGRESSION POTENTIAL:
  - medium: it changes (incorrect) existing behaviour so https://xkcd.com/1172/ 
may apply

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

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

[Touch-packages] [Bug 942856] [network-manager/bionic] verification still needed

The fix for this bug has been awaiting testing feedback in the -proposed
repository for bionic for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

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

Title:
  NetworkManager does not support AES-encrypted private keys for WPA
  802.1x authentication

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Selecting AES-{192,256}-CBC keys to connect isn't working

  * Test case

  1. Start with a working (cleartext or DES-3) private key/cert for a network.  
Set up a connection and verify that everything works.
  2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in 
working-key.pem -out aes-key.pem -aes256" (the output should have a line 
starting with "DEK-Info: AES-256-CBC,")
  3. Delete the settings for the test network and attempt to reconnect using 
the new key. 

  That should work

  * Regression potential

  That's new code for an extra type of keys, it shouldn't impact
  existing options

  --

  NetworkManager does not appear to support private keys encrypted with
  AES.  At the very least, it will not validate such a key in nm-util
  when setting up a WPA 802.1x TLS wifi connection.

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

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

[Touch-packages] [Bug 984390] Re: $PATH is taken from login.defs not /etc/environment

** Description changed:

  $PATH isn't sourced from /etc/environment, instead the version in
  /etc/login.defs is used.  (The example below comes from a precise install.)
  
  | james@panlong:~$ echo $PATH
  | /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
- | buildd@panlong:~$ cat /etc/environment 
+ | buildd@panlong:~$ cat /etc/environment
  | 
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
- | buildd@panlong:~$ grep PATH /etc/login.defs 
+ | buildd@panlong:~$ grep PATH /etc/login.defs
  | # Three items must be defined:  MAIL_DIR, ENV_SUPATH, and ENV_PATH.
  | # *REQUIRED*  The default PATH settings, for superuser and normal users.
  | ENV_SUPATH  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  | ENV_PATH
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | #CRACKLIB_DICTPATH
- | buildd@panlong:~$ sudo sed -i -e "s#^ENV_PATH.*#ENV_PATH
PATH=/wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games#" 
/etc/login.defs  
+ | buildd@panlong:~$ sudo sed -i -e "s#^ENV_PATH.*#ENV_PATH
PATH=/wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games#" 
/etc/login.defs
  | buildd@panlong:~$ logout
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$
+ 
+ REGRESSION POTENTIAL:
+ - medium: it changes (incorrect) existing behaviour so https://xkcd.com/1172/ 
may apply

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

Title:
  $PATH is taken from login.defs not /etc/environment

Status in shadow package in Ubuntu:
  Triaged
Status in shadow source package in Precise:
  Won't Fix
Status in shadow source package in Xenial:
  New
Status in shadow source package in Bionic:
  New

Bug description:
  $PATH isn't sourced from /etc/environment, instead the version in
  /etc/login.defs is used.  (The example below comes from a precise install.)

  | james@panlong:~$ echo $PATH
  | /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$ cat /etc/environment
  | 
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
  | buildd@panlong:~$ grep PATH /etc/login.defs
  | # Three items must be defined:  MAIL_DIR, ENV_SUPATH, and ENV_PATH.
  | # *REQUIRED*  The default PATH settings, for superuser and normal users.
  | ENV_SUPATH  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  | ENV_PATH
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | #CRACKLIB_DICTPATH
  | buildd@panlong:~$ sudo sed -i -e "s#^ENV_PATH.*#ENV_PATH
PATH=/wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games#" 
/etc/login.defs
  | buildd@panlong:~$ logout
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$

  REGRESSION POTENTIAL:
  - medium: it changes (incorrect) existing behaviour so https://xkcd.com/1172/ 
may apply

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

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

[Touch-packages] [Bug 984390] Re: $PATH is taken from login.defs not /etc/environment

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

** Also affects: shadow (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: shadow (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  $PATH is taken from login.defs not /etc/environment

Status in shadow package in Ubuntu:
  Triaged
Status in shadow source package in Precise:
  Won't Fix
Status in shadow source package in Xenial:
  New
Status in shadow source package in Bionic:
  New

Bug description:
  $PATH isn't sourced from /etc/environment, instead the version in
  /etc/login.defs is used.  (The example below comes from a precise install.)

  | james@panlong:~$ echo $PATH
  | /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$ cat /etc/environment
  | 
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
  | buildd@panlong:~$ grep PATH /etc/login.defs
  | # Three items must be defined:  MAIL_DIR, ENV_SUPATH, and ENV_PATH.
  | # *REQUIRED*  The default PATH settings, for superuser and normal users.
  | ENV_SUPATH  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  | ENV_PATH
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | #CRACKLIB_DICTPATH
  | buildd@panlong:~$ sudo sed -i -e "s#^ENV_PATH.*#ENV_PATH
PATH=/wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games#" 
/etc/login.defs
  | buildd@panlong:~$ logout
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$

  REGRESSION POTENTIAL:
  - medium: it changes (incorrect) existing behaviour so https://xkcd.com/1172/ 
may apply

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

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

[Touch-packages] [Bug 1821397] [NEW] internal error when attempting to calibrate monitor using Spyder Pro 2

2019-03-22 Thread Perri Poirier

Public bug reported:

ColorVision Spdyer 2 Pro was confirmed to work with Windows as I was
able to calibrate another monitor 15 min after "internal error" message
on Ubuntu, also tried using alt driver for GTX-970 video card
(proprietary and x-org)

The message occurs after being asked to place the Spyder Pro 2 on the
screen and click NEXT to proceed.

Ubuntu 18.04.2 LTS
Kernel  : Linux 4.15.0-46-generic (x86_64)
Version : #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019
C Library   : GNU C Library / (Ubuntu GLIBC 2.27-3ubuntu1) 2.27
Distribution: Ubuntu 18.04.2 LTS

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
NonfreeKernelModules: 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  390.116  Sun Jan 27 07:21:36 
PST 2019
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 22 11:32:36 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.116, 4.15.0-46-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GM204 [GeForce GTX 970] [3842:2974]
InstallationDate: Installed on 2019-03-21 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
 Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=a8972fc6-077e-4117-a465-f0088a2989c9 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0805
dmi.board.asset.tag: Default string
dmi.board.name: TUF Z390-PRO GAMING
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.:bvr0805:bd09/21/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFZ390-PROGAMING: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
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1821397

Title:
  internal error when attempting to calibrate monitor using Spyder Pro 2

Status in xorg package in Ubuntu:
  New

Bug description:
  ColorVision Spdyer 2 Pro was confirmed to work with Windows as I was
  able to calibrate another monitor 15 min after "internal error"
  message on Ubuntu, also tried using alt driver for GTX-970 video card
  (proprietary and x-org)

  The message occurs after being asked to place the Spyder Pro 2 on the
  screen and click NEXT to proceed.

  Ubuntu 18.04.2 LTS
  Kernel: Linux 4.15.0-46-generic (x86_64)
  Version   : #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019
  C Library : GNU C Library / (Ubuntu GLIBC 2.27-3ubuntu1) 2.27
  Distribution  :

[Touch-packages] [Bug 1659534] Re: userdel doesn't supports extrausers

SRUs for xenial,bionic are uploaded and in the unapproved queue.

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

Title:
  userdel doesn't supports extrausers

Status in Snappy:
  In Progress
Status in shadow package in Ubuntu:
  In Progress
Status in shadow source package in Xenial:
  In Progress
Status in shadow source package in Bionic:
  In Progress

Bug description:
  TEST CASE:
  - run userdel --extrausers foo on a ubuntu core system

  REGRESSION POTENTIAL:
  - low, this option will only take effect when "userdel --extrauser" is used.

  On an Ubuntu Core system is impossible to delete an user from the
  extrausers db:

  root@localhost:/# userdel --extrausers alice
  userdel: unrecognized option '--extrausers'

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

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

[Touch-packages] [Bug 1821398] [NEW] cannot calibrate monitor with Spyder Pro 2

2019-03-22 Thread Perri Poirier

Public bug reported:

"Internal Error" when using x-org driver for NVIDIA GTX-980 video card
when clicking on NEXT button after being asked to place the Spyder Pro 2
on the screen.

Same error occurs if I use proprietary driver for video card.

The Spyder Pro 2 has been testes confirmed to work with Windows after
this fail in Ubuntu 18.04

Kernel  : Linux 4.15.0-46-generic (x86_64)
Version : #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019
C Library   : GNU C Library / (Ubuntu GLIBC 2.27-3ubuntu1) 2.27
Distribution: Ubuntu 18.04.2 LTS

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-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  390.116  Sun Jan 27 07:21:36 
PST 2019
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 22 13:12:47 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GM204 [GeForce GTX 970] [3842:2974]
InstallationDate: Installed on 2019-03-21 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
 Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth
 Bus 001 Device 005: ID 085c:0200 ColorVision, Inc. Spyder 2
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=a8972fc6-077e-4117-a465-f0088a2989c9 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0805
dmi.board.asset.tag: Default string
dmi.board.name: TUF Z390-PRO GAMING
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.:bvr0805:bd09/21/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFZ390-PROGAMING: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
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1821398

Title:
  cannot calibrate monitor with Spyder Pro 2

Status in xorg package in Ubuntu:
  New

Bug description:
  "Internal Error" when using x-org driver for NVIDIA GTX-980 video card
  when clicking on NEXT button after being asked to place the Spyder Pro
  2 on the screen.

  Same error occurs if I use proprietary driver for video card.

  The Spyder Pro 2 has been testes confirmed to work with Windows after
  this fail in Ubuntu 18.04

  Kernel: Linux 4.15.0-46-generic (x86_64)
  Version   : #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019
  C Library : GNU C Library / (Ubuntu GLIBC 2.27-3ubuntu1) 2.27
  Distribution  : Ubuntu 18.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64

[Touch-packages] [Bug 1659534] Re: userdel doesn't supports extrausers

** Patch added: "debdiff for bionic"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1659534/+attachment/5248606/+files/shadow_4.5-1ubuntu1.debdiff

** Changed in: shadow (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: shadow (Ubuntu Bionic)
   Status: New => In Progress

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

Title:
  userdel doesn't supports extrausers

Status in Snappy:
  In Progress
Status in shadow package in Ubuntu:
  In Progress
Status in shadow source package in Xenial:
  In Progress
Status in shadow source package in Bionic:
  In Progress

Bug description:
  TEST CASE:
  - run userdel --extrausers foo on a ubuntu core system

  REGRESSION POTENTIAL:
  - low, this option will only take effect when "userdel --extrauser" is used.

  On an Ubuntu Core system is impossible to delete an user from the
  extrausers db:

  root@localhost:/# userdel --extrausers alice
  userdel: unrecognized option '--extrausers'

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

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

[Touch-packages] [Bug 1659534] Re: userdel doesn't supports extrausers

** Patch added: "debdiff for xenial"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1659534/+attachment/5248605/+files/shadow_4.2-3.1ubuntu5.4.debdiff

** Description changed:

+ TEST CASE:
+ - run userdel --extrausers foo on a ubuntu core system
+ 
+ REGRESSION POTENTIAL:
+ - low, this option will only take effect when "userdel --extrauser" is used.
+ 
  On an Ubuntu Core system is impossible to delete an user from the
  extrausers db:
  
  root@localhost:/# userdel --extrausers alice
  userdel: unrecognized option '--extrausers'

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

Title:
  userdel doesn't supports extrausers

Status in Snappy:
  In Progress
Status in shadow package in Ubuntu:
  In Progress
Status in shadow source package in Xenial:
  New
Status in shadow source package in Bionic:
  New

Bug description:
  TEST CASE:
  - run userdel --extrausers foo on a ubuntu core system

  REGRESSION POTENTIAL:
  - low, this option will only take effect when "userdel --extrauser" is used.

  On an Ubuntu Core system is impossible to delete an user from the
  extrausers db:

  root@localhost:/# userdel --extrausers alice
  userdel: unrecognized option '--extrausers'

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

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

[Touch-packages] [Bug 1810241] Re: NULL dereference when decompressing specially crafted archives

2019-03-22 Thread Seth Arnold

Use CVE-2019-9923.

Thanks

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

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

Title:
  NULL dereference when decompressing specially crafted archives

Status in tar package in Ubuntu:
  New

Bug description:
  Hi,

  Fuzzing tar with checksums disabled reveals a NULL pointer dereference
  when parsing certain archives that have malformed extended headers.
  This affects tar from (at least) Trusty, Bionic and Cosmic. I haven't
  tested Xenial's version.

  A test case with fixed checksums is attached. To avoid breaking
  anything that looks inside tar archives, I have converted it to text
  with xxd. To reproduce:

  $ xxd -r gnutar-crash.tar.txt gnutar-crash.tar
  $ tar Oxf gnutar-crash.tar 
  tar: Ignoring unknown extended header keyword 'GNU.sparse.minTr'
  tar: Malformed extended header: missing length
  Segmentation fault (core dumped)

  I have also attached a patch against the latest upstream git and
  against 1.30 (in Cosmic). This fixes the issue by detecting the null
  result before it is dereferenced.

  Regards,
  Daniel

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

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

[Touch-packages] [Bug 1659534] Re: userdel doesn't supports extrausers

This is the fix for disco

** Patch added: "debdiff for disco"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1659534/+attachment/5248602/+files/shadow_4.5-1.1ubuntu2.debdiff

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

Title:
  userdel doesn't supports extrausers

Status in Snappy:
  In Progress
Status in shadow package in Ubuntu:
  In Progress
Status in shadow source package in Xenial:
  New
Status in shadow source package in Bionic:
  New

Bug description:
  On an Ubuntu Core system is impossible to delete an user from the
  extrausers db:

  root@localhost:/# userdel --extrausers alice
  userdel: unrecognized option '--extrausers'

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

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

[Touch-packages] [Bug 1821318] Re: FFe: Wayland 1.17 for disco

2019-03-22 Thread El jinete sin cabeza

> Is there anything that's useful for disco?
> I don't see it.

August 24, 2018 -> Wayland 1.16
March 20, 2019 -> Wayland 1.17

~6.8 months of work.

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

Title:
  FFe: Wayland 1.17 for disco

Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  https://wayland.freedesktop.org/releases.html
  https://lists.freedesktop.org/archives/wayland-devel/2019-March/040335.html

  ---

  Please upload the new version of Wayland (1.17) published on March 20,
  2019, as it is complementary in the graphic, if there are usability
  problems you can stop using changing the configuration in GDM3. From
  Wayland to Xorg.

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

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

[Touch-packages] [Bug 1659534] Re: userdel doesn't supports extrausers

** Patch added: "debdiff for disco"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1659534/+attachment/5248603/+files/shadow_4.5-1.1ubuntu2.debdiff

** Patch removed: "debdiff for disco"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1659534/+attachment/5248602/+files/shadow_4.5-1.1ubuntu2.debdiff

** Also affects: shadow (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: snappy
   Status: Confirmed => In Progress

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

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

Title:
  userdel doesn't supports extrausers

Status in Snappy:
  In Progress
Status in shadow package in Ubuntu:
  In Progress
Status in shadow source package in Xenial:
  New
Status in shadow source package in Bionic:
  New

Bug description:
  On an Ubuntu Core system is impossible to delete an user from the
  extrausers db:

  root@localhost:/# userdel --extrausers alice
  userdel: unrecognized option '--extrausers'

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

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

The sysv init script does some funky parsing of configuration files that
might give us some trouble in an independent service file. I'll check if
we can't work around that and do away with the sysv init script
altogether, otherwise we might as well go with the drop-in override
since the new service wouldn't be much different from it.

** Patch removed: "debdiff for disco"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248489/+files/lp1821343-disco.debdiff

** Patch removed: "debdiff for cosmic"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248490/+files/lp1821343-cosmic.debdiff

** Patch removed: "debdiff for bionic"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248492/+files/lp1821343-bionic.debdiff

** Patch removed: "debdiff for xenial"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248493/+files/lp1821343-xenial.debdiff

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
 Memory: 712.6M
 CGroup: /system.slice/slapd.service
 └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

[Touch-packages] [Bug 574287] Re: tasksel: forcefully removes packages when tasks overlap

2019-03-22 Thread Elias M Ward

I just ran into this bug. Started uninstalling everything when I was
removing lamp-server. Thankfully I caught it at about 15% and killed the
session when I started noticing things disappearing. This is a critical
disastrous bug. How has it not been touched in so long?

If it's not going to get fixed, at least remove tasksel out of
production or at least remove the remove function from it. This is
ridiculous.

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

Title:
  tasksel: forcefully removes packages when tasks overlap

Status in apt package in Ubuntu:
  Invalid
Status in tasksel package in Ubuntu:
  Confirmed
Status in tasksel package in Debian:
  Fix Released

Bug description:
  TEST CASE

  1. Boot Lucid LiveCD

  2. run "sudo tasksel" and select "virtual machine host"

  3. run "sudo tasksel" and deselect "virtual machine host"

  4. watch how tasksel uninstalls your system

  OBSERVATIONS

  What seems to happen is that apt vengefully removes ALL of the items
  associated with one task, including several base dependencies of other
  tasks (e.g. ubuntu-desktop)

  One illustrative example is the openssh-server task:
  This one includes the packages openssh-server, tcpd and libwrap0.
  From a normal ubuntu-desktop (e.g. ~liveCD) both tcpd and libwrap0 are 
already installed, and the task-install pulls in only openssh-server.
  However when the task is removed, all these three packages (openssh-server, 
tcpd and libwrap0) are forcefully removed.
  Since libwrap0 is a core dependency of gnome, a large part of gnome will be 
removed alongside the removal of the task.

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

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

[Touch-packages] [Bug 1821318] Re: FFe: Wayland 1.17 for disco

this is the more interesting changelog from rc1:

Chris Billington (1):
  wayland-util.h: add forward declaration for wl_object

Derek Foreman (1):
  configure.ac: bump version to 1.16.93 for the RC1 release

Pekka Paalanen (3):
  contributing: use Gitlab merge request workflow
  tests: add request_bogus_size
  connection: fix demarshal of invalid header


Is there anything that's useful for disco? I don't see it.

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

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

Title:
  FFe: Wayland 1.17 for disco

Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  https://wayland.freedesktop.org/releases.html
  https://lists.freedesktop.org/archives/wayland-devel/2019-March/040335.html

  ---

  Please upload the new version of Wayland (1.17) published on March 20,
  2019, as it is complementary in the graphic, if there are usability
  problems you can stop using changing the configuration in GDM3. From
  Wayland to Xorg.

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

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

2019-03-22 Thread Dan Streetman

> Do you need a whole service file for this? I thought you could achieve
> the same with a drop-in that just overrides the required keys

why would we do a SRU to hack in an override when it's just as easy to
do a SRU to actually create a correct service file so no override hack
is needed?

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
 Memory: 712.6M
 CGroup: /system.slice/slapd.service
 └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

-- 
Mailing list: https://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 1821343] [NEW] slapd process failure is not detected by systemd

2019-03-22 Thread Ryan Tandy

Hello Hector,

On Fri, Mar 22, 2019 at 12:36:57PM -, Heitor R. Alves de Siqueira wrote:
>The slapd package for OpenLDAP is shipped with a SysV-style init script 
>(/etc/init.d/slapd). Systemd automatically converts this to a systemd 
>service by generating the unit file using the systemd-sysv-generator(8) 
>utility. The generated unit file contains Type=forking and 
>RemainAfterExit=yes directives.
>
>If the slapd daemon process exits due to some failure (e.g., it receives
>a SIGTERM or SIGKILL), the failure is not detected properly by systemd.
>The service is still reported as active even though the child (daemon)
>process has exited with a signal.
>
>We can easily fix this by including a proper systemd service file for
>slapd in the openldap package.

Do you need a whole service file for this? I thought you could achieve 
the same with a drop-in that just overrides the required keys:

/etc/systemd/systems/slapd.service.d/remain-after-exit.conf:

[Service]
Type=forking
RemainAfterExit=no
Restart=on-failure

(untested, based on bug 1488962)

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
 Memory: 712.6M
 CGroup: /system.slice/slapd.service
 └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

[Touch-packages] [Bug 1821376] [NEW] Report packages kept back by origins

2019-03-22 Thread Balint Reczey

Public bug reported:

Packages kept back are listed in the email report, but it is not clear
from which origins they are installable. This information may help
administrators to decide if the packages need to be manually upgraded.

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

** Description changed:

  Packages kept back are listed in the email report, but it is not clear
  from which origins they are installable. This information may help
- administrators to decide if the package needs to be manually upgraded.
+ administrators to decide if the packages need to be manually upgraded.

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

Title:
  Report packages kept back by origins

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Packages kept back are listed in the email report, but it is not clear
  from which origins they are installable. This information may help
  administrators to decide if the packages need to be manually upgraded.

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

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

2019-03-22 Thread Ubuntu Foundations Team Bug Bot

The attachment "debdiff for disco" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
 Memory: 712.6M
 CGroup: /system.slice/slapd.service
 └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

[Touch-packages] [Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces

2019-03-22 Thread Dan Streetman

** Tags added: sts

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

Title:
  netplan should consider adding more udev attribute for exact matching
  of failover 3-netdev interfaces

Status in netplan:
  Triaged
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  This bug is a follow-up to

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815268

  after applying the 0001-net_failover-delay-taking-over-primary-device-
  to-acc.patch attached in that bug, the VF interface "eth0" is renamed
  to "rename4" instead of "ens4". Log is showing that attempt to rename
  "eth0" to "ens3" failed because of conflict with existing name, so
  that's why it ends up with rename4.

  vsbalakr@ubuntu-18:~$ uname -a
  Linux ubuntu-18 4.15.0-1009-oracle #11+lp1815268 SMP Tue Mar 12 15:20:15 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-18:~$ ip l 
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 
00:00:00:00:00:00 
  2: ens3:  mtu 1500 qdisc noqueue state UP 
mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd 
ff:ff:ff:ff:ff:ff 
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP mode DEFAULT group default qlen 1000 link/ether 
ba:fb:9f:12:2f:02 brd ff:ff:ff:ff:ff:ff 
  4: rename4:  mtu 1500 qdisc mq master ens3 
state UP mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd 
ff:ff:ff:ff:ff:ff

  vsbalakr@ubuntu-18:~$ egrep -i '(rename4|busy)' /var/log/syslog
  ...
  Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]:  [1552932112.9591] 
device (rename4): carrier: link connected
  Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]:  [1552932112.9591] 
device (rename4): enslaved to non-master-type device ens3; ignoring
  Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: error changing net interface 
name 'eth0' to 'ens3': Device or resource busy
  Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: could not rename interface '4' 
from 'eth0' to 'ens3': Device or resource busy

  Within VM there's netplan config as below:

  vsbalakr@ubuntu-18:~$ cat /etc/netplan/01-netcfg.yaml
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  ens3:
dhcp4: yes
gateway4: 10.211.8.1
nameservers:
addresses: [10.211.11.1,10.209.76.197]

  By running udevadm test, we can see the conflicting ens3 name comes
  from netplan's /run/udev/rules.d/99-netplan-ens3.rules

  vsbalakr@ubuntu-18:~$ cat /run/udev/rules.d/99-netplan-ens3.rules
  SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="ba:fb:9f:12:2f:02", NAME="ens3"

  vsbalakr@ubuntu-18:/lib/udev/rules.d$ udevadm test --action="add" 
/sys/class/net/eth0
  calling: test
  version 237
  This program is for debugging only, it does not run any program
  specified by a RUN key. It may show incorrect results, because
  some values may be different, or not available at a simulation run.

  Load module index
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed configuration file /run/systemd/network/10-netplan-ens3.link
  Created link configuration context.
  Reading rules file: /lib/udev/rules.d/01-md-raid-creating.rules
  ..
  Reading rules file: /lib/udev/rules.d/99-vmware-scsi-udev.rules
  rules contain 393216 bytes tokens (32768 * 12 bytes), 38638 bytes strings
  25317 strings (216160 bytes), 21957 de-duplicated (180883 bytes), 3361 trie 
nodes used
  RUN '/lib/open-iscsi/net-interface-handler start' 
/lib/udev/rules.d/70-iscsi-network-interface.rules:2
  IMPORT builtin 'net_id' /lib/udev/rules.d/75-net-description.rules:6
  IMPORT builtin 'hwdb' /lib/udev/rules.d/75-net-description.rules:12
  RUN 'ifupdown-hotplug' /lib/udev/rules.d/80-ifupdown.rules:5
  IMPORT builtin 'path_id' /lib/udev/rules.d/80-net-setup-link.rules:5
  IMPORT builtin 'net_setup_link' /lib/udev/rules.d/80-net-setup-link.rules:9
  Config file /lib/systemd/network/99-default.link applies to device eth0
  link_config: autonegotiation is unset or enabled, the speed and duplex are 
not writable.
  link_config: could not set ethtool features for eth0
  Could not set offload features of eth0: Operation not permitted
  NAME 'ens4' /lib/udev/rules.d/80-net-setup-link.rules:11
  NAME 'ens3' /run/udev/rules.d/99-netplan-ens3.rules:1
  RUN '/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/$name 
--prefix=/net/ipv4/neigh/$name --prefix=/net/ipv6/conf/$name 
--prefix=/net/ipv6/neigh/$name' /lib/udev/rules.d/99-systemd.rules:60
  error changing net interface name 'eth0' to 'ens3': Operation not permitted
  could not rename interface '4' from 'eth0' to 'ens3': Operation not permitted
  ACTION=add

[Touch-packages] [Bug 1821371] [NEW] starting

2019-03-22 Thread delmotte

Public bug reported:

when i start , i can't have ubuntu , but black screen with some icones
flashing , my arrow of the mouse can move but do nothing , i'm french so
excuse me for my language

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_4_15_0_36_39_generic_48
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Fri Mar 22 16:34:18 2019
DistUpgraded: 2018-07-23 08:19:08,090 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GK107 [GeForce GT 740] [1458:368d]
InstallationDate: Installed on 2017-05-19 (672 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Olidata S.p.A. To Be Filled By O.E.M.
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=4bf32425-67a7-4926-91a8-f1fb1b97baaf ro splash quiet plymouth:debug=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-07-23 (242 days ago)
dmi.bios.date: 01/23/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.20
dmi.board.name: B85M DASH/OL R2.0
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/23/2015:svnOlidataS.p.A.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85MDASH/OLR2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: Olidata S.p.A.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sun Jul 22 08:14:02 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB Receiver KEYBOARD, id 8
 inputLogitech USB Receiver MOUSE, id 9
 inputLogitech USB Receiver KEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2

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


** Tags: amd64 apport-bug bionic 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/1821371

Title:
  starting

Status in xorg package in Ubuntu:
  New

Bug description:
  when i start , i can't have ubuntu , but black screen with some icones
  flashing , my arrow of the mouse can move but do nothing , i'm french
  so excuse me for my language

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_36_39_generic_48
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Mar 22 16:34:18 2019
  DistUpgraded: 2018-07-23 08:19:08,090 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GK107 [GeForce GT 740] [1458:368d]
  InstallationDate: Installed on 2017-05-19 (672 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Olidata S.p.A. To Be Filled By O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=4bf32425-67a7-4926-91a8-f1fb1b97baaf ro splash quiet plymouth:debug=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-07-23 (242 days ago)
  dmi.bios.date: 01/23/2015

[Touch-packages] [Bug 1821364] [NEW] xfce4 install on Ubuntu 18.04 has no polkit agent

2019-03-22 Thread markling

Public bug reported:

The problem was evident as en error message when trying run 'Language
Support' (gnome-language-selector) after install. (This was the advised
way to get the Atom spell-checker working).

Error described here: https://askubuntu.com/questions/1031319/language-
support-in-18-04-not-working-org-freedesktop-policykiterror-
failed/1127862#1127862

It occurred on a fresh install of Ubuntu 18.04 after installing xfce4.

No PolicyKit Authentication Agent was installed - or at least not one
that xfce seemed to recognise.

I solved the problem by installing one:

$ sudo apt install policykit-1-gnome

That installed the package: /usr/lib/policykit-1-gnome/polkit-gnome-
authentication-agent-1.

It seemed to update the autostart list.

Though there is such a thing as 'xfce-polkit' and 'xfce-polkit-git', I
could not see them on my machine and Debian [reports][3], in it's
account of the package policykit-1-gnome, that xfce still uses the gnome
polkit agent:

"This implementation was originally designed for GNOME 2, but most
GNOME-based desktop environments, including GNOME 3, GNOME Flashback,
and MATE, have their own built-in PolicyKit agents and no longer use
this one. The remaining users of this implementation are Cinnamon, XFCE
and Unity."

(https://packages.debian.org/sid/policykit-1-gnome)

It is worth noting that the terminal emulator that comes default in
Ubuntu and is still default after installing xfce (gnome terminal) would
not run polkit-gnome-authentication-agent-1 after install. I understand
it may have been necessary, perhaps ironically, to run it an an xterm. I
didn't attempt this. But all was well after restart.

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


** Tags: 18.04 agent authentication gnome polkit 
polkit-gnome-authentication-agent-1 ubuntu xfce4

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

Title:
  xfce4 install on Ubuntu 18.04 has no polkit agent

Status in dbus package in Ubuntu:
  New

Bug description:
  The problem was evident as en error message when trying run 'Language
  Support' (gnome-language-selector) after install. (This was the
  advised way to get the Atom spell-checker working).

  Error described here: https://askubuntu.com/questions/1031319
  /language-support-in-18-04-not-working-org-freedesktop-policykiterror-
  failed/1127862#1127862

  It occurred on a fresh install of Ubuntu 18.04 after installing xfce4.

  No PolicyKit Authentication Agent was installed - or at least not one
  that xfce seemed to recognise.

  I solved the problem by installing one:

  $ sudo apt install policykit-1-gnome

  That installed the package: /usr/lib/policykit-1-gnome/polkit-gnome-
  authentication-agent-1.

  It seemed to update the autostart list.

  Though there is such a thing as 'xfce-polkit' and 'xfce-polkit-git', I
  could not see them on my machine and Debian [reports][3], in it's
  account of the package policykit-1-gnome, that xfce still uses the
  gnome polkit agent:

  "This implementation was originally designed for GNOME 2, but most
  GNOME-based desktop environments, including GNOME 3, GNOME Flashback,
  and MATE, have their own built-in PolicyKit agents and no longer use
  this one. The remaining users of this implementation are Cinnamon,
  XFCE and Unity."

  (https://packages.debian.org/sid/policykit-1-gnome)

  It is worth noting that the terminal emulator that comes default in
  Ubuntu and is still default after installing xfce (gnome terminal)
  would not run polkit-gnome-authentication-agent-1 after install. I
  understand it may have been necessary, perhaps ironically, to run it
  an an xterm. I didn't attempt this. But all was well after restart.

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

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

** Patch added: "debdiff for disco"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248489/+files/lp1821343-disco.debdiff

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
 Memory: 712.6M
 CGroup: /system.slice/slapd.service
 └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

** Patch added: "debdiff for xenial"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248493/+files/lp1821343-xenial.debdiff

** Tags added: sts-sponsor

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
 Memory: 712.6M
 CGroup: /system.slice/slapd.service
 └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

** Patch added: "debdiff for bionic"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248492/+files/lp1821343-bionic.debdiff

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
 Memory: 712.6M
 CGroup: /system.slice/slapd.service
 └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
 Memory: 712.6M
 CGroup: /system.slice/slapd.service
 └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

** Patch added: "debdiff for cosmic"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248490/+files/lp1821343-cosmic.debdiff

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
 Memory: 712.6M
 CGroup: /system.slice/slapd.service
 └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

[Touch-packages] [Bug 1821348] [NEW] ubuntu 16.04 and win10 double system y7000 1050ti , press the shutdown no response , after that I can use the computer fluently , when i use the code it tell me

2019-03-22 Thread trojan

Public bug reported:

ubuntu 16.04 and win10 double system y7000 1050ti , press the shutdown
no response ,after that I can use the computer fluently , when i use the
code  it tell me  have the same process or restart process ,,and
the  computer can't   close  it will not screen , what i should do

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

Title:
  ubuntu 16.04 and win10 double system y7000 1050ti , press the shutdown
  no response ,after that I can use the computer fluently , when i use
  the code  it tell me  have the same process or restart process ,,
  and   the  computer can't   close  it will not screen , what i should
  do

Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu 16.04 and win10 double system y7000 1050ti , press the shutdown
  no response ,after that I can use the computer fluently , when i use
  the code  it tell me  have the same process or restart process ,,
  and   the  computer can't   close  it will not screen , what i should
  do

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

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

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

Hello Marco, or anyone else affected,

Accepted glib2.0 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.56.4-0ubuntu0.18.04.2 in
a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  SRU 2.56.4 to bionic

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  New upstream bug fix microrelease

  * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582)

  * Bug fixes:
   #1588 Moving a bookmark item to the same URI causes a crash
   #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56

  Plus fix for LP: #1760569

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Test various parts of the desktop.

    - Logging in
    - Shutting down
    - Starting a variety of apps and checking that they work
  + rhythmbox (play a song using gstreamer)
  + cheese (look at yourself with your webcam using gstreamer)
  + network-manager
  + epiphany (web stuff works)

  Monitor the error tracker for any increases.

  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

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

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

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

Hello Karl, or anyone else affected,

Accepted glib2.0 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.56.4-0ubuntu0.18.04.2 in
a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Nautilus crashes in g_free -> g_bookmark_file_move_item ->
  gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in nautilus source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  A crasher when using nautilus. No clear reproducer.

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Make sure nautilus works, and that the error tracker buckets listed
  below at least don't increase more rapidly (but hopefully tail off
  with the new version)

  
  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

  [ Original description ]

  Happens when there's a "rename" to a file to its same value, no known
  reproducer though.

  Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456

  https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45
  https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AssertionMessage: munmap_chunk(): invalid pointer
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 09:04:45 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-03-31 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid 
pointer") at malloc.c:5350
   munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846
   __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117
   g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus assert failure: munmap_chunk(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

-- 
Mailing list: https://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 1821308] Re: apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

2019-03-22 Thread larsen

> (1) burp 2.0.54 is not in a repo, only locally installed

That is correct.

Output as requested:

# apt-cache policy burp
burp:
   Installed: 2.0.54-1
   Candidate: 2.0.54-1
   Package pin: 2.0.54-1
   Version table:
  *** 2.0.54-1 1000
 100 /var/lib/dpkg/status
  1.3.48-4.1 1000
 500 https://ftp-stud.hs-esslingen.de/debian/ jessie/main amd64
Packages

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

Title:
  apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Trusty:
  Triaged

Bug description:
  I have updated apt this morning:

  Start-Date: 2019-03-22  09:36:18
  Commandline: apt-get dist-upgrade
  Upgrade: apt:amd64 (1.0.1ubuntu2.20, 1.0.1ubuntu2.22), ...

  
  Afterwards, apt-get ignores my pinning preferences:

  # apt-get --dry-run upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be DOWNGRADED:
burp
  0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
  Inst burp [2.0.54-1] (1.3.48-4 Ubuntu:14.04/trusty [amd64])
  Conf burp (1.3.48-4 Ubuntu:14.04/trusty [amd64])

  
  # cat /etc/apt/preferences.d/burp.pref
  Package: burp
  Pin: version 2.0.54*
  Pin-Priority: 1000

  
  This might be caused by bug 1814727 as it's the only thing I can see in the 
changelog regarding apt/pinning.

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

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

[Touch-packages] [Bug 1821308] Re: apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

2019-03-22 Thread Francis Ginther

** Tags added: id-5c94c4fd0a7a583861e90c88

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

Title:
  apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Trusty:
  Triaged

Bug description:
  I have updated apt this morning:

  Start-Date: 2019-03-22  09:36:18
  Commandline: apt-get dist-upgrade
  Upgrade: apt:amd64 (1.0.1ubuntu2.20, 1.0.1ubuntu2.22), ...

  
  Afterwards, apt-get ignores my pinning preferences:

  # apt-get --dry-run upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be DOWNGRADED:
burp
  0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
  Inst burp [2.0.54-1] (1.3.48-4 Ubuntu:14.04/trusty [amd64])
  Conf burp (1.3.48-4 Ubuntu:14.04/trusty [amd64])

  
  # cat /etc/apt/preferences.d/burp.pref
  Package: burp
  Pin: version 2.0.54*
  Pin-Priority: 1000

  
  This might be caused by bug 1814727 as it's the only thing I can see in the 
changelog regarding apt/pinning.

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

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

[Touch-packages] [Bug 1821343] [NEW] slapd process failure is not detected by systemd

Public bug reported:

[Impact]
Systemd service reports slapd as active, even though it may have failed

[Description]
The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

If the slapd daemon process exits due to some failure (e.g., it receives
a SIGTERM or SIGKILL), the failure is not detected properly by systemd.
The service is still reported as active even though the child (daemon)
process has exited with a signal.

We can easily fix this by including a proper systemd service file for
slapd in the openldap package. Since the init.d script already does most
of the necessary work (parsing configs, setting up PID files, etc.), we
don't need anything complicated for the systemd unit file. Just making
sure that RemainAfterExit is set to "no" makes the systemd service
behave in the expected way.

[Test Case]
1) Deploy a disco container
$ lxc launch images:ubuntu/disco disco

2) Install slapd
ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

3) Verify that slapd is running with the auto-generated service
ubuntu@disco:~$ systemctl status slapd
● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access 
Protocol)
   Loaded: loaded (/etc/init.d/slapd; generated)
   Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
 Docs: man:systemd-sysv-generator(8)
  Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
Tasks: 3 (limit: 4915)
   Memory: 712.6M
   CGroup: /system.slice/slapd.service
   └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap 
-F /etc/ldap/slapd.d

4) SIGKILL the slapd process (PID is displayed in systemctl status output)
ubuntu@disco:~$ sudo kill -9 1109

5) Check if systemd service lists slapd as still active, even though it was 
terminated
ubuntu@disco:~$ systemctl status slapd
● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access 
Protocol)
   Loaded: loaded (/etc/init.d/slapd; generated)
   Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
 Docs: man:systemd-sysv-generator(8)
  Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

[Regression Potential]
The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

** Affects: openldap (Ubuntu)
 Importance: Medium
 Assignee: Heitor R. Alves de Siqueira (halves)
 Status: Confirmed

** Affects: openldap (Ubuntu Xenial)
 Importance: Medium
 Assignee: Heitor R. Alves de Siqueira (halves)
 Status: Confirmed

** Affects: openldap (Ubuntu Bionic)
 Importance: Medium
 Assignee: Heitor R. Alves de Siqueira (halves)
 Status: Confirmed

** Affects: openldap (Ubuntu Cosmic)
 Importance: Medium
 Assignee: Heitor R. Alves de Siqueira (halves)
 Status: Confirmed


** Tags: sts

** Also affects: openldap (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: openldap (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: openldap (Ubuntu Xenial)
 Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)

** Changed in: openldap (Ubuntu Bionic)
 Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)

** Changed in: openldap (Ubuntu Cosmic)
 Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)

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

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

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

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

[Touch-packages] [Bug 1816547] Re: SRU 2.56.4 to bionic

2019-03-22 Thread Iain Lane

bah, it failed on i386 and s390x:

Bail out! 
GLib:ERROR:../../../../glib/gvariant-serialiser.c:174:g_variant_serialised_check:
 assertion failed (alignment & (gsize) serialised.data == 0): (3 == 0)
ERROR: gvariant - Bail out! 
GLib:ERROR:../../../../glib/gvariant-serialiser.c:174:g_variant_serialised_check:
 assertion failed (alignment & (gsize) serialised.data == 0): (3 == 0)

I guess we need these from the branch:

*   commit d202953c47284a17d03dd2d14b67756aa5edc872
|\  Merge: 8723aba59 4ef58e566
| | Author: Simon McVittie 
| | Date:   Fri Jan 4 14:14:56 2019 +
| | 
| | Merge branch 'backport-552-gvariant-test-alignment-glib-2-56' into 
'glib-2-56'
| | 
| | Backport tests: Allocate gvariant data from the heap to guarantee 
alignment to glib-2-56
| | 
| | See merge request GNOME/glib!557
| | 
| * commit 4ef58e5661849317a1110c9b93957f2c608677dd
| | Author: Simon McVittie 
| | Date:   Thu Jan 3 08:21:40 2019 +
| | 
| | gvariant test: Also force alignment for tuple test data
| | 
| | glib!552 (commit 9eed22b3) fixed this for the tests that failed on i686,
| | but this additional test failed on Debian's s390x port
| | (IBM z/Architecture, 64-bit big-endian).
| | 
| | Signed-off-by: Simon McVittie 
| | 
| * commit 85c4031696add9797e2334ced20678edcd96c869
|/  Author: Mart Raudsepp 
|   Date:   Wed Dec 19 16:22:21 2018 +0200
|   
|   tests: Allocate gvariant data from the heap to guarantee alignment
|   
|   On glib-2-58 branch we don't have !455, thus we need aligned data
|   for the gvariant tests to not fail on i686.
|   
|   Fixes #1626


probably.

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

Title:
  SRU 2.56.4 to bionic

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  New upstream bug fix microrelease

  * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582)

  * Bug fixes:
   #1588 Moving a bookmark item to the same URI causes a crash
   #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56

  Plus fix for LP: #1760569

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Test various parts of the desktop.

    - Logging in
    - Shutting down
    - Starting a variety of apps and checking that they work
  + rhythmbox (play a song using gstreamer)
  + cheese (look at yourself with your webcam using gstreamer)
  + network-manager
  + epiphany (web stuff works)

  Monitor the error tracker for any increases.

  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

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

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

[Touch-packages] [Bug 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

Hello Karl, or anyone else affected,

Accepted glib2.0 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.56.4-0ubuntu0.18.04.1 in
a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  Nautilus crashes in g_free -> g_bookmark_file_move_item ->
  gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in nautilus source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  A crasher when using nautilus. No clear reproducer.

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Make sure nautilus works, and that the error tracker buckets listed
  below at least don't increase more rapidly (but hopefully tail off
  with the new version)

  
  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

  [ Original description ]

  Happens when there's a "rename" to a file to its same value, no known
  reproducer though.

  Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456

  https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45
  https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AssertionMessage: munmap_chunk(): invalid pointer
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 09:04:45 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-03-31 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid 
pointer") at malloc.c:5350
   munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846
   __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117
   g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus assert failure: munmap_chunk(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Touch-packages] [Bug 1816547] Re: SRU 2.56.4 to bionic

Hello Marco, or anyone else affected,

Accepted glib2.0 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.56.4-0ubuntu0.18.04.1 in
a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  SRU 2.56.4 to bionic

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  New upstream bug fix microrelease

  * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582)

  * Bug fixes:
   #1588 Moving a bookmark item to the same URI causes a crash
   #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56

  Plus fix for LP: #1760569

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Test various parts of the desktop.

    - Logging in
    - Shutting down
    - Starting a variety of apps and checking that they work
  + rhythmbox (play a song using gstreamer)
  + cheese (look at yourself with your webcam using gstreamer)
  + network-manager
  + epiphany (web stuff works)

  Monitor the error tracker for any increases.

  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

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

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

[Touch-packages] [Bug 1821308] Re: apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

2019-03-22 Thread Julian Andres Klode

FWIW, reading the code for trusty, I assume that

(1) burp 2.0.54 is not in a repo, only locally installed
(2) hence the code that checks whether the specified pin can be valid says "no" 
and ignores it, because it does not find any source, and thus concludes that 
the package only has available sources marked as "never".

Should be easy to fix.

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

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

** Changed in: apt (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: apt (Ubuntu Trusty)
   Importance: Undecided => Critical

** Changed in: apt (Ubuntu Trusty)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Trusty:
  Triaged

Bug description:
  I have updated apt this morning:

  Start-Date: 2019-03-22  09:36:18
  Commandline: apt-get dist-upgrade
  Upgrade: apt:amd64 (1.0.1ubuntu2.20, 1.0.1ubuntu2.22), ...

  
  Afterwards, apt-get ignores my pinning preferences:

  # apt-get --dry-run upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be DOWNGRADED:
burp
  0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
  Inst burp [2.0.54-1] (1.3.48-4 Ubuntu:14.04/trusty [amd64])
  Conf burp (1.3.48-4 Ubuntu:14.04/trusty [amd64])

  
  # cat /etc/apt/preferences.d/burp.pref
  Package: burp
  Pin: version 2.0.54*
  Pin-Priority: 1000

  
  This might be caused by bug 1814727 as it's the only thing I can see in the 
changelog regarding apt/pinning.

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

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

[Touch-packages] [Bug 1821308] Re: apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

2019-03-22 Thread Julian Andres Klode

Please provide apt-cache policy output, and there are probably other
pinnings in your preferences files.

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

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

Title:
  apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Trusty:
  Triaged

Bug description:
  I have updated apt this morning:

  Start-Date: 2019-03-22  09:36:18
  Commandline: apt-get dist-upgrade
  Upgrade: apt:amd64 (1.0.1ubuntu2.20, 1.0.1ubuntu2.22), ...

  
  Afterwards, apt-get ignores my pinning preferences:

  # apt-get --dry-run upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be DOWNGRADED:
burp
  0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
  Inst burp [2.0.54-1] (1.3.48-4 Ubuntu:14.04/trusty [amd64])
  Conf burp (1.3.48-4 Ubuntu:14.04/trusty [amd64])

  
  # cat /etc/apt/preferences.d/burp.pref
  Package: burp
  Pin: version 2.0.54*
  Pin-Priority: 1000

  
  This might be caused by bug 1814727 as it's the only thing I can see in the 
changelog regarding apt/pinning.

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

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

[Touch-packages] [Bug 1821308] Re: apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

2019-03-22 Thread Julian Andres Klode

apt-cache policy burp, that is

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

Title:
  apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Trusty:
  Triaged

Bug description:
  I have updated apt this morning:

  Start-Date: 2019-03-22  09:36:18
  Commandline: apt-get dist-upgrade
  Upgrade: apt:amd64 (1.0.1ubuntu2.20, 1.0.1ubuntu2.22), ...

  
  Afterwards, apt-get ignores my pinning preferences:

  # apt-get --dry-run upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be DOWNGRADED:
burp
  0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
  Inst burp [2.0.54-1] (1.3.48-4 Ubuntu:14.04/trusty [amd64])
  Conf burp (1.3.48-4 Ubuntu:14.04/trusty [amd64])

  
  # cat /etc/apt/preferences.d/burp.pref
  Package: burp
  Pin: version 2.0.54*
  Pin-Priority: 1000

  
  This might be caused by bug 1814727 as it's the only thing I can see in the 
changelog regarding apt/pinning.

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

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

[Touch-packages] [Bug 1806407] Re: Mobile broadband SIM doesn't work but does on same machine booted into Windows

mate@mate-Lenovo-YOGA-330-11IGM:~$ dig google.com

; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached
mate@mate-Lenovo-YOGA-330-11IGM:~$

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

Title:
  Mobile broadband SIM doesn't work but does on same machine booted into
  Windows

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I am trying to use a mobile broadband sim with my TabletPC running
  Ubuntu 18.04, but it doesn't work, I get: "Connection Failed:
  Activation of network connection failed" when trying to connect with
  it. HOWEVER, if I boot this same TabletPC into Windows 10, the sim
  works fine. So it is not a problem with the SIM nor a problem the
  TabletPC hardware. It is a problem with Ubuntu.

  Can I ask what testing/Quality Assurance (QA) you did on Ubuntu for
  mobile broadband and where your testing records are kept?

  
  Further details here:
  
https://askubuntu.com/questions/1079689/mobile-broadband-sim-doesnt-work-with-ubuntu-18-04-but-does-work-in-same-device

  "I have a Panasonic FZ-G1 MkIII Toughpad touchscreen tablet PC which
  is based on an x86-64bit Intel® Core™ i5-5300U CPU @ 2.30GHz, with 4Gb
  RAM.

  This is dual-booted with Windows 10 Pro 64bit (build 1803) and Ubuntu
  18.04.1 LTS 64bit.

  The mobile sim is a standard giffgaff sim which works fine in Windows
  on this machine - it is recognised and internet access via it works,
  detected as LTE (4G). So this proves that the sim is working correctly
  with the WLAN modem hardware in this tablet.

  However, when the same tablet is booted into Ubuntu 18.04.1 LTS 64bit,
  the same sim that worked in the Windows partition, does not work in
  Ubuntu. Error message: "Connection Failed: Activation of network
  connection failed" pops up when attempting connection via Settings. "

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

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

[Touch-packages] [Bug 1821318] [NEW] FFe: Wayland 1.17 for disco

2019-03-22 Thread El jinete sin cabeza

Public bug reported:

https://wayland.freedesktop.org/releases.html
https://lists.freedesktop.org/archives/wayland-devel/2019-March/040335.html

---

Please upload the new version of Wayland (1.17) published on March 20,
2019, as it is complementary in the graphic, if there are usability
problems you can stop using changing the configuration in GDM3. From
Wayland to Xorg.

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


** Tags: amd64 disco wayland-session

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

Title:
  FFe: Wayland 1.17 for disco

Status in wayland package in Ubuntu:
  New

Bug description:
  https://wayland.freedesktop.org/releases.html
  https://lists.freedesktop.org/archives/wayland-devel/2019-March/040335.html

  ---

  Please upload the new version of Wayland (1.17) published on March 20,
  2019, as it is complementary in the graphic, if there are usability
  problems you can stop using changing the configuration in GDM3. From
  Wayland to Xorg.

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

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

[Touch-packages] [Bug 1821298] Re: Evince with beamer multimedia: video content covers slides

2019-03-22 Thread Giampiero Salvi

** Package changed: poppler (Ubuntu) => evince (Ubuntu)

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

Title:
  Evince with beamer multimedia: video content covers slides

Status in evince package in Ubuntu:
  New

Bug description:
  Hi,
  I have been using beamer and the multimedia package for many years to play 
video and audio content in my slides. Until now, the only free viewer that 
could display the material that I am aware of was Okular. However, since Ubuntu 
18.04, okular has become extremely unstable with continuous crashes, so I have 
given another try to Evince.

  Evince can display the videos just fine, but unfortunately, when the
  video ends, the last frame remains on top of any new slide covering
  the slide material. I believe this should be an easy fix. There must
  be some cleaning up that needs to be done at the end of the video, or
  when the slide is changed that is clearly not performed. For example,
  if I play the video and at the same time change slide, the video
  continues to play on top.

  I am using
  Ubuntu 18.04.1
  Evince 3.28.4
  texlive 2017.20180305-1
  kernel 4.15.0-46-generic

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

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

[Touch-packages] [Bug 1821308] [NEW] apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

2019-03-22 Thread larsen

Public bug reported:

I have updated apt this morning:

Start-Date: 2019-03-22  09:36:18
Commandline: apt-get dist-upgrade
Upgrade: apt:amd64 (1.0.1ubuntu2.20, 1.0.1ubuntu2.22), ...


Afterwards, apt-get ignores my pinning preferences:

# apt-get --dry-run upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be DOWNGRADED:
  burp
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
Inst burp [2.0.54-1] (1.3.48-4 Ubuntu:14.04/trusty [amd64])
Conf burp (1.3.48-4 Ubuntu:14.04/trusty [amd64])


# cat /etc/apt/preferences.d/burp.pref
Package: burp
Pin: version 2.0.54*
Pin-Priority: 1000


This might be caused by bug 1814727 as it's the only thing I can see in the 
changelog regarding apt/pinning.

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


** Tags: regression-update

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

Title:
  apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

Status in apt package in Ubuntu:
  New

Bug description:
  I have updated apt this morning:

  Start-Date: 2019-03-22  09:36:18
  Commandline: apt-get dist-upgrade
  Upgrade: apt:amd64 (1.0.1ubuntu2.20, 1.0.1ubuntu2.22), ...

  
  Afterwards, apt-get ignores my pinning preferences:

  # apt-get --dry-run upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be DOWNGRADED:
burp
  0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
  Inst burp [2.0.54-1] (1.3.48-4 Ubuntu:14.04/trusty [amd64])
  Conf burp (1.3.48-4 Ubuntu:14.04/trusty [amd64])

  
  # cat /etc/apt/preferences.d/burp.pref
  Package: burp
  Pin: version 2.0.54*
  Pin-Priority: 1000

  
  This might be caused by bug 1814727 as it's the only thing I can see in the 
changelog regarding apt/pinning.

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

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

[Touch-packages] [Bug 1772512] Re: Unable to install i386 and amd64 arch at the same time

Hello Maciej, or anyone else affected,

Accepted libxkbcommon into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libxkbcommon/0.8.2-1~ubuntu18.04.1
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libxkbcommon (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  Unable to install i386 and amd64 arch at the same time

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the 
package isn't properly multi-archified in bionic

  [Test case]
  apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64

  should succeed

  [Regression potential]
  not really

  
  --

  Not sure if this is intended, but it's not possible to install two
  architectures of the libxkbcommon-dev at the same time. On Ubuntu
  16.04 and 18.04 apt-get says that they are in conflict.

  The package is a dependency for libegl1-mesa-dev, which I need to have
  installed in 64 and 32-bit variants.

  Please see the example output below:

  $ lsb_release --all
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

  $ sudo apt-get install libxkbcommon-dev:*
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be 
installed
   libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected,

Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.04.1 in
a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: netplan.io (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

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

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released
Status in netplan.io source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

no need to re-test this on bionic/cosmic

** Changed in: netplan.io (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

** Changed in: netplan.io (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic 
verification-done-cosmic

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released
Status in netplan.io source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected,

Accepted netplan.io into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.10.1 in
a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: netplan.io (Ubuntu Cosmic)
   Status: Fix Released => Fix Committed

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

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released
Status in netplan.io source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,

[Touch-packages] [Bug 1821301] Re: Totem was unable to read a mkv file (video: V_MPEG4/ISO/AVC, audio: A_OPUS)

2019-03-22 Thread Joseph Maillardet

** Attachment added: "English localised mkvinfo of the played video file"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1821301/+attachment/5248401/+files/mkvinfo.txt

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

Title:
  Totem was unable to read a mkv file (video: V_MPEG4/ISO/AVC, audio:
  A_OPUS)

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  I try to read a video with totem, I heard some digital noise (less
  than one second) and only see a black screen. Nothing append after
  that, totem UI work but the video file don't play.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libgstreamer1.0-0 1.15.2-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 09:48:13 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to disco on 2018-11-14 (127 days ago)
  XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'/var/log/Xorg.0.log'

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

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

[Touch-packages] [Bug 1806407] Re: Mobile broadband SIM doesn't work but does on same machine booted into Windows

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

Title:
Mobile broadband SIM doesn't work but does on same machine booted into
Windows

Status in network-manager package in Ubuntu:
Confirmed

Bug description:
I am trying to use a mobile broadband sim with my TabletPC running
Ubuntu 18.04, but it doesn't work, I get: "Connection Failed:
Activation of network connection failed" when trying to connect with
it. HOWEVER, if I boot this same TabletPC into Windows 10, the sim
works fine. So it is not a problem with the SIM nor a problem the
TabletPC hardware. It is a problem with Ubuntu.

Can I ask what testing/Quality Assurance (QA) you did on Ubuntu for
mobile broadband and where your testing records are kept?

Further details here:

https://askubuntu.com/questions/1079689/mobile-broadband-sim-doesnt-work-with-ubuntu-18-04-but-does-work-in-same-device

"I have a Panasonic FZ-G1 MkIII Toughpad touchscreen tablet PC which
is based on an x86-64bit Intel® Core™ i5-5300U CPU @ 2.30GHz, with 4Gb
RAM.

This is dual-booted with Windows 10 Pro 64bit (build 1803) and Ubuntu
18.04.1 LTS 64bit.

The mobile sim is a standard giffgaff sim which works fine in Windows
on this machine - it is recognised and internet access via it works,
detected as LTE (4G). So this proves that the sim is working correctly
with the WLAN modem hardware in this tablet.

However, when the same tablet is booted into Ubuntu 18.04.1 LTS 64bit,
the same sim that worked in the Windows partition, does not work in
Ubuntu. Error message: "Connection Failed: Activation of network
connection failed" pops up when attempting connection via Settings. "

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

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

[Touch-packages] [Bug 1821301] [NEW] Totem was unable to read a mkv file (video: V_MPEG4/ISO/AVC, audio: A_OPUS)

2019-03-22 Thread Joseph Maillardet

Public bug reported:

I try to read a video with totem, I heard some digital noise (less than
one second) and only see a black screen. Nothing append after that,
totem UI work but the video file don't play.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libgstreamer1.0-0 1.15.2-1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 22 09:48:13 2019
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gstreamer1.0
UpgradeStatus: Upgraded to disco on 2018-11-14 (127 days ago)
XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'/var/log/Xorg.0.log'

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


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

** Attachment added: "mkvinfo of the played file"
   
https://bugs.launchpad.net/bugs/1821301/+attachment/5248396/+files/mkvinfo.txt

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

Title:
  Totem was unable to read a mkv file (video: V_MPEG4/ISO/AVC, audio:
  A_OPUS)

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  I try to read a video with totem, I heard some digital noise (less
  than one second) and only see a black screen. Nothing append after
  that, totem UI work but the video file don't play.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libgstreamer1.0-0 1.15.2-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 09:48:13 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to disco on 2018-11-14 (127 days ago)
  XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'/var/log/Xorg.0.log'

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

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

[Touch-packages] [Bug 1806407] Re: Mobile broadband SIM doesn't work but does on same machine booted into Windows

still no luck when i change /etc/NetworkManager/NetworkManager.conf to
bypass system-resolved with

[main]
dns=default

and i already try replace system-resolved with dnsmasq with
NetworkManager.conf

[main]
dns=dnsmasq

still no lock with those things

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

Title:
  Mobile broadband SIM doesn't work but does on same machine booted into
  Windows

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I am trying to use a mobile broadband sim with my TabletPC running
  Ubuntu 18.04, but it doesn't work, I get: "Connection Failed:
  Activation of network connection failed" when trying to connect with
  it. HOWEVER, if I boot this same TabletPC into Windows 10, the sim
  works fine. So it is not a problem with the SIM nor a problem the
  TabletPC hardware. It is a problem with Ubuntu.

  Can I ask what testing/Quality Assurance (QA) you did on Ubuntu for
  mobile broadband and where your testing records are kept?

  
  Further details here:
  
https://askubuntu.com/questions/1079689/mobile-broadband-sim-doesnt-work-with-ubuntu-18-04-but-does-work-in-same-device

  "I have a Panasonic FZ-G1 MkIII Toughpad touchscreen tablet PC which
  is based on an x86-64bit Intel® Core™ i5-5300U CPU @ 2.30GHz, with 4Gb
  RAM.

  This is dual-booted with Windows 10 Pro 64bit (build 1803) and Ubuntu
  18.04.1 LTS 64bit.

  The mobile sim is a standard giffgaff sim which works fine in Windows
  on this machine - it is recognised and internet access via it works,
  detected as LTE (4G). So this proves that the sim is working correctly
  with the WLAN modem hardware in this tablet.

  However, when the same tablet is booted into Ubuntu 18.04.1 LTS 64bit,
  the same sim that worked in the Windows partition, does not work in
  Ubuntu. Error message: "Connection Failed: Activation of network
  connection failed" pops up when attempting connection via Settings. "

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

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

[Touch-packages] [Bug 1806407] Re: Mobile broadband SIM doesn't work but does on same machine booted into Windows

Mar 22 15:46:59 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using
degraded feature set (TCP) for DNS server 112.215.71.243.
Mar 22 15:47:03 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using
degraded feature set (UDP) for DNS server 112.215.198.254.
Mar 22 15:47:05 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using
degraded feature set (UDP) for DNS server 112.215.71.243.
Mar 22 15:47:08 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using
degraded feature set (TCP) for DNS server 112.215.71.243.
Mar 22 15:47:08 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using
degraded feature set (TCP) for DNS server 112.215.198.254.
Mar 22 15:47:14 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using
degraded feature set (UDP) for DNS server 112.215.71.243.
Mar 22 15:47:14 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using
degraded feature set (UDP) for DNS server 112.215.198.254.

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

Title:
Mobile broadband SIM doesn't work but does on same machine booted into
Windows

Status in network-manager package in Ubuntu:
Confirmed

Can I ask what testing/Quality Assurance (QA) you did on Ubuntu for
mobile broadband and where your testing records are kept?

Further details here:

https://askubuntu.com/questions/1079689/mobile-broadband-sim-doesnt-work-with-ubuntu-18-04-but-does-work-in-same-device

"I have a Panasonic FZ-G1 MkIII Toughpad touchscreen tablet PC which
is based on an x86-64bit Intel® Core™ i5-5300U CPU @ 2.30GHz, with 4Gb
RAM.

This is dual-booted with Windows 10 Pro 64bit (build 1803) and Ubuntu
18.04.1 LTS 64bit.

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

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

[Touch-packages] [Bug 1821298] [NEW] Evince with beamer multimedia: video content covers slides

2019-03-22 Thread Giampiero Salvi

Public bug reported:

Hi,
I have been using beamer and the multimedia package for many years to play 
video and audio content in my slides. Until now, the only free viewer that 
could display the material that I am aware of was Okular. However, since Ubuntu 
18.04, okular has become extremely unstable with continuous crashes, so I have 
given another try to Evince.

Evince can display the videos just fine, but unfortunately, when the
video ends, the last frame remains on top of any new slide covering the
slide material. I believe this should be an easy fix. There must be some
cleaning up that needs to be done at the end of the video, or when the
slide is changed that is clearly not performed. For example, if I play
the video and at the same time change slide, the video continues to play
on top.

I am using
Ubuntu 18.04.1
Evince 3.28.4
texlive 2017.20180305-1
kernel 4.15.0-46-generic

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

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

Title:
  Evince with beamer multimedia: video content covers slides

Status in poppler package in Ubuntu:
  New

Bug description:
  Hi,
  I have been using beamer and the multimedia package for many years to play 
video and audio content in my slides. Until now, the only free viewer that 
could display the material that I am aware of was Okular. However, since Ubuntu 
18.04, okular has become extremely unstable with continuous crashes, so I have 
given another try to Evince.

  Evince can display the videos just fine, but unfortunately, when the
  video ends, the last frame remains on top of any new slide covering
  the slide material. I believe this should be an easy fix. There must
  be some cleaning up that needs to be done at the end of the video, or
  when the slide is changed that is clearly not performed. For example,
  if I play the video and at the same time change slide, the video
  continues to play on top.

  I am using
  Ubuntu 18.04.1
  Evince 3.28.4
  texlive 2017.20180305-1
  kernel 4.15.0-46-generic

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

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

[Touch-packages] [Bug 1806407] Re: Mobile broadband SIM doesn't work but does on same machine booted into Windows

in my Ubuntu-MATE 18.04.2, all my three modems after connect to provider but
browser says it cannot Resolve domains. in /var/log/syslog somehow appears
'degraded nameserver' or something. But Wifi connection works smooth. i have
Ubuntu-MATE 16.04.2 and my modems work fine.

How to fix this bug?

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

Title:
Mobile broadband SIM doesn't work but does on same machine booted into
Windows

Status in network-manager package in Ubuntu:
New

Can I ask what testing/Quality Assurance (QA) you did on Ubuntu for
mobile broadband and where your testing records are kept?

Further details here:

https://askubuntu.com/questions/1079689/mobile-broadband-sim-doesnt-work-with-ubuntu-18-04-but-does-work-in-same-device

"I have a Panasonic FZ-G1 MkIII Toughpad touchscreen tablet PC which
is based on an x86-64bit Intel® Core™ i5-5300U CPU @ 2.30GHz, with 4Gb
RAM.

This is dual-booted with Windows 10 Pro 64bit (build 1803) and Ubuntu
18.04.1 LTS 64bit.

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

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

[Touch-packages] [Bug 1806407] Re: Mobile broadband SIM doesn't work but does on same machine booted into Windows