[Touch-packages] [Bug 1793555] Re: networkd tears down bridge ip address when the last device is pulled out from the bridge

[Scati Labs I+D]

This issue has been fixed upstream:
https://github.com/systemd/systemd/pull/10597

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

Title:
  networkd tears down bridge ip address when the last device is pulled
  out from the bridge

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 18.04.1 LTS (systemd 237) pulling out the last device out of
  the bridge removes the bridge ip address.

  given the following config:

  # cat /etc/systemd/network/vmbr0.netdev
  [NetDev]
  Name=vmbr0
  Kind=bridge

  [Bridge]
  HelloTimeSec=0
  ForwardDelaySec=0
  STP=no

  # cat /etc/systemd/network/vmbr0.network
  [Match]
  Name=vmbr0

  [Network]
  Address=10.10.0.1/16
  ConfigureWithoutCarrier=yes
  DHCP=no
  IPForward=yes
  IPv6AcceptRA=no
  LinkLocalAddressing=no

  networkd would bring up vmbr0 with 10.10.0.1/16 on system boot despite
  it not having any devices, allowing services to bind to 10.10.0.1.

  However, if you add a device and then remove it (e.g. by starting and
  then stopping a virtual machine connected to the bridge), networkd
  would tear down the interface:

  3: vmbr0:  mtu 1500 qdisc noqueue state 
DOWN group default qlen 1000
  link/ether 16:19:4c:7f:e8:c4 brd ff:ff:ff:ff:ff:ff

  thus making any service listening on 10.10.0.1 inaccessible.

  previously on Xenial the bridge would stay intact.

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

-- 
Mailing list: https://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 1773859] Please test proposed package

[José Enrique]

Mira esta solucion
Saludos

El jue., 29 nov. 2018 19:31, Alejandro <1773...@bugs.launchpad.net>
escribió:

> José Enrique,disculpa y gracias por contestarme.Quería pedirte si me
> puedes contar brevemente ¿cómo pudiste borrar el systemd-shim package?No se
> cómo accederloMuchas graciasAlejandro
>   -
>   -
>  -
>
>
>   -
>  - -
> José Enrique <1773...@bugs.launchpad.net>
>
>   -
>   - Nov 19 at 2:01 PM
>
>
>- To avertaness...@yahoo.com
>   -
>
> Message body
> Thanks a lot for your help. I resolved my problem erasing systemd-shim and
> updating.
> I'll try new solution in another pc.
> Kind regards
>
>
>   From: José Enrique <1773...@bugs.launchpad.net>
>  To: avertaness...@yahoo.com
>  Sent: Tuesday, November 27, 2018 3:01 PM
>  Subject: Re: [Bug 1773859] Please test proposed package
>
> Lo siento Alejandro, no soy Lucas
>  Saludos
>
> El mar., 27 nov. 2018 18:51, Alejandro <1773...@bugs.launchpad.net>
> escribió:
>
> > Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make
> > this test in the last weeks I will make them as soon as
> > possibleRegardsAlejandro
> >
> >  From: Łukasz Zemczak <1773...@bugs.launchpad.net>
> >  To: avertaness...@yahoo.com
> >  Sent: Tuesday, November 20, 2018 9:21 AM
> >  Subject: [Bug 1773859] Please test proposed package
> >
> > Hello Kees, or anyone else affected,
> >
> > Accepted systemd into bionic-proposed. The package will build now and be
> > available at
> > https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 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 subscribed to a
> > duplicate bug report (1796221).
> > https://bugs.launchpad.net/bugs/1773859
> >
> > Title:
> >  upgrades to 18.04 fail
> >
> > Status in systemd package in Ubuntu:
> >  Fix Released
> > Status in systemd-shim package in Ubuntu:
> >  Won't Fix
> > Status in systemd source package in Bionic:
> >  Fix Committed
> > Status in systemd-shim source package in Bionic:
> >  Won't Fix
> > Status in systemd source package in Cosmic:
> >  Fix Released
> > Status in systemd-shim source package in Cosmic:
> >  Won't Fix
> >
> > Bug description:
> >  [Impact]
> >
> >* Some systems fail to upgrade due to conflicts between systemd and
> >  the (now removed from the archive) systemd-shim / upstart.
> >
> >* Instead of trying to work out what's the problem in ordering /
> >  removal of diverts, ensure that systemd is never unpacked whilst
> >  systemd-shim/upstart are still on disk. Thus declare conflicts against
> >  systemd-shim/upstart packages in systemd package.
> >
> >  [Test Case]
> >
> >* monitor drop-off of upgrades with below reported problem
> >
> >* Check that it is possible to upgrade to bionic's libpam-systemd
> >  from xenial with systemd-shim installed on xenial, ie.
> >
> >  lxc launch ubuntu-daily:xenial test-shim-upgrade
> >  lxc exec test-shim-upgrade
> >  apt update
> >  apt install systemd-shim
> >  wget
> >
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
> >  apt install ./systemd-shim_10-3_amd64.deb
> >  sed 's/xenial/bionic/' -i /etc/apt/sources.list
> >  apt update
> >  apt install systemd
> >
> >  this currently passes, however, systemd-shim remains installed. It
> >  should be removed instead. Apt install systemd should have lines like
> >  this:
> >
> >  The following packages will be REMOVED:
> >systemd-shim
> >  ...
> >  Removing 'diversion of
> > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> >
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> > by systemd-shim'
> >  ...
> >
> >
> >  [Regression Potential]
> >
> >* systemd-shim/upstart are both removed and not supported in bionic,
> >  thus forcing their removal via conflicts should bring the system into
> >  an expected stat

Re: [Touch-packages] [Bug 1773859] Please test proposed package

[José Enrique]

Hola mira esta solución.

Saludos.

El jue., 29 nov. 2018 22:51, b0w <1773...@bugs.launchpad.net> escribió:

> Yo tambien tengo dudas de como resolverlo! I Still have some doubts on how
> to fix it, but if in 7 days it will be available for everyone i will just
> wait the update.
> Greetings!
>
> On Thu, Nov 29, 2018 at 12:31 PM Alejandro <1773...@bugs.launchpad.net>
> wrote:
>
> > José Enrique,disculpa y gracias por contestarme.Quería pedirte si me
> > puedes contar brevemente ¿cómo pudiste borrar el systemd-shim package?No
> se
> > cómo accederloMuchas graciasAlejandro
> >   -
> >   -
> >  -
> >
> >
> >   -
> >  - -
> > José Enrique <1773...@bugs.launchpad.net>
> >
> >   -
> >   - Nov 19 at 2:01 PM
> >
> >
> >- To avertaness...@yahoo.com
> >   -
> >
> > Message body
> > Thanks a lot for your help. I resolved my problem erasing systemd-shim
> and
> > updating.
> > I'll try new solution in another pc.
> > Kind regards
> >
> >
> >   From: José Enrique <1773...@bugs.launchpad.net>
> >  To: avertaness...@yahoo.com
> >  Sent: Tuesday, November 27, 2018 3:01 PM
> >  Subject: Re: [Bug 1773859] Please test proposed package
> >
> > Lo siento Alejandro, no soy Lucas
> >  Saludos
> >
> > El mar., 27 nov. 2018 18:51, Alejandro <1773...@bugs.launchpad.net>
> > escribió:
> >
> > > Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make
> > > this test in the last weeks I will make them as soon as
> > > possibleRegardsAlejandro
> > >
> > >  From: Łukasz Zemczak <1773...@bugs.launchpad.net>
> > >  To: avertaness...@yahoo.com
> > >  Sent: Tuesday, November 20, 2018 9:21 AM
> > >  Subject: [Bug 1773859] Please test proposed package
> > >
> > > Hello Kees, or anyone else affected,
> > >
> > > Accepted systemd into bionic-proposed. The package will build now and
> be
> > > available at
> > > https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 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 subscribed to a
> > > duplicate bug report (1796221).
> > > https://bugs.launchpad.net/bugs/1773859
> > >
> > > Title:
> > >  upgrades to 18.04 fail
> > >
> > > Status in systemd package in Ubuntu:
> > >  Fix Released
> > > Status in systemd-shim package in Ubuntu:
> > >  Won't Fix
> > > Status in systemd source package in Bionic:
> > >  Fix Committed
> > > Status in systemd-shim source package in Bionic:
> > >  Won't Fix
> > > Status in systemd source package in Cosmic:
> > >  Fix Released
> > > Status in systemd-shim source package in Cosmic:
> > >  Won't Fix
> > >
> > > Bug description:
> > >  [Impact]
> > >
> > >* Some systems fail to upgrade due to conflicts between systemd and
> > >  the (now removed from the archive) systemd-shim / upstart.
> > >
> > >* Instead of trying to work out what's the problem in ordering /
> > >  removal of diverts, ensure that systemd is never unpacked whilst
> > >  systemd-shim/upstart are still on disk. Thus declare conflicts against
> > >  systemd-shim/upstart packages in systemd package.
> > >
> > >  [Test Case]
> > >
> > >* monitor drop-off of upgrades with below reported problem
> > >
> > >* Check that it is possible to upgrade to bionic's libpam-systemd
> > >  from xenial with systemd-shim installed on xenial, ie.
> > >
> > >  lxc launch ubuntu-daily:xenial test-shim-upgrade
> > >  lxc exec test-shim-upgrade
> > >  apt update
> > >  apt install systemd-shim
> > >  wget
> > >
> >
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
> > >  apt install ./systemd-shim_10-3_amd64.deb
> > >  sed 's/xenial/bionic/' -i /etc/apt/sources.list
> > >  apt update
> > >  apt install systemd
> > >
> > >  this currently passes, however, systemd-shim remains installed. It
> > >  should be removed instead. Apt install sys

[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)

[Brian Burch]

Things are much improved now on cosmic 18.04 ubuntu studio:-

/sys/class/power_supply/BAT0/capacity:100
/sys/class/power_supply/hid-34:88:5d:87:92:8c-battery/capacity:85

Linux 4.18.0-11-lowlatency #12-Ubuntu SMP PREEMPT Tue Oct 23 21:12:42
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

[The mouse is OK again on 17.10, while the ASUS docking station is still
not correct. I will update this bug report with details soon.]

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel
  4.15 and later)

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

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1788810] Re: Computer won't suspend, DBUS reports that a suspend or shutdown operation already in progress

[Launchpad Bug Tracker]

