[Touch-packages] [Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)

2019-02-26 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [meta-bug] Inverted Internal microphone (phase inversion)

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  This is a metabug for all machines that are having phase inverted
  internal microphones.

  If your internal mic is either completely silent (no signal), or you
  can possibly pick a very small sound, with much background noise, even
  though you have set gain to maximum, there is something you could try.

  Install the pavucontrol application, start it and go to the "Input Devices" 
tab. Unlock the channels (there is a keylock icon), then mute the right channel 
while keeping the left channel at the volume you want.
  If the internal mic is now working correctly, you have an inverted internal 
mic, so that your right channel cancels out the left one.

  (If you're not running PulseAudio, you can try doing the same through
  AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try
  changing "Capture" level or "Internal Mic" or "Internal Mic Boost"
  using the Q,E,Z,C keys.)

  If so, please file a separate bug against the alsa-driver for your
  issue, make sure hardware info gets attached to it (either alsa-info
  as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones
  that follows when you do "ubuntu-bug alsa-driver" ), then write a
  comment in this bug, with your machine name and a pointer to the other
  bug.

  As time permits, I'll try to work on fixing them for the next Ubuntu release. 
Thanks!
   -- David Henningsson

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

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


[Touch-packages] [Bug 1817793] Re: Audio is not switchable through Plasma widgets

2019-02-26 Thread Kai-Heng Feng
** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Audio is not switchable through Plasma widgets

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

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1817666] Re: system hangs

2019-02-26 Thread Daniel van Vugt
Are you able to say what you were/are doing when the system hangs?

Also, does that include the mouse pointer? Or does the mouse pointer
still move?

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Summary changed:

- system hangs
+ [nouveau] system hangs

** Tags added: nouveau

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

Title:
  [nouveau] system hangs

Status in xorg-server package in Ubuntu:
  New

Bug description:
  i dont know

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-79.100~14.04.1-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Feb 26 12:19:26 2019
  DistUpgraded: 2016-11-14 14:16:19,712 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
   NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 
[VGA controller])
  InstallationDate: Installed on 2016-11-12 (835 days ago)
  InstallationMedia: Edubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803.1)
  MachineType: LENOVO 20157
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic 
root=UUID=3006e45f-5f40-45c8-a376-3b9473cb4f8b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2016-11-14 (833 days ago)
  dmi.bios.date: 02/01/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 62CN44WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake 2
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr62CN44WW:bd02/01/2013:svnLENOVO:pn20157:pvrLenovoG580:rvnLENOVO:rnEmeraldLake2:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.name: 20157
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Feb 26 09:04:52 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16978 
   vendor SEC
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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


[Touch-packages] [Bug 1817617] Re: Video driver

2019-02-26 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (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/1817617

Title:
  Video driver

Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid

Bug description:
  ~apt-get install xserver-xorg-vt-get install xserver-xorg-video-intel
  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:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Feb 25 17:05:43 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.18.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2019-02-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 3442
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0P8H6J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1817617/+subscriptions

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


[Touch-packages] [Bug 1817391] Re: [Acer Aspire XC-603] Audio stuttering

2019-02-26 Thread Daniel van Vugt
Your system has a modified config file here:

https://launchpadlibrarian.net/412444169/modified.conffile..etc.modprobe.d
.alsa-base.conf.txt

--- /etc/modprobe.d/alsa-base.conf  2015-07-31 11:42:17.0 +0800
+++ Downloads/modified.conffile..etc.modprobe.d.alsa-base.conf.txt  
2019-02-27 10:26:15.241596972 +0800
@@ -41,3 +41,4 @@
 options snd-pcsp index=-2
 # Keep snd-usb-audio from beeing loaded as first soundcard
 options snd-usb-audio index=-2
+options snd-hda-intel position_fix=2

but I don't know if that's relevant to this bug. In case it is then
please try commenting out the line:

  options snd-hda-intel position_fix=2

by changing it to:

  #options snd-hda-intel position_fix=2

and reboot.

As for testing other flavours, that's not the same as testing other
versions. Please follow the links in comment #3, boot each of the live
sessions and tell us if they exhibit the same bug.

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

Title:
  [Acer Aspire XC-603] Audio stuttering

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Since installing Ubuntu 18.10 on my system which previously had
  windows 10 I now get an intermittent stutter or hiccup for want of a
  better word. It happens in Firefox Quantum and Chrome/Chromium I have
  tried a number of fixes from you tube and various forums, but it still
  happens and I'm at my wits end as it is so random.

  My system is a Acer Aspire XC-603

  1tb HDD
  4gb ram
  Intel Celeron J1900 @ 1.99 GHz

  The sound card is integrated on the mother board

  HDA-Intell-HDA intel PCH this problem is so random i never know when
  its going to happen some times it does it one sometimes multiple
  times.

  I'm totally at a loss

  Can any one help ? I'm relatively new to this

  I'm unable to locate the package version

  I expected a clean audio output without any bugs and I'm getting
  hiccups and stuttering

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 5045 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 23 16:10:25 2019
  InstallationDate: Installed on 2019-02-22 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-B1
  dmi.board.name: Aspire XC-603
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-B1:bd06/16/2014:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Aspire XC-603
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-02-23T12:07:26.743044

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

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


[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument

2019-02-26 Thread utnubudnai
ubuntu 16.04, hit the same issue as this. swapon -v shows these:

```
swapon: /my/swap: found swap signature: version 1d, page-size 4, same byte order
swapon: /my/swap: pagesize=4096, swapsize=13..., devsize=13
swapon: /my/swap: swapon failed: Invalid argument
```

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

Title:
  swapon failed: invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Environment:
   - Ubuntu 18.04.1 LTS
   - Linux 4.15.0-32-generic i686

  Description:
  When I try to mount my swap partition or my swap file, I get "swapon failed: 
invalid argument" .

  Steps to reproduce:
  1) sudo bash
  2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
  3) mkswap /swapfile
  4) chown root:root /swapfile
  5) chmod 0600 /swapfile
  6) swapon /swapfile
  Last execution returns "swapon failed: invalid argument" .

  I'm almost sure it's a bug because I have no problems using Linux
  4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
  problems using Ubuntu 18.04.1 LTS Live CD.

  Regards.

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

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


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

2019-02-26 Thread Brian Murray
Hello Kaj, or anyone else affected,

Accepted pulseaudio into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1758736

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Committed
Status in pulseaudio source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * User is only able to get mono audio from steelseries headsets
  because they provide both a stereo and mono output.  PA selects the
  mono output by default.

   * This should be backported to stable releases because this fix is 
 isolated to code that only applies to the affected headsets.  
 Additionally other gaming headsets may be more easily enabled by adding 
  ATTRS{idVendor}=="", ATTRS{idProduct}=="", 
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
 to /lib/udev/rules.d/90-pulseaudio.rules now.  Such as the Lucidsound 
 LS31 which I own.

   * The upload fixes the bug by conditionally setting a pulseaudio
  profile for the headset based on specific usb vendor and product ids
  in the udev rules.

  [Test Case]

   1. Acquire headset.
   2. Open sound settings, and click test speakers.
   3. Only option available will be mono sound

  [Regression Potential]

   * Risk of regressions should be mitigated to those who own the
  headset.  In which case it is likely that their headset is already not
  working.

  [Other Info]
   
   * All patches originate from upstream pulseaudio, and are documented as
 such including the shas.
   
   * I will be pursuing enabling other similar headsets in the coming weeks.
   * I plan to work with upstream pulseaudio to enable my own headset and to
 also make the headset templates backported here more generic.

  
   Original Description -

  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.pr

