date:20160913

[Touch-packages] [Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel

2016-09-13 Thread Simon Fels

Output of

  sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd

ubuntu@nirvana:~$   sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd
sudo: unable to resolve host nirvana: Connection refused
Failed to connect to bus, trying again in 5s: No such file or directory
timestamp of '/etc/systemd/network' changed
p2p0: Flags change: +MULTICAST +BROADCAST
p2p0: Link 7 added
p2p0: udev initialized link
p2p0: Saved original MTU: 1500
sit0: MAC address not found for new device, continuing without
sit0: Flags change: +NOARP
sit0: Link 6 added
sit0: udev initialized link
sit0: Saved original MTU: 1480
wlan0: Flags change: +MULTICAST +BROADCAST
wlan0: Link 5 added
wlan0: udev initialized link
wlan0: Saved original MTU: 1500
enx00606e43a573: Flags change: +MULTICAST +BROADCAST
enx00606e43a573: Link 4 added
enx00606e43a573: udev initialized link
enx00606e43a573: Saved original MTU: 1500
enp1s0: Flags change: +MULTICAST +BROADCAST
enp1s0: Link 3 added
enp1s0: udev initialized link
enp1s0: Saved original MTU: 1500
dummy0: Flags change: +BROADCAST +NOARP
dummy0: Link 2 added
dummy0: udev initialized link
dummy0: Saved original MTU: 1500
lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING
lo: Link 1 added
lo: udev initialized link
lo: Saved original MTU: 16436
lo: Adding address: ::1/128 (valid forever)
lo: Adding address: 127.0.0.1/8 (valid forever)
Enumeration completed
p2p0: Link state is up-to-date
p2p0: Unmanaged
sit0: Link state is up-to-date
sit0: Unmanaged
wlan0: Link state is up-to-date
wlan0: Unmanaged
enx00606e43a573: Link state is up-to-date
enx00606e43a573: Unmanaged
enp1s0: Link state is up-to-date
enp1s0: found matching network '/etc/systemd/network/enp1s0.network'
enp1s0: Bringing link up
enp1s0: Setting addresses
dummy0: Link state is up-to-date
dummy0: Unmanaged
lo: Link state is up-to-date
lo: Unmanaged
enp1s0: Could not bring up interface: Invalid argument
enp1s0: Updating address: 192.168.178.30/24 (valid forever)
enp1s0: Addresses set
enp1s0: Setting routes
enp1s0: Could not set route: Invalid argument
enp1s0: Routes set

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

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

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

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

[Touch-packages] [Bug 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

2016-09-13 Thread Andreas Pokorny

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

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

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

Title:
  keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

Status in Canonical System Image:
  Confirmed
Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in libertine package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  New
Status in libertine source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server package in Ubuntu RTM:
  New

Bug description:
  [Impact]

  Auto key repeating does not work in Libertine X apps which is very
  frustrating to users.

  [Test Case]

  1. Install xterm in libertine
  2. Start xterm from the "Xapps" scope
  3. Wait for xterm to appear
  4. Press and hold a key

  See how it only appears once and not multiple times as it should.

  [Regression Potential]

  Non observed.

  
  Original Description:

  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

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

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

[Touch-packages] [Bug 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

2016-09-13 Thread Bug Watch Updater

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

** Changed in: gtk
   Importance: Unknown => Medium

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

Title:
  keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

Status in Canonical System Image:
  Confirmed
Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in libertine package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  New
Status in libertine source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server package in Ubuntu RTM:
  New

Bug description:
  [Impact]

  Auto key repeating does not work in Libertine X apps which is very
  frustrating to users.

  [Test Case]

  1. Install xterm in libertine
  2. Start xterm from the "Xapps" scope
  3. Wait for xterm to appear
  4. Press and hold a key

  See how it only appears once and not multiple times as it should.

  [Regression Potential]

  Non observed.

  
  Original Description:

  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

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

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

[Touch-packages] [Bug 1612270] Re: [MIR] qdjango

2016-09-13 Thread Sebastien Bacher

should it be assigned to security team then?

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

Title:
  [MIR] qdjango

Status in qdjango package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8 infographics

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   All dependencies are already in main

  [Standards compliance]
   * This package uses qmake and does not require translations.

  [Maintenance]
   * This package is maintained by Jeremy Laine, upstream in Debian and 
actively in use on the phone images.

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

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

[Touch-packages] [Bug 1614210] Re: Remove incomplete fips in openssl in xenial.

2016-09-13 Thread Marc Deslauriers

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Remove incomplete fips in openssl in xenial.

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Committed
Status in openssl source package in Yakkety:
  Fix Released

Bug description:
  Package: openssl-1.0.2g-1ubuntu4.1
  Distro: xenial

  The openssl contains incomplete fips patches. In light that the fips
  is incomplete and will not be completed in the main archive and they
  are impacting customers, they should be withdrawn. See lp bugs
  1593953, 1591797, 1594748, 1588524, 1613658. Removal of these fips
  patches will remove these fips-related issues.

  [Test case]
  1. Problem in 1594748
  Note: this problem was reported in upstream openssl and testcase posted there 
also.
  https://rt.openssl.org/Ticket/Display.html?id=4559

  CRYPTO_set_mem_functions() always returns 0 because library
  initialization within fips code already calls CRYPTO_malloc() and
  disables it.

  This testcase should cause openssl to abort, but instead it returns a
  context.

  #include 
  #include 
  #include 
  void * my_alloc(size_t n) { abort(); }
  void my_free(void *p) { abort(); }
  void * my_realloc(void *p, size_t n) { abort(); }
  int main(int argc, const char **argv)
  {
    const SSL_METHOD *method;
    SSL_CTX *ctx;
    CRYPTO_set_mem_functions(my_alloc, my_realloc, my_free);
    SSL_library_init();
    method = SSLv23_client_method();
    ctx = SSL_CTX_new(method);
    printf("Got ctx %p\n", ctx);
    return 0;
  }

  2. Problem in 1593953
  EC key generation allows user to generate keys using EC curves that the EC 
sign and verify
  do not support when OPENSSL_FIPS is defined.
  Testcase taken from lp #1593953

  openssl ecparam -genkey -name Oakley-EC2N-4

  will fail when OPENSSL_FIPS is defined since it causes a fips key-pair 
consistency check to be done.
  Otherwise, without OPENSSL_FIPS defined, the check is not done.

  3. Problem reported in 1588524
  Error code being skipped...

  Testcase taken from lp #1588524

  #include 
  #include 

  int main() {
  int rc;
  unsigned long fips_err;
  SSL_library_init();
  SSL_load_error_strings();
  ERR_load_crypto_strings();
  OpenSSL_add_all_algorithms();
  rc = FIPS_mode_set(1);
  fips_err = ERR_peek_last_error();

  // FIPS_mode_set will return 0 on failure, which is expected if
  // the FIPS module is not compiled. In this case, we should then
  // be able to get the error code
  // CRYPTO_R_FIPS_MODE_NOT_SUPPORTED (0xf06d065)
  // https://wiki.openssl.org/index.php/FIPS_mode_set%28%29
  printf("%d %lu\n", rc, fips_err);
  ERR_print_errors_fp(stdout);

  ERR_free_strings();
  return 0;
  }

  Should report an error message.

  [ Regression potential ]
  Removing the fips patches should decrease regression potential of openssl in 
the main archive.

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

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

[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-09-13 Thread Joakim Koed

Scott: Good idea. I will look into that this weekend and see if I can
figure it out :)

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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

[Touch-packages] [Bug 1602737] Re: PCI RoCE Interface could not be renamed from default name with link file

2016-09-13 Thread ChristianEhrhardt

Quickly clarified - that was running on Xenial + kernel mainline ppa.

That means it is nothing in e.g. udev in userspace.

Barbara will try to test 4.5, 4.6 quickly as well.
Only if also 4.5 mainline is good too she will test 4.4 from mainline as well 
(to check if a diff to the xenial 4.4 is causing the issue).

Then I expect it is up to recreating and bisecting on our side?

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

Title:
  PCI RoCE Interface could not be renamed from default name with link
  file

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Helmut Grauer  - 2016-07-13 
09:05:27 ==
  Try to rename PCI Roce Interface with .link file

  root@s35lp02:/etc/systemd/network# cat 10-net.link
  [Match]
  Path=pci-:00:00.0*
  MACAddress=82:01:14:07:85:70

  [Link]
  Name=hug0
  root@s35lp02:/etc/systemd/network#

  do  a reboot and journalctl show old interface name for RoCE PCI
  Interface

  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed from 
eth0
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed from 
eth1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed 
from eth3
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed from 
eth2
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file system 
using the ext4 subsystem
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with 
ordered data mode. Opts: (null)

  udevadm test show the following output

  oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0
  calling: test
  version 229
  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.

  === trie on-disk ===
  tool version:  229
  file size: 6841701 bytes
  header size 80 bytes
  strings1755245 bytes
  nodes  5086376 bytes
  Load module index
  timestamp of '/etc/systemd/network' changed
  Skipping overridden file: /usr/lib/systemd/network/99-default.link.
  Skipping overridden file: /usr/lib/systemd/network/10-net.link.
  Skipping overridden file: /lib/systemd/network/99-default.link.
  Skipping overridden file: /lib/systemd/network/10-net.link.
  Parsed configuration file /etc/systemd/network/99-default.link
  Parsed configuration file /lib/systemd/network/90-mac-for-usb.link
  Parsed configuration file /etc/systemd/network/11-net.link
  Parsed configuration file /etc/systemd/network/10-net.link
  Created link configuration context.
  timestamp of '/etc/udev/rules.d' changed
  Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules
  Reading rules file: /lib/udev/rules.d/40-z90crypt.rules
  Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af06.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af07.rules
  Reading rules file: /etc/udev/rules.d/41-generic-ccw-0.0.0009.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.b100.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.f500.rules
  Reading rules file: /lib/udev/rules.d/50-firmware.rules
  Reading rules file: /lib/udev/rules.d/50-udev-default.rules
  Reading rules file: /lib/udev/rules.d/55-dm.rules
  Reading rules file: /lib/udev/rules.d/55-scsi-sg3_id.rules
  Reading rules file: /lib/udev/rules.d/56-dm-mpath-lvm.rules
  Reading rules file: /lib/udev/rules.d/56-lvm.rules
  Reading rules file: /lib/udev/rules.d/58-scsi-sg3_symlink.rules
  Reading rules file: /lib/udev/rules.d/59-dasd.rules
  Reading rules file: /lib/udev/rules.d/60-block.rules
  Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules
  Reading rules file: /lib/udev/rules.d/60-crda.rules
  Reading rules file: /lib/udev/rules.d/60-drm.rules
  Reading rules file:

[Touch-packages] [Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel

2016-09-13 Thread Martin Pitt

Just to collect all the info, can you please re-run with

  sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd

I assume this is a missing kernel feature (systemd only officially
supports kernels ≤ 2 years old), so we'd need some fallback. Can you
please step through with gdb and figure out which call fails in
particular? I don't immediately see where this comes from --
readlinkat() is only called in some wrapper functions in src/basic/fs-
util.c and copy_tree_at, neither of which are being called by networkd.
So I sugguest to build a debug version with CFLAGS="-g -O0" (from
upstream or the Debian package) and gdb through networkd.

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

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

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

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

[Touch-packages] [Bug 1531622] Re: default config still using a legacy keyword: KLogPermitNonKernelFacility

2016-09-13 Thread Simon Déziel

Xenial debdiff with the proper version number, thanks stgraber.

** Patch removed: "lp1531622-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622/+attachment/4736972/+files/lp1531622-xenial.debdiff

** Patch added: "lp1531622-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622/+attachment/4740141/+files/lp1531622-xenial.debdiff

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

Title:
  default config still using a legacy keyword:
  KLogPermitNonKernelFacility

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  /etc/rsyslog.conf contains:

    $KLogPermitNonKernelFacility on

  But this no longer supported and trigger this log message:

   Jan  5 08:56:16 simon-laptop rsyslogd-: command
  'KLogPermitNonKernelFacility' is currently not permitted - did you
  already set it via a RainerScript command (v6+ config)? [v8.14.0 try
  http://www.rsyslog.com/e/ ]

  Error  is described as "legacy parameter no longer permitted".

  This legacy parameter causes config syntax checks (rsyslogd -N1) to
  fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rsyslog 8.14.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan  6 15:47:15 2016
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logcheck.ignore.d.server.rsyslog: [deleted]

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

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

[Touch-packages] [Bug 1616448] Re: [MIR] qtsensors-opensource-src

2016-09-13 Thread Sebastien Bacher

the source was in main until 15.10 so just need to be repromoted

** Changed in: qtsensors-opensource-src (Ubuntu)
Importance: Undecided => Low

** Changed in: qtsensors-opensource-src (Ubuntu)
Status: New => Invalid

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

Title:
[MIR] qtsensors-opensource-src

Status in qtsensors-opensource-src package in Ubuntu:
Invalid

Bug description:
Availability: In universe, builds for all archs.

Rationale: A goal for Ubuntu 16.10 is to have unity8 installed by
default as an optional session. qtsensors is part of the stack that is
needed for this goal. Qtsensors was already in main earlier when
qtwebkit was, bug #1192567.

Security: No known security history. No daemons or services.

Quality assurance: No bugs open in Debian. A bug about certain tests
failing on builders is in Ubuntu (those tests only work in local
installations and are disabled with a patch). The latest upstream
stable LTS version is part of yakkety and upcoming Debian release. For
yakkety, we will not upgrade to Qt 5.7 but stay with the 5.6 LTS.

Dependencies: All binary dependencies are in main.

Standard compliance: Packaging seems compliant with 1 lintian warning.

Maintenance: Qt Company maintains qtsensors as an official module in
Qt. Qt 5.6 will be supported for bug and security fixes for three
years.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsensors-opensource-src/+bug/1616448/+subscriptions

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

1 2 >

1 - 100 of 155 matches

Mail list logo