[Expired for dbus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: dbus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Computer won't suspend, DBUS reports that a suspend or shutdown
  operation already in progress

Status in dbus package in Ubuntu:
  Expired

Bug description:
  After a fresh boot computer suspends fine, however further attempts to
  suspend result in failure with the above mentioned error message. When
  that happens, shutdown doesn't work either; shutdown process gets
  stuck at some point and I must forcibly turn off or reset the
  computer. Sometimes the shutdown almost completes, but THEN the
  computer enters suspend, after which I must wake it up to complete
  shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dbus 1.12.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Aug 24 10:39:30 2018
  SourcePackage: dbus
  UpgradeStatus: Upgraded to bionic on 2018-06-19 (65 days ago)

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

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

[Touch-packages] [Bug 1805955] Re: systemd 237-3ubuntu10.9 ADT test failure with linux-gcp 4.15.0-1025.26

[Khaled El Mously]

There's a new test in this version of adt, "TEST-22-TMPFILES". It looks
like this test fails because there's a permission problem on the test
script itself "test.sh"

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

Title:
  systemd 237-3ubuntu10.9 ADT test failure with linux-gcp 4.15.0-1025.26

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20181123_064313_f146e@/log.gz

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

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

[Touch-packages] [Bug 1805955] [NEW] systemd 237-3ubuntu10.9 ADT test failure with linux-gcp 4.15.0-1025.26

[Khaled El Mously]

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20181123_064313_f146e@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  systemd 237-3ubuntu10.9 ADT test failure with linux-gcp 4.15.0-1025.26

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20181123_064313_f146e@/log.gz

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

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

[Touch-packages] [Bug 1805953] Re: perl is not installed correctly ubuntu-18.10-server-amd64.iso

[Steve Langasek]

This bug includes no details about what you mean by "not installed
correctly".  Perl is a base package and there is no problem with its
installation in the common case.

** Package changed: libsocket-linux-perl (Ubuntu) => perl (Ubuntu)

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

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

Title:
  perl is not installed correctly ubuntu-18.10-server-amd64.iso

Status in perl package in Ubuntu:
  Incomplete

Bug description:
  perl is not installed correctly in ubuntu-18.10-server-amd64.iso.

  It can be fixed when reinstall perl with command "apt install perl"

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

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

[Touch-packages] [Bug 1805953] [NEW] perl is not installed correctly ubuntu-18.10-server-amd64.iso

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

perl is not installed correctly in ubuntu-18.10-server-amd64.iso.

It can be fixed when reinstall perl with command "apt install perl"

** Affects: perl (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
perl is not installed correctly ubuntu-18.10-server-amd64.iso
https://bugs.launchpad.net/bugs/1805953
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to perl in Ubuntu.

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

[Touch-packages] [Bug 1805148] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1805148

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  [radeon] Lock screen corrupt since upgrade to 18.04.01

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

Bug description:
  Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of this 
laptop (an HP 6910p) became corrupt. When logged in and using the system, video 
display is fine, but the lock screen is consistently garbled as in the attached 
photo. Switching to Wayland made no difference in this behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-01-23 (1038 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (104 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1805148] Re: [radeon] Lock screen corrupt since upgrade to 18.04.01

[Daniel van Vugt]

** Summary changed:

- [i945] Lock screen corrupt since upgrade to 18.04.01
+ [radeon] Lock screen corrupt since upgrade to 18.04.01

** Tags added: radeon

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

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

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

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

Title:
  [radeon] Lock screen corrupt since upgrade to 18.04.01

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

Bug description:
  Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of this 
laptop (an HP 6910p) became corrupt. When logged in and using the system, video 
display is fine, but the lock screen is consistently garbled as in the attached 
photo. Switching to Wayland made no difference in this behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-01-23 (1038 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (104 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1805148] Re: [i945] Lock screen corrupt since upgrade to 18.04.01

[Paul Chambre]

00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory 
Controller Hub (rev 0c)
Subsystem: Hewlett-Packard Company Compaq 6910p
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root 
Port (rev 0c)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.0 Communication controller: Intel Corporation Mobile PM965/GM965 MEI 
Controller (rev 0c)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: mei_me
Kernel modules: mei_me
00:03.2 IDE interface: Intel Corporation Mobile PM965/GM965 PT IDER Controller 
(rev 0c)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: ata_generic
Kernel modules: pata_acpi
00:03.3 Serial controller: Intel Corporation Mobile PM965/GM965 KT Controller 
(rev 0c)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: serial
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network 
Connection (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #4 (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: uhci_hcd
00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #5 (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: uhci_hcd
00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #2 (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 
(rev 03)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 
(rev 03)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #1 (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: uhci_hcd
00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #2 (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: uhci_hcd
00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #3 (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: uhci_hcd
00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #1 (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: ehci-pci
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M-E) LPC Interface 
Controller (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE 
Controller (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: ata_piix
Kernel modules: pata_acpi
00:1f.2 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA 
Controller [AHCI mode] (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: ahci
Kernel modules: ahci
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV516/M64-S [Mobility Radeon X2300]
Subsystem: Hewlett-Packard Company 6910p
Kernel driver in use: radeon
Kernel modules: radeon
02:06.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b9)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: yenta_cardbus
Kernel modules: yenta_socket
02:06.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b9)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: yenta_cardbus
Kernel modules: yenta_socket
02:06.3 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host 
Adapter (rev 20)
Subsystem: Hewlett-Packard Company Compaq 6910p
Kernel driver in use: sdhci-pci
Kernel modules: sdhci_pci



** Attachment added: "allpackages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805148/+attachment/5217565/+files/allpackages.txt

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

Title:
  [i945] Lock screen corrupt since upgra

[Touch-packages] [Bug 1805924] [NEW] package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Daniela Moscoso Pinto]

Public bug reported:

I tried to install the actualization pack, and every time it star tu run
the download, pop's up a notification that says "there has an error
occurred"

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
 libssh-4:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Nov 29 22:21:33 2018
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2018-09-08 (82 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: glib2.0
Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I tried to install the actualization pack, and every time it star tu
  run the download, pop's up a notification that says "there has an
  error occurred"

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   libssh-4:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Nov 29 22:21:33 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2018-09-08 (82 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: glib2.0
  Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1805821] Re: GUI performance is poor

[Daniel van Vugt]

It looks the those messages are coming from the kernel. Although you
might not encounter the problem till xserver-xorg-video-amdgpu is
enabled.

** Tags added: amdgpu

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

** Summary changed:

- GUI performance is poor
+ [amdgpu] GUI performance is poor

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

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

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

Title:
  [amdgpu] GUI performance is poor

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Response is slow, amdgpu driver gives warning in dmesg which is below

  [0.00] Linux version 4.15.0-36-generic (buildd@lgw01-amd64-031) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 
2018 (Ubuntu 4.15.0-36.39-generic 4.15.18)
  [0.00] random: get_random_u32 called from bsp_init_amd+0x255/0x2a0 
with crng_init=0
  [0.966765] amd_uncore: AMD NB counters detected
  [1.165305] pcie_mp2_amd: AMD(R) PCI-E MP2 Communication Driver Version: 
1.0
  [1.716922] amdkcl: loading out-of-tree module taints kernel.
  [1.716947] amdkcl: module verification failed: signature and/or required 
key missing - tainting kernel
  [1.827886] [drm] amdgpu kernel modesetting enabled.
  [1.827887] [drm] amdgpu version: 18.30.2.15
  [1.833528] fb: switching to amdgpudrmfb from EFI VGA
  [1.850977] amdgpu :00:01.0: VRAM: 1024M 0x00F4 - 
0x00F43FFF (1024M used)
  [1.850979] amdgpu :00:01.0: GTT: 1024M 0x - 
0x3FFF
  [1.851137] [drm] amdgpu: 1024M of VRAM memory ready
  [1.851139] [drm] amdgpu: 14975M of GTT memory ready.
  [1.851291] [drm] amdgpu: dpm initialized
  [1.853722] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:1! type 0 expected 3
  [1.853779] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:3! type 0 expected 3
  [1.853825] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:4! type 0 expected 3
  [1.853872] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:5! type 0 expected 3
  [2.064038] fbcon: amdgpudrmfb (fb0) is primary device
  [2.128334] amdgpu :00:01.0: fb0: amdgpudrmfb frame buffer device
  [2.145953] [drm] Initialized amdgpu 3.26.0 20150101 for :00:01.0 on 
minor 0
  [5.265031] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [6.277293] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [7.289439] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [8.301565] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [9.313691] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [   10.325849] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [   11.338007] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [   12.350159] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [   13.362305] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [   14.374463] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [   14.394355] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
giving up!!!
  [   14.394396] [drm:amdgpu_device_ip_set_powergating_state [amdgpu]] *ERROR* 
set_powergating_state of IP block  failed -110
  [   15.420234] [drm:amdgpu_vce_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test 
timed out.
  [   15.420321] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed 
testing IB on ring 12 (-110).
  [   15.420369] [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* 
ib ring test failed (-110).
  [   23.736730] EDAC amd64: Node 0: DRAM ECC disabled.
  [   23.736731] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
  [ 1566.370793] audit: type=1400 audit(1543500426.678:40): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/usr/share/libdrm/amdgpu.ids" pid=7169 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  
  Takes too for software center to install .deb package where as it happens in 
a few seconds in terminal via dpkg -i.

  Problems are after installation of amdgpu.

  ProblemType: 

[Touch-packages] [Bug 1805027] Re: systemd-resolved can't resolve Comcast mail server addresses

[Trev Peterson]

This certainly seems like an ubuntu 18.04 bug.  3 machines here all
affected.  dig imap.comcast.net resolves to imap.ge.xfinity.com.  Ping,
telnet, wget are all unable to resolve imap.comcast.net.

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

Title:
  systemd-resolved can't resolve Comcast mail server addresses

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu release:  18.10
  2) systemd-resolved version: (Default latest version that comes with Ubuntu 
18.10)
  3) Expected behavior: Comcast's POP3 mail server addresses to be resolved to 
IP addresses
  4) Actual behavior:  Comcast's POP3 mail server addresses can't be resolved 
to IP addresses

  Starting on Monday, November 19, 2018, Comcast made a DNS change
  related to its POP3 mail servers (mail.comcast.net and
  pop3.comcast.net) that prevent resolved from being able to resolve
  those domains into IP addresses.  When I try to ping either host
  (mail.comcast.net or pop2.comcast.net), I get this error:

  tom@deathstar:~$ ping mail.comcast.net
  ping: mail.comcast.net: Name or service not known
  tom@deathstar:~$

  When I manually lookup up the domain, I get these results:

  tom@deathstar:~$ nslookup mail.comcast.net
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  Non-authoritative answer:
  mail.comcast.net  canonical name = imap.ge.xfinity.com.
  Name: imap.ge.xfinity.com
  Address: 96.118.242.209
  Name: imap.ge.xfinity.com
  Address: 96.118.242.197
  Name: imap.ge.xfinity.com
  Address: 96.118.242.233
  Name: imap.ge.xfinity.com
  Address: 96.118.242.225
  Name: imap.ge.xfinity.com
  Address: 96.118.242.226
  Name: imap.ge.xfinity.com
  Address: 96.118.242.217
  Name: imap.ge.xfinity.com
  Address: 96.118.242.208
  Name: imap.ge.xfinity.com
  Address: 96.118.242.230
  Name: imap.ge.xfinity.com
  Address: 96.118.242.232
  Name: imap.ge.xfinity.com
  Address: 96.118.242.218
  Name: imap.ge.xfinity.com
  Address: 96.118.242.211
  Name: imap.ge.xfinity.com
  Address: 96.118.242.242
  Name: imap.ge.xfinity.com
  Address: 96.118.242.221
  Name: imap.ge.xfinity.com
  Address: 96.118.242.196
  Name: imap.ge.xfinity.com
  Address: 96.118.208.40
  Name: imap.ge.xfinity.com
  Address: 96.118.208.99
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fee8:4f07
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe7d:1b0c
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe25:5ae5
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fef6:babc
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe87:c172
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fee6:7a57
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe0f:a4a
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:2:f816:3eff:fec7:cb93
  Name: imap.ge.xfinity.com
  Address: 2001:558:fee2:1000:f816:3eff:fe42:4f14
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe33:9aaa
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:feb2:8c0d
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fef1:25a5
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:febd:320a
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe36:aba3
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe3f:76f2
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe45:1d1e

  tom@deathstar:~$ dig mail.comcast.net

  ; <<>> DiG 9.11.4-3ubuntu5-Ubuntu <<>> mail.comcast.net
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15037
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 17, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mail.comcast.net.IN  A

  ;; ANSWER SECTION:
  mail.comcast.net. 15  IN  CNAME   imap.ge.xfinity.com.
  imap.ge.xfinity.com.  12  IN  A   96.117.3.119
  imap.ge.xfinity.com.  12  IN  A   96.117.3.96
  imap.ge.xfinity.com.  12  IN  A   96.117.3.143
  imap.ge.xfinity.com.  12  IN  A   96.117.3.145
  imap.ge.xfinity.com.  12  IN  A   96.117.3.129
  imap.ge.xfinity.com.  12  IN  A   96.117.3.148
  imap.ge.xfinity.com.  12  IN  A   96.117.3.201
  imap.ge.xfinity.com.  12  IN  A   96.117.3.136
  imap.ge.xfinity.com.  12  IN  A   96.118.133.238
  imap.ge.xfinity.com.  12  IN  A   96.117.3.128
  imap.ge.xfinity.com.  12  IN  A   96.117.3.144
  imap.ge.xfinity.com.  12  IN  A   96.117.2.238
  imap.ge.xfinity.com.  12  IN  A   96.117.3.110
  imap.ge.xfinity.com.  12  IN  A   96.117.3.140
  imap.ge.xfinity.com.  12  IN  A   96.117.3.154
  imap

[Touch-packages] [Bug 1805027] Re: systemd-resolved can't resolve Comcast mail server addresses

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd-resolved can't resolve Comcast mail server addresses

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu release:  18.10
  2) systemd-resolved version: (Default latest version that comes with Ubuntu 
18.10)
  3) Expected behavior: Comcast's POP3 mail server addresses to be resolved to 
IP addresses
  4) Actual behavior:  Comcast's POP3 mail server addresses can't be resolved 
to IP addresses

  Starting on Monday, November 19, 2018, Comcast made a DNS change
  related to its POP3 mail servers (mail.comcast.net and
  pop3.comcast.net) that prevent resolved from being able to resolve
  those domains into IP addresses.  When I try to ping either host
  (mail.comcast.net or pop2.comcast.net), I get this error:

  tom@deathstar:~$ ping mail.comcast.net
  ping: mail.comcast.net: Name or service not known
  tom@deathstar:~$

  When I manually lookup up the domain, I get these results:

  tom@deathstar:~$ nslookup mail.comcast.net
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  Non-authoritative answer:
  mail.comcast.net  canonical name = imap.ge.xfinity.com.
  Name: imap.ge.xfinity.com
  Address: 96.118.242.209
  Name: imap.ge.xfinity.com
  Address: 96.118.242.197
  Name: imap.ge.xfinity.com
  Address: 96.118.242.233
  Name: imap.ge.xfinity.com
  Address: 96.118.242.225
  Name: imap.ge.xfinity.com
  Address: 96.118.242.226
  Name: imap.ge.xfinity.com
  Address: 96.118.242.217
  Name: imap.ge.xfinity.com
  Address: 96.118.242.208
  Name: imap.ge.xfinity.com
  Address: 96.118.242.230
  Name: imap.ge.xfinity.com
  Address: 96.118.242.232
  Name: imap.ge.xfinity.com
  Address: 96.118.242.218
  Name: imap.ge.xfinity.com
  Address: 96.118.242.211
  Name: imap.ge.xfinity.com
  Address: 96.118.242.242
  Name: imap.ge.xfinity.com
  Address: 96.118.242.221
  Name: imap.ge.xfinity.com
  Address: 96.118.242.196
  Name: imap.ge.xfinity.com
  Address: 96.118.208.40
  Name: imap.ge.xfinity.com
  Address: 96.118.208.99
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fee8:4f07
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe7d:1b0c
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe25:5ae5
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fef6:babc
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe87:c172
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fee6:7a57
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe0f:a4a
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:2:f816:3eff:fec7:cb93
  Name: imap.ge.xfinity.com
  Address: 2001:558:fee2:1000:f816:3eff:fe42:4f14
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe33:9aaa
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:feb2:8c0d
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fef1:25a5
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:febd:320a
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe36:aba3
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe3f:76f2
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe45:1d1e

  tom@deathstar:~$ dig mail.comcast.net

  ; <<>> DiG 9.11.4-3ubuntu5-Ubuntu <<>> mail.comcast.net
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15037
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 17, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mail.comcast.net.IN  A

  ;; ANSWER SECTION:
  mail.comcast.net. 15  IN  CNAME   imap.ge.xfinity.com.
  imap.ge.xfinity.com.  12  IN  A   96.117.3.119
  imap.ge.xfinity.com.  12  IN  A   96.117.3.96
  imap.ge.xfinity.com.  12  IN  A   96.117.3.143
  imap.ge.xfinity.com.  12  IN  A   96.117.3.145
  imap.ge.xfinity.com.  12  IN  A   96.117.3.129
  imap.ge.xfinity.com.  12  IN  A   96.117.3.148
  imap.ge.xfinity.com.  12  IN  A   96.117.3.201
  imap.ge.xfinity.com.  12  IN  A   96.117.3.136
  imap.ge.xfinity.com.  12  IN  A   96.118.133.238
  imap.ge.xfinity.com.  12  IN  A   96.117.3.128
  imap.ge.xfinity.com.  12  IN  A   96.117.3.144
  imap.ge.xfinity.com.  12  IN  A   96.117.2.238
  imap.ge.xfinity.com.  12  IN  A   96.117.3.110
  imap.ge.xfinity.com.  12  IN  A   96.117.3.140
  imap.ge.xfinity.com.  12  IN  A   96.117.3.154
  imap.ge.xfinity.com.  12  IN  A   96.117.3.132

  ;; Q

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358164

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in landscape-client source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

  
  Used Landscape (Paid Canonical Subscription) to upgrade one of my machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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

[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled

[Bug Watch Updater]

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

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

Title:
  systemd-resolved has issues when the answer is over 512 bytes with
  EDNS disabled

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd package in Debian:
  Unknown

Bug description:
  [Impact]

  TCP stub is cutting down the payload to 512 bytes when EDNS is
  disabled. This makes non-EDNS clients (nslookup) receive a "shortened"
  answer even when UDP returns a truncated reply for a new TCP query.
  For instance,

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  In the second case, no-EDNS, TCP should provide the complete answer,
  but it's capped at UDP's size.

  [Test Case]

  Query systemd-resolved with a domain name that resolves to multiple
  (lots.. 30+) A records. A client with EDNS support (dig) will receive
  all of them, a client without support (nslookup or dig +noedns) will
  have a truncated list. Using the example above:

  EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 
| wc -l

  [Regression potential]

  Minimal. This change only affects TCP requests, and the new size is
  already used in the code for other requests.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10816
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce

  [Original Description]

  Querying a domain name that has >512 bytes in records (e.g. 30+ A
  records), the number of results depends on the DNS client used:

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  Normally a client that doesn't support EDNS would receive a truncated
  reply from the initial UDP connection (limited by the spec to 512
  bytes) and a second query would be established via TCP to receive the
  complete results. In this case, the number of results is the same
  regardless of the protocol used (29).

  Upstream bug: https://github.com/systemd/systemd/issues/10816

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

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

[Touch-packages] [Bug 1802525] Re: (s)ata disks do not have /dev/disk/by-path links created

[Dan Streetman]

the linux-* autopkgtest failures are known and expected (bug 1723223)
and can be ignored.

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

Title:
  (s)ata disks do not have /dev/disk/by-path links created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  [impact]

  udev (in trusty) does not create symlinks in /dev/disk/by-path/ for
  any disks that are connected via sata.

  [test case]

  Install trusty onto a system with sata drives, and check /dev/disk/by-
  path/ for symlink(s) to those sata drive(s).

  [regression potential]

  the (s)ata by-path symlinks were removed due to apparent possibility of 
non-uniqueness:
  https://git.kernel.org/pub/scm/linux/hotplug/udev.git/commit/?id=481dcf7c8f

  however that was *long* ago and it has been added back in:
  
https://github.com/systemd/systemd/commit/ba86822db70d9ffd02ad78cd02b237ff8c569c7a

  if there is still a possibility for non-uniqueness, then /dev/disk/by-
  path/ symlink(s) might be created that are non-deterministic as far as
  the actual disk/path they point to.

  [other info]

  this is 'fixed' (the by-path symlinks are created for ata disks) in
  Xenial and later systemd/udev.

  Also bug 1611945 indicates that sata devices connected via PMP (port
  multiplier device) may still have incorrect by-path symlinks created,
  even upstream.  However, since Xenial and later currently do have udev
  code that creates ata by-path symlinks, that is a separate issue and
  not a reason for keeping ata by-path symlinks about of trusty udev.

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

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

[Touch-packages] [Bug 1802525] Re: (s)ata disks do not have /dev/disk/by-path links created

[Dan Streetman]

ubuntu@dwalin:~$ dpkg -l | grep ' udev '
ii  udev  204-5ubuntu20.28  
   amd64/dev/ and hotplug management daemon
ubuntu@dwalin:~$ ls -l /dev/disk/by-path/
ls: cannot access /dev/disk/by-path/: No such file or directory


ubuntu@dwalin:~$ dpkg -l | grep ' udev '
ii  udev  204-5ubuntu20.29  
   amd64/dev/ and hotplug management daemon
ubuntu@dwalin:~$ ls -l /dev/disk/by-path/
total 0
lrwxrwxrwx 1 root root  9 Nov 29 21:43 pci-:00:1f.2-ata-1 -> ../../sda
lrwxrwxrwx 1 root root 10 Nov 29 21:43 pci-:00:1f.2-ata-1-part1 -> 
../../sda1


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

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

Title:
  (s)ata disks do not have /dev/disk/by-path links created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  [impact]

  udev (in trusty) does not create symlinks in /dev/disk/by-path/ for
  any disks that are connected via sata.

  [test case]

  Install trusty onto a system with sata drives, and check /dev/disk/by-
  path/ for symlink(s) to those sata drive(s).

  [regression potential]

  the (s)ata by-path symlinks were removed due to apparent possibility of 
non-uniqueness:
  https://git.kernel.org/pub/scm/linux/hotplug/udev.git/commit/?id=481dcf7c8f

  however that was *long* ago and it has been added back in:
  
https://github.com/systemd/systemd/commit/ba86822db70d9ffd02ad78cd02b237ff8c569c7a

  if there is still a possibility for non-uniqueness, then /dev/disk/by-
  path/ symlink(s) might be created that are non-deterministic as far as
  the actual disk/path they point to.

  [other info]

  this is 'fixed' (the by-path symlinks are created for ata disks) in
  Xenial and later systemd/udev.

  Also bug 1611945 indicates that sata devices connected via PMP (port
  multiplier device) may still have incorrect by-path symlinks created,
  even upstream.  However, since Xenial and later currently do have udev
  code that creates ata by-path symlinks, that is a separate issue and
  not a reason for keeping ata by-path symlinks about of trusty udev.

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

-- 
Mailing list: https://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 1773859] Please test proposed package

[b0w]

Yo tambien tengo dudas de como resolverlo! I Still have some doubts on how
to fix it, but if in 7 days it will be available for everyone i will just
wait the update.
Greetings!

On Thu, Nov 29, 2018 at 12:31 PM Alejandro <1773...@bugs.launchpad.net>
wrote:

> José Enrique,disculpa y gracias por contestarme.Quería pedirte si me
> puedes contar brevemente ¿cómo pudiste borrar el systemd-shim package?No se
> cómo accederloMuchas graciasAlejandro
>   -
>   -
>  -
>
>
>   -
>  - -
> José Enrique <1773...@bugs.launchpad.net>
>
>   -
>   - Nov 19 at 2:01 PM
>
>
>- To avertaness...@yahoo.com
>   -
>
> Message body
> Thanks a lot for your help. I resolved my problem erasing systemd-shim and
> updating.
> I'll try new solution in another pc.
> Kind regards
>
>
>   From: José Enrique <1773...@bugs.launchpad.net>
>  To: avertaness...@yahoo.com
>  Sent: Tuesday, November 27, 2018 3:01 PM
>  Subject: Re: [Bug 1773859] Please test proposed package
>
> Lo siento Alejandro, no soy Lucas
>  Saludos
>
> El mar., 27 nov. 2018 18:51, Alejandro <1773...@bugs.launchpad.net>
> escribió:
>
> > Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make
> > this test in the last weeks I will make them as soon as
> > possibleRegardsAlejandro
> >
> >  From: Łukasz Zemczak <1773...@bugs.launchpad.net>
> >  To: avertaness...@yahoo.com
> >  Sent: Tuesday, November 20, 2018 9:21 AM
> >  Subject: [Bug 1773859] Please test proposed package
> >
> > Hello Kees, or anyone else affected,
> >
> > Accepted systemd into bionic-proposed. The package will build now and be
> > available at
> > https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 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 subscribed to a
> > duplicate bug report (1796221).
> > https://bugs.launchpad.net/bugs/1773859
> >
> > Title:
> >  upgrades to 18.04 fail
> >
> > Status in systemd package in Ubuntu:
> >  Fix Released
> > Status in systemd-shim package in Ubuntu:
> >  Won't Fix
> > Status in systemd source package in Bionic:
> >  Fix Committed
> > Status in systemd-shim source package in Bionic:
> >  Won't Fix
> > Status in systemd source package in Cosmic:
> >  Fix Released
> > Status in systemd-shim source package in Cosmic:
> >  Won't Fix
> >
> > Bug description:
> >  [Impact]
> >
> >* Some systems fail to upgrade due to conflicts between systemd and
> >  the (now removed from the archive) systemd-shim / upstart.
> >
> >* Instead of trying to work out what's the problem in ordering /
> >  removal of diverts, ensure that systemd is never unpacked whilst
> >  systemd-shim/upstart are still on disk. Thus declare conflicts against
> >  systemd-shim/upstart packages in systemd package.
> >
> >  [Test Case]
> >
> >* monitor drop-off of upgrades with below reported problem
> >
> >* Check that it is possible to upgrade to bionic's libpam-systemd
> >  from xenial with systemd-shim installed on xenial, ie.
> >
> >  lxc launch ubuntu-daily:xenial test-shim-upgrade
> >  lxc exec test-shim-upgrade
> >  apt update
> >  apt install systemd-shim
> >  wget
> >
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
> >  apt install ./systemd-shim_10-3_amd64.deb
> >  sed 's/xenial/bionic/' -i /etc/apt/sources.list
> >  apt update
> >  apt install systemd
> >
> >  this currently passes, however, systemd-shim remains installed. It
> >  should be removed instead. Apt install systemd should have lines like
> >  this:
> >
> >  The following packages will be REMOVED:
> >systemd-shim
> >  ...
> >  Removing 'diversion of
> > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> >
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> > by systemd-shim'
> >  ...
> >
> >
> >  [Regression Potential]
> >
> >* systemd-shim

[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

[b0w]

Is there any package available that fix this thing?

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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

[Touch-packages] [Bug 1805757] Re: libjack-jackd2-dev can't be installed on ubuntu 18.10

[Lukas Florea]

Apparently there are new wine package sources for Ubuntu 18.10. I removed 
wine-staging, installed the ffmpeg build dependencies, compiled ffmpeg and 
installed the wine packages again like this:
(see: https://wiki.winehq.org/Ubuntu )

wget -nc 
https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/Ubuntu_18.10_standard/Release.key
sudo apt-key add Release.key
sudo apt-add-repository 'deb 
https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/Ubuntu_18.10_standard
 ./'
sudo apt-get install wine-staging

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

Title:
  libjack-jackd2-dev can't be installed on ubuntu 18.10

Status in jackd2 package in Ubuntu:
  Invalid

Bug description:
  I need the package for the build-dep of ffmpeg. But it can't be installed:
  sudo apt-get install libjack-jackd2-dev
  Paketlisten werden gelesen... Fertig
  Abhängigkeitsbaum wird aufgebaut.   
  Statusinformationen werden eingelesen Fertig
  Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
  Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
  Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
  nicht erstellt wurden oder Incoming noch nicht verlassen haben.
  Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

  Die folgenden Pakete haben unerfüllte Abhängigkeiten:
   libjack-jackd2-dev : Hängt ab von: libjack-jackd2-0 (= 1.9.12~dfsg-2) aber 
2:1.9.11~20160223-1~wily1 soll installiert werden
  E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte 
Pakete.

  Sorry it is in German, I don't know how to set apt back to English...
  But it basically says that it depends from libjack-jackd2-0 (=
  1.9.12~dfsg-2) but 2:1.9.11~20160223-1~wily1 should be installed.

  Output of "apt policy libjack-jackd2-dev libjack-jackd2-0":
  libjack-jackd2-dev:
Installiert:   (keine)
Installationskandidat: 1.9.12~dfsg-2
Versionstabelle:
   1.9.12~dfsg-2 500
  500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  libjack-jackd2-0:
Installiert:   2:1.9.11~20160223-1~wily1
Installationskandidat: 2:1.9.11~20160223-1~wily1
Versionstabelle:
   *** 2:1.9.11~20160223-1~wily1 100
  100 /var/lib/dpkg/status
   1.9.12~dfsg-2 500
  500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages

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

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

[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 18.2.6-1ubuntu1

---
mesa (18.2.6-1ubuntu1) disco; urgency=medium

  * Merge from Debian.
- add missing i965 pci-id's (LP: #1789924)

 -- Timo Aaltonen   Wed, 28 Nov 2018 23:14:08 +0200

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

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  New
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails

[Rene Meier]

Yes but only because they have reverted the changes from CVE-2018-6954. This 
will come back very soon. Have a look at 
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.10 and 
https://launchpad.net/bugs/1804847 . 

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

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

Title:
  systemd-tmpfiles-setup.service fails

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service
  fails with:

  Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and 
Directories...
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/var": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/home": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/srv": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main 
process exited, code=exited, status=1/FAILURE
  Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed 
with result 'exit-code'.
  Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files 
and Directories.

  This happens on btrfs root filesystems in real hardware and on our
  virtualized servers as well. 237-3ubuntu10.6 didnt show this errors
  and going back to 237-3ubuntu10 removes them as well.

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

  # apt-cache policy systemd
  systemd:
Installiert:   237-3ubuntu10.9
Installationskandidat: 237-3ubuntu10.9
Versionstabelle:
   *** 237-3ubuntu10.9 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

[Rene Meier]

Could someone please have a look at https://launchpad.net/bugs/1804603
because the changes made to fix CVE-2018-6954 break systemd-tmpfiles
also in a different way.

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

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

  To verify I tried this:

  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument

  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade
  of systemd to 229-4ubuntu21.8.

  At this point I don't know what to do.

  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
    i->uid_set ? i->uid : UID_INVALID,
    i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../

  Tag v238

  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../

  Any help fixing this problem would be highly appreciated.
  Many thanks,
  Rafael

  === Notes ===
  fchownat() was added to Linux in kernel 2.6.16;
  library support was added to glibc in version 2.4.
  checkinf if it is blocked/filtered/sandboxed, rarther than unavailable.
  glibc in bionic requires minimum linux 3.2.

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[aditya lele]

Same problem with Asus Zenbook UX533FD.

Also, can someone please specify the windows shutdown method?
"i.e. go to shutdown on the windows start menu and hold shift while pressing 
restart. A screen will appear where you can select to shutdown." This doesn't 
work.

I am dual booting Win10 and Ubuntu 18.04.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1798073] Update Released

[Brian Murray]

The verification of the Stable Release Update for ubuntu-keyring 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 ubuntu-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1798073

Title:
  [SRU] Provide 2018 archive signing key on stable releases

Status in ubuntu-keyring package in Ubuntu:
  Fix Released
Status in ubuntu-keyring source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * For LTS releases to be able to bootstrap dual and single signed
  future releases, and validate all signatures, 2018 archive signing key
  should be SRUed back

   * Also build process has improved documentation and vague validation
  that all key snippets are signed correctly

  [Test Case]

   * $ apt-key list
  ...
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
  --
  pub   rsa4096 2018-09-17 [SC]
    F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2018) 

  ...

  apt-key list should contain the 2018 archive key.

  [Regression Potential]

   * Build-process, key algo, and key size, and file format are the same
  as previous key snippets thus supported by all of gpg1 gpg2 gpgv1
  gpgv2.

  [Other Info]

   * 2018 key is to be used for dual-signing in DD series and up

   * Bileto PPA is built against security pocket only, suitable to be
  released into both -security and -updates

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

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

[Touch-packages] [Bug 1798073] Re: [SRU] Provide 2018 archive signing key on stable releases

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-keyring - 2018.09.18.1~18.04.0

---
ubuntu-keyring (2018.09.18.1~18.04.0) bionic; urgency=medium

  * keyrings/ubuntu-keyring-2018-archive.gpg,
keyrings/ubuntu-archive-keyring.gpg: add new archive signing key.
  * Improve README.Source with upgrade/change instructions.
  * Validate that all shipped fragments are signed.
  * LP: #1798073

 -- Dimitri John Ledkov   Tue, 18 Sep 2018 17:03:46
+0200

** Changed in: ubuntu-keyring (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 ubuntu-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1798073

Title:
  [SRU] Provide 2018 archive signing key on stable releases

Status in ubuntu-keyring package in Ubuntu:
  Fix Released
Status in ubuntu-keyring source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * For LTS releases to be able to bootstrap dual and single signed
  future releases, and validate all signatures, 2018 archive signing key
  should be SRUed back

   * Also build process has improved documentation and vague validation
  that all key snippets are signed correctly

  [Test Case]

   * $ apt-key list
  ...
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
  --
  pub   rsa4096 2018-09-17 [SC]
    F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2018) 

  ...

  apt-key list should contain the 2018 archive key.

  [Regression Potential]

   * Build-process, key algo, and key size, and file format are the same
  as previous key snippets thus supported by all of gpg1 gpg2 gpgv1
  gpgv2.

  [Other Info]

   * 2018 key is to be used for dual-signing in DD series and up

   * Bileto PPA is built against security pocket only, suitable to be
  released into both -security and -updates

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

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

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[Andreas Hasenack]

** Changed in: landscape-client (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: landscape-client (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: landscape-client (Ubuntu Bionic)
 Assignee: (unassigned) => Simon Poirier (simpoir)

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in landscape-client source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

  
  Used Landscape (Paid Canonical Subscription) to upgrade one of my machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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

[Touch-packages] [Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep

[Yan Li]

Also seeing this problem with 18.10 Cosmic. The offending Qt application
is the VirtualBox from Ubuntu repo.

** Tags added: cosmic

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

Title:
  icons from qt applications disappear after screen lock/sleep

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Indicators of some Qt apps are not showing after unlocking the screen
  or shell restart.

  
  [Test case]

  - Login to 17.10
  - launch dropbox (if not already launched)
  - Launch telegram (snap version or without libappindicator support)
  - Observe icons in taskbar
  - Lock screen with Super+L
  - Unlock screen
  - Icons should still be there

  
  [Possible regressions]

  Icons that should be hidden could be visible instead

  The fix doesn't apply to snapped applications

  In the Ubuntu Xorg session, with the Ubuntu Appindicator extension
  enabled, the tray icons for QT apps (in my case, both owncloud-client
  from the Ubuntu repos and enpass, from their own repo) show up after
  first logging in. But once the screen has been left idle long enough
  to be put to sleep, and is then woken up (I don't actually have screen
  *lock* enabled, but it still goes comes back to the clock screen and a
  further gesture is needed to scroll that up to get the desktop), then
  the icons for those QT apps are gone. Non-QT apps (eg: in my case
  hexchat, from the ubuntu repos) remain.

  For a while and due to inattention it seemed more random than that,
  but I'm fairly sure now it's just the display sleep/wake thing that
  kills it.

  The applications are still running in the background (so for instance
  enpass is still available via the browser extension), and can be seen
  in the process list. It's just the icons that have disappeared. If I
  then kill those apps (from the commandline with 'kill [pid]' because
  there's no other interface to do it from) and relaunch them, they
  reappear back in the appindicator area.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 24 17:12:43 2017
  Dependencies:

  InstallationDate: Installed on 2017-07-30 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to artful on 2017-08-22 (2 days ago)

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

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

[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled

[Dan Streetman]

** Bug watch added: Debian Bug tracker #915049
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915049

** Also affects: systemd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915049
   Importance: Unknown
   Status: Unknown

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

Title:
  systemd-resolved has issues when the answer is over 512 bytes with
  EDNS disabled

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd package in Debian:
  Unknown

Bug description:
  [Impact]

  TCP stub is cutting down the payload to 512 bytes when EDNS is
  disabled. This makes non-EDNS clients (nslookup) receive a "shortened"
  answer even when UDP returns a truncated reply for a new TCP query.
  For instance,

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  In the second case, no-EDNS, TCP should provide the complete answer,
  but it's capped at UDP's size.

  [Test Case]

  Query systemd-resolved with a domain name that resolves to multiple
  (lots.. 30+) A records. A client with EDNS support (dig) will receive
  all of them, a client without support (nslookup or dig +noedns) will
  have a truncated list. Using the example above:

  EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 
| wc -l

  [Regression potential]

  Minimal. This change only affects TCP requests, and the new size is
  already used in the code for other requests.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10816
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce

  [Original Description]

  Querying a domain name that has >512 bytes in records (e.g. 30+ A
  records), the number of results depends on the DNS client used:

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  Normally a client that doesn't support EDNS would receive a truncated
  reply from the initial UDP connection (limited by the spec to 512
  bytes) and a second query would be established via TCP to receive the
  complete results. In this case, the number of results is the same
  regardless of the protocol used (29).

  Upstream bug: https://github.com/systemd/systemd/issues/10816

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

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

[Touch-packages] [Bug 1781440] Re: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1

[Till Kamppeter]

Now the update from Bionic to Cosmic is correctly working. Thank you for
the fix.

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

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

Title:
  package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which
  is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1

Status in wayland package in Ubuntu:
  Fix Released
Status in wayland source package in Bionic:
  Fix Committed
Status in wayland source package in Cosmic:
  Fix Committed

Bug description:
  [impact]

  upgrade from bionic fails if libwayland-dev & libegl1-mesa-dev was
  installed

  [test case]

  install libwayland-dev & libegl1-mesa-dev on bionic, upgrade to cosmic

  [regression potential]

  none, the fix only changes the version numbers in Breaks/Replaces

  
  --

  Occured when upgrading from Bionic to Cosmic.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libwayland-dev 1.15.0-2
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.10-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jul 12 18:41:26 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package 
libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 620 [17aa:224e]
  InstallationDate: Installed on 2018-02-07 (155 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
  MachineType: LENOVO 20JDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=150ad8bc-1d20-4de9-a767-b2b0679455f3 ro quiet splash acpi_osi= 
vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu3
   apt  1.7.0~alpha2
  SourcePackage: wayland
  Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also 
in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1NET33W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1NET33W(1.20):bd10/26/2017:svnLENOVO:pn20JDCTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 2nd
  dmi.product.name: 20JDCTO1WW
  dmi.product.version: ThinkPad X1 Yoga 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.3-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1805178] Re: Apparmor should include letsencrypt directory for Slapd

[Jamie Strandboge]

I echo ahasenack's question. /etc/letsencrypt/** is pretty broad
(especially if it contains private keys).

Once those details are worked out, updating slapd is conceptually fine.
We may want to consider updating the ssl_certs and ssl_keys abstractions
accordingly if letsencrypt organizing things clearly. (We could also
create a letsencrypt abstraction, but let's not go there just yet).

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

Title:
  Apparmor should include letsencrypt directory for Slapd

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  Apparmor denies access to /etc/letsencrypt for slapd, which is
  confusing for users trying to secure ldap with Letsencrypt in a stock
  configuration.

  The fix is inserting the following line in
  /etc/apparmor.d/usr.sbin.slapd:

/etc/letsencrypt/** r,

  and then refreshing the profile:

  # apparmor_parser -vr usr.sbin.slapd

  This line should simply be included.

  tarek : )

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

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

[Touch-packages] [Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

[Andreas Hasenack]

According to
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1420522 it's
fixed in seahorse 3.30, which is present in ubuntu cosmic and later.

>From https://bugzilla.redhat.com/show_bug.cgi?id=1435924, this should 
>reproduce the problem:
1. Generate a ssh key using the keytype ed25519 and enter a password when 
creating the key:
$ ssh-keygen -t ed25519
2. Log out from your computer and log in again
3. Start a ssh session to a remote host:
$ ssh u...@domain.tld

I tried that with bionic, which has seahorse 3.20.0

Comment #88 hints that trusty is affected and also broke, can someone
confirm that please? trusty has seahorse 3.10.2-0ubuntu1

Releases older than trusty are EOL by now.

** Bug watch added: Red Hat Bugzilla #1435924
   https://bugzilla.redhat.com/show_bug.cgi?id=1435924

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

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

Title:
  ssh Agent admitted failure to sign using the key on big endian
  machines

Status in seahorse:
  Fix Released
Status in gnome-keyring package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  on hardy (preserved home folder from feisty) i get the following when
  i try to ssh

  Agent admitted failure to sign using the key.
  Permission denied (publickey).

  or with verbose on

  sam@titania:~$ ssh -v oberon
  OpenSSH_4.7p1 Debian-4ubuntu1, OpenSSL 0.9.8g 19 Oct 2007
  debug1: Reading configuration data /home/sam/.ssh/config
  debug1: Applying options for oberon
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: Applying options for *
  debug1: Connecting to ## [##] port ##.
  debug1: Connection established.
  debug1: identity file /home/sam/.ssh/identity type -1
  debug1: identity file /home/sam/.ssh/id_rsa type 1
  debug1: identity file /home/sam/.ssh/id_dsa type -1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_4.6p1 
Debian-5ubuntu0.1
  debug1: match: OpenSSH_4.6p1 Debian-5ubuntu0.1 pat OpenSSH*
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-4ubuntu1
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: server->client aes128-cbc hmac-md5 none
  debug1: kex: client->server aes128-cbc hmac-md5 none
  debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
  debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
  debug1: using hostkeyalias: oberon
  debug1: Host 'oberon' is known and matches the RSA host key.
  debug1: Found key in /home/sam/.ssh/known_hosts:1
  debug1: ssh_rsa_verify: signature correct
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_SERVICE_REQUEST sent
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: publickey
  debug1: Next authentication method: publickey
  debug1: Offering public key: /home/sam/.ssh/id_rsa
  debug1: Server accepts key: pkalg ssh-rsa blen 277
  Agent admitted failure to sign using the key.
  debug1: Trying private key: /home/sam/.ssh/identity
  debug1: Trying private key: /home/sam/.ssh/id_dsa
  debug1: No more authentication methods to try.
  Permission denied (publickey).

  I tried generating a new key. this worked for a few logons, but then i
  get back to this error.

  I think it is to do with the local key agent. i found that
   SSH_AUTH_SOCK=0 ssh oberon
  works fine.

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

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

[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled

[Dan Streetman]

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

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/10816
   Importance: Unknown
   Status: Unknown

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

Title:
  systemd-resolved has issues when the answer is over 512 bytes with
  EDNS disabled

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [Impact]

  TCP stub is cutting down the payload to 512 bytes when EDNS is
  disabled. This makes non-EDNS clients (nslookup) receive a "shortened"
  answer even when UDP returns a truncated reply for a new TCP query.
  For instance,

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  In the second case, no-EDNS, TCP should provide the complete answer,
  but it's capped at UDP's size.

  [Test Case]

  Query systemd-resolved with a domain name that resolves to multiple
  (lots.. 30+) A records. A client with EDNS support (dig) will receive
  all of them, a client without support (nslookup or dig +noedns) will
  have a truncated list. Using the example above:

  EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 
| wc -l

  [Regression potential]

  Minimal. This change only affects TCP requests, and the new size is
  already used in the code for other requests.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10816
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce

  [Original Description]

  Querying a domain name that has >512 bytes in records (e.g. 30+ A
  records), the number of results depends on the DNS client used:

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  Normally a client that doesn't support EDNS would receive a truncated
  reply from the initial UDP connection (limited by the spec to 512
  bytes) and a second query would be established via TCP to receive the
  complete results. In this case, the number of results is the same
  regardless of the protocol used (29).

  Upstream bug: https://github.com/systemd/systemd/issues/10816

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

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

[Touch-packages] [Bug 1799038] Re: Ubuntu 18.10 does not suspend on lid close

[Gert van de Kraats]

I have the same problem on a fresh installed 18.10 for 32-bits, but only if 
external monitor is connected.
Indeed this is a well known peoblem at internet.

sudo journalctl -b -u systemd-logind  with debugging on 
(systemd.log-level=debug) without external monitor shows succeeding suspend:
Nov 29 16:56:04 Gert2 systemd-logind[438]: Lid closed
Nov 29 16:56:04 Gert2 systemd-logind[438]: device-enumerator: scan all dirs
Nov 29 16:56:04 Gert2 systemd-logind[438]:   device-enumerator: scanning 
/sys/bus
Nov 29 16:56:04 Gert2 systemd-logind[438]:   device-enumerator: scanning 
/sys/class
Nov 29 16:56:04 Gert2 systemd-logind[438]: Failed to open configuration file 
'/etc/systemd/sleep.conf': No such file or directory
Nov 29 16:56:04 Gert2 systemd-logind[438]: Suspending...

sudo journalctl -b -u systemd-logind  with debugging on 
(systemd.log-level=debug) with connected external monitor shows refusing 
suspend:
Nov 29 15:05:58 Gert2 systemd-logind[426]: Lid closed.
Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scan all dirs
Nov 29 15:05:58 Gert2 systemd-logind[426]:   device-enumerator: scanning 
/sys/bus
Nov 29 15:05:58 Gert2 systemd-logind[426]:   device-enumerator: scanning 
/sys/class
Nov 29 15:05:58 Gert2 systemd-logind[426]: External (1) displays connected.
Nov 29 15:05:58 Gert2 systemd-logind[426]: Refusing operation, as it is turned 
off.
Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scan all dirs
Nov 29 15:05:58 Gert2 systemd-logind[426]:   device-enumerator: scanning 
/sys/bus
Nov 29 15:05:58 Gert2 systemd-logind[426]:   device-enumerator: scanning 
/sys/class
Nov 29 15:05:58 Gert2 systemd-logind[426]: External (1) displays connected.
Nov 29 15:05:58 Gert2 systemd-logind[426]: Refusing operation, as it is turned 
off.
Nov 29 15:05:59 Gert2 systemd-logind[426]: Got message type=method_call 
sender=:1.238 destination=:1.3 path=/org/freedesktop/login1/session/_32 
interface=org.freedesktop.login1.Session member=ReleaseDevice cookie=154 
reply_cookie=0 signature=uu error-name=n/a error-message=n/a
Nov 29 15:05:59 Gert2 systemd-logind[426]: Sent message type=signal sender=n/a 
destination=:1.238 path=/org/freedesktop/login1/session/_32 
interface=org.freedesktop.login1.Session member=PauseDevice cookie=227 
reply_cookie=0 signature=uus error-name=n/a error-message=n/a
Nov 29 15:05:59 Gert2 systemd[1]: systemd-logind.service: Got notification 
message from PID 426 (FDSTOREREMOVE=1, FDNAME=session-2-device-13-71)
Nov 29 15:05:59 Gert2 systemd[1]: systemd-logind.service: Got explicit request 
to remove fd 174 (session-2-device-13-71), closing.
Nov 29 15:05:59 Gert2 systemd-logind[426]: Sent message type=method_return 
sender=n/a destination=:1.238 path=n/a interface=n/a member=n/a cookie=228 
reply_cookie=154 signature=n/a error-name=n/a error-message=n/a
Nov 29 15:05:59 Gert2 systemd-logind[426]: device-enumerator: scan all dirs
Nov 29 15:05:59 Gert2 systemd-logind[426]:   device-enumerator: scanning 
/sys/bus
Nov 29 15:05:59 Gert2 systemd-logind[426]:   device-enumerator: scanning 
/sys/class
Nov 29 15:05:59 Gert2 systemd-logind[426]: External (1) displays connected.
Nov 29 15:05:59 Gert2 systemd-logind[426]: Refusing operation, as it is turned 
off.
Nov 29 15:06:10 Gert2 systemd-logind[426]: Lid opened.

The command systemd-inhibit --list shows next entry as soon as an external 
monitor is attached to the laptop.
 Who: gert (UID 1000/gert, PID 2342/gsd-power)
What: handle-lid-switch
 Why: Multiple displays attached
Mode: block

So program gsd-power is responsible for inhibiting the handling of the
lid-switch.  The suspend-action will not occcur. This is not
configurable and I think that is ridiculous.

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

Title:
  Ubuntu 18.10 does not suspend on lid close

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid
  on notebooks does not work any more.

  The machine goes to suspend mode but wakes up immediately due to some
  events (can be network, or others).

  In 18.04 this issue was fixed (we had the same situation with any
  version since 14.04).

  Seems a regression.

  Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. 
The changes do NOTHING.
  One might spare the time to experiment.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: systemd 239-7ubuntu10
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 11:55:48 2018
  InstallationDate: Installed on 2018-04-30 (174 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux F

[Touch-packages] [Bug 1805178] Re: Apparmor should include letsencrypt directory for Slapd

[John Johansen]

Marked this public security for now so it is on the security team radar
and it can be reviewed by them.


** Information type changed from Public to Public Security

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

Title:
  Apparmor should include letsencrypt directory for Slapd

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  Apparmor denies access to /etc/letsencrypt for slapd, which is
  confusing for users trying to secure ldap with Letsencrypt in a stock
  configuration.

  The fix is inserting the following line in
  /etc/apparmor.d/usr.sbin.slapd:

/etc/letsencrypt/** r,

  and then refreshing the profile:

  # apparmor_parser -vr usr.sbin.slapd

  This line should simply be included.

  tarek : )

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

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

[Touch-packages] [Bug 1805178] Re: Apparmor should include letsencrypt directory for Slapd

[Andreas Hasenack]

I'm removing apparmor from the affected list because the apparmor
profile is shipped with slapd.

** No longer affects: apparmor (Ubuntu)

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

Title:
  Apparmor should include letsencrypt directory for Slapd

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  Apparmor denies access to /etc/letsencrypt for slapd, which is
  confusing for users trying to secure ldap with Letsencrypt in a stock
  configuration.

  The fix is inserting the following line in
  /etc/apparmor.d/usr.sbin.slapd:

/etc/letsencrypt/** r,

  and then refreshing the profile:

  # apparmor_parser -vr usr.sbin.slapd

  This line should simply be included.

  tarek : )

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

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

[Touch-packages] [Bug 1805178] Re: Apparmor should include letsencrypt directory for Slapd

[Andreas Hasenack]

Thanks for filing this bug in Ubuntu.

First, let me suggest that any local modifications to apparmor profiles
be made in /etc/apparmor.d/local instead of the profile in
/etc/apparmor.d, otherwise you will get dpkg conf prompts with every
upgrade. For slapd, for example, you have
/etc/apparmor.d/local/usr.sbin.slapd

Second, what is the structure of files and directories in
/etc/letsencrypt? Is it separated by user, service, or do all certs go
in there? It would be good if we could come up with a rule that's a bit
more specific.

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

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

Title:
  Apparmor should include letsencrypt directory for Slapd

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  Apparmor denies access to /etc/letsencrypt for slapd, which is
  confusing for users trying to secure ldap with Letsencrypt in a stock
  configuration.

  The fix is inserting the following line in
  /etc/apparmor.d/usr.sbin.slapd:

/etc/letsencrypt/** r,

  and then refreshing the profile:

  # apparmor_parser -vr usr.sbin.slapd

  This line should simply be included.

  tarek : )

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

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

[Touch-packages] [Bug 1788643] Re: zombies pile up, system becomes unresponsive

[Launchpad Bug Tracker]

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

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

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

Title:
  zombies pile up, system becomes unresponsive

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 16.04.5 LTS
  Release:16.04

  systemd:
Installed: 229-4ubuntu21.4
Candidate: 229-4ubuntu21.4
Version table:
   *** 229-4ubuntu21.4 500
  500 http://azure.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu21.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://azure.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  This problem is in Azure. We are seeing these problems on different
  systems. Worker nodes (Ubuntu 16.04) in a hadoop cluster start piling
  up zombies and become unresponsive. The syslog and the kernel logs
  don't provide much information.

  The only error we could correlate with what we are seeing was in the
  audit logs. See at the end of this message, the "Connection timed out"
  and the "Cannot create session: Already running in a session"
  messages.

  Our first suspect was memory pressure on the machines. We added
  logging and settings to reboot on out of memory, but all these turned
  to be red herrings.

  Aug 18 19:11:08 wn2-d3ncsp su[112600]: Successful su for root by root
  Aug 18 19:11:08 wn2-d3ncsp su[112600]: + ??? root:root
  Aug 18 19:11:08 wn2-d3ncsp su[112600]: pam_unix(su:session): session opened 
for user root by (uid=0)
  Aug 18 19:11:08 wn2-d3ncsp systemd-logind[1486]: New session c8 of user root.
  Aug 18 19:11:26 wn2-d3ncsp sshd[112690]: Did not receive identification 
string from 10.84.93.35
  Aug 18 19:11:34 wn2-d3ncsp su[112600]: pam_systemd(su:session): Failed to 
create session: Connection timed out
  Aug 18 19:11:34 wn2-d3ncsp su[112600]: pam_unix(su:session): session closed 
for user root
  Aug 18 19:11:34 wn2-d3ncsp systemd-logind[1486]: Removed session c8.

   
  Aug 18 19:12:03 wn2-d3ncsp sudo: ehiadmin : TTY=pts/1 ; PWD=/home/ehiadmin ; 
USER=root ; COMMAND=/bin/su -
  Aug 18 19:12:03 wn2-d3ncsp sudo: pam_unix(sudo:session): session opened for 
user root by ehiadmin(uid=0)
  Aug 18 19:12:03 wn2-d3ncsp su[113085]: Successful su for root by root
  Aug 18 19:12:03 wn2-d3ncsp su[113085]: + /dev/pts/1 root:root
  Aug 18 19:12:03 wn2-d3ncsp su[113085]: pam_unix(su:session): session opened 
for user root by ehiadmin(uid=0)
  Aug 18 19:12:03 wn2-d3ncsp su[113085]: pam_systemd(su:session): Cannot create 
session: Already running in a session
  Aug 18 19:12:42 wn2-d3ncsp sshd[113274]: Did not receive identification 
string from 10.84.93.42
  Aug 18 19:13:37 wn2-d3ncsp su[113085]: pam_unix(su:session): session closed 
for user root
  Aug 18 19:13:37 wn2-d3ncsp sudo: pam_unix(sudo:session): session closed for 
user root
  Aug 18 19:13:37 wn2-d3ncsp sshd[112285]: pam_unix(sshd:session): session 
closed for user ehiadmin
  Aug 18 19:13:37 wn2-d3ncsp systemd-logind[1486]: Removed session 1291.

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

-- 
Mailing list: https://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 1773859] Please test proposed package

[Alejandro]

José Enrique,disculpa y gracias por contestarme.Quería pedirte si me puedes 
contar brevemente ¿cómo pudiste borrar el systemd-shim package?No se cómo 
accederloMuchas graciasAlejandro   
  -   
  -  
 -  


  -  
 - -
José Enrique <1773...@bugs.launchpad.net>
   
  - 
  - Nov 19 at 2:01 PM

   
   - To avertaness...@yahoo.com
  - 

Message body
Thanks a lot for your help. I resolved my problem erasing systemd-shim and
updating.
I'll try new solution in another pc.
Kind regards


  From: José Enrique <1773...@bugs.launchpad.net>
 To: avertaness...@yahoo.com 
 Sent: Tuesday, November 27, 2018 3:01 PM
 Subject: Re: [Bug 1773859] Please test proposed package
   
Lo siento Alejandro, no soy Lucas
 Saludos

El mar., 27 nov. 2018 18:51, Alejandro <1773...@bugs.launchpad.net>
escribió:

> Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make
> this test in the last weeks I will make them as soon as
> possibleRegardsAlejandro
>
>      From: Łukasz Zemczak <1773...@bugs.launchpad.net>
>  To: avertaness...@yahoo.com
>  Sent: Tuesday, November 20, 2018 9:21 AM
>  Subject: [Bug 1773859] Please test proposed package
>
> Hello Kees, or anyone else affected,
>
> Accepted systemd into bionic-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 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 subscribed to a
> duplicate bug report (1796221).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
>  upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
>  Fix Released
> Status in systemd-shim package in Ubuntu:
>  Won't Fix
> Status in systemd source package in Bionic:
>  Fix Committed
> Status in systemd-shim source package in Bionic:
>  Won't Fix
> Status in systemd source package in Cosmic:
>  Fix Released
> Status in systemd-shim source package in Cosmic:
>  Won't Fix
>
> Bug description:
>  [Impact]
>
>    * Some systems fail to upgrade due to conflicts between systemd and
>  the (now removed from the archive) systemd-shim / upstart.
>
>    * Instead of trying to work out what's the problem in ordering /
>  removal of diverts, ensure that systemd is never unpacked whilst
>  systemd-shim/upstart are still on disk. Thus declare conflicts against
>  systemd-shim/upstart packages in systemd package.
>
>  [Test Case]
>
>    * monitor drop-off of upgrades with below reported problem
>
>    * Check that it is possible to upgrade to bionic's libpam-systemd
>  from xenial with systemd-shim installed on xenial, ie.
>
>  lxc launch ubuntu-daily:xenial test-shim-upgrade
>  lxc exec test-shim-upgrade
>  apt update
>  apt install systemd-shim
>  wget
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
>  apt install ./systemd-shim_10-3_amd64.deb
>  sed 's/xenial/bionic/' -i /etc/apt/sources.list
>  apt update
>  apt install systemd
>
>  this currently passes, however, systemd-shim remains installed. It
>  should be removed instead. Apt install systemd should have lines like
>  this:
>
>  The following packages will be REMOVED:
>    systemd-shim
>  ...
>  Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
>  ...
>
>
>  [Regression Potential]
>
>    * systemd-shim/upstart are both removed and not supported in bionic,
>  thus forcing their removal via conflicts should bring the system into
>  an expected state.
>
>  [Other Info]
>
>    * original bug report
>
>  $ sudo apt upgrade
>  Reading package lists... Done
>  Building dependency tree
>  Reading state information... Done
>  Calculating upgrade... Done
>  The following packages will be REMOVED:
>    systemd-shim
>  0 upgraded, 0 newly installed, 1 to remove and 0 not upgrad

[Touch-packages] [Bug 1805635] Re: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Robie Basak]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it
helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.


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

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I wasn't doing anything. Bug was there when I returned to screen first
  thing in the morning.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.6
  ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Nov 28 06:21:09 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-04-14 (227 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1799647] Re: Patch: Add configuration for german provider winSIM

[Iain Lane]

hey,

thanks!

The upstream repository has moved to: https://gitlab.gnome.org/GNOME
/mobile-broadband-provider-info - could you try submitting there please?

I just edited that wiki page to update the links.

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

Title:
  Patch: Add configuration for german provider winSIM

Status in mobile-broadband-provider-info package in Ubuntu:
  New

Bug description:
  I was unable to contribute a patch to the upstream gnome package:
  
https://wiki.gnome.org/Projects/NetworkManager/MobileBroadband/ServiceProviders
  (They seem to have migrated their git servers away)

  I still think this little config change adds value to Ubuntu users, hence I 
am opening this issue.
  Find the patchfile attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mobile-broadband-provider-info/+bug/1799647/+subscriptions

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

[Touch-packages] [Bug 1779157] Re: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-upgrade@1927:main:do_install

[Balint Reczey]

** Description changed:

+ [Impact]
+ 
+  * Unattended-upgrades can be crashing when packages are marked for removal 
after collecting upgradable packages.
+  * The fix clear the cache when it may be in an invalid state to lose 
markings.
+ 
+ [Test Case]
+ 
+  * Observe
+ https://errors.ubuntu.com/problem/66b5fef8d6dd83a7db6c494c807cfc067626c0c2
+ not occurring in fixed versions.
+ 
+ [Regression Potential]
+ 
+  * The extra cache.clear() can take extra CPU time when invoked
+ needlessly or can cause skipping updates when invoked at the wrong time.
+ However the fix received extensive testing in newer releases making
+ unnoticed regressions unlikely to surface.
+ 
+ [Original Bug Text]
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.1, the problem page at 
https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.
  
  Traceback
  
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1927, in 
  sys.exit(main(options))
    File "/usr/bin/unattended-upgrade", line 1782, in main
  logfile_dpkg)
    File "/usr/bin/unattended-upgrade", line 1057, in do_install
  "removal:%s" % "".join([pkg.name for pkg in marked_delete]))
  AssertionError: Internal error. The following packages are marked for 
removal:linux-headers-4.15.0-20-generic
  
  Also seen as:
  https://errors.ubuntu.com/problem/733d2e7865692e215f406231edd3692a6a1810c5

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

Title:
  /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-
  upgrade@1927:main:do_install

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades can be crashing when packages are marked for removal 
after collecting upgradable packages.
   * The fix clear the cache when it may be in an invalid state to lose 
markings.

  [Test Case]

   * Observe
  https://errors.ubuntu.com/problem/66b5fef8d6dd83a7db6c494c807cfc067626c0c2
  not occurring in fixed versions.

  [Regression Potential]

   * The extra cache.clear() can take extra CPU time when invoked
  needlessly or can cause skipping updates when invoked at the wrong
  time. However the fix received extensive testing in newer releases
  making unnoticed regressions unlikely to surface.

  [Original Bug Text]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.1, the problem page at 
https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Traceback

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1927, in 
  sys.exit(main(options))
    File "/usr/bin/unattended-upgrade", line 1782, in main
  logfile_dpkg)
    File "/usr/bin/unattended-upgrade", line 1057, in do_install
  "removal:%s" % "".join([pkg.name for pkg in marked_delete]))
  AssertionError: Internal error. The following packages are marked for 
removal:linux-headers-4.15.0-20-generic

  Also seen as:
  https://errors.ubuntu.com/problem/733d2e7865692e215f406231edd3692a6a1810c5

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

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

[Touch-packages] [Bug 1801439] Re: Unable to add software sources via the software-properties

[Brian Murray]

This is specific to software-properties-qt as I was unable to recreate
the crash using software-properties-gtk on Ubuntu 18.10.

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

Title:
  Unable to add software sources via the software-properties

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Test
  1. Start Software-properties. E.g. sudo software-properties-qt
  2. Navigate to Other Software (Tab), Add -> Add, to add a PPA
  3. Insert the PPA string. E.g. "deb 
http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " (or even the 
example repo given in the dialog, which is not a PPA)
  4. Click Okay.

  The software sources list does not contain the new field. Executing in
  terminal results in the following error message.

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 627, in on_add_clicked
  self.add_source_from_line(line)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
752, in add_source_from_line
  enable_source_code=enable_source_code)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
769, in add_source_from_shortcut
  worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
709, in check_and_add_key_for_whitelisted_shortcut
  self.options.keyserver)})
  AttributeError: type object 'OptionParsed' has no attribute 'keyserver'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: software-properties-qt 0.96.27
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sat Nov  3 09:59:52 2018
  InstallationDate: Installed on 2018-10-19 (14 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1702793] Re: Full backport SRU for unattended-upgrades

[Balint Reczey]

** Description changed:

  [Impact]
  
  * I would like to propose a one-off full backport of unattended-upgrades
  1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because 
selectively backporting fixes for crashes and for issues that made u-u 
unreliable would be more risky thanks to the huge number of fixes and the
  inter-dependencies between them.
  
  [Test Case]
  
  * Since this backport involves fixing several bugs and this bug itself
  covers the full backport I suggest that this bug should be considered
  verified when the following list of bugs are verified:
  
  - TODO add most important bugs
     + LP: #1615381 : apt-get autoremove may remove current kernel
  
  and the following tests are passing:
   - TODO add tests not covered by bugs above
  
  All LP bugs fixed by the backport, comments are welcome:
     + LP: #1230246
     + LP: #1260041 SRU template ok
-    + LP: #1269177 SRU template ok
+    + LP: #1269177 already fixed in 0.90ubuntu0.9
     + LP: #1357093
     + LP: #1396787 SRU template ok
     + LP: #1446552
     + LP: #1455097
     + LP: #1458204
-    + LP: #1544942
+    + LP: #1544942 already fixed in 0.90ubuntu0.8
     + LP: #1577215
     + LP: #1602536 SRU template ok
     + LP: #1615381
     + LP: #1624644 SRU template ok
     + LP: #1632361
     + LP: #1649709
     + LP: #1654070
     + LP: #1654600 SRU template ok
     + LP: #1675079 SRU template ok
     + LP: #1680599
     + LP: #1686470 SRU template ok
-    + LP: #1687129 to add u-u test case
+    + LP: #1687129 already fixed in 0.90ubuntu0.6
     + LP: #1690980
     + LP: #1698159
     + LP: #1702793 this bug
     + LP: #1714019 just a merge request
     + LP: #1718419 just a merge request
     + LP: #1719630
     + LP: #1722426 just a merge request
     + LP: #1737441
     + LP: #1737442 to add u-u test case
     + LP: #1737635
     + LP: #1737637
     + LP: #1737717
     + LP: #1741579
     + LP: #1764797 just a merge request
     + LP: #1773033 SRU template ok
     + LP: #1775292 SRU template ok
     + LP: #1775307 SRU template ok
     + LP: #1778219 SRU template ok
     + LP: #1778800 SRU template ok
     + LP: #1779157
     + LP: #1781176 SRU template ok
     + LP: #1781183 SRU template ok
     + LP: #1781446 SRU template ok
     + LP: #1781586 SRU template ok
     + LP: #1785093 SRU template ok
     + LP: #1789637 SRU template ok
     + LP: #1803749 SRU template ok
  
  [Regression Potential]
  
  * Due to this update covering the full backport unattended-upgrades can 
regress in any imaginable way including failing to install, upgrade, run, or 
removing essential packages from the system. Those are unlikely.
  * There are open bugs about u-u being slower than in the past, thus this may 
be a likely regression but IMO the pending speed optimizations should not be 
blocking the backport because the reliability issues are more important to fix 
and speed optimizations can be cherry-picked later.
  
  [Other Info]
  
  I asked for an exception for the package in following the SRU process:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-May/004479.html
  
  I'm preparing the backport in ppa:rbalint/scratch and also run
  autopkgtests on it in addition to testing it manually in VMs.
  
  [Original Bug Text]
  
  Changes to support day-of-week patching and logging to syslog were added
  to upstream (https://github.com/mvo5/unattended-upgrades) over a year
  ago. These changes are not present in the latest Xenial nor Trusty
  packages (0.90 and 0.82.1) - requesting that these changes be pulled
  from upstream.

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

Title:
  Full backport SRU for unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  * I would like to propose a one-off full backport of unattended-upgrades
  1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because 
selectively backporting fixes for crashes and for issues that made u-u 
unreliable would be more risky thanks to the huge number of fixes and the
  inter-dependencies between them.

  [Test Case]

  * Since this backport involves fixing several bugs and this bug itself
  covers the full backport I suggest that this bug should be considered
  verified when the following list of bugs are verified:

  - TODO add most important bugs
     + LP: #1615381 : apt-get autoremove may remove current kernel

  and the following tests are passing:
   - TODO add tests not covered by bugs above

  All LP bugs fixed by the backport, comments are welcome:
     + LP: #1230246
     + LP: #1260041 SRU template ok
     + LP: #1269177 already fixed in 0.90ubuntu0.9
     + LP: #1357093
     + LP: #1396787 SRU template ok
     + LP: #1446552
     + LP: #1455097
     + LP: #1458204
     + LP: #1544942 already fixed in 0.90ubuntu0.8
     

[Touch-packages] [Bug 1805115] Re: problem with (ubuntu/cosmic)mawk /^[[:space:]]*

[Andreas Hasenack]

Fails from trusty onwards, all the way to disco.

use this to test:
printf %s '; 
rel="next", ; 
rel="last"' | mawk '
BEGIN { RS=", "; FS="; "; OFS=": " }
{
sub(/^rel="/, "", $2); sub(/"$/, "", $2)
sub(/^[[:space:]]*$/, "", $1)
print "Link_" $2, $1
}'

Output should have no "<" char before the http link.

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

** Changed in: mawk (Ubuntu)
   Importance: Undecided => Low

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

Title:
   problem with (ubuntu/cosmic)mawk /^[[:space:]]*http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  ###

  more background @ 
  https://github.com/whiteinge/ok.sh/issues/66# problem with 
(ubuntu/cosmic)mawk /^[[:space:]]*https://api.github.com/repositories/3386088/issues?page=2>; 
rel="next", ; 
rel="last"' | awk '
  BEGIN { RS=", "; FS="; "; OFS=": " }
  {
  sub(/^rel="/, "", $2); sub(/"$/, "", $2)
  sub(/^ *$/, "", $1)
  print "Link_" $2, $1
  }'
  Link_next: https://api.github.com/repositories/3386088/issues?page=2
  Link_last: https://api.github.com/repositories/3386088/issues?page=33
  -

  fails using [[:space:]]
  eg
  -
  printf %s '; 
rel="next", ; 
rel="last"' | awk '
  BEGIN { RS=", "; FS="; "; OFS=": " }
  {
  sub(/^rel="/, "", $2); sub(/"$/, "", $2)
  sub(/^[[:space:]]*$/, "", $1)
  print "Link_" $2, $1
  }'
  Link_next: 

[Touch-packages] [Bug 1805115] Re: problem with (ubuntu/cosmic)mawk /^[[:space:]]*

[Andreas Hasenack]

Confirmed working with gawk, failing with mawk.

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

Title:
   problem with (ubuntu/cosmic)mawk /^[[:space:]]*http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  ###

  more background @ 
  https://github.com/whiteinge/ok.sh/issues/66# problem with 
(ubuntu/cosmic)mawk /^[[:space:]]*https://api.github.com/repositories/3386088/issues?page=2>; 
rel="next", ; 
rel="last"' | awk '
  BEGIN { RS=", "; FS="; "; OFS=": " }
  {
  sub(/^rel="/, "", $2); sub(/"$/, "", $2)
  sub(/^ *$/, "", $1)
  print "Link_" $2, $1
  }'
  Link_next: https://api.github.com/repositories/3386088/issues?page=2
  Link_last: https://api.github.com/repositories/3386088/issues?page=33
  -

  fails using [[:space:]]
  eg
  -
  printf %s '; 
rel="next", ; 
rel="last"' | awk '
  BEGIN { RS=", "; FS="; "; OFS=": " }
  {
  sub(/^rel="/, "", $2); sub(/"$/, "", $2)
  sub(/^[[:space:]]*$/, "", $1)
  print "Link_" $2, $1
  }'
  Link_next: 

[Touch-packages] [Bug 1801439] Re: Unable to add software sources via the software-properties

[Brian Murray]

Here's an error bucket with the same Traceback:

https://errors.ubuntu.com/problem/41fef3749e47609b969c6d83cd4274def59e3ccf

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

Title:
  Unable to add software sources via the software-properties

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Test
  1. Start Software-properties. E.g. sudo software-properties-qt
  2. Navigate to Other Software (Tab), Add -> Add, to add a PPA
  3. Insert the PPA string. E.g. "deb 
http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " (or even the 
example repo given in the dialog, which is not a PPA)
  4. Click Okay.

  The software sources list does not contain the new field. Executing in
  terminal results in the following error message.

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 627, in on_add_clicked
  self.add_source_from_line(line)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
752, in add_source_from_line
  enable_source_code=enable_source_code)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
769, in add_source_from_shortcut
  worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
709, in check_and_add_key_for_whitelisted_shortcut
  self.options.keyserver)})
  AttributeError: type object 'OptionParsed' has no attribute 'keyserver'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: software-properties-qt 0.96.27
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sat Nov  3 09:59:52 2018
  InstallationDate: Installed on 2018-10-19 (14 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails

[Renato Lorenzi]

Now I received a update from 229-4ubuntu21.9 to 229-4ubuntu21.10 and
everything worked again.

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

Title:
  systemd-tmpfiles-setup.service fails

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service
  fails with:

  Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and 
Directories...
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/var": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/home": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/srv": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main 
process exited, code=exited, status=1/FAILURE
  Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed 
with result 'exit-code'.
  Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files 
and Directories.

  This happens on btrfs root filesystems in real hardware and on our
  virtualized servers as well. 237-3ubuntu10.6 didnt show this errors
  and going back to 237-3ubuntu10 removes them as well.

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

  # apt-cache policy systemd
  systemd:
Installiert:   237-3ubuntu10.9
Installationskandidat: 237-3ubuntu10.9
Versionstabelle:
   *** 237-3ubuntu10.9 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
  systemd-resolved has issues when the answer is over 512 bytes with
  EDNS disabled

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [Impact]

  TCP stub is cutting down the payload to 512 bytes when EDNS is
  disabled. This makes non-EDNS clients (nslookup) receive a "shortened"
  answer even when UDP returns a truncated reply for a new TCP query.
  For instance,

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  In the second case, no-EDNS, TCP should provide the complete answer,
  but it's capped at UDP's size.

  [Test Case]

  Query systemd-resolved with a domain name that resolves to multiple
  (lots.. 30+) A records. A client with EDNS support (dig) will receive
  all of them, a client without support (nslookup or dig +noedns) will
  have a truncated list. Using the example above:

  EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 
| wc -l

  [Regression potential]

  Minimal. This change only affects TCP requests, and the new size is
  already used in the code for other requests.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10816
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce

  [Original Description]

  Querying a domain name that has >512 bytes in records (e.g. 30+ A
  records), the number of results depends on the DNS client used:

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  Normally a client that doesn't support EDNS would receive a truncated
  reply from the initial UDP connection (limited by the spec to 512
  bytes) and a second query would be established via TCP to receive the
  complete results. In this case, the number of results is the same
  regardless of the protocol used (29).

  Upstream bug: https://github.com/systemd/systemd/issues/10816

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

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

[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

[Ken VanDine]

** Also affects: gtk+3.0 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: cups-filters (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: gtk+3.0 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: cups-filters (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in cups-filters source package in Bionic:
  Invalid
Status in gtk+3.0 source package in Bionic:
  New
Status in cups-filters source package in Cosmic:
  Invalid
Status in gtk+3.0 source package in Cosmic:
  New

Bug description:
  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

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

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

[Touch-packages] [Bug 1797625] Re: Missing the 'Call Trace' with the cases of 'KernelOops'

[Brian Murray]

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

** Changed in: kerneloops (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Missing the 'Call Trace' with the cases of 'KernelOops'

Status in apport package in Ubuntu:
  Incomplete
Status in kerneloops package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I am working with these two reports:

  * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
  https://bugs.launchpad.net/bugs/1796385

  * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  https://bugs.launchpad.net/bugs/1797538

  And the file: 'OopsText.txt' does not appear in the 'Call Trace'.

  Others:
  https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3
  "The bug in lauchpad, unless I am missing something, provides not a single 
actionable traceback. I don't think it is even possible to identify where 
exactly the CPU hangs unless additional information is provided. There is no 
traceback in dmesg, and OopsText doesn't include it either.

  Given that, it is not possible to identify the responsible subsystem,
  much less to fix the underlying problem. The only thing we can say for
  sure is that it is _not_ a watchdog driver problem."

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu11
  Uname: Linux 4.18.13-gnu x86_64
  ApportLog:

  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 12 16:12:58 2018
  InstallationDate: Installed on 2017-10-13 (364 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1702793] Re: Full backport SRU for unattended-upgrades

[Balint Reczey]

** Description changed:

  [Impact]
  
  * I would like to propose a one-off full backport of unattended-upgrades
  1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because 
selectively backporting fixes for crashes and for issues that made u-u 
unreliable would be more risky thanks to the huge number of fixes and the
  inter-dependencies between them.
  
  [Test Case]
  
  * Since this backport involves fixing several bugs and this bug itself
  covers the full backport I suggest that this bug should be considered
  verified when the following list of bugs are verified:
  
  - TODO add most important bugs
     + LP: #1615381 : apt-get autoremove may remove current kernel
  
  and the following tests are passing:
   - TODO add tests not covered by bugs above
  
  All LP bugs fixed by the backport, comments are welcome:
     + LP: #1230246
     + LP: #1260041 SRU template ok
     + LP: #1269177 SRU template ok
     + LP: #1357093
     + LP: #1396787 SRU template ok
     + LP: #1446552
     + LP: #1455097
     + LP: #1458204
     + LP: #1544942
     + LP: #1577215
     + LP: #1602536 SRU template ok
     + LP: #1615381
     + LP: #1624644 SRU template ok
     + LP: #1632361
     + LP: #1649709
     + LP: #1654070
     + LP: #1654600 SRU template ok
     + LP: #1675079 SRU template ok
     + LP: #1680599
     + LP: #1686470 SRU template ok
     + LP: #1687129 to add u-u test case
-    + LP: #1690980 
+    + LP: #1690980
     + LP: #1698159
     + LP: #1702793 this bug
     + LP: #1714019 just a merge request
     + LP: #1718419 just a merge request
     + LP: #1719630
     + LP: #1722426 just a merge request
     + LP: #1737441
     + LP: #1737442 to add u-u test case
     + LP: #1737635
     + LP: #1737637
     + LP: #1737717
     + LP: #1741579
     + LP: #1764797 just a merge request
     + LP: #1773033 SRU template ok
     + LP: #1775292 SRU template ok
     + LP: #1775307 SRU template ok
     + LP: #1778219 SRU template ok
     + LP: #1778800 SRU template ok
     + LP: #1779157
     + LP: #1781176 SRU template ok
     + LP: #1781183 SRU template ok
     + LP: #1781446 SRU template ok
     + LP: #1781586 SRU template ok
     + LP: #1785093 SRU template ok
     + LP: #1789637 SRU template ok
     + LP: #1803749 SRU template ok
  
  [Regression Potential]
  
  * Due to this update covering the full backport unattended-upgrades can 
regress in any imaginable way including failing to install, upgrade, run, or 
removing essential packages from the system. Those are unlikely.
  * There are open bugs about u-u being slower than in the past, thus this may 
be a likely regression but IMO the pending speed optimizations should not be 
blocking the backport because the reliability issues are more important to fix 
and speed optimizations can be cherry-picked later.
- * LP: #1773033 is a regression causing u-u to not install upgrades on 
shutdown when the system was started on battery. I have a WIP fix and can add 
the fix to the SRU if needed.
  
  [Other Info]
  
  I asked for an exception for the package in following the SRU process:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-May/004479.html
  
  I'm preparing the backport in ppa:rbalint/scratch and also run
  autopkgtests on it in addition to testing it manually in VMs.
  
  [Original Bug Text]
  
  Changes to support day-of-week patching and logging to syslog were added
  to upstream (https://github.com/mvo5/unattended-upgrades) over a year
  ago. These changes are not present in the latest Xenial nor Trusty
  packages (0.90 and 0.82.1) - requesting that these changes be pulled
  from upstream.

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

Title:
  Full backport SRU for unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  * I would like to propose a one-off full backport of unattended-upgrades
  1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because 
selectively backporting fixes for crashes and for issues that made u-u 
unreliable would be more risky thanks to the huge number of fixes and the
  inter-dependencies between them.

  [Test Case]

  * Since this backport involves fixing several bugs and this bug itself
  covers the full backport I suggest that this bug should be considered
  verified when the following list of bugs are verified:

  - TODO add most important bugs
     + LP: #1615381 : apt-get autoremove may remove current kernel

  and the following tests are passing:
   - TODO add tests not covered by bugs above

  All LP bugs fixed by the backport, comments are welcome:
     + LP: #1230246
     + LP: #1260041 SRU template ok
     + LP: #1269177 SRU template ok
     + LP: #1357093
     + LP: #1396787 SRU template ok
     + LP: #1446552
     + LP: #1455097
     + LP: #1458204
     + LP: #1544942
 

[Touch-packages] [Bug 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[Pablo Merighi]

Solved with

sudo apt-get install --reinstall hplip hplip-data
sudo apt-get install --reinstall python3

Thanks

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

Title:
  package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  Only Ubuntu Update

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Jun 28 22:51:28 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2018-04-13 (76 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago)

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

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

[Touch-packages] [Bug 1789258] Re: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out

[Darko Veberic]

the same bug confirmed also on Acer TravelMate 6492 with Intel
GM965/GL960 graphics running Ubuntu 16.04.5 LTS.

the kernel command-line option above fixes the problem.

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

Title:
  drm:drm_atomic_helper_wait_for_dependencies flip_done timed out

Status in libdrm package in Ubuntu:
  New

Bug description:
  every now an then the system freezes but eventually comes back to
  life. the boot process is especially slow, login greeter takes ages to
  come up and then, while there, needs some extra time to unfreeze and
  actually allow typing in the password.

  the freeze can be easily reproduced each time when switching from
  graphics to console (with ctrl-alt-fN) and back. each time the dmesg
  gets also gets appended with the error messages that can be found in
  the attached text file.

  is the workaround really to uninstall intel's xorg drivers?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libdrm-intel1 2.4.91-2
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Aug 27 20:03:14 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [17aa:383e]
 Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [17aa:383e]
  InstallationDate: Installed on 2018-08-24 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 0769BJG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=5c1b96ff-002e-4358-bf56-8dd74e76584d ro dis_ucode_ldr
  SourcePackage: libdrm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET37WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769BJG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Lenovo
  dmi.product.name: 0769BJG
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1798313] Re: traceoute6 gives error sendto: Invalid argument

[Sebastien Bacher]

The Debian bug referenced is fixed in the version your are using/bionic,
https://launchpad.net/ubuntu/+source/iputils/3:20161105-1ubuntu1

Some other change might be required though?

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

Title:
  traceoute6 gives error sendto: Invalid argument

Status in Iputils:
  Fix Released
Status in iputils package in Ubuntu:
  Confirmed
Status in iputils package in Debian:
  Fix Released

Bug description:
  When running the following command all get is an error. (traceroute6.db works)
  # traceroute6.iputils 2001:4860:4860::
  traceroute to 2001:4860:4860:: (2001:4860:4860::) from 
2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets
  sendto: Invalid argument
   1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *

  This seems like a regression of Debian bug https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=843264

  Package version installed:
  iputils-tracepath 3:20161105-1ubuntu2 amd64

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

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

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

[Touch-packages] [Bug 1767453] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[miguelquiros]

No success in my case (difference with Maurice report). Tried again today to 
upgrade (via dpkg -i) to 20180409 and got an error message saying that 
post-installation script produces an output status of "1" (this means error 
when executing the postinst script, doesn't it?). Package left unconfigured and 
20170717~16.04.1 needs to be reinstalled to get a system without broken 
packages.
Is there some way to get more verbose information about what is going wrong 
with the post installation script?

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  Happened during upgrade to ubunut 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 17:51:26 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

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

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

[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled

[Dan Streetman]

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

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

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

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

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Victor Tapia (vtapia)

** Changed in: systemd (Ubuntu Cosmic)
 Assignee: (unassigned) => Victor Tapia (vtapia)

** Changed in: systemd (Ubuntu Disco)
 Assignee: (unassigned) => Victor Tapia (vtapia)

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

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

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

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

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

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

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

Title:
  systemd-resolved has issues when the answer is over 512 bytes with
  EDNS disabled

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [Impact]

  TCP stub is cutting down the payload to 512 bytes when EDNS is
  disabled. This makes non-EDNS clients (nslookup) receive a "shortened"
  answer even when UDP returns a truncated reply for a new TCP query.
  For instance,

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  In the second case, no-EDNS, TCP should provide the complete answer,
  but it's capped at UDP's size.

  [Test Case]

  Query systemd-resolved with a domain name that resolves to multiple
  (lots.. 30+) A records. A client with EDNS support (dig) will receive
  all of them, a client without support (nslookup or dig +noedns) will
  have a truncated list. Using the example above:

  EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 
| wc -l

  [Regression potential]

  Minimal. This change only affects TCP requests, and the new size is
  already used in the code for other requests.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10816
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce

  [Original Description]

  Querying a domain name that has >512 bytes in records (e.g. 30+ A
  records), the number of results depends on the DNS client used:

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  Normally a client that doesn't support EDNS would receive a truncated
  reply from the initial UDP connection (limited by the spec to 512
  bytes) and a second query would be established via TCP to receive the
  complete results. In this case, the number of results is the same
  regardless of the protocol used (29).

  Upstream bug: https://github.com/systemd/systemd/issues/10816

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

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

[Touch-packages] [Bug 1768789] Re: connectivity results in limited when behind proxy

[Sebastien Bacher]

Thank you for your bug report. That seems similar to what has been
discussed upstream on https://bugzilla.gnome.org/show_bug.cgi?id=738694

The outcome of their discussion is that at this point it's probably best
in your case to just uninstall the network-manager-config-connectivity-
ubuntu binary

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

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

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

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

Title:
  connectivity results in limited when behind proxy

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  The connectivity for a connection results in limited when behind a
  proxy for NetworkManager.

  $ sudo nmcli general 
  STATE  CONNECTIVITY  WIFI-HW  WIFI WWAN-HW  WWAN
  connected (site only)  limited   enabled  enabled  enabled  enabled

  $ sudo nmcli networking connectivity check 
  limited

  I have configured my proxy in both '/etc/environment' and via the GUI
  under 'Settings'->'Network'->'Network Proxy'->'Automatic'.

  After this is set I can do an HTTP GET against the URL/URI you have
  configured in the '/usr/lib/NetworkManager/conf.d/20-connectivity-
  ubuntu.conf' file.

  $ curl -I http://connectivity-check.ubuntu.com/
  HTTP/1.1 204 No Content
  Date: Thu, 03 May 2018 09:01:34 GMT
  Server: Apache/2.4.18 (Ubuntu)
  X-NetworkManager-Status: online
  X-Cache: MISS from proxy.example.com
  X-Cache-Lookup: MISS from proxy.example.com:3128
  Via: 1.1 proxy.example.com (squid/3.3.8)
  Connection: keep-alive

  $ env|grep -i proxy
  auto_proxy=http://proxy.example.com/auto
  https_proxy=http://proxy.example.com:3128
  http_proxy=http://proxy.example.com:3128

  But network connectivity still fails to use the proxy.

  I assume that the 'network-manager-config-connectivity-ubuntu' package
  is used for this feature after reading the following output.

  $ dpkg -S /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  network-manager-config-connectivity-ubuntu: 
/usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf

  If I remove the '/usr/lib/NetworkManager/conf.d/20-connectivity-
  ubuntu.conf' file the connectivity check succeeds or I don't get
  limited connectivity at least.

  --
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

  $ uname -a
  Linux lnxhplap2 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ dpkg -l|grep network-manager
  ii  network-manager1.10.6-2ubuntu1
 amd64network management framework (daemon and userspace tools)
  ii  network-manager-config-connectivity-ubuntu 1.10.6-2ubuntu1
 all  NetworkManager configuration to enable connectivity checking
  ii  network-manager-gnome  1.8.10-2ubuntu1
 amd64network management framework (GNOME frontend)
  ii  network-manager-pptp   1.2.6-1
 amd64network management framework (PPTP plugin core)
  ii  network-manager-pptp-gnome 1.2.6-1
 amd64network management framework (PPTP plugin GNOME GUI)
  --

  Note: I have used "proxy.example.com" as substitute for our proxy
  server in this bug report for privacy reasons.

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

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

[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled

[Victor Tapia]

** Patch added: "systemd-TCP-size-bionic.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804487/+attachment/5217389/+files/systemd-TCP-size-bionic.debdiff

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

Title:
  systemd-resolved has issues when the answer is over 512 bytes with
  EDNS disabled

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [Impact]

  TCP stub is cutting down the payload to 512 bytes when EDNS is
  disabled. This makes non-EDNS clients (nslookup) receive a "shortened"
  answer even when UDP returns a truncated reply for a new TCP query.
  For instance,

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  In the second case, no-EDNS, TCP should provide the complete answer,
  but it's capped at UDP's size.

  [Test Case]

  Query systemd-resolved with a domain name that resolves to multiple
  (lots.. 30+) A records. A client with EDNS support (dig) will receive
  all of them, a client without support (nslookup or dig +noedns) will
  have a truncated list. Using the example above:

  EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 
| wc -l

  [Regression potential]

  Minimal. This change only affects TCP requests, and the new size is
  already used in the code for other requests.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10816
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce

  [Original Description]

  Querying a domain name that has >512 bytes in records (e.g. 30+ A
  records), the number of results depends on the DNS client used:

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  Normally a client that doesn't support EDNS would receive a truncated
  reply from the initial UDP connection (limited by the spec to 512
  bytes) and a second query would be established via TCP to receive the
  complete results. In this case, the number of results is the same
  regardless of the protocol used (29).

  Upstream bug: https://github.com/systemd/systemd/issues/10816

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

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

[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled

[Victor Tapia]

** Patch added: "systemd-TCP-size-disco.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804487/+attachment/5217391/+files/systemd-TCP-size-disco.debdiff

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

Title:
  systemd-resolved has issues when the answer is over 512 bytes with
  EDNS disabled

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [Impact]

  TCP stub is cutting down the payload to 512 bytes when EDNS is
  disabled. This makes non-EDNS clients (nslookup) receive a "shortened"
  answer even when UDP returns a truncated reply for a new TCP query.
  For instance,

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  In the second case, no-EDNS, TCP should provide the complete answer,
  but it's capped at UDP's size.

  [Test Case]

  Query systemd-resolved with a domain name that resolves to multiple
  (lots.. 30+) A records. A client with EDNS support (dig) will receive
  all of them, a client without support (nslookup or dig +noedns) will
  have a truncated list. Using the example above:

  EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 
| wc -l

  [Regression potential]

  Minimal. This change only affects TCP requests, and the new size is
  already used in the code for other requests.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10816
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce

  [Original Description]

  Querying a domain name that has >512 bytes in records (e.g. 30+ A
  records), the number of results depends on the DNS client used:

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  Normally a client that doesn't support EDNS would receive a truncated
  reply from the initial UDP connection (limited by the spec to 512
  bytes) and a second query would be established via TCP to receive the
  complete results. In this case, the number of results is the same
  regardless of the protocol used (29).

  Upstream bug: https://github.com/systemd/systemd/issues/10816

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

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

[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled

[Victor Tapia]

** Patch added: "systemd-TCP-size-cosmic.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804487/+attachment/5217390/+files/systemd-TCP-size-cosmic.debdiff

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

Title:
  systemd-resolved has issues when the answer is over 512 bytes with
  EDNS disabled

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [Impact]

  TCP stub is cutting down the payload to 512 bytes when EDNS is
  disabled. This makes non-EDNS clients (nslookup) receive a "shortened"
  answer even when UDP returns a truncated reply for a new TCP query.
  For instance,

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  In the second case, no-EDNS, TCP should provide the complete answer,
  but it's capped at UDP's size.

  [Test Case]

  Query systemd-resolved with a domain name that resolves to multiple
  (lots.. 30+) A records. A client with EDNS support (dig) will receive
  all of them, a client without support (nslookup or dig +noedns) will
  have a truncated list. Using the example above:

  EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 
| wc -l

  [Regression potential]

  Minimal. This change only affects TCP requests, and the new size is
  already used in the code for other requests.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10816
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce

  [Original Description]

  Querying a domain name that has >512 bytes in records (e.g. 30+ A
  records), the number of results depends on the DNS client used:

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  Normally a client that doesn't support EDNS would receive a truncated
  reply from the initial UDP connection (limited by the spec to 512
  bytes) and a second query would be established via TCP to receive the
  complete results. In this case, the number of results is the same
  regardless of the protocol used (29).

  Upstream bug: https://github.com/systemd/systemd/issues/10816

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

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

[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled

[Victor Tapia]

** Description changed:

+ [Impact]
+ 
+ TCP stub is cutting down the payload to 512 bytes when EDNS is disabled.
+ This makes non-EDNS clients (nslookup) receive a "shortened" answer even
+ when UDP returns a truncated reply for a new TCP query. For instance,
+ 
+ - If the client supports EDNS:
+ 
+ $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
+ 30
+ 
+ - If the client does not support EDNS:
+ 
+ $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
+ 29
+ 
+ In the second case, no-EDNS, TCP should provide the complete answer, but
+ it's capped at UDP's size.
+ 
+ [Test Case]
+ 
+ Query systemd-resolved with a domain name that resolves to multiple
+ (lots.. 30+) A records. A client with EDNS support (dig) will receive
+ all of them, a client without support (nslookup or dig +noedns) will
+ have a truncated list.
+ 
+ [Regression potential]
+ 
+ Minimal. This change only affects TCP requests, and the new size is
+ already used in the code for other requests.
+ 
+ [Other Info]
+ 
+ Upstream bug: https://github.com/systemd/systemd/issues/10816
+ Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce
+ 
+ [Original Description]
+ 
  Querying a domain name that has >512 bytes in records (e.g. 30+ A
  records), the number of results depends on the DNS client used:
  
  - If the client supports EDNS:
  
  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
- 30 
+ 30
  
  - If the client does not support EDNS:
  
  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29
  
  Normally a client that doesn't support EDNS would receive a truncated
  reply from the initial UDP connection (limited by the spec to 512 bytes)
  and a second query would be established via TCP to receive the complete
  results. In this case, the number of results is the same regardless of
  the protocol used (29).
  
  Upstream bug: https://github.com/systemd/systemd/issues/10816

** Description changed:

  [Impact]
  
  TCP stub is cutting down the payload to 512 bytes when EDNS is disabled.
  This makes non-EDNS clients (nslookup) receive a "shortened" answer even
  when UDP returns a truncated reply for a new TCP query. For instance,
  
  - If the client supports EDNS:
  
  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30
  
  - If the client does not support EDNS:
  
  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29
  
  In the second case, no-EDNS, TCP should provide the complete answer, but
  it's capped at UDP's size.
  
  [Test Case]
  
  Query systemd-resolved with a domain name that resolves to multiple
  (lots.. 30+) A records. A client with EDNS support (dig) will receive
  all of them, a client without support (nslookup or dig +noedns) will
- have a truncated list.
+ have a truncated list. Using the example above:
+ 
+ EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
+ non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 
| wc -l
  
  [Regression potential]
  
  Minimal. This change only affects TCP requests, and the new size is
  already used in the code for other requests.
  
  [Other Info]
  
  Upstream bug: https://github.com/systemd/systemd/issues/10816
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce
  
  [Original Description]
  
  Querying a domain name that has >512 bytes in records (e.g. 30+ A
  records), the number of results depends on the DNS client used:
  
  - If the client supports EDNS:
  
  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30
  
  - If the client does not support EDNS:
  
  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29
  
  Normally a client that doesn't support EDNS would receive a truncated
  reply from the initial UDP connection (limited by the spec to 512 bytes)
  and a second query would be established via TCP to receive the complete
  results. In this case, the number of results is the same regardless of
  the protocol used (29).
  
  Upstream bug: https://github.com/systemd/systemd/issues/10816

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

Title:
  systemd-resolved has issues when the answer is over 512 bytes with
  EDNS disabled

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [Impact]

  TCP stub is cutting down the payload to 512 bytes when EDNS is
  disabled. This makes non-EDNS clients (nslookup) receive a "shortened"
  answer even wh

[Touch-packages] [Bug 1805857] Re: network-manager dep8 failure blocks dnsmasq proposed migration

[Sebastien Bacher]

Thanks Robie!

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

** Tags added: rls-dd-incoming

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

Title:
  network-manager dep8 failure blocks dnsmasq proposed migration

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  dnsmasq 2.80-1 is blocked from migrating to the release pocket because
  of, amongst other things, a network-manager dep8 regression.

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

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

[Touch-packages] [Bug 1805857] [NEW] network-manager dep8 failure blocks dnsmasq proposed migration

[Robie Basak]

Public bug reported:

dnsmasq 2.80-1 is blocked from migrating to the release pocket because
of, amongst other things, a network-manager dep8 regression.

** Affects: network-manager (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: rls-dd-incoming

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

Title:
  network-manager dep8 failure blocks dnsmasq proposed migration

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  dnsmasq 2.80-1 is blocked from migrating to the release pocket because
  of, amongst other things, a network-manager dep8 regression.

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

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

[Touch-packages] [Bug 1805857] Re: network-manager dep8 failure blocks dnsmasq proposed migration

[Robie Basak]

I've done some investigation and my best educated guess right now is
that there race somewhere, most like in the n-m dep8 tests but possibly
in n-m, which is being triggered by an unrelated timing change in the
newer dnsmasq and is causing some unwanted result that results in the
dep8 test teardown to fail.

I reproduced by:

Creating a VM running Disco and dist-upgrading it and rebooting (without
-proposed enabled).

Pulling the network-manager source and installing the test dependencies
listed against "nm" in debian/tests/control

Running "sudo ./nm" from debian/tests/ by hand.

This passed, but a subsequent upgrade of dnsmasq-base (only) from disco-
proposed reproduced the failure.

I isolated by:

Modifying the dep8 test to allow isolation
(https://code.launchpad.net/~racb/network-manager/+git/network-
manager/+merge/359837)

Running "sudo python3 -m unittest
nm.ColdplugWifi.test_open_b_ip6_raonly_no_pe" from debian/tests/ by
hand.

I found that after a test failure a reboot of the VM was necessary to
cause the tests to work again. Swapping between the release pocket and
proposed pocket version of dnsmasq-base mostly caused the failure to
come and go as expected. However I believe that one time I saw the test
pass against dnsmasq-base from proposed, which is why I think it's a
race condition.

To get to the actual failure reason, I applied the follow patch:

--- a/debian/tests/nm.py
+++ b/debian/tests/nm.py
@@ -532,7 +538,6 @@ wpa_passphrase=12345678
 # connections and such); as it is very brittle and hard to track down
 # all remaining references to any NM* object after a test, we rather
 # run each test in a separate subprocess
-@network_test_base.run_in_subprocess
 def do_test(self, hostapd_conf, ipv6_mode, expected_max_bitrate,
 secret=None, ip6_privacy=None):
 '''Actual test code, parameterized for the particular test case'''

This gave me the following output:

==
FAIL: test_open_b_ip6_raonly_no_pe (nm.ColdplugWifi)
Open network, 802.11b, IPv6 with only RA, PE disabled
--
Traceback (most recent call last):
  File "/home/ubuntu/network-manager/debian/tests/nm.py", line 165, in 
shutdown_connections
self.assert_iface_down(self.dev_e_client)
  File "/home/ubuntu/network-manager/debian/tests/nm.py", line 195, in 
assert_iface_down
self.assertIn('state DOWN', out)
AssertionError: 'state DOWN' not found in '4: eth42@veth42: 
 mtu 1500 qdisc noqueue state 
LOWERLAYERDOWN group default qlen 1000\nlink/ether 1e:64:0d:9f:da:2e brd 
ff:ff:ff:ff:ff:ff\n'

--
Ran 1 test in 35.639s

FAILED (failures=1)

The following didn't fix the problem:

--- a/debian/tests/nm.py
+++ b/debian/tests/nm.py
@@ -187,12 +187,18 @@ class 
NetworkManagerTest(network_test_base.NetworkTestBase):
 else:
 self.fail(message or 'timed out waiting for ' + str(condition))
 
+@staticmethod
+def iface_is_down(iface):
+out = subprocess.check_output(['ip', 'a', 'show', 'dev', iface],
+  universal_newlines=True)
+return 'state DOWN' in out
+
 def assert_iface_down(self, iface):
 '''Assert that client interface is down'''
 
+self.assertEventually(lambda: self.iface_is_down(iface))
 out = subprocess.check_output(['ip', 'a', 'show', 'dev', iface],
   universal_newlines=True)
-self.assertIn('state DOWN', out)
 self.assertNotIn('inet 192', out)
 self.assertNotIn('inet6 2600', out)

So I think the race is causing some change prior to this point.

I don't think it's clear that this is definitely not a dnsmasq
regression, but it seems more likely to me to be an issue in n-m or its
tests. I don't think it'd be useful for me to learn n-m internals
wearing my server team hat to fix this since the server team doesn't get
much involved in n-m, so I'm leaving this to the desktop team for now.
Please let me know though if you disagree with my assessment or if it
starts looking like a dnsmasq regression, and I'll be happy to look
again.

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

Title:
  network-manager dep8 failure blocks dnsmasq proposed migration

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  dnsmasq 2.80-1 is blocked from migrating to the release pocket because
  of, amongst other things, a network-manager dep8 regression.

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

Resetting the tags to verification-done as per the discussion above.

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

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed
Status in netplan.io source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link

[Touch-packages] [Bug 1702793] Re: Full backport SRU for unattended-upgrades

[Balint Reczey]

** Description changed:

  [Impact]
  
  * I would like to propose a one-off full backport of unattended-upgrades
  1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because 
selectively backporting fixes for crashes and for issues that made u-u 
unreliable would be more risky thanks to the huge number of fixes and the
  inter-dependencies between them.
  
  [Test Case]
  
  * Since this backport involves fixing several bugs and this bug itself
  covers the full backport I suggest that this bug should be considered
  verified when the following list of bugs are verified:
  
  - TODO add most important bugs
     + LP: #1615381 : apt-get autoremove may remove current kernel
  
  and the following tests are passing:
   - TODO add tests not covered by bugs above
  
  All LP bugs fixed by the backport, comments are welcome:
-+ LP: #1230246
-+ LP: #1260041
-+ LP: #1269177
-+ LP: #1357093
-+ LP: #1396787
-+ LP: #1446552
-+ LP: #1455097
-+ LP: #1458204
-+ LP: #1544942
-+ LP: #1577215
-+ LP: #1602536
-+ LP: #1615381
-+ LP: #1624644
-+ LP: #1632361
-+ LP: #1649709
-+ LP: #1654070
-+ LP: #1654600
-+ LP: #1675079
-+ LP: #1680599
-+ LP: #1686470
-+ LP: #1687129
-+ LP: #1690980
-+ LP: #1698159
-+ LP: #1702793
-+ LP: #1714019
-+ LP: #1718419
-+ LP: #1719630
-+ LP: #1722426
-+ LP: #1737441
-+ LP: #1737442
-+ LP: #1737635
-+ LP: #1737637
-+ LP: #1737717
-+ LP: #1741579
-+ LP: #1764797
-+ LP: #1773033
-+ LP: #1775292
-+ LP: #1775307
-+ LP: #1778219
-+ LP: #1778800
-+ LP: #1779157
-+ LP: #1781176
-+ LP: #1781183
-+ LP: #1781446
-+ LP: #1781586
-+ LP: #1785093
-+ LP: #1789637
-+ LP: #1803749
- 
+    + LP: #1230246
+    + LP: #1260041 SRU template ok
+    + LP: #1269177 SRU template ok
+    + LP: #1357093
+    + LP: #1396787 SRU template ok
+    + LP: #1446552
+    + LP: #1455097
+    + LP: #1458204
+    + LP: #1544942
+    + LP: #1577215
+    + LP: #1602536 SRU template ok
+    + LP: #1615381
+    + LP: #1624644 SRU template ok
+    + LP: #1632361
+    + LP: #1649709
+    + LP: #1654070
+    + LP: #1654600 SRU template ok
+    + LP: #1675079 SRU template ok
+    + LP: #1680599
+    + LP: #1686470 SRU template ok
+    + LP: #1687129 to add u-u test case
+    + LP: #1690980 
+    + LP: #1698159
+    + LP: #1702793 this bug
+    + LP: #1714019 just a merge request
+    + LP: #1718419 just a merge request
+    + LP: #1719630
+    + LP: #1722426 just a merge request
+    + LP: #1737441
+    + LP: #1737442 to add u-u test case
+    + LP: #1737635
+    + LP: #1737637
+    + LP: #1737717
+    + LP: #1741579
+    + LP: #1764797 just a merge request
+    + LP: #1773033 SRU template ok
+    + LP: #1775292 SRU template ok
+    + LP: #1775307 SRU template ok
+    + LP: #1778219 SRU template ok
+    + LP: #1778800 SRU template ok
+    + LP: #1779157
+    + LP: #1781176 SRU template ok
+    + LP: #1781183 SRU template ok
+    + LP: #1781446 SRU template ok
+    + LP: #1781586 SRU template ok
+    + LP: #1785093 SRU template ok
+    + LP: #1789637 SRU template ok
+    + LP: #1803749 SRU template ok
  
  [Regression Potential]
  
  * Due to this update covering the full backport unattended-upgrades can 
regress in any imaginable way including failing to install, upgrade, run, or 
removing essential packages from the system. Those are unlikely.
  * There are open bugs about u-u being slower than in the past, thus this may 
be a likely regression but IMO the pending speed optimizations should not be 
blocking the backport because the reliability issues are more important to fix 
and speed optimizations can be cherry-picked later.
  * LP: #1773033 is a regression causing u-u to not install upgrades on 
shutdown when the system was started on battery. I have a WIP fix and can add 
the fix to the SRU if needed.
  
  [Other Info]
  
  I asked for an exception for the package in following the SRU process:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-May/004479.html
  
  I'm preparing the backport in ppa:rbalint/scratch and also run
  autopkgtests on it in addition to testing it manually in VMs.
  
  [Original Bug Text]
  
  Changes to support day-of-week patching and logging to syslog were added
  to upstream (https://github.com/mvo5/unattended-upgrades) over a year
  ago. These changes are not present in the latest Xenial nor Trusty
  packages (0.90 and 0.82.1) - requesting that these changes be pulled
  from upstream.

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

Title:
  Full backport SRU for unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  * I would like to propose a one-off full backport of unattended-upgrades
  1.2ubun

[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

[Martin Wildam]

Then it really looks like a bug. It would be good to have logfiles for
both cases to compare them.

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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

[Touch-packages] [Bug 1805757] Re: libjack-jackd2-dev can't be installed on ubuntu 18.10

[Lukas Florea]

When I try this, it says that it will remove wine-staging. I think I
have wine-staging from a ppa because it is not included in ubuntu but I
will double check this. How can I resolve the dependency issues? I need
wine-staging... Or is there any chance that ubuntu will include nvenc in
ffmpeg again?

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

Title:
  libjack-jackd2-dev can't be installed on ubuntu 18.10

Status in jackd2 package in Ubuntu:
  Invalid

Bug description:
  I need the package for the build-dep of ffmpeg. But it can't be installed:
  sudo apt-get install libjack-jackd2-dev
  Paketlisten werden gelesen... Fertig
  Abhängigkeitsbaum wird aufgebaut.   
  Statusinformationen werden eingelesen Fertig
  Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
  Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
  Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
  nicht erstellt wurden oder Incoming noch nicht verlassen haben.
  Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

  Die folgenden Pakete haben unerfüllte Abhängigkeiten:
   libjack-jackd2-dev : Hängt ab von: libjack-jackd2-0 (= 1.9.12~dfsg-2) aber 
2:1.9.11~20160223-1~wily1 soll installiert werden
  E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte 
Pakete.

  Sorry it is in German, I don't know how to set apt back to English...
  But it basically says that it depends from libjack-jackd2-0 (=
  1.9.12~dfsg-2) but 2:1.9.11~20160223-1~wily1 should be installed.

  Output of "apt policy libjack-jackd2-dev libjack-jackd2-0":
  libjack-jackd2-dev:
Installiert:   (keine)
Installationskandidat: 1.9.12~dfsg-2
Versionstabelle:
   1.9.12~dfsg-2 500
  500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  libjack-jackd2-0:
Installiert:   2:1.9.11~20160223-1~wily1
Installationskandidat: 2:1.9.11~20160223-1~wily1
Versionstabelle:
   *** 2:1.9.11~20160223-1~wily1 100
  100 /var/lib/dpkg/status
   1.9.12~dfsg-2 500
  500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages

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

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

[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

[Vivien GUEANT]

@Martin: On the same PC, it is impossible to connect to WiFi with Ubuntu
18.10, but it works with a bootable USB key Ubuntu 16.04.05

WiFi-Security :
- Security: WPA2 Enterprise
- Authentification: Protected EAP (PEAP)
- CA certificate : No CA certificate
- PEAP version : version 0
- Inner authentification : MSCHAPv2

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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

[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

[Sebastien Bacher]

Thanks!

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

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

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

[Touch-packages] [Bug 1803316] Re: VPN connection is stopped

[Marek Tenus]

It works with 18.04 and does not work with 16.04
It connects with other gates of VPN provider but not with this one I have set.

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

Title:
  VPN connection is stopped

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  From a few days I cannot connect via VPN, It worked from a few months

  *sudo apt policy network-manager*

  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.3
Candidate: 1.2.6-0ubuntu0.16.04.3
Versions:
   *** 1.2.6-0ubuntu0.16.04.3 500
  500 http://ftp.agh.edu.pl/ubuntu xenial-updates/main amd64 Packages
  500 http://ftp.agh.edu.pl/ubuntu xenial-security/main amd64 Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://ftp.agh.edu.pl/ubuntu xenial/main amd64 Packages

  
  */var/sys/log*

  
  Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.8520] audit: 
op="connection-activate" uuid="3872fc1d-94ce-465e-8d52-7bbeb3eb72fe" name="HS 
VPN" pid=13561 uid=1000 result="success"
  Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.8706] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: 
Started the VPN service, PID 2396
  Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.8815] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Saw 
the service appear; activating connection
  Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.9989] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
connection: (ConnectInteractive) reply received
  Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: pppd started with pid 
2405
  Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0148] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state changed: starting (3)
  Nov 14 10:46:08 hs pppd[2405]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
  Nov 14 10:46:08 hs NetworkManager[1081]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
  Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(plugin_init): initializing
  Nov 14 10:46:08 hs pppd[2405]: pppd 2.4.7 started by root, uid 0
  Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 3 / phase 'serial connection'
  Nov 14 10:46:08 hs NetworkManager[1081]: nm_device_get_device_type: assertion 
'NM_IS_DEVICE (self)' failed
  Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0226] manager: 
(ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/47)
  Nov 14 10:46:08 hs pptp[2411]: nm-pptp-service-2396 log[main:pptp.c:350]: The 
synchronous pptp option is NOT activated
  Nov 14 10:46:08 hs pppd[2405]: Using interface ppp0
  Nov 14 10:46:08 hs NetworkManager[1081]: Using interface ppp0
  Nov 14 10:46:08 hs pppd[2405]: Connect: ppp0 <--> /dev/pts/22
  Nov 14 10:46:08 hs NetworkManager[1081]: Connect: ppp0 <--> /dev/pts/22
  Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 5 / phase 'establish'
  Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0391] devices 
added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
  Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0392] device 
added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown 
configuration found.
  Nov 14 10:46:39 hs pppd[2405]: LCP: timeout sending Config-Requests
  Nov 14 10:46:39 hs NetworkManager[1081]: LCP: timeout sending Config-Requests
  Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 11 / phase 'disconnect'
  Nov 14 10:46:39 hs NetworkManager[1081]: Connection terminated.
  Nov 14 10:46:39 hs pppd[2405]: Connection terminated.
  Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: Terminated ppp daemon 
with PID 2405.
  Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0566] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: failed: connect-failed (1)
  Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0577] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state changed: stopping (5)
  Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0579] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state changed: stopped (6)
  Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0680] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state change reason: unknown (0)
  Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0802] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