[Touch-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

2019-02-26 Thread Brian Murray
Hello Kaj, or anyone else affected,

Accepted pulseaudio into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:12.2-0ubuntu5 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: pulseaudio (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: pulseaudio (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Committed
Status in pulseaudio source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * User is only able to get mono audio from steelseries headsets
  because they provide both a stereo and mono output.  PA selects the
  mono output by default.

   * This should be backported to stable releases because this fix is 
 isolated to code that only applies to the affected headsets.  
 Additionally other gaming headsets may be more easily enabled by adding 
  ATTRS{idVendor}=="", ATTRS{idProduct}=="", 
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
 to /lib/udev/rules.d/90-pulseaudio.rules now.  Such as the Lucidsound 
 LS31 which I own.

   * The upload fixes the bug by conditionally setting a pulseaudio
  profile for the headset based on specific usb vendor and product ids
  in the udev rules.

  [Test Case]

   1. Acquire headset.
   2. Open sound settings, and click test speakers.
   3. Only option available will be mono sound

  [Regression Potential]

   * Risk of regressions should be mitigated to those who own the
  headset.  In which case it is likely that their headset is already not
  working.

  [Other Info]
   
   * All patches originate from upstream pulseaudio, and are documented as
 such including the shas.
   
   * I will be pursuing enabling other similar headsets in the coming weeks.
   * I plan to work with upstream pulseaudio to enable my own headset and to
 also make the headset templates backported here more generic.

  
   Original Description -

  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chass

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

2019-02-26 Thread William Grant
** Attachment removed: "job-vs-career-og.png"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721223/+attachment/5241750/+files/job-vs-career-og.png

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

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

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

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

  Below steps to replicate the issue.

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

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

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

  We check directly from console the network interface setting with the
  tool ip, checking continuously the value for i

[Touch-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2019-02-26 Thread Theo Linkspfeifer
No changes were made to xubuntu-core and xubuntu-desktop yet, so the bug
is obviously not fixed yet. However, the part regarding xfce4-session
was fixed (should not pull in xscreensaver anymore).

** Changed in: xfce4-session (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: openjpa (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in openjpa package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in sitemesh package in Ubuntu:
  New
Status in snakeyaml package in Ubuntu:
  New
Status in trove3 package in Ubuntu:
  New
Status in uimaj package in Ubuntu:
  New
Status in unsafe-mock package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in writer2latex package in Ubuntu:
  New
Status in xmlbeans package in Ubuntu:
  New
Status in zeroc-ice package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in 

Re: [Touch-packages] [Bug 1817391] Re: Audio stuttering

2019-02-26 Thread Andrew Crome
Hi

all the suggestions that have been offered I have tried no changes were 
made as far as I know, I tried other flavours  all do the same !

On 25/2/19 1:16 pm, Daniel van Vugt wrote:
> It seems you have made some changes to the sound configuration, so can
> you please first try live booting:
>
>http://releases.ubuntu.com/18.10/
>
> and 19.04:
>
>http://cdimages.ubuntu.com/daily-live/current/
>
> then tell us if they have the same problem in a live session?
>
> ** Also affects: pulseaudio (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Summary changed:
>
> - Audio stuttering
> + [Acer Aspire XC-603] Audio stuttering
>
> ** Changed in: alsa-driver (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: pulseaudio (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  [Acer Aspire XC-603] Audio stuttering

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Since installing Ubuntu 18.10 on my system which previously had
  windows 10 I now get an intermittent stutter or hiccup for want of a
  better word. It happens in Firefox Quantum and Chrome/Chromium I have
  tried a number of fixes from you tube and various forums, but it still
  happens and I'm at my wits end as it is so random.

  My system is a Acer Aspire XC-603

  1tb HDD
  4gb ram
  Intel Celeron J1900 @ 1.99 GHz

  The sound card is integrated on the mother board

  HDA-Intell-HDA intel PCH this problem is so random i never know when
  its going to happen some times it does it one sometimes multiple
  times.

  I'm totally at a loss

  Can any one help ? I'm relatively new to this

  I'm unable to locate the package version

  I expected a clean audio output without any bugs and I'm getting
  hiccups and stuttering

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 5045 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 23 16:10:25 2019
  InstallationDate: Installed on 2019-02-22 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-B1
  dmi.board.name: Aspire XC-603
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-B1:bd06/16/2014:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Aspire XC-603
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-02-23T12:07:26.743044

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

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


[Touch-packages] [Bug 1817799] [NEW] [FFe] apparmor 2.13

2019-02-26 Thread Jamie Strandboge
Public bug reported:

TODO

** Affects: apparmor (Ubuntu)
 Importance: Undecided
 Assignee: Jamie Strandboge (jdstrand)
 Status: In Progress

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

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

Title:
  [FFe] apparmor 2.13

Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  TODO

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

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


[Touch-packages] [Bug 1809909] Re: package apport 2.20.1-0ubuntu2.18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239.

2019-02-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package apport 2.20.1-0ubuntu2.18 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 239.

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Happened while upgrading via apt.
  apport did not upgrade, gave a segmentation fault.

  Now, the OS (Ubuntu 16.04.5 LTS) does not even boot sometimes.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.18
  ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CrashReports:
   640:0:116:406436:2018-12-27 20:44:57.411726236 +0530:2018-12-27 
20:44:58.411726236 +0530:/var/crash/_usr_lib_xorg_Xorg.0.crash
   600:0:116:454368:2018-12-26 23:50:15.102489948 +0530:2018-12-26 
23:50:16.102489948 +0530:/var/crash/apport.0.crash
  Date: Wed Dec 26 23:50:15 2018
  DuplicateSignature:
   package:apport:2.20.1-0ubuntu2.18
   Installing new version of config file /etc/init/apport.conf ...
   Segmentation fault
   dpkg: error processing package apport (--configure):
subprocess installed post-installation script returned error exit status 239
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 239
  InstallationDate: Installed on 2018-12-26 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.18 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 239
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1798861] Re: Tooltips flicker constantly in GTK3 applications

2019-02-26 Thread Jeremy Bicha
The fix for this has completed verification and is rolling out as an
update to Ubuntu 18.10 computers over the next few days.

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

Title:
  Tooltips flicker constantly in GTK3 applications

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Cosmic:
  Fix Released
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  Tooltips are flicker constantly (i.e. repeatedly shown and the hidden
  again) in GTK3 applications under XFCE.

  It is a regression in the recent GTK 3.24.

  This is the upstream report and fix:
  https://gitlab.gnome.org/GNOME/gtk/issues/1371
  
https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2

  A workaround for XFCE is as follows:

  Open Settings Editor.
  Set xsettings -> Gtk -> CursorThemeSize to 16.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgtk-3-0 3.24.1-1ubuntu2
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Oct 19 12:23:53 2018
  InstallationDate: Installed on 2017-02-01 (624 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1798861/+subscriptions

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


[Touch-packages] [Bug 1683428] Re: read_csv on bzip2 file unzips only the first block

2019-02-26 Thread Rebecca Palmer
('invalid' = 'not our (pandas') bug')

As noted in the linked upstream bug, this only affects Python 2 (python-
pandas), not current Python 3 (python3-pandas).

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

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

Title:
  read_csv on bzip2 file unzips only the first block

Status in pandas package in Ubuntu:
  Invalid
Status in python2.7 package in Ubuntu:
  Won't Fix

Bug description:
  It seems that the read_csv() suffers the same symptoms as eg the early
  boost implementations, see
  https://svn.boost.org/trac/boost/ticket/3853 for details. The bz2
  files can namely be composed of many concatenated bz2 blocks which
  have to be treated as a continuous stream.

  How to test: create large csv file, much larger than 900k. Compress
  with pbzip2 (each process creates one bz2 block). Alternatively create
  many such csv files, bzip2 them individually and then cat *.bz2
  >joined.bz2

  read_csv() will uncompress and read only the first block.

  Note that this is a severe bug since the parallel bzip2 is getting
  increasingly common on multi-core systems.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: python-pandas 0.17.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Apr 17 18:42:52 2017
  InstallationDate: Installed on 2014-10-21 (909 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: pandas
  UpgradeStatus: Upgraded to yakkety on 2016-10-20 (179 days ago)

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

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


[Touch-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2019-02-26 Thread Norbert
Bug still exists. Simple installation of Xubuntu Desktop on top of 19.04
(disco) mini.iso with `sudo apt install xubuntu-desktop` results in long
list of unwanted GNOME packages.

I have created two outputs of `dpkg -l` before (mini.iso) and after
xubuntu-desktop installation.


$ diff before after  | grep gnome | awk '{print $3}'
language-pack-gnome-en
language-pack-gnome-en-base
libsoup-gnome2.4-1:amd64
gir1.2-gnomebluetooth-1.0:amd64
gir1.2-gnomedesktop-3.0:amd64
gkbd-capplet
gnome-accessibility-themes
gnome-bluetooth
gnome-control-center
gnome-control-center-data
gnome-control-center-faces
gnome-desktop3-data
gnome-font-viewer
gnome-icon-theme
gnome-keyring
gnome-keyring-pkcs11:amd64
gnome-menus
gnome-mines
gnome-online-accounts
gnome-power-manager
gnome-screensaver
gnome-session-bin
gnome-session-common
gnome-settings-daemon
gnome-settings-daemon-common
gnome-shell
gnome-shell-common
gnome-software
gnome-software-common
gnome-software-plugin-snap
gnome-startup-applications
gnome-sudoku
gnome-system-tools
gnome-themes-extra:amd64
gnome-themes-extra-data
gnome-themes-standard
gnome-user-docs
language-pack-gnome-en
language-pack-gnome-en-base
language-selector-gnome
libgnome-bluetooth13:amd64
libgnome-desktop-3-17:amd64
libgnome-games-support-1-3:amd64
libgnome-games-support-common
libgnome-menu-3-0:amd64
libgnomekbd-common
libgnomekbd8:amd64
libpam-gnome-keyring:amd64
libreoffice-gnome
libsoup-gnome2.4-1:amd64
network-manager-gnome
network-manager-pptp-gnome
pinentry-gnome3
policykit-1-gnome
yaru-theme-gnome-shell


and unity:

$ diff before after  | grep unity | awk '{print $3}'
libmeanwhile1:amd64
libunity-control-center1
libunity-protocol-private0:amd64
libunity-scopes-json-def-desktop
libunity-settings-daemon1:amd64
libunity9:amd64
unity-control-center
unity-greeter
unity-settings-daemon
xubuntu-community-wallpapers
xubuntu-community-wallpapers-bionic
yaru-theme-gnome-shell

So user still can't simply install Xubuntu on top of minimal system.

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1799913] Re: Unhandled lockdown error (-2) - iphone ios 12

2019-02-26 Thread Oliver Kamer
I have the same issue,  but I just double checked, it works on my
machine with bionic, the problem only arises on my cosmic machine.

iPad version: 12.1.4
works with 18.04.01 LTS
doesn't work on 18.10

If anyone has any ideas for me to try, please let me know, I'm happy to
try.

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

Title:
  Unhandled lockdown error (-2) - iphone ios 12

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on 
the Documents in the file manager, I got this error: Unhandled lockdown error 
(-2). 
  I attached a screenshot about this error.

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

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


[Touch-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2019-02-26 Thread Norbert
** Changed in: xfce4-session (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1817627] Re: systemd-analyze verify reports failure

2019-02-26 Thread Sebastien Bacher
The commit fixing the issue is
https://github.com/systemd/systemd/commit/114110cd

Could you describe why you think it's an issue important enough to
justify a stable update, it seems only a warning but not having
consequences? Do you use a real mount for the /tmp directory?

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

Title:
  systemd-analyze verify reports failure

Status in Ubuntu Manpage Repository:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Version 237 and 238 of systemd-analyze have a known issue:
  https://github.com/systemd/systemd/issues/8592

  When will a fix be posted?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manpage-repository/+bug/1817627/+subscriptions

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


[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted maven-jaxb2-plugin into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/maven-
jaxb2-plugin/0.14.0-1~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: maven-jaxb2-plugin (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsa

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** No longer affects: graxxia (Ubuntu)

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in sitemesh package in Ubuntu:
  New
Status in snakeyaml package in Ubuntu:
  New
Status in trove3 package in Ubuntu:
  New
Status in uimaj package in Ubuntu:
  New
Status in unsafe-mock package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in writer2latex package in Ubuntu:
  New
Status in xmlbeans package in Ubuntu:
  New
Status in zeroc-ice package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source pa

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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted maven-plugin-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/maven-
plugin-tools/3.5-6ubuntu1~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.

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp

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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted maven-enforcer into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/maven-
enforcer/3.0.0~M2-1~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: maven-plugin-tools (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam pack

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted maven-bundle-plugin into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/maven-bundle-plugin/3.5.1-2~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: maven-bundle-plugin (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: maven-enforcer (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx packa

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: zeroc-ice (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in graxxia package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in sitemesh package in Ubuntu:
  New
Status in snakeyaml package in Ubuntu:
  New
Status in trove3 package in Ubuntu:
  New
Status in uimaj package in Ubuntu:
  New
Status in unsafe-mock package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in writer2latex package in Ubuntu:
  New
Status in xmlbeans package in Ubuntu:
  New
Status in zeroc-ice package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status i

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

2019-02-26 Thread Eric Desrochers
Don van der Haghen (donvdh),

Seems like you need a sponsor. If I sponsor the patch for you, will you
be amenable to test the packages once found in $RELEASE-proposed ?

If cosmic is impacted, could you also please provide a debdiff for it,
before I proceed.

Regards,
Eric

** Tags added: sts

** Changed in: pam (Ubuntu Bionic)
 Assignee: (unassigned) => Don van der Haghen (donvdh)

** Changed in: pam (Ubuntu Xenial)
 Assignee: (unassigned) => Don van der Haghen (donvdh)

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

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

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

Title:
  pam_tty_audit failed in pam_open_session

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Xenial:
  In Progress
Status in pam source package in Bionic:
  In Progress
Status in pam package in Debian:
  Fix Released

Bug description:
  Dear Maintainer.

  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2

  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2

  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting 
current audit status: Invalid argument
  May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot 
make/remove an entry for the specified session
  May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: 
disconnected by user

  -- syslog --
  May 18 14:47:03 vm audispd: node=vm type=USER_ACCT 
msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): 
pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1
  May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE 
msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set 
old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0
  May 18 14:47:03 vm audispd: node=vm type=USER_START 
msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=failed'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_DISP 
msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'

  Thanks regards.

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

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


[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

2019-02-26 Thread Eric Desrochers
and could you please fill the SRU template ?
https://wiki.ubuntu.com/StableReleaseUpdates

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

Title:
  pam_tty_audit failed in pam_open_session

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Xenial:
  In Progress
Status in pam source package in Bionic:
  In Progress
Status in pam package in Debian:
  Fix Released

Bug description:
  Dear Maintainer.

  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2

  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2

  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting 
current audit status: Invalid argument
  May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot 
make/remove an entry for the specified session
  May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: 
disconnected by user

  -- syslog --
  May 18 14:47:03 vm audispd: node=vm type=USER_ACCT 
msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): 
pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1
  May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE 
msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set 
old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0
  May 18 14:47:03 vm audispd: node=vm type=USER_START 
msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=failed'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_DISP 
msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'

  Thanks regards.

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

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


[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot

2019-02-26 Thread Matt P
Okay.  I guess I would have expected that if there was a dependency on a
specific kernel version, that I wouldn't be able to install a package
that wasn't compatible and breaks the system by installing a security
update.  It would be preferable to be informed there is a security
update but that I can't install it because I am running an out of date
kernel...then I know I am insecure and that the kernel is the issue.
But I guess that is a topic for the package management guys.  The error
message from systemd-tmpfiles about too many symlinks isn't particularly
helpful either since in this case the problem (apparently) has nothing
to do with symlinks but rather filesystem apis in the old kernel (I
guess?).

Yes of course I can contact the hosting provider and ask them to provide
an updated kernel and the likely result may be that I just have to use
an alternate provider if I want this to work.  Perhaps I should anyway
since the hosting provider having such old kernels isn't a good sign.

I also saw this comment:
https://github.com/systemd/systemd/commit/6a89d671dfdd92c0b1b703d7fcb5b0551cafb570

For now I have worked around this issue by just updating the paths to
point to /run instead of /var/run so systemd-tmpfiles doesn't barf on
the symlinks.

sed -i -e 's;/var/run;/run;g' /usr/lib/tmpfiles.d/*.conf

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

Title:
  systemd fails to start sshd at reboot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  So far reported issues turned out to be:
  - obsolete/buggy/vulnerable 3rd party provided kernels
  - bad permissions on /

  Please ensure / is owned by root:root.
  Please ensure you are running up to date kernels.

  
  ===

  Ubuntu 16.04.5, systemd 229-4ubuntu21.15

  The latest systemd update has somehow changed the method it uses to
  start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if
  /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and
  /var/run/sshd/ does not already exist. Being as this is the default,
  virtually EVERY Ubuntu 16.04 server in the world has
  UsePrivilegeSeparation set to yes. Furthermore, at the time when the
  user performs 'apt upgrade' and receives the newest version of
  systemd, /var/run/sshd/ already exists, so sshd successfully reloads
  for as long as the server doesn't get rebooted. BUT, as soon as the
  server is rebooted for any reason, /var/run/sshd/ gets cleaned away,
  and sshd fails to start, causing the remote user to be completely
  locked out of his system. This is a MAJOR issue for millions of VPS
  servers worldwide, as they are all about to get locked out of their
  servers and potentially lose data. The next reboot is a ticking time
  bomb waiting to spring. The bomb can be defused by implicitly setting
  'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however
  unsuspecting administrators are bound to be caught out by the
  millions. I got caught by it in the middle of setting up a new server
  yesterday, and it took a whole day to find the source.

  The appropriate fix would be to ensure that systemd can successfully
  'start ssh.service' even when 'UsePrivilegeSeparation yes' is set.
  systemd needs to test that /var/run/sshd/ exists before starting sshd,
  just as the init.d script for sshd does. openssl could also be patched
  so that UsePrivilegeSeparation is no longer enabled by default,
  however that is not going to solve the problem for millions of pre-
  existing config files. Only an update to openssl to force-override
  that flag to 'no' would solve the problem. Thus systemd still needs to
  be responsible for ensuring that it inits sshd properly by ensuring
  that /var/run/sshd/ exists before it sends the 'start' command.

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

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


[Touch-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white

2019-02-26 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.22.30-1ubuntu2

---
gtk+3.0 (3.22.30-1ubuntu2) bionic; urgency=medium

  * Cherry-pick Force-emoji-presentation.patch:
- Ensure that all emoji from the emoji chooser use emoji presentation
  instead of the black-and-white text presentation (LP: #1807719)
  * Cherry-pick emojichooser-Pass-chooser-to-add_emoji.patch:
- Fix variant selector in emoji chooser (LP: #1807721)
  * Update Vcs fields for ubuntu/bionic branch

 -- Jeremy Bicha   Mon, 10 Dec 2018 13:39:31 -0500

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Released
Status in gtk+3.0 source package in Cosmic:
  Fix Released

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

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

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked
  in LP: #1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+subscriptions

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


[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: bindex (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gatk-native-bindings (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Also affects: jackson-module-jaxb-annotations (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: jameica-datasource (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: jboss-jdeparser2 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: jboss-modules (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libxml-security-java (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in graxxia package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in 

[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser

2019-02-26 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.22.30-1ubuntu2

---
gtk+3.0 (3.22.30-1ubuntu2) bionic; urgency=medium

  * Cherry-pick Force-emoji-presentation.patch:
- Ensure that all emoji from the emoji chooser use emoji presentation
  instead of the black-and-white text presentation (LP: #1807719)
  * Cherry-pick emojichooser-Pass-chooser-to-add_emoji.patch:
- Fix variant selector in emoji chooser (LP: #1807721)
  * Update Vcs fields for ubuntu/bionic branch

 -- Jeremy Bicha   Mon, 10 Dec 2018 13:39:31 -0500

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Released
Status in gtk+3.0 source package in Cosmic:
  Fix Released

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

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

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

  Other Info
  ==
  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: 
#1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+subscriptions

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


[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Olivier Tilloy
** Also affects: libreoffice (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libreoffice-l10n (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in graxxia package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in sitemesh package in Ubuntu:
  New
Status in snakeyaml package in Ubuntu:
  New
Status in trove3 package in Ubuntu:
  New
Status in uimaj package in Ubuntu:
  New
Status in unsafe-mock package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in writer2latex package in Ubuntu:
  New
Status in xmlbeans package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper sourc

[Touch-packages] [Bug 1807719] Update Released

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

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Released

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

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

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked
  in LP: #1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+subscriptions

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


[Touch-packages] [Bug 1807721] Update Released

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

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Released

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

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

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

  Other Info
  ==
  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: 
#1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+subscriptions

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


[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser

2019-02-26 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.24.4-0ubuntu1

---
gtk+3.0 (3.24.4-0ubuntu1) cosmic; urgency=medium

  * New upstream release (LP: #1808233)
- Ensure that all emoji from the emoji chooser use emoji presentation
  instead of the black-and-white text presentation (LP: #1807719)
- Fix variant selector in emoji chooser (LP: #1807721)
  * debian/libgtk-3-0.symbols: Add new symbols
  * Add patches to revert late changes that broke our build tests
- Revert-update-some-a11y-test-results.patch
- Revert-Update-a11-test-output.patch
  * Drop wayland-Avoid-crashes-inside-wl_proxy_marshal.patch:
- Applied in new release
  * Update Vcs fields for ubuntu/cosmic branch

 -- Jeremy Bicha   Mon, 21 Jan 2019 12:13:24 -0500

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Released

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

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

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

  Other Info
  ==
  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: 
#1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+subscriptions

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


[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.4

2019-02-26 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.24.4-0ubuntu1

---
gtk+3.0 (3.24.4-0ubuntu1) cosmic; urgency=medium

  * New upstream release (LP: #1808233)
- Ensure that all emoji from the emoji chooser use emoji presentation
  instead of the black-and-white text presentation (LP: #1807719)
- Fix variant selector in emoji chooser (LP: #1807721)
  * debian/libgtk-3-0.symbols: Add new symbols
  * Add patches to revert late changes that broke our build tests
- Revert-update-some-a11y-test-results.patch
- Revert-Update-a11-test-output.patch
  * Drop wayland-Avoid-crashes-inside-wl_proxy_marshal.patch:
- Applied in new release
  * Update Vcs fields for ubuntu/cosmic branch

 -- Jeremy Bicha   Mon, 21 Jan 2019 12:13:24 -0500

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  Update gtk to 3.24.4

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Released

Bug description:
  Impact
  ==
  There is a new release in the stable 3.24 series.

  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721
  and the Xfce flickering fix from LP: #1798861.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
  https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.4

  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.

  Make sure that GTK switches look OK.

  We will also be checking Xfce to validate the fix for LP: #1798861.

  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.

  I believe this is the second time in recent history that we've pushed
  a gtk point release as an SRU. The other example was 3.22.25 for
  Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu
  18.04 LTS since it already included 3.22.30, the final 3.22 release.
  It hasn't been practical to update 18.04's gtk to  the 3.24 series
  (bumped dependencies are one problem).

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

  By the way, pre-release gtk3 is actually getting a bit more testing
  than a year ago since more developers and users are using development
  Flatpak releases of popular GNOME apps. (On the other hand, there were
  a few regressions in the 3.24.2 and 3.24.3 releases.)

  This update changes the ON/OFF switches for GNOME's default Adwaita
  theme to use ❙/○ for all languages (or ⏽/⭘ if they are supported in a
  font you have installed: currently, that's fonts-symbola which we no
  longer install by default). Previously, it was ❙/○ for most languages
  but ON/OFF for English (because English has short words that could fit
  on a switch). This doesn't affect default Ubuntu 18.10 which uses Yaru
  which doesn't use labels on its switches. This is technically a UI
  change, but it is useful for compatibility with Flatpak apps that are
  being built with the new GTK. This change is small enough that it
  could be reverted for Ubuntu 18.10 if necessary.

  Other Info
  ==
  The commit history shows themeing changes to the GNOME default themes 
(Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes 
were reverted for this release to make it easier for distros like us to push 
the update to our stable release.

  The next scheduled gtk3 release (3.24.5 ? in March?) will include
  those changes. See https://blog.gtk.org/2019/01/14/theme-changes-in-
  gtk-3/ for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+subscriptions

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


[Touch-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white

2019-02-26 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.24.4-0ubuntu1

---
gtk+3.0 (3.24.4-0ubuntu1) cosmic; urgency=medium

  * New upstream release (LP: #1808233)
- Ensure that all emoji from the emoji chooser use emoji presentation
  instead of the black-and-white text presentation (LP: #1807719)
- Fix variant selector in emoji chooser (LP: #1807721)
  * debian/libgtk-3-0.symbols: Add new symbols
  * Add patches to revert late changes that broke our build tests
- Revert-update-some-a11y-test-results.patch
- Revert-Update-a11-test-output.patch
  * Drop wayland-Avoid-crashes-inside-wl_proxy_marshal.patch:
- Applied in new release
  * Update Vcs fields for ubuntu/cosmic branch

 -- Jeremy Bicha   Mon, 21 Jan 2019 12:13:24 -0500

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Released

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

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

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked
  in LP: #1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+subscriptions

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


[Touch-packages] [Bug 1808233] Update Released

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

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

Title:
  Update gtk to 3.24.4

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Released

Bug description:
  Impact
  ==
  There is a new release in the stable 3.24 series.

  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721
  and the Xfce flickering fix from LP: #1798861.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
  https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.4

  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.

  Make sure that GTK switches look OK.

  We will also be checking Xfce to validate the fix for LP: #1798861.

  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.

  I believe this is the second time in recent history that we've pushed
  a gtk point release as an SRU. The other example was 3.22.25 for
  Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu
  18.04 LTS since it already included 3.22.30, the final 3.22 release.
  It hasn't been practical to update 18.04's gtk to  the 3.24 series
  (bumped dependencies are one problem).

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

  By the way, pre-release gtk3 is actually getting a bit more testing
  than a year ago since more developers and users are using development
  Flatpak releases of popular GNOME apps. (On the other hand, there were
  a few regressions in the 3.24.2 and 3.24.3 releases.)

  This update changes the ON/OFF switches for GNOME's default Adwaita
  theme to use ❙/○ for all languages (or ⏽/⭘ if they are supported in a
  font you have installed: currently, that's fonts-symbola which we no
  longer install by default). Previously, it was ❙/○ for most languages
  but ON/OFF for English (because English has short words that could fit
  on a switch). This doesn't affect default Ubuntu 18.10 which uses Yaru
  which doesn't use labels on its switches. This is technically a UI
  change, but it is useful for compatibility with Flatpak apps that are
  being built with the new GTK. This change is small enough that it
  could be reverted for Ubuntu 18.10 if necessary.

  Other Info
  ==
  The commit history shows themeing changes to the GNOME default themes 
(Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes 
were reverted for this release to make it easier for distros like us to push 
the update to our stable release.

  The next scheduled gtk3 release (3.24.5 ? in March?) will include
  those changes. See https://blog.gtk.org/2019/01/14/theme-changes-in-
  gtk-3/ for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+subscriptions

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


[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: mckoisqldb (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: jameica-util (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in snakeyaml package in Ubuntu:
  New
Status in trove3 package in Ubuntu:
  New
Status in uimaj package in Ubuntu:
  New
Status in unsafe-mock package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in writer2latex package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fi

Re: [Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot

2019-02-26 Thread Steve Langasek
On Tue, Feb 26, 2019 at 02:39:55PM -, Matt P wrote:

> Anyway, root cause seems to be this systemd-tmpfiles error.  Tmpfile gets
> purged at reboot and doesn't get recreated.

> Seems pretty major that applying security updates would lock you out of
> your server.  If I didn't happen to have a serial console with this
> particular VPS provider (some others I use don't provide one)...I would
> have no idea what was going on.

> I get this might be due to weird openvz image or older kernel...but
> these ubuntu openvz images are very common.

As per
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/comments/14
you must have at least 042stab134.7 installed.  Your comment shows that you
have 042sta120.18 installed.  You will need to contact your hosting provider
about updating.

Given that an updated kernel exists, we do not intend to reduce security for
all other Ubuntu users on account of hosting providers who are both running
Ubuntu container guests on top of an unsupported non-Ubuntu kernel, *and*
are not keeping their kernel up to date.

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

Title:
  systemd fails to start sshd at reboot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  So far reported issues turned out to be:
  - obsolete/buggy/vulnerable 3rd party provided kernels
  - bad permissions on /

  Please ensure / is owned by root:root.
  Please ensure you are running up to date kernels.

  
  ===

  Ubuntu 16.04.5, systemd 229-4ubuntu21.15

  The latest systemd update has somehow changed the method it uses to
  start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if
  /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and
  /var/run/sshd/ does not already exist. Being as this is the default,
  virtually EVERY Ubuntu 16.04 server in the world has
  UsePrivilegeSeparation set to yes. Furthermore, at the time when the
  user performs 'apt upgrade' and receives the newest version of
  systemd, /var/run/sshd/ already exists, so sshd successfully reloads
  for as long as the server doesn't get rebooted. BUT, as soon as the
  server is rebooted for any reason, /var/run/sshd/ gets cleaned away,
  and sshd fails to start, causing the remote user to be completely
  locked out of his system. This is a MAJOR issue for millions of VPS
  servers worldwide, as they are all about to get locked out of their
  servers and potentially lose data. The next reboot is a ticking time
  bomb waiting to spring. The bomb can be defused by implicitly setting
  'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however
  unsuspecting administrators are bound to be caught out by the
  millions. I got caught by it in the middle of setting up a new server
  yesterday, and it took a whole day to find the source.

  The appropriate fix would be to ensure that systemd can successfully
  'start ssh.service' even when 'UsePrivilegeSeparation yes' is set.
  systemd needs to test that /var/run/sshd/ exists before starting sshd,
  just as the init.d script for sshd does. openssl could also be patched
  so that UsePrivilegeSeparation is no longer enabled by default,
  however that is not going to solve the problem for millions of pre-
  existing config files. Only an update to openssl to force-override
  that flag to 'no' would solve the problem. Thus systemd still needs to
  be responsible for ensuring that it inits sshd properly by ensuring
  that /var/run/sshd/ exists before it sends the 'start' command.

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

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


[Touch-packages] [Bug 1815649] Re: Vim on Ubuntu Disc 19.04 does not work

2019-02-26 Thread Sebastien Bacher
** Changed in: vim (Ubuntu)
   Status: Incomplete => New

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

Title:
  Vim on Ubuntu Disc 19.04 does not work

Status in vim package in Ubuntu:
  New

Bug description:
  Hi guys

  The Vim on Ubuntu Disk 19.04 comes installed by default, but so far does not 
work.
  It is stated that it is installed by the Ubuntu software, but by the terminal 
says it is not installed as can be seen in the attached image.

  Command 'vim' not found, but can be installed with:

  Awaiting arrangements and correction

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

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


[Touch-packages] [Bug 1817627] Re: systemd-analyze verify reports failure

2019-02-26 Thread Joshua Powers
Marking the Ubuntu Manpage Repository task invalid and adding the
systemd (Ubuntu) task.

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

** Changed in: ubuntu-manpage-repository
   Status: New => Invalid

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

Title:
  systemd-analyze verify reports failure

Status in Ubuntu Manpage Repository:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Version 237 and 238 of systemd-analyze have a known issue:
  https://github.com/systemd/systemd/issues/8592

  When will a fix be posted?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manpage-repository/+bug/1817627/+subscriptions

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


[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: rdp-alignment (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: rdp-readseq (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: rdp-classifier (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: resteasy3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: unsafe-mock (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in snakeyaml package in Ubuntu:
  New
Status in trove3 package in Ubuntu:
  New
Status in uimaj package in Ubuntu:
  New
Status in unsafe-mock package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in writer2latex package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Commit

Re: [Touch-packages] [Bug 1817376] Re: krb5-admin-server postinst has broken debconf if RUN_KADMIND set in /etc/default/krb5-admin-server

2019-02-26 Thread Sam Hartman
Robie any chance I could get you to sync krb5 1.17-2 from Debian
unstable to disco?
It's probably not a big deal but there's no reason not to take the fix
into Disco.

> "Robie" == Robie Basak <1817...@bugs.launchpad.net> writes:

Robie> Thanks Clark and Sam.  Ubuntu doesn't support upgrade paths
Robie> that skip LTS releases. So, ignoring EOL releases, we only
Robie> need to consider Trusty->Xenial,
Xenial-> Bionic, Bionic->Cosmic and Cosmic->Disco. If only upgrading from 
1.12 is affected,
Robie> then from Ubuntu is Trusty->Xenial the only upgrade path
Robie> affected?

yes.

Robie> If so, is it just Xenial that we need to fix?


I was working with this a bit testing the upgrade from wheezy to buster
on the Debian side.  Wheezy is the only Debian release that is vaguely
extant where this could come up.
In my testing, Debconf didn't actually remove the template on an
upgrade.
So, The two cases where I found that I could reproduce the situation
Were:

* remove krb5-admin-server on the old release and install it on the new
  release (without doing an upgrade)

* Copy in a /etc/default/krb5-admin-server from another system.

Neither of those seems serious enough to backport a fix for.  I'd rather
wait until we get a better understanding of how this gets triggered
before doing any changes to xenial.  I agree though that if we need to
change any old release xenial is the only target.

--Sam

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

Title:
  krb5-admin-server postinst has broken debconf if RUN_KADMIND set in
  /etc/default/krb5-admin-server

Status in krb5 package in Ubuntu:
  Triaged

Bug description:
  Package installation fails on postinst due to broken debconf when
  /etc/default/krb5-admin-server sets RUN_KADMIND to a value.

  This happens because the .config script [0] sets debconf question krb5
  -admin-server/kadmind to the defaults file value when set to a value.
  But the .templates file [1] has no entry for this question resulting
  in a lookup failure.

  [0] 
https://git.launchpad.net/ubuntu/+source/krb5/tree/debian/krb5-admin-server.config#n16
  [1] 
https://git.launchpad.net/ubuntu/+source/krb5/tree/debian/krb5-admin-server.templates

  This bug seems to go back to at least Xenial (and also affects debian
  packaging too). We worked around this locally by removing RUN_KADMIND
  from our local defaults file, but this was an annoying bug to sort out
  and should probably be fixed. That said I'm not sure if it would be
  more appropraite to remove the db_set from [0] or add the question
  back to [1].

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

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


[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: libjdo-api-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libjdom1-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libnetx-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libquartz-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libswingx-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libxstream-java (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: orthanc-imagej (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
S

[Touch-packages] [Bug 1817617] Re: Video driver

2019-02-26 Thread Timo Aaltonen
you have the hwe stack, so install -intel-hwe-18.04 (and then configure
it)

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

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

Title:
  Video driver

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  ~apt-get install xserver-xorg-vt-get install xserver-xorg-video-intel
  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:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Feb 25 17:05:43 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.18.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2019-02-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 3442
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0P8H6J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Touch-packages] [Bug 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk

2019-02-26 Thread Sebastien Bacher
** Changed in: network-manager (Ubuntu Cosmic)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  NetworkManager IPv6 DAD lifetime behavior introduce security risk

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Cosmic:
  New
Status in network-manager source package in Disco:
  Fix Released

Bug description:
  Description:
  When performing IPv6 certification test, two DAD test cases (3.2.5c and d) 
check the remaining lifetime feature of the IPv6 packets.  The Network trace 
shows that the remaining lifetime becomes infinite when running these test 
cases.  Hence when running in IPv6 environment with Network Manager enabled, 
there is a risk of packets travelling in network which has valid lifetime 
always. If these packets are snooped by a hacker he can reply to these packets 
and they can send legitimate packets which are actually not.  

  According to https://tools.ietf.org/search/rfc4862, page 19:
  "The above rules address a specific denial-of-service attack in which a bogus 
advertisement could contain prefixes with very small Valid Lifetimes.  Without 
the above rules, a single unauthenticated advertisement containing bogus Prefix 
Information options with short Valid Lifetimes could cause all of a node's 
addresses to expire prematurely.  The above rules ensure that legitimate 
advertisements (which are sent periodically) will "cancel" the short Valid 
Lifetimes before they actually take effect."

  Other notes:
  - 2 test cases pass without NetworkManager.
  - Tested with different Linux Desktop Distributions, as long as 
NetworkManager is running, those DAD test cases fail.

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

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


[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: libjackson-json-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libcommons-collections4-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libcommons-collections3-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libbtm-java (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being bu

[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot

2019-02-26 Thread Matt P
Same situation.  Ubuntu 16.04 openvz vps image of unknown origin.

Minimized image, ran security updates and rebooted.  openssh server
failed to start due to systemd-tmpfiles failing with

Failed to validate path /var/run/sshd: Too many levels of symbolic
links

Which then causes ssh server to fail to start with error:

Missing privilege separation directory: /var/run/sshd


#
# pre breaking update
#

# uname -a
Linux NJ01 2.6.32-openvz-042stab120.18-amd64 #1 SMP Fri Jan 13 10:33:34 MSK 
2017 x86_64 x86_64 x86_64 GNU/Linux

# cat /usr/lib/tmpfiles.d/sshd.conf
d /var/run/sshd 0755 root root

# systemd-tmpfiles --version
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

# systemd-tmpfiles --create /usr/lib/tmpfiles.d/sshd.conf
# # success

# ls -ld /
drwxr-xr-x 23 root root 4096 Feb 26 09:35 /
# ls -ld /var
drwxr-xr-x 12 root root 4096 Nov 26  2016 /var
# ls -ld /var/run
lrwxrwxrwx 1 root root 4 Nov 26  2016 /var/run -> /run
# ls -ld /var/run/sshd
drwxr-xr-x 2 root root 40 Feb 26 09:35 /var/run/sshd

# apt-cache policy systemd
systemd:
  Installed: 229-4ubuntu12
  Candidate: 229-4ubuntu12
  Version table:
 *** 229-4ubuntu12 100
100 /var/lib/dpkg/status

#---BREAKING UPDATE START

apt-get update

# "minimize" the system
export DEBIAN_FRONTEND=noninteractive
apt-get --assume-yes install aptitude ubuntu-minimal
aptitude --assume-yes markauto 
'~i!?name(ubuntu-minimal~|linux-generic~|openssh-server~|systemd)'
aptitude --assume-yes purge '~c'

# apply security updates
apt-get --assume-yes install unattended-upgrades
unattended-upgrade

# reboot
shutdown -r now

#---BREAKING UPDATE END

# post update (pre-reboot).
# apt-cache policy systemd
systemd:
  Installed: 229-4ubuntu21.16
  Candidate: 229-4ubuntu21.16
  Version table:
 *** 229-4ubuntu21.16 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
 229-4ubuntu4 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
# ls -ld /
drwxr-xr-x 23 root root 4096 Feb 26 09:03 /
# ls -ld /var
drwxr-xr-x 12 root root 4096 Nov 26  2016 /var
# ls -ld /var/run
lrwxrwxrwx 1 root root 4 Nov 26  2016 /var/run -> /run
# ls -ld /var/run/sshd
drwxr-xr-x 2 root root 40 Feb 26 09:03 /var/run/sshd
# systemd-tmpfiles --version
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN
# systemd-tmpfiles --create /usr/lib/tmpfiles.d/sshd.conf
Failed to validate path /var/run/sshd: Too many levels of symbolic links


Anyway, root cause seems to be this systemd-tmpfiles error.  Tmpfile gets 
purged at reboot and doesn't get recreated.  

Seems pretty major that applying security updates would lock you out of
your server.  If I didn't happen to have a serial console with this
particular VPS provider (some others I use don't provide one)...I would
have no idea what was going on.

I get this might be due to weird openvz image or older kernel...but
these ubuntu openvz images are very common.

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

Title:
  systemd fails to start sshd at reboot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  So far reported issues turned out to be:
  - obsolete/buggy/vulnerable 3rd party provided kernels
  - bad permissions on /

  Please ensure / is owned by root:root.
  Please ensure you are running up to date kernels.

  
  ===

  Ubuntu 16.04.5, systemd 229-4ubuntu21.15

  The latest systemd update has somehow changed the method it uses to
  start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if
  /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and
  /var/run/sshd/ does not already exist. Being as this is the default,
  virtually EVERY Ubuntu 16.04 server in the world has
  UsePrivilegeSeparation set to yes. Furthermore, at the time when the
  user performs 'apt upgrade' and receives the newest version of
  systemd, /var/run/sshd/ already exists, so sshd successfully reloads
  for as long as the server doesn't get rebooted. BUT, as soon as the
  server is rebooted for any reason, /var/run/sshd/ gets cleaned away,
  and sshd fails to start, causing the remote user to be completely
  locked out of his system. This is a MAJOR issue for millions of VPS
  servers worldwide, as they are all about to get locked out of their
  servers and potentially lose data. The next reboot is a ticking time
  bomb waiting to spring. The bomb can be defused by implicitly setting
  'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however
  unsuspecting administrators are bound to be caught out by the
  millions. I got caugh

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: jmdns (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libscram-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mariadb-connector-java (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely on the security pocket and are separated in stages.

  The agreed process among foundations and the security team is that
  packages in the PPAs will be binary copied into bionic-proposed,
  checked for migration issues, and - no issues pending - cop

[Touch-packages] [Bug 1815649] Re: Vim on Ubuntu Disc 19.04 does not work

2019-02-26 Thread Edson José dos Santos
As synaptci it is installed

See attachment

Conforme synaptci ele encontra-se instalado

Vide anexo

** Attachment added: "Captura de tela de 2019-02-26 10-34-33.png"
   
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1815649/+attachment/5241785/+files/Captura%20de%20tela%20de%202019-02-26%2010-34-33.png

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

Title:
  Vim on Ubuntu Disc 19.04 does not work

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Hi guys

  The Vim on Ubuntu Disk 19.04 comes installed by default, but so far does not 
work.
  It is stated that it is installed by the Ubuntu software, but by the terminal 
says it is not installed as can be seen in the attached image.

  Command 'vim' not found, but can be installed with:

  Awaiting arrangements and correction

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

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


[Touch-packages] [Bug 1815649] Re: Vim on Ubuntu Disc 19.04 does not work

2019-02-26 Thread Edson José dos Santos
Vim still does not open

See attachment

O Vim continua não abrindo

Vide anexo


** Attachment added: "Captura de tela de 2019-02-26 10-34-19.png"
   
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1815649/+attachment/5241784/+files/Captura%20de%20tela%20de%202019-02-26%2010-34-19.png

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

Title:
  Vim on Ubuntu Disc 19.04 does not work

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Hi guys

  The Vim on Ubuntu Disk 19.04 comes installed by default, but so far does not 
work.
  It is stated that it is installed by the Ubuntu software, but by the terminal 
says it is not installed as can be seen in the attached image.

  Command 'vim' not found, but can be installed with:

  Awaiting arrangements and correction

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

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


[Touch-packages] [Bug 1815742] Re: latest network-manager segfaults in disco

2019-02-26 Thread Bas Zoetekouw
Unfortunately, NetworkManager is still segfaulting at the same line
(src/settings/nm-settings-plugin.c:147)

╰─▶ dpkg -l network-manager|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion Architecture Description
+++-===-===--=
ii  network-manager 1.15.2-0ubuntu2 amd64network management framework 
(daemon and userspace tools)


feb 26 14:15:31 regan systemd[1]: Started Process Core Dump (PID 27019/UID 0).
feb 26 14:15:32 regan systemd-coredump[27022]: Process 26991 (NetworkManager) 
of user 0 dumped core.
   
   Stack trace of thread 26991:
   #0  0x7f566794f077 
__GI_raise (libc.so.6)
   #1  0x7f5667930535 
__GI_abort (libc.so.6)
   #2  0x7f5667efadc3 
g_assertion_message (libglib-2.0.so.0)
   #3  0x7f5667f55b7a 
g_assertion_message_expr (libglib-2.0.so.0)
   #4  0x562133f2d6d6 
_nm_settings_plugin_emit_signal_connection_added (
   #5  0x7f56683e059c 
initialize (libnm-settings-plugin-ifupdown.so)
   #6  0x562133ec7d90 
add_plugin (NetworkManager)
   #7  0x562133ecb3a5 
add_plugin_load_file (NetworkManager)
   #8  0x562133d6a0b1 
nm_manager_start (NetworkManager)
   #9  0x562133d2efe9 main 
(NetworkManager)
   #10 0x7f566793209b 
__libc_start_main (libc.so.6)
   #11 0x562133d2f31a _start 
(NetworkManager)
   
   Stack trace of thread 27006:
   #0  0x7f5667a22219 syscall 
(libc.so.6)
   #1  0x7f5667f78a3a 
g_cond_wait_until (libglib-2.0.so.0)
   #2  0x7f5667eff0c1 
g_async_queue_pop_intern_unlocked (libglib-2.0.so.
   #3  0x7f5667f57412 
g_thread_pool_wait_for_new_task (libglib-2.0.so.0)
   #4  0x7f5667f5690d 
g_thread_proxy (libglib-2.0.so.0)
   #5  0x7f5667b00164 
start_thread (libpthread.so.0)
   #6  0x7f5667a28def __clone 
(libc.so.6)
   
   Stack trace of thread 27003:
   #0  0x7f5667a1c6d9 
__GI___poll (libc.so.6)
   #1  0x7f5667f2dc76 
g_main_context_poll (libglib-2.0.so.0)
   #2  0x7f5667f2dd9c 
g_main_context_iteration (libglib-2.0.so.0)
   #3  0x7f5667f2dde1 
glib_worker_main (libglib-2.0.so.0)
   #4  0x7f5667f5690d 
g_thread_proxy (libglib-2.0.so.0)
   #5  0x7f5667b00164 
start_thread (libpthread.so.0)
   #6  0x7f5667a28def __clone 
(libc.so.6)
   
   Stack trace of thread 27010:
   #0  0x7f5667a22219 syscall 
(libc.so.6)
   #1  0x7f5667f78a3a 
g_cond_wait_until (libglib-2.0.so.0)
   #2  0x7f5667eff0c1 
g_async_queue_pop_intern_unlocked (libglib-2.0.so.
   #3  0x7f5667f57412 
g_thread_pool_wait_for_new_task (libglib-2.0.so.0)
   #4  0x7f5667f5690d 
g_thread_proxy (libglib-2.0.so.0)
   #5  0x7f5667b00164 
start_thread (libpthread.so.0)
   #6  0x7f5667a28def __clone 
(libc.so.6)
   
   Stack trace of thread 27007:
   #0  0x7f5667a1c6d9 
__GI___poll (libc.so.6)
  

[Touch-packages] [Bug 1817721] [NEW] autopkgtest success rate in Bionic reached an unusable amount

2019-02-26 Thread Christian Ehrhardt 
Public bug reported:

Hi,
Sorry to bother you - it seems we have this discussion every few months or so.

I was looking at this due to an SRU and I realized that the last 50-100 tests 
on all architectures are currently failing.
http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/amd64
http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/i386
http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/ppc64el
http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/s390x

On one hand I see the known flaky boot-and-smoke but that is fine.
On the other hand I see the test "upstream" failing always and it seems not 
related to the actual proposed packages.

Please help to resolve this mid-term.
Short term I'll submit a force-badtest for this as it seems to hold up more and 
more with no gain of seeing plenty of peopl just hitting retry every now and 
then.

If test "upstream" is utterly broken consider skipping it in the next
upload that you do for regular service. That would bring back at least
the remaining tests coverage.

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

** Branch linked: lp:~paelzer/britney/hints-ubuntu-bionic-
systemd-237-3ubuntu10.13

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

Title:
  autopkgtest success rate in Bionic reached an unusable amount

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  Sorry to bother you - it seems we have this discussion every few months or so.

  I was looking at this due to an SRU and I realized that the last 50-100 tests 
on all architectures are currently failing.
  http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/amd64
  http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/i386
  http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/ppc64el
  http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/s390x

  On one hand I see the known flaky boot-and-smoke but that is fine.
  On the other hand I see the test "upstream" failing always and it seems not 
related to the actual proposed packages.

  Please help to resolve this mid-term.
  Short term I'll submit a force-badtest for this as it seems to hold up more 
and more with no gain of seeing plenty of peopl just hitting retry every now 
and then.

  If test "upstream" is utterly broken consider skipping it in the next
  upload that you do for regular service. That would bring back at least
  the remaining tests coverage.

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

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


[Touch-packages] [Bug 1754472] Re: autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there

2019-02-26 Thread Christian Ehrhardt 
This is outdated, lets close it in favor of focusing on new/recent
issues.

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

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

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

Title:
  autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there

Status in systemd package in Ubuntu:
  Opinion

Bug description:
  The test really seems to be triggered all of the time to resolve a flaky test.
  That is just not worth the test.
  But it provides goo coverage, so an override in britney would loose all that.

  Lets skip the offending test on the arch it is known to be flaky
  (s390x).

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

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


[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: activemq (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: carrotsearch-hppc (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: commons-httpclient (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely o

[Touch-packages] [Bug 1783499] Re: systemd: Failed to send signal

2019-02-26 Thread Attila
I have activated RuntimeWatchdogSec=20s and ShutdownWatchdogSec=1min in
/etc/systemd/system.conf  and set the reboot, the server get stuck in
105min.

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

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

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

2019-02-26 Thread Iain Lane
uploaded to the SRU queue, now we wait

-- 
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:
  In Progress
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

2019-02-26 Thread Iain Lane
uploaded to the SRU queue, now we wait

-- 
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:
  In Progress

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


Re: [Touch-packages] [Bug 1817537] Re: libsoup should support ntlmv2

2019-02-26 Thread Lars Behrens
Am Montag, den 25.02.2019, 15:29 + schrieb Sebastien Bacher:
> The issue is fixed in the current Ubuntu version, closing for the
> current serie.

Hm, cannot confirm. At least evolution-ews fron cosmic cannot connect
to our server with ntlm selected.

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

Title:
  libsoup should support ntlmv2

Status in libsoup2.4 package in Ubuntu:
  Fix Released

Bug description:
  Our Exchange admins recently made NTLMv2 obligatory. Since then
  interaction with Exchange through Evolution isn't possible anymore.

  In newer versions of libsoup that has been implemented, see
  https://gitlab.gnome.org/GNOME/evolution-ews/issues/38

  Could that be backported to Ubuntu 18.04?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsoup2.4-1 2.62.1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb 25 12:10:26 2019
  SourcePackage: libsoup2.4
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+subscriptions

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


[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: hsqldb (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: hsqldb1.8.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely on the security pocket and are separated in stages.

  The agreed process among foundations and the security team is that
  packages in the PPAs will be binary copied into bionic-proposed,
  checked for migration issues, and - no issues pending - copied into
  bionic-security.

  NOTE TO SRU MEMBERS: The packages are to be released into bionic-
  security ONLY. This will be done/decided by the security team.

  A few packages might also need to be updated in Cosmic, but as an
  exception that will be done after the Bionic transition is worked out.

  [2019-02-21]
  Packages in stage 1 and stage 2 have been verified by the security team and 
are ready to be copied into bionic-proposed.

  Notes:
   - jtreg and testng are new versions required as build dependencies of 
openjdk-11
   - all other packages are backports that must be build/bootstrapped

[Touch-packages] [Bug 1817376] Re: krb5-admin-server postinst has broken debconf if RUN_KADMIND set in /etc/default/krb5-admin-server

2019-02-26 Thread Robie Basak
Thanks Clark and Sam.

Ubuntu doesn't support upgrade paths that skip LTS releases. So,
ignoring EOL releases, we only need to consider Trusty->Xenial,
Xenial->Bionic, Bionic->Cosmic and Cosmic->Disco. Does that save us a
whole bunch of work? If only upgrading from 1.12 is affected, then from
Ubuntu is Trusty->Xenial the only upgrade path affected? If so, is it
just Xenial that we need to fix?

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

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

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

Title:
  krb5-admin-server postinst has broken debconf if RUN_KADMIND set in
  /etc/default/krb5-admin-server

Status in krb5 package in Ubuntu:
  Triaged

Bug description:
  Package installation fails on postinst due to broken debconf when
  /etc/default/krb5-admin-server sets RUN_KADMIND to a value.

  This happens because the .config script [0] sets debconf question krb5
  -admin-server/kadmind to the defaults file value when set to a value.
  But the .templates file [1] has no entry for this question resulting
  in a lookup failure.

  [0] 
https://git.launchpad.net/ubuntu/+source/krb5/tree/debian/krb5-admin-server.config#n16
  [1] 
https://git.launchpad.net/ubuntu/+source/krb5/tree/debian/krb5-admin-server.templates

  This bug seems to go back to at least Xenial (and also affects debian
  packaging too). We worked around this locally by removing RUN_KADMIND
  from our local defaults file, but this was an annoying bug to sort out
  and should probably be fixed. That said I'm not sure if it would be
  more appropraite to remove the db_set from [0] or add the question
  back to [1].

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

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


[Touch-packages] [Bug 1817317] Re: OpenSSH is not "OpenBSD Secure Shell" and never be. /etc/init.d/ssh

2019-02-26 Thread Robie Basak
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Please make sure a bug exists against the Debian package for this.
Linking to that bug from here would then be helpful. Ubuntu derives its
packaging from Debian, so once Debian updates Ubuntu will pick up the
change.

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

** Tags added: needs-upstream-report

** Summary changed:

- OpenSSH is not "OpenBSD Secure Shell" and never be. /etc/init.d/ssh
+ OpenSSH calls itself "OpenBSD Secure Shell" in /etc/init.d/ssh

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

Title:
  OpenSSH calls itself "OpenBSD Secure Shell" in /etc/init.d/ssh

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  openssh-server.ssh.init.new
  --- openssh-server.ssh.init 2018-11-07 22:52:49.0 +0900
  +++ openssh-server.ssh.init.new 2019-02-22 21:50:05.010233405 +0900
  @@ -6,7 +6,7 @@
   # Required-Stop:   $remote_fs $syslog
   # Default-Start:   2 3 4 5
   # Default-Stop:
  -# Short-Description:   OpenBSD Secure Shell server
  +# Short-Description:   OpenSSH server
   ### END INIT INFO
   
   set -e

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

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


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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted openjdk-lts into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/openjdk-
lts/11.0.2+9-3ubuntu1~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: openjfx (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which re

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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted maven-javadoc-plugin into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/maven-javadoc-plugin/3.0.1-3~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: openjdk-lts (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS iss

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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted openjdk-11-jre-dcevm into bionic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/openjdk-11-jre-
dcevm/11.0.1+8-1~18.04 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 gettext in Ubuntu.
https://bugs.launchpad.net/bugs/1814133

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as

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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted scala into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/scala/2.11.12-4~18.04
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: openjdk-11-jre-dcevm (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  b

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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted openjfx into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openjfx/11.0.2+1-1~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: scala (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports

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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted javatools into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/javatools/0.72.1~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.

** Also affects: jnr-posix (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: jnr-posix (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10

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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted libgpars-groovy-java into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/libgpars-groovy-java/1.2.1-10~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: logback (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues

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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted logback into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/logback/1:1.2.3-2ubuntu1~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: maven-javadoc-plugin (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which

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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted jruby into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/jruby/9.1.17.0-1~18.04
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: jython (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of m

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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted jnr-posix into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/jnr-
posix/3.0.45-2~18.04 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: jruby (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backport

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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted jython into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/jython/2.7.1+repack-5~18.04 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: libgpars-groovy-java (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requi

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted java-common into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/java-
common/0.68ubuntu1~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: java-common (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: javatools (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-11-jre-dcevm source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in scala source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from o

[Touch-packages] [Bug 1814124] Re: sshd does not start after update

2019-02-26 Thread Robie Basak
> The entry in /usr/lib/tmpfiles.d/sshd.conf SHOULD be...

I don't agree, even if this happens to work for you. It's valid for it
to be /var/run/sshd provided that your system is properly up-to-date
(see related bug 1804847). If you're using some environment that is
broken, please ask the people who develop that environment to fix the
problem.

I'm reluctant to "just" proposed to change it the other way in a stable
release, because other users may be regressed in other ways by that
change. If your system is broken in this behaviour, it may be broken in
other ways too that will manifest later.

Since there's no action planned to be taken in Ubuntu for this
behaviour, I'm marking the bug status Invalid to make this clear to
users.

For users with broken systems, the workaround for this specific symptom
(rather than the general problem) is to override your tmpfiles.d entry
in /etc/tmpfiles.d. DO NOT EDIT /usr/lib/tmpfiles.d/sshd.conf since this
will be overwritten in a future package update. The right way to make
local configuration changes is in /etc/tmpfiles.d/. See tmpfiles.d(5)
for details. I'd appreciate if somebody could test and provide step-by-
step instructions to help other users.

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

** Description changed:

+ [Triage Notes]
+ 
+ This issue is caused on Ubuntu derivatives due to problematic symlink
+ handling on those systems. See bug 1804847 for details, and comment 10
+ below for details.
+ 
+ Proper Ubuntu systems do not appear to be affected.
+ 
+ [Original Description]
+ 
  After processing system update by:
  apt-get clean && apt-get autoclean && apt-get autoremove && apt-get update && 
apt-get upgrade && apt-get dist-upgrade && reboot
  
  ssh server stops starting at system boot.
  
  It starts after doing:
  mkdir /var/run/sshd
  chmod 0755 /var/run/sshd
  service ssh start
  
  It happens on fresh Ubuntu-16.04 installs on every VPS provide I have
  tested so far.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.6
  Uname: Linux 2.6.32-042stab127.2 x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Jan 31 10:18:56 2019
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
+  TERM=xterm
+  PATH=(custom, no user)
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  [Triage Notes]
  
  This issue is caused on Ubuntu derivatives due to problematic symlink
  handling on those systems. See bug 1804847 for details, and comment 10
- below for details.
+ below for details and a workaround.
  
  Proper Ubuntu systems do not appear to be affected.
  
  [Original Description]
  
  After processing system update by:
  apt-get clean && apt-get autoclean && apt-get autoremove && apt-get update && 
apt-get upgrade && apt-get dist-upgrade && reboot
  
  ssh server stops starting at system boot.
  
  It starts after doing:
  mkdir /var/run/sshd
  chmod 0755 /var/run/sshd
  service ssh start
  
  It happens on fresh Ubuntu-16.04 installs on every VPS provide I have
  tested so far.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.6
  Uname: Linux 2.6.32-042stab127.2 x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Jan 31 10:18:56 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- sshd does not start after update
+ sshd does not start after update on non-Ubuntu kernels where fchownat() is 
broken

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

Title:
  sshd does not start after update on non-Ubuntu kernels where
  fchownat() is broken

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  [Triage Notes]

  This issue is caused on Ubuntu derivatives due to problematic symlink
  handling on those systems. See bug 1804847 for details, and comment 10
  below for details and a workaround.

  Proper Ubuntu systems do not appear to be affected.

  [Original Description]

  After processing system update by:
  apt-get clean && apt-get autoclean && apt-get autoremove && apt-get update && 
apt-get upgrade && apt-get dist-upgrade && reboot

  ssh server stops starting at system boot.

  It starts after doing:
  mkdir /var/run/sshd
  chmod 0755 /var/run/sshd
  service ssh start

  It happens on fresh Ubuntu-16.04 installs on every VPS provide I have
  tested so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
 

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: jruby-openssl (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in openjfx source package in Bionic:
  New
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely on the security pocket and are separated in stages.

  The agreed process among foundations and the security team is that
  packages in the PPAs will be binary copied into bionic-proposed,
  checked for migration issues, and - no issues pending - copied into
  bionic-security.

  NOTE TO SRU MEMBERS: The packages are to be released into bionic-
  security ONLY. This will be done/decided by the security team.

  A few packages might also need to be updated in Cosmic, but as an
  exception that will be done after the Bionic transition is worked out.

  [2019-02-21]
  Packages in stage 1 and stage 2 have been verified by the security team and 
are ready to be copied into bionic-proposed.

  Notes:
   - jtreg and testng are new versions required as build dependencies of 
openjdk-11
   - all other packages are backports that must be build/bootstrapped with 
openjdk-10

  PPAs:
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2

  Please copy them in the following order/grouping.

  Group 1:
  * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted gettext into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gettext/0.19.8.1-6ubuntu0.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.

** Changed in: gettext (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: insubstantial (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the

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

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted insubstantial into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/insubstantial/7.3+dfsg3-4~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.

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in maven-javadoc-plugin source package in Bionic:
  Fix Committed
Status in openjdk-lts source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely on the security pocket and are separated in stages.

  The agreed pr

[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

2019-02-26 Thread Iain Lane
** Description changed:

+ [ 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:

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

-- 
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:
  In Progress
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 

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

2019-02-26 Thread Iain Lane
** Description changed:

+ [ 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
- 
+  #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)

** Description changed:

  [ 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)
+   - 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.

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

-- 
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:
  In Progress

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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

2019-02-26 Thread john smith
Networked fails to set the IP address between leases if IP address changes on 
Ubuntu Core. The network fails to renew a lease, specifically, it fails to 
change IPv4.
If anyone is searching a good job click here https://careerjobs360.in/


** Attachment added: "job-vs-career-og.png"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721223/+attachment/5241750/+files/job-vs-career-og.png

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

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

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

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

  Below steps to replicate the issue.

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

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

[Touch-packages] [Bug 1816530] Re: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04

2019-02-26 Thread Zoltán Süle
do you need me to add any files to the report?

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

Title:
  DNS servers are not being set in the system correctly when you upgrade
  from 16.04 to 18.04

Status in resolvconf package in Ubuntu:
  New

Bug description:
  I upgraded my 16.04 to 18.04 before the official release. After the
  upgrade I noticed that I don't have internet access. The wired network
  and the wifi settings looked good, but the internet didn't work. After
  the login the system always switched itself into airplane mode. I
  tethered the network via USB and Bluetooth by my mobile but they also
  didn't work.

  I found a useful answer from @andrew-woodhead666:
  https://answers.launchpad.net/ubuntu/+question/665374

  it seems this bug is still not fixed for the upgraded dists in the main 
release and affects a few dozens of ubuntu users.
  
https://askubuntu.com/questions/1021884/no-internet-after-upgrade-from-16-04-to-18-04

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

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


[Touch-packages] [Bug 1817451] Re: iconv error on command line for bg_BG on Ubuntu 16.04 LTS, Hunspell 1.3.3

2019-02-26 Thread Pander
Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909577

** Bug watch added: Debian Bug tracker #909577
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909577

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

Title:
  iconv error on command line for bg_BG on Ubuntu 16.04 LTS, Hunspell
  1.3.3

Status in hunspell package in Ubuntu:
  Confirmed

Bug description:
  While trying to run Hunspell on the command line for the Bulgarian
  locale, I get the following error:

    $ hunspell -d bg_BG
    error - iconv_open: UTF-8 -> microsoft-cp1251
    Hunspell 1.3.3

  Operating system: Ubuntu 16.04 LTS

  I guess the solution would be to reencode the dictionary as UTF-8?

  I tried to supply the -i parameter, but without any luck.

  Originally reported at:
  https://github.com/hunspell/hunspell/issues/458

  And patched in that repo:
  
https://github.com/hunspell/hunspell/commit/3b837d8cb6125820202da9dc8721ffc92a7ce19b

  And fixed in LibreOffice:
  https://bugs.documentfoundation.org/show_bug.cgi?id=117392

  The bug is still there in Linux Mint though. Version info:

  Linux version 4.15.0-45-generic (buildd@lgw01-amd64-031) (gcc version
  7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC
  2019

  @(#) International Ispell Version 3.2.06 (but really Hunspell 1.6.2)

  Package version for hunspell-bg: 1:6.0.3-3

  See also https://bugs.launchpad.net/ubuntu/+source/libreoffice-
  dictionaries/+bug/1675547

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

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


[Touch-packages] [Bug 1817451] Re: iconv error on command line for bg_BG on Ubuntu 16.04 LTS, Hunspell 1.3.3

2019-02-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  iconv error on command line for bg_BG on Ubuntu 16.04 LTS, Hunspell
  1.3.3

Status in hunspell package in Ubuntu:
  Confirmed

Bug description:
  While trying to run Hunspell on the command line for the Bulgarian
  locale, I get the following error:

    $ hunspell -d bg_BG
    error - iconv_open: UTF-8 -> microsoft-cp1251
    Hunspell 1.3.3

  Operating system: Ubuntu 16.04 LTS

  I guess the solution would be to reencode the dictionary as UTF-8?

  I tried to supply the -i parameter, but without any luck.

  Originally reported at:
  https://github.com/hunspell/hunspell/issues/458

  And patched in that repo:
  
https://github.com/hunspell/hunspell/commit/3b837d8cb6125820202da9dc8721ffc92a7ce19b

  And fixed in LibreOffice:
  https://bugs.documentfoundation.org/show_bug.cgi?id=117392

  The bug is still there in Linux Mint though. Version info:

  Linux version 4.15.0-45-generic (buildd@lgw01-amd64-031) (gcc version
  7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC
  2019

  @(#) International Ispell Version 3.2.06 (but really Hunspell 1.6.2)

  Package version for hunspell-bg: 1:6.0.3-3

  See also https://bugs.launchpad.net/ubuntu/+source/libreoffice-
  dictionaries/+bug/1675547

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

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


[Touch-packages] [Bug 1817662] Re: [SRU] Need to support WWAN module DW5820e

2019-02-26 Thread Will Cooke
** Summary changed:

- Need to support WWAN module DW5820e
+ [SRU] Need to support WWAN module DW5820e

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

Title:
  [SRU] Need to support WWAN module DW5820e

Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  New

Bug description:
  * Impact

  New WWAN module like DW5820e is not supported.

  * Test case

  1. Install the new Modem manager on the target machine that have DW5820e 
installed.
  2. Plugged sim card, create a connection and make sure the internet 
connection is working.
  3. Test a few exsting WWAN module and make sure they works.

  * Regression potential

  As far as know (and we've been in communication with Aleksandr), MM 1.10
  should be fully backwards compatible with NM 1.2x.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1817662/+subscriptions

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


[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: jruby (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely on the security pocket and are separated in stages.

  The agreed process among foundations and the security team is that
  packages in the PPAs will be binary copied into bionic-proposed,
  checked for migration issues, and - no issues pending - copied into
  bionic-security.

  NOTE TO SRU MEMBERS: The packages are to be released into bionic-
  security ONLY. This will be done/decided by the security team.

  A few packages might also need to be updated in Cosmic, but as an
  exception that will be done after the Bionic transition is worked out.

  [2019-02-21]
  Packages in stage 1 and stage 2 have been verified by the security team and 
are ready to be copied into bionic-proposed.

  Notes:
   - jtreg and testng are new versions required as build dependencies of 
openjdk-11
   - all other packages are backports that must be build/bootstrapped with 
openjdk-10

  PPAs:
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2

  Please copy them in the following order/grouping.

  Group 1:
  * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 2:
  * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05)
  * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05)

  Please upload libcommons-lang3-java from stage 2 (ignore the version
  in stage 1).

  Group 3:
  * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06)
  * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx 
(2019-02-05)
  * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 4:
  * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 5:
  * groovy 2.4.16-1ubuntu1~18.04.1 Ti

[Touch-packages] [Bug 1783499] Re: systemd: Failed to send signal

2019-02-26 Thread Attila
The test server get stuck after ~9h, here is the debug log.

** Attachment added: "shutdown-log-process.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5241740/+files/shutdown-log-process.txt

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

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

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