service disappeared
  Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 

[Touch-packages] [Bug 1768789] Re: connectivity results in limited when behind proxy

[Markus Lindberg]

Has someone taken a look at this? Bionic has been out for a couple of
months now.

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

Title:
  connectivity results in limited when behind proxy

Status in network-manager package in Ubuntu:
  New

Bug description:
  The connectivity for a connection results in limited when behind a
  proxy for NetworkManager.

  $ sudo nmcli general 
  STATE  CONNECTIVITY  WIFI-HW  WIFI WWAN-HW  WWAN
  connected (site only)  limited   enabled  enabled  enabled  enabled

  $ sudo nmcli networking connectivity check 
  limited

  I have configured my proxy in both '/etc/environment' and via the GUI
  under 'Settings'->'Network'->'Network Proxy'->'Automatic'.

  After this is set I can do an HTTP GET against the URL/URI you have
  configured in the '/usr/lib/NetworkManager/conf.d/20-connectivity-
  ubuntu.conf' file.

  $ curl -I http://connectivity-check.ubuntu.com/
  HTTP/1.1 204 No Content
  Date: Thu, 03 May 2018 09:01:34 GMT
  Server: Apache/2.4.18 (Ubuntu)
  X-NetworkManager-Status: online
  X-Cache: MISS from proxy.example.com
  X-Cache-Lookup: MISS from proxy.example.com:3128
  Via: 1.1 proxy.example.com (squid/3.3.8)
  Connection: keep-alive

  $ env|grep -i proxy
  auto_proxy=http://proxy.example.com/auto
  https_proxy=http://proxy.example.com:3128
  http_proxy=http://proxy.example.com:3128

  But network connectivity still fails to use the proxy.

  I assume that the 'network-manager-config-connectivity-ubuntu' package
  is used for this feature after reading the following output.

  $ dpkg -S /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  network-manager-config-connectivity-ubuntu: 
/usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf

  If I remove the '/usr/lib/NetworkManager/conf.d/20-connectivity-
  ubuntu.conf' file the connectivity check succeeds or I don't get
  limited connectivity at least.

  --
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

  $ uname -a
  Linux lnxhplap2 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ dpkg -l|grep network-manager
  ii  network-manager1.10.6-2ubuntu1
 amd64network management framework (daemon and userspace tools)
  ii  network-manager-config-connectivity-ubuntu 1.10.6-2ubuntu1
 all  NetworkManager configuration to enable connectivity checking
  ii  network-manager-gnome  1.8.10-2ubuntu1
 amd64network management framework (GNOME frontend)
  ii  network-manager-pptp   1.2.6-1
 amd64network management framework (PPTP plugin core)
  ii  network-manager-pptp-gnome 1.2.6-1
 amd64network management framework (PPTP plugin GNOME GUI)
  --

  Note: I have used "proxy.example.com" as substitute for our proxy
  server in this bug report for privacy reasons.

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

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

[Touch-packages] [Bug 1805834] [NEW] systemd 237-3ubuntu10.9 ADT test failure with linux-aws 4.15.0-1029.30

[Kleber Sacilotto de Souza]

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20181129_104127_fbcbf@/log.gz

upstream:test/TEST-22-TMPFILES is a new testcases and has been failing
with all 4.15 kernels (at least on Bionic).

upstream:test/TEST-03-JOBS test/TEST-09-ISSUE-2691 test/TEST-19-DELEGATE
have been flaky for the last releases.

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

** Description changed:

  Testing failed on:
- amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20181129_104127_fbcbf@/log.gz
+ amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20181129_104127_fbcbf@/log.gz
+ 
+ upstream:test/TEST-22-TMPFILES is a new testcases and has been failing
+ with all 4.15 kernels (at least on Bionic).
+ 
+ upstream:test/TEST-03-JOBS test/TEST-09-ISSUE-2691 test/TEST-19-DELEGATE
+ have been flaky for the last releases.

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

Title:
  systemd 237-3ubuntu10.9 ADT test failure with linux-aws 4.15.0-1029.30

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20181129_104127_fbcbf@/log.gz

  upstream:test/TEST-22-TMPFILES is a new testcases and has been failing
  with all 4.15 kernels (at least on Bionic).

  upstream:test/TEST-03-JOBS test/TEST-09-ISSUE-2691
  test/TEST-19-DELEGATE have been flaky for the last releases.

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

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

[Touch-packages] [Bug 1337262] Re: kmod should permit use of compressed modules

[Paul Richards]

Is there any plan to backport this fix to Xenial?

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

Title:
  kmod should permit use of compressed modules

Status in kmod package in Ubuntu:
  Triaged
Status in kmod package in Debian:
  Fix Released

Bug description:
  kmod should permit use of compressed modules. This enables images that
  boot from RAM to be much smaller. In essence this requires only
  changing a build option. Uncompressed modules are still supported.

  A patch is here:
  https://github.com/abligh/kmod/commit/31795c8078ba9ccb6f064d11d0c9e640f8e0fab1

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

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

[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

[Till Kamppeter]

Done. Pull request posted:
https://gitlab.gnome.org/GNOME/gtk/merge_requests/434

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

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

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

[Touch-packages] [Bug 1805820] Re: Dependency error installing fontconfig-dbgsym

[Stephen Kitt]

It’s a bug in your Dockerfile. You should drop the proposed line. See
https://unix.stackexchange.com/q/484875/86440 for details.

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

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

Title:
  Dependency error installing fontconfig-dbgsym

Status in fontconfig package in Ubuntu:
  Invalid

Bug description:
  I am trying to install fontconfig-dbgsym under Ubuntu 18.04 inside
  Docker, running on Docker for Mac.

  I use the following Dockerfile:

  FROM ubuntu:18.04
  ENV DEBIAN_FRONTEND=noninteractive
  RUN apt-get update
  RUN apt-get install -y ubuntu-dbgsym-keyring lsb-release
  RUN \
( \
echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main 
restricted universe multiverse"; \
echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates 
main restricted universe multiverse"; \
echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed 
main restricted universe multiverse"; \
) > /etc/apt/sources.list.d/ddebs.list 
  RUN apt-get update
  RUN apt-get install -y fontconfig
  RUN apt-get install -y fontconfig-dbgsym

  Everything works except the last step, which fails with:

  Reading package lists...
  Building dependency tree...
  Reading state information...
  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:
   fontconfig-dbgsym : Depends: fontconfig (= 2.12.6-0ubuntu2.2) but 
2.12.6-0ubuntu2 is to be installed
  E: Unable to correct problems, you have held broken packages.
  The command '/bin/sh -c apt-get install -y fontconfig-dbgsym' returned a 
non-zero code: 100

  It complains the dependency `fontconfig=2.12.6-0ubuntu2.2` isn't
  installed, but it was successfully installed by the previous step.

  This looks like a bug.

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

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

[Touch-packages] [Bug 1805821] [NEW] GUI performance is poor

[Chandan]

Public bug reported:

Response is slow, amdgpu driver gives warning in dmesg which is below

[0.00] Linux version 4.15.0-36-generic (buildd@lgw01-amd64-031) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 
2018 (Ubuntu 4.15.0-36.39-generic 4.15.18)
[0.00] random: get_random_u32 called from bsp_init_amd+0x255/0x2a0 with 
crng_init=0
[0.966765] amd_uncore: AMD NB counters detected
[1.165305] pcie_mp2_amd: AMD(R) PCI-E MP2 Communication Driver Version: 1.0
[1.716922] amdkcl: loading out-of-tree module taints kernel.
[1.716947] amdkcl: module verification failed: signature and/or required 
key missing - tainting kernel
[1.827886] [drm] amdgpu kernel modesetting enabled.
[1.827887] [drm] amdgpu version: 18.30.2.15
[1.833528] fb: switching to amdgpudrmfb from EFI VGA
[1.850977] amdgpu :00:01.0: VRAM: 1024M 0x00F4 - 
0x00F43FFF (1024M used)
[1.850979] amdgpu :00:01.0: GTT: 1024M 0x - 
0x3FFF
[1.851137] [drm] amdgpu: 1024M of VRAM memory ready
[1.851139] [drm] amdgpu: 14975M of GTT memory ready.
[1.851291] [drm] amdgpu: dpm initialized
[1.853722] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:1! type 0 expected 3
[1.853779] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:3! type 0 expected 3
[1.853825] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:4! type 0 expected 3
[1.853872] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:5! type 0 expected 3
[2.064038] fbcon: amdgpudrmfb (fb0) is primary device
[2.128334] amdgpu :00:01.0: fb0: amdgpudrmfb frame buffer device
[2.145953] [drm] Initialized amdgpu 3.26.0 20150101 for :00:01.0 on 
minor 0
[5.265031] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying 
to reset the ECPU!!!
[6.277293] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying 
to reset the ECPU!!!
[7.289439] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying 
to reset the ECPU!!!
[8.301565] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying 
to reset the ECPU!!!
[9.313691] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying 
to reset the ECPU!!!
[   10.325849] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying 
to reset the ECPU!!!
[   11.338007] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying 
to reset the ECPU!!!
[   12.350159] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying 
to reset the ECPU!!!
[   13.362305] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying 
to reset the ECPU!!!
[   14.374463] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying 
to reset the ECPU!!!
[   14.394355] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, giving 
up!!!
[   14.394396] [drm:amdgpu_device_ip_set_powergating_state [amdgpu]] *ERROR* 
set_powergating_state of IP block  failed -110
[   15.420234] [drm:amdgpu_vce_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test 
timed out.
[   15.420321] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed 
testing IB on ring 12 (-110).
[   15.420369] [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* 
ib ring test failed (-110).
[   23.736730] EDAC amd64: Node 0: DRAM ECC disabled.
[   23.736731] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
[ 1566.370793] audit: type=1400 audit(1543500426.678:40): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/usr/share/libdrm/amdgpu.ids" pid=7169 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0


Takes too for software center to install .deb package where as it happens in a 
few seconds in terminal via dpkg -i.

Problems are after installation of amdgpu.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 29 19:44:18 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 amdgpu, 1.9-211, 4.15.0-36-generic, x86_64: installed
 amdgpu, 1.9-211, 4.15.0-39-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] 
(rev d4) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Kaveri [Radeon 

[Touch-packages] [Bug 1805820] [NEW] Dependency error installing fontconfig-dbgsym

[Simon Kissane]

Public bug reported:

I am trying to install fontconfig-dbgsym under Ubuntu 18.04 inside
Docker, running on Docker for Mac.

I use the following Dockerfile:

FROM ubuntu:18.04
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update
RUN apt-get install -y ubuntu-dbgsym-keyring lsb-release
RUN \
( \
echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main 
restricted universe multiverse"; \
echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates 
main restricted universe multiverse"; \
echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed 
main restricted universe multiverse"; \
) > /etc/apt/sources.list.d/ddebs.list 
RUN apt-get update
RUN apt-get install -y fontconfig
RUN apt-get install -y fontconfig-dbgsym

Everything works except the last step, which fails with:

Reading package lists...
Building dependency tree...
Reading state information...
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:
 fontconfig-dbgsym : Depends: fontconfig (= 2.12.6-0ubuntu2.2) but 
2.12.6-0ubuntu2 is to be installed
E: Unable to correct problems, you have held broken packages.
The command '/bin/sh -c apt-get install -y fontconfig-dbgsym' returned a 
non-zero code: 100

It complains the dependency `fontconfig=2.12.6-0ubuntu2.2` isn't
installed, but it was successfully installed by the previous step.

This looks like a bug.

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

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

Title:
  Dependency error installing fontconfig-dbgsym

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I am trying to install fontconfig-dbgsym under Ubuntu 18.04 inside
  Docker, running on Docker for Mac.

  I use the following Dockerfile:

  FROM ubuntu:18.04
  ENV DEBIAN_FRONTEND=noninteractive
  RUN apt-get update
  RUN apt-get install -y ubuntu-dbgsym-keyring lsb-release
  RUN \
( \
echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main 
restricted universe multiverse"; \
echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates 
main restricted universe multiverse"; \
echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed 
main restricted universe multiverse"; \
) > /etc/apt/sources.list.d/ddebs.list 
  RUN apt-get update
  RUN apt-get install -y fontconfig
  RUN apt-get install -y fontconfig-dbgsym

  Everything works except the last step, which fails with:

  Reading package lists...
  Building dependency tree...
  Reading state information...
  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:
   fontconfig-dbgsym : Depends: fontconfig (= 2.12.6-0ubuntu2.2) but 
2.12.6-0ubuntu2 is to be installed
  E: Unable to correct problems, you have held broken packages.
  The command '/bin/sh -c apt-get install -y fontconfig-dbgsym' returned a 
non-zero code: 100

  It complains the dependency `fontconfig=2.12.6-0ubuntu2.2` isn't
  installed, but it was successfully installed by the previous step.

  This looks like a bug.

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

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

[Touch-packages] [Bug 1803316] Re: VPN connection is stopped

[Marek Tenus]

VPN provider wrote to me that everything is ok on their side.

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

Title:
  VPN connection is stopped

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  From a few days I cannot connect via VPN, It worked from a few months

  *sudo apt policy network-manager*

  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.3
Candidate: 1.2.6-0ubuntu0.16.04.3
Versions:
   *** 1.2.6-0ubuntu0.16.04.3 500
  500 http://ftp.agh.edu.pl/ubuntu xenial-updates/main amd64 Packages
  500 http://ftp.agh.edu.pl/ubuntu xenial-security/main amd64 Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://ftp.agh.edu.pl/ubuntu xenial/main amd64 Packages

  
  */var/sys/log*

  
  Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.8520] audit: 
op="connection-activate" uuid="3872fc1d-94ce-465e-8d52-7bbeb3eb72fe" name="HS 
VPN" pid=13561 uid=1000 result="success"
  Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.8706] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: 
Started the VPN service, PID 2396
  Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.8815] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Saw 
the service appear; activating connection
  Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.9989] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
connection: (ConnectInteractive) reply received
  Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: pppd started with pid 
2405
  Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0148] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state changed: starting (3)
  Nov 14 10:46:08 hs pppd[2405]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
  Nov 14 10:46:08 hs NetworkManager[1081]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
  Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(plugin_init): initializing
  Nov 14 10:46:08 hs pppd[2405]: pppd 2.4.7 started by root, uid 0
  Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 3 / phase 'serial connection'
  Nov 14 10:46:08 hs NetworkManager[1081]: nm_device_get_device_type: assertion 
'NM_IS_DEVICE (self)' failed
  Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0226] manager: 
(ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/47)
  Nov 14 10:46:08 hs pptp[2411]: nm-pptp-service-2396 log[main:pptp.c:350]: The 
synchronous pptp option is NOT activated
  Nov 14 10:46:08 hs pppd[2405]: Using interface ppp0
  Nov 14 10:46:08 hs NetworkManager[1081]: Using interface ppp0
  Nov 14 10:46:08 hs pppd[2405]: Connect: ppp0 <--> /dev/pts/22
  Nov 14 10:46:08 hs NetworkManager[1081]: Connect: ppp0 <--> /dev/pts/22
  Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 5 / phase 'establish'
  Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0391] devices 
added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
  Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0392] device 
added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown 
configuration found.
  Nov 14 10:46:39 hs pppd[2405]: LCP: timeout sending Config-Requests
  Nov 14 10:46:39 hs NetworkManager[1081]: LCP: timeout sending Config-Requests
  Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 11 / phase 'disconnect'
  Nov 14 10:46:39 hs NetworkManager[1081]: Connection terminated.
  Nov 14 10:46:39 hs pppd[2405]: Connection terminated.
  Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: Terminated ppp daemon 
with PID 2405.
  Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0566] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: failed: connect-failed (1)
  Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0577] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state changed: stopping (5)
  Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0579] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state changed: stopped (6)
  Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0680] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state change reason: unknown (0)
  Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0802] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
service disappeared
  Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 1 / phase 'dead'
  Nov 14 10:46:39 hs Net

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~osomon/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/359817

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in gnome-shell package in Ubuntu:
  Triaged
Status in ibus package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/391

  ---

  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean
  users are simply unable to fill in password fields that previously
  were working fine. (see "ACTUAL RESULTS" below)

  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
    (click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).

  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1805436] Re: [SRU] Enable support for Stein Cloud Archive

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.28

---
software-properties (0.96.28) disco; urgency=medium

  * cloudarchive: Enable support for the Stein Ubuntu Cloud Archive on
18.04 (LP: #1805436).
  * Fix pyflakes error in properties/ppa.py:305: local variable
'e' is assigned to but never used.

 -- Corey Bryant   Tue, 27 Nov 2018 08:57:35
-0500

** Changed in: software-properties (Ubuntu Disco)
   Status: Triaged => Fix Released

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

Title:
  [SRU] Enable support for Stein Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Triaged
Status in software-properties source package in Disco:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:stein
 cloud-archive:stein-proposed

  This will also need to be SRU'd back to bionic.

  [Impact]
  End users have to manually enable the stein cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:stein
  sudo add-apt-repository cloud-archive:stein-proposed

  [Regression potential]
  Limited - just a data item addition

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

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

[Touch-packages] [Bug 1798313] Re: traceoute6 gives error sendto: Invalid argument

[Sebastien Bacher]

** Tags added: rls-bb-incoming

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

Title:
  traceoute6 gives error sendto: Invalid argument

Status in Iputils:
  Fix Released
Status in iputils package in Ubuntu:
  Confirmed
Status in iputils package in Debian:
  Fix Released

Bug description:
  When running the following command all get is an error. (traceroute6.db works)
  # traceroute6.iputils 2001:4860:4860::
  traceroute to 2001:4860:4860:: (2001:4860:4860::) from 
2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets
  sendto: Invalid argument
   1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *

  This seems like a regression of Debian bug https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=843264

  Package version installed:
  iputils-tracepath 3:20161105-1ubuntu2 amd64

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

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

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

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Sebastien Bacher]

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

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in gnome-shell package in Ubuntu:
  Triaged
Status in ibus package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/391

  ---

  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean
  users are simply unable to fill in password fields that previously
  were working fine. (see "ACTUAL RESULTS" below)

  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
    (click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).

  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

[Sebastien Bacher]

@Till, k, can you add that to your todolist then?

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

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

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

[Touch-packages] [Bug 1784499] Re: AppArmor treats regular NFS file access as network op

[Ingar Smedstad]

** Also affects: apparmor
   Importance: Undecided
   Status: New

** No longer affects: apparmor

** Also affects: snapd
   Importance: Undecided
   Status: New

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

Title:
  AppArmor treats regular NFS file access as network op

Status in snapd:
  New
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic.

  I have the usr.bin.man profile enforced, and home directories in NFS.

  The log excerpt copied below is the result of a single invocation of
  "man ls" by an unprivileged user. (The program did display the man
  page correctly to the user.)

  It does not seem appropriate for AppArmor to report the man(1) program
  as having attempted to contact the NFS server directly, when it only
  tried to access an NFS-served file in the normal way. "man" is not a
  network-aware program and the log below misleadingly implies
  otherwise.

  

  Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 
callbacks suppressed
  Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 
audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 
audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 
audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 
audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 
audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 
audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 
audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 
audit(1532986715.862:221): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.062006] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.062014] audit: type=1400 
audit(1532986715.862:222): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.066404] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.066434] audit: type=1400 
audit(1532986715.866:223): apparmor="DENIED" operati

[Touch-packages] [Bug 1691556] Re: Can't send audio to Amazon Echo via Bluetooth

[review]

my issue:
a2dp-source profile connect failed for XX:XX:XX:XX:XX: Device or resource busy


** Attachment added: "bluetooth status - ubuntu and echo"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+attachment/5217251/+files/bluetooth_echo2.png

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

Title:
  Can't send audio to Amazon Echo via Bluetooth

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Pairing and coupling to Amazon Echo works, but no sound is heard.

  I believe the issue is related to the fact that Amazon Echo is paired
  as a handset (i.e., speaker + microphone) rather than just as a
  speaker.  I believe the critical error is found in a dmesg line such
  as:

  Feb 28 10:59:05 n1 bluetoothd[1025]: a2dp-source profile connect
  failed for 50:F5:DA:A6:3F:EA: Device or resource busy

  as I describe in the askubuntu.com discussion at:

  https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo-
  via-bluetooth

  I have clarified there my thinking and the steps I've taken thus far
  on this issue, which includes trying debug bluetooth per the Ubuntu
  wiki page which describes how to do so.

  This is probably an upstream issue, as Mike H-R has commented there
  that the problem also occurs on ArchLinux.

  I and a few others would like to get this resolved, and I am happy to
  help (I'm a software developer).  However, at this point, I'm not sure
  how to proceed without some assistance.  I suppose I could report it
  to Debain, but I've only ever used Debain vis a vis Ubuntu, so I
  thought it best to start here.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 17 22:27:59 2017
  InstallationDate: Installed on 2015-12-26 (507 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (78 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
    UP RUNNING PSCAN
    RX bytes:13547334 acl:58 sco:0 events:1935087 errors:0
    TX bytes:1652407651 acl:1934967 sco:0 commands:76 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

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

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

[Touch-packages] [Bug 1691556] Re: Can't send audio to Amazon Echo via Bluetooth

[review]

I am using Ubuntu 18.04 and I have same issue. My echo was working fine
from many days and suddenly I have this issue where when I goto
bluetooth devices and right click on Echo and click on Audio Source, It
says "Now connected to Ubuntu" but does not play sound.

If I give the foolwoing command in terminal: sudo service bluetooth status
I see the issue might be with "a2dp-source profile connect failed for 
XX:XX:XX:XX:XX:XX: Device or resource busy"

Not sure how to fix it. I have removed and paired the device again and
restarted my computer couple of time but of no use.

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

Title:
  Can't send audio to Amazon Echo via Bluetooth

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Pairing and coupling to Amazon Echo works, but no sound is heard.

  I believe the issue is related to the fact that Amazon Echo is paired
  as a handset (i.e., speaker + microphone) rather than just as a
  speaker.  I believe the critical error is found in a dmesg line such
  as:

  Feb 28 10:59:05 n1 bluetoothd[1025]: a2dp-source profile connect
  failed for 50:F5:DA:A6:3F:EA: Device or resource busy

  as I describe in the askubuntu.com discussion at:

  https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo-
  via-bluetooth

  I have clarified there my thinking and the steps I've taken thus far
  on this issue, which includes trying debug bluetooth per the Ubuntu
  wiki page which describes how to do so.

  This is probably an upstream issue, as Mike H-R has commented there
  that the problem also occurs on ArchLinux.

  I and a few others would like to get this resolved, and I am happy to
  help (I'm a software developer).  However, at this point, I'm not sure
  how to proceed without some assistance.  I suppose I could report it
  to Debain, but I've only ever used Debain vis a vis Ubuntu, so I
  thought it best to start here.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 17 22:27:59 2017
  InstallationDate: Installed on 2015-12-26 (507 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (78 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
    UP RUNNING PSCAN
    RX bytes:13547334 acl:58 sco:0 events:1935087 errors:0
    TX bytes:1652407651 acl:1934967 sco:0 commands:76 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

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

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

[Touch-packages] [Bug 1798073] Re: [SRU] Provide 2018 archive signing key on stable releases

[Dimitri John Ledkov]

$ schroot -u root -c bionic-amd64
(bionic-amd64)root@ottawa:~# apt-key list
/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg
--
pub   rsa4096 2012-05-11 [SC]
  790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
uid   [ unknown] Ubuntu Archive Automatic Signing Key (2012) 


/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg
--
pub   rsa4096 2012-05-11 [SC]
  8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
uid   [ unknown] Ubuntu CD Image Automatic Signing Key (2012) 


(bionic-amd64)root@ottawa:~# gpg --no-default-keyring --keyring 
/usr/share/keyrings/ubuntu-
ubuntu-archive-keyring.gpg   ubuntu-archive-removed-keys.gpg  
ubuntu-master-keyring.gpg
(bionic-amd64)root@ottawa:~# gpg --no-default-keyring --keyring 
/usr/share/keyrings/ubuntu-archive-keyring.gpg -k   
gpg: /root/.gnupg/trustdb.gpg: trustdb created
/usr/share/keyrings/ubuntu-archive-keyring.gpg
--
pub   rsa4096 2012-05-11 [SC]
  790BC7277767219C42C86F933B4FE6ACC0B21F32
uid   [ unknown] Ubuntu Archive Automatic Signing Key (2012) 


pub   rsa4096 2012-05-11 [SC]
  843938DF228D22F7B3742BC0D94AA3F0EFE21092
uid   [ unknown] Ubuntu CD Image Automatic Signing Key (2012) 


(bionic-amd64)root@ottawa:~# dpkg-query -W ubuntu-keyring
ubuntu-keyring  2016.10.27


Upgrading ubuntu-keyring

(bionic-amd64)root@ottawa:~# dpkg-query -W ubuntu-keyring
ubuntu-keyring  2018.09.18.1~18.04.0

# apt-key list
/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg
--
pub   rsa4096 2012-05-11 [SC]
  790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
uid   [ unknown] Ubuntu Archive Automatic Signing Key (2012) 


/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg
--
pub   rsa4096 2012-05-11 [SC]
  8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
uid   [ unknown] Ubuntu CD Image Automatic Signing Key (2012) 


/etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
--
pub   rsa4096 2018-09-17 [SC]
  F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
uid   [ unknown] Ubuntu Archive Automatic Signing Key (2018) 


(bionic-amd64)root@ottawa:~# gpg --no-default-keyring --keyring 
/usr/share/keyrings/ubuntu-archive-keyring.gpg -k
/usr/share/keyrings/ubuntu-archive-keyring.gpg
--
pub   rsa4096 2012-05-11 [SC]
  790BC7277767219C42C86F933B4FE6ACC0B21F32
uid   [ unknown] Ubuntu Archive Automatic Signing Key (2012) 


pub   rsa4096 2012-05-11 [SC]
  843938DF228D22F7B3742BC0D94AA3F0EFE21092
uid   [ unknown] Ubuntu CD Image Automatic Signing Key (2012) 


pub   rsa4096 2018-09-17 [SC]
  F6ECB3762474EDA9D21B7022871920D1991BC93C
uid   [ unknown] Ubuntu Archive Automatic Signing Key (2018) 



No keys are removed, and only the 2018 key added as a snippet and in the 
keyring.

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

Title:
  [SRU] Provide 2018 archive signing key on stable releases

Status in ubuntu-keyring package in Ubuntu:
  Fix Released
Status in ubuntu-keyring source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * For LTS releases to be able to bootstrap dual and single signed
  future releases, and validate all signatures, 2018 archive signing key
  should be SRUed back

   * Also build process has improved documentation and vague validation
  that all key snippets are signed correctly

  [Test Case]

   * $ apt-key list
  ...
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
  --
  pub   rsa4096 2018-09-17 [SC]
    F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2018) 

  ...

  apt-key list should contain the 2018 archive key.

  [Regression Potential]

   * Build-process, key algo, and key size, and file format are the same
  as previous key snippets thus supported by all of gpg1 gpg2 gpgv1
  gpgv2.

  [Other Info]

   * 2018 key is to be used for dual-signing in DD series and up

   * Bileto PPA is built against security pocket only, suitable to be
  released into both -security and -updates

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

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

[Touch-packages] [Bug 1803707] Re: merge nss 2:3.39-1 from Debian unstable

[Launchpad Bug Tracker]

This bug was fixed in the package nss - 2:3.39-1ubuntu1

---
nss (2:3.39-1ubuntu1) disco; urgency=medium

  * Merge with Debian unstable. Remaining changes (LP: #1803707):
- d/libnss3.links: make freebl3 available as library (LP 1744328)
  - d/control: add dh-exec to Build-Depends
  - d/rules: make mkdir tolerate debian/tmp existing (due to dh-exec)
  * Dropped changes:
- d/rules: when building with -O3 on ppc64el this FTBFS, build with
  -Wno-error=maybe-uninitialized to avoid that

nss (2:3.39-1) unstable; urgency=medium

  * New upstream release.
- Fixes CVE-2018-12384. Closes: #908332.
  * debian/libnss3.symbols: Add NSS_3_39 and NSSUTIL_3_39 symbol versions.

nss (2:3.38-1) unstable; urgency=medium

  * New upstream release.
  * debian/libnss3.symbols: Add NSSUTIL_3_38 symbol version.

nss (2:3.37.1-1) unstable; urgency=medium

  * New upstream release.
  * nss/lib/freebl/Makefile: Build FStar.c when not building with int128
support. bz#1459739. Closes: #900227

nss (2:3.37-1) unstable; urgency=medium

  * New upstream release. Fixes: #898496.
  * debian/control, debian/rules: Generate dbgsym package.AA
  * debian/copyright: Switch to machine-readable format.
  * debian/control: Bump Standards-Version to 4.1.4.

 -- Christian Ehrhardt   Fri, 16 Nov
2018 14:27:39 +0100

** Changed in: nss (Ubuntu)
   Status: In Progress => Fix Released

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

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

Title:
  merge nss 2:3.39-1 from Debian unstable

Status in nss package in Ubuntu:
  Fix Released

Bug description:
  please merge newer nss for disco

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

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