[Touch-packages] [Bug 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

[Daniel van Vugt]

Is the client crashing? See bug 1668466

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

Title:
  Unity8 crashed right clicking on vlc [terminate called after throwing
  an instance of 'std::out_of_range' what(): map::at]

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Incomplete
Status in Mir 0.26 series:
  Incomplete
Status in MirAL:
  Incomplete
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install vlc, launch it from app drawer or launcher
  try to use the menu, the menu shows for a split second and closes 
  try to right click on vlc, here it just crashes/restarts unity8

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

-- 
Mailing list: https://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 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

[Daniel van Vugt]

** Changed in: mir
Milestone: 0.27.0 => 0.28.0

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

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  In Progress
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

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

-- 
Mailing list: https://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 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

[Alan Griffiths]

I can now see something like this with miral-shell:

[terminal 1]
$ miral-shell

[terminal 2]
$ miral-xrun vlc

Right click a few times in rapid succession.

Expect: nothing bad
Actual: [terminal 1] Aborted (core dumped)

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

Title:
  Unity8 crashed right clicking on vlc [terminate called after throwing
  an instance of 'std::out_of_range' what(): map::at]

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Incomplete
Status in Mir 0.26 series:
  Incomplete
Status in MirAL:
  Incomplete
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install vlc, launch it from app drawer or launcher
  try to use the menu, the menu shows for a split second and closes 
  try to right click on vlc, here it just crashes/restarts unity8

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

-- 
Mailing list: https://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 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload

[ChristianEhrhardt]

Hi,
I wanted to notify that the merge of systemd version 234 fixed this bug - it is 
only in proposed so far, but I checked against that.
So we can consider artful done (soon), but it would be great to consider SRUs.

** Changed in: systemd (Ubuntu Artful)
   Status: New => Fix Released

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Released => Fix Committed

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

Title:
  Systemd fails to serialize tasks correctly on daemon-reload

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  Fix Committed
Status in systemd package in Debian:
  Confirmed

Bug description:
  Hi,
  I was initially tracking down a libvirt bug [1], but happened to realize it 
is actually a general systemd issue.
  From there I got to file, discuss and test [2].

  For now I file the bug to be ablte to do my tests correctly, but if it
  really fixes the issue I'd like to suggest to fix it in the release -
  so better file upfront and do even my test patches right.

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379
  [2]: https://github.com/systemd/systemd/issues/6299.

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

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

[Steve Langasek]

Hello Jeremy, or anyone else affected,

Accepted shim-signed into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.32~14.04.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

Title:
  update-secure-boot-policy behaving badly with unattended-upgrades

Status in shim-signed package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in shim-signed source package in Trusty:
  Fix Committed
Status in unattended-upgrades source package in Trusty:
  Invalid
Status in shim-signed source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Invalid
Status in shim-signed source package in Yakkety:
  Fix Released
Status in unattended-upgrades source package in Yakkety:
  Invalid

Bug description:
  [Impact]
  Any user with unattended upgrades enabled and DKMS packages in a Secure Boot 
environment might be prompted to change Secure Boot policy, which will fail and 
crash in unattended-upgrades.

  [Test case]
  = unattended upgrade =
  1) Create /var/lib/dkms/TEST-DKMS
  2) Install new package
  3) Trigger unattended-upgrades: unattended-upgrades -d

  Upgrade should run smoothly for all the processing but fail to
  complete; shim-signed should end the unattended upgrade with a error
  as unattended change of the Secure Boot policy can not be done.
  Upgrade should not hang in high CPU usage.

  = standard upgrade =
  1) Create /var/lib/dkms/TEST-DKMS
  2) install new package.
  3) Verify that the upgrade completes normally. 

  
  [Regression Potential]
  Any failure to prompt for or change Secure Boot policy in mokutil while in an 
*attended* upgrade scenario would constitute a regression of this SRU.

  Any other issues related to booting in Secure Boot mode should instead
  be directed to bug 1637290 (shim update).

  ---

  Currently, unattended-upgrades will automatically install all updates
  for those running development releases of Ubuntu (LP: #1649709)

  Today, my computer was acting very sluggish. Looking at my process
  list, I saw/ usr/sbin/update-secureboot-policy was using a log of CPU.

  I killed the process. I have a /var/crash/shim-signed.0.crash but
  since it's 750 MB, I didn't bother submitting it or looking at it
  more. Maybe it crashed because I killed the process. Also, I see that
  unattended-upgrades-dpkg.log is 722 MB.

  Today's update included both VirtualBox and the linux kernel.

  I am attaching an excerpt of /var/log/unattended-upgrades/unattended-
  upgrades-dpkg.log

  This message was repeated a very large number of times (but I only
  included it once in the attachment:

  "Invalid password

  The Secure Boot key you've entered is not valid. The password used must be
  between 8 and 16 characters."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: shim-signed 1.23+0.9+1474479173.6c180c6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 17 11:15:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-23 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  SourcePackage: shim-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

[Alan Griffiths]

The fix released in Mir 0.27 covers the API for only one of the three
functions mentioned.

** Changed in: mir
   Status: Fix Released => In Progress

** Changed in: mir (Ubuntu)
   Status: Fix Released => In Progress

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

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  In Progress
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

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

-- 
Mailing list: https://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 1670269] Re: Add com.ubuntu.usbcreator.format for usb creator action

[Khurshid Alam]

** Tags added: julyshakedown

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

Title:
  Add com.ubuntu.usbcreator.format for usb creator action

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  Usb creator still asks for password when formatting or trying to
  install boot-loader. If user doesn't respond within a sepecific time,
  it fails and user has to start the process all over again.

  Adding "com.ubuntu.usbcreator.format" to Action solves the issue.

  ### PATCH
  -

  --- a/com.ubuntu.desktop.pkla
  +++ b/com.ubuntu.desktop.pkla
  @@ -25,7 +25,7 @@
   
   [usb-creator]
   Identity=unix-group:admin;unix-group:sudo
  -Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image
  
+Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image;com.ubuntu.usbcreator.format
   ResultActive=yes
   
   [Printer administration]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1670269/+subscriptions

-- 
Mailing list: https://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 1347553] Re: Ubuntu GNOME: reboot dialog in live image shows 6 versions of the live user logged in on the console

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubuntu GNOME: reboot dialog in live image shows 6 versions of the live
  user logged in on the console

Status in gnome-shell package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When attempting to shutdown from the power menu on Ubuntu GNOME live
  session the live session user is shown logged in roughly 6 times on
  (console).  Talking to ~xnox this is likely related to systemd-logind.

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

-- 
Mailing list: https://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 1308291] Re: network-manager icon is gone in 14.04

[Launchpad Bug Tracker]

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

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

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

Title:
  network-manager icon is gone in 14.04

Status in gnome-shell package in Ubuntu:
  Expired
Status in network-manager package in Ubuntu:
  Expired

Bug description:
  After upgrading to 14.04, the network-manger icon is no longer shown
  by gnome-shell.

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

-- 
Mailing list: https://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 1308291] Re: network-manager icon is gone in 14.04

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  network-manager icon is gone in 14.04

Status in gnome-shell package in Ubuntu:
  Expired
Status in network-manager package in Ubuntu:
  Expired

Bug description:
  After upgrading to 14.04, the network-manger icon is no longer shown
  by gnome-shell.

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

-- 
Mailing list: https://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 1704911] Re: package fontconfig 2.11.94-0ubuntu2 failed to install%2Fupgrade%3A subprocess installed post-installation script returned error exit status 1

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: hardware-error

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

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

Title:
  package fontconfig 2.11.94-0ubuntu2 failed to install%2Fupgrade%3A
  subprocess installed post-installation script returned error exit
  status 1

Status in fontconfig package in Ubuntu:
  Invalid

Bug description:
  The error occurred during distribution upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: fontconfig 2.11.94-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: i386
  Date: Mon Jul 17 19:35:30 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  FontConfigLog: Bus error
  InstallationDate: Installed on 2011-05-03 (2267 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-07-17 (0 days ago)

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

-- 
Mailing list: https://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 1704807] Re: Audio doesn't switch automatically to BT speaker when hotplugged after application playback started

[Daniel van Vugt]

Partially confirmed, but...

* Only confirmed in Totem. VLC did automatically switch back to
bluetooth for me (so its menu says). Except I then lost all sound. One
possibly related observation is that VLC provides a menu for you to
select the current audio device. I don't think Totem does or can
(because GStreamer is too generalised to expose devices by name?).

* PulseAudio is designed to allow different applications to use
different audio devices of their choosing. So choosing to ignore newly
added devices may in fact be an application bug/feature. The recent
fixes to PulseAudio mostly relate to default devices (that which is used
at application startup, not switched to during application execution).


** Summary changed:

- output doesn't switch automatically to BT speaker when available
+ Audio doesn't switch automatically to BT speaker when hotplugged after 
application playback started

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

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

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

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

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

** Summary changed:

- Audio doesn't switch automatically to BT speaker when hotplugged after 
application playback started
+ Audio doesn't switch automatically to Bluetooth speaker when hotplugged after 
application playback started

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

Title:
  Audio doesn't switch automatically to Bluetooth speaker when
  hotplugged after application playback started

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  artful desktop

  Test Case.
  1. Pair a BT Speaker and set the output channel to the speaker
  2. Play something with vlc or totem (and make sure it uses the speaker with 
pavucontrol for instance)
  3. Switch the output to another channel eg internal speaker and turn the BT 
speaker off (do not close the music player)
  4. Turn the speaker back on and wait until it connects
  5. If the speaker is not selected automatically as the output, select it in 
the sound settings
  6. Resume playing in VLC

  Expected result
  The track plays on the speaker

  Actual result
  It plays on the internal audio.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 17 17:09:17 2017
  InstallationDate: Installed on 2013-09-03 (1412 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/pulseaudio/+bug/1704807/+subscriptions

-- 
Mailing list: https://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 1704911] Re: package fontconfig 2.11.94-0ubuntu2 failed to install%2Fupgrade%3A subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package fontconfig 2.11.94-0ubuntu2 failed to install%2Fupgrade%3A
  subprocess installed post-installation script returned error exit
  status 1

Status in fontconfig package in Ubuntu:
  New

Bug description:
  The error occurred during distribution upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: fontconfig 2.11.94-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: i386
  Date: Mon Jul 17 19:35:30 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  FontConfigLog: Bus error
  InstallationDate: Installed on 2011-05-03 (2267 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-07-17 (0 days ago)

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

-- 
Mailing list: https://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 1704911] [NEW] package fontconfig 2.11.94-0ubuntu2 failed to install%2Fupgrade%3A subprocess installed post-installation script returned error exit status 1

[John Line]

Public bug reported:

The error occurred during distribution upgrade.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: fontconfig 2.11.94-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic i686
NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv nvidia_uvm nvidia
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: i386
Date: Mon Jul 17 19:35:30 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
FontConfigLog: Bus error
InstallationDate: Installed on 2011-05-03 (2267 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to zesty on 2017-07-17 (0 days ago)

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


** Tags: apport-package i386 zesty

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

Title:
  package fontconfig 2.11.94-0ubuntu2 failed to install%2Fupgrade%3A
  subprocess installed post-installation script returned error exit
  status 1

Status in fontconfig package in Ubuntu:
  New

Bug description:
  The error occurred during distribution upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: fontconfig 2.11.94-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: i386
  Date: Mon Jul 17 19:35:30 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  FontConfigLog: Bus error
  InstallationDate: Installed on 2011-05-03 (2267 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-07-17 (0 days ago)

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

-- 
Mailing list: https://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 762349] Re: [SRU] Difficult to distinguish which tab is selected

[Daniel van Vugt]

Nicolas, please log a new bug so it's more obvious that this /new/
problem exists...

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

Title:
  [SRU] Difficult to distinguish which tab is selected

Status in Ayatana Design:
  Fix Committed
Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Released

Bug description:
  [Impact]
   * When a user opens multiple tabs in GNOME terminal all tabs are styled in a 
*very* visually similar manner.  This makes it very hard to distinguish between 
the current active tab and all the others and on a HiDPI screen pretty much 
impossible.

  * This fix has been ack'd by design and was targeted for X but didn't
  get reviewed and OK'd in time.  Design team have approved this
  styling.

  * This bug is fixed by extending the CSS specifically for Terminal
  (i.e. no other applications are affected) giving the active tab a
  darker background colour (using only theme defined colours) and
  reworks the borders around the tabs to remove the graduated image
  borders that only look right on a light coloured background.  Changes
  have been made for both Ambiance and Radiance.

  [Test Case]
   * On a stock 16.04 install open GNOME Terminal (ctrl-alt-t)
   * Open five new tabs (ctrl-shift-t)
   * Click on the tab in the middle
   * Note that it is hard to see at a glance which tab is currently selected
   * Close Terminal and all open tabs.
   * Install the patched theme
   * Open Terminal and open five new tabs
   * Click on the tab in the middle and note that it takes on a light grey 
background compared to the unselected tabs which are dark grey.

  [Regression Potential]
   * The patch only addresses tabs that are placed at the top of the window. 
However this is the only option in Terminal, so should not cause any problems.
   * There is a work-around to match the "actions bar" (the bit with the 
dropdown selector and + button).  This bug is supposed to be fixed in v3.20 and 
could be removed.  This is commented in the CSS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/762349/+subscriptions

-- 
Mailing list: https://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 1697375] Re: whoopsie's network-manager state querying is broken

[Launchpad Bug Tracker]

This bug was fixed in the package whoopsie - 0.2.57

---
whoopsie (0.2.57) artful; urgency=medium

  * src/connectivity.c: query the correct property when trying to
network-manager's state. (LP: #1697375)
  * Modify the whoopsie service file to start after networking is on-line.

 -- Brian Murray   Mon, 17 Jul 2017 13:08:38 -0700

** Changed in: whoopsie (Ubuntu Artful)
   Status: In Progress => Fix Released

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

Title:
  whoopsie's network-manager state querying is broken

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Xenial:
  Triaged
Status in whoopsie source package in Zesty:
  Triaged
Status in whoopsie source package in Artful:
  Fix Released

Bug description:
  [Impact]
  whoopsie's querying of network-manager's state is broken and this results in 
whoopsie only being able to detect if the system is on-line when network 
manager's state changes. Subsequently, if one manually restarts whoopsie then 
whoopsie will stay off-line until an n-m state change. This can result in 
crashes not being uploaded.  Additionally, whoopsie's systemd service file does 
not start after networking which is incorrect since it initially needs to query 
network-manager's state. (However, this ended up allowing crash reports to 
still be submitted because whoopsie would start first then the n-m's state 
would change and whoopsie would detect that.)

  [Test Case] (state detection failure)
  1) Manually restart the whoopsie service
  2) Observe the following two messages:
  "Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] Could not get the Network 
Manager state:
  Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property 'state'"

  with the version of network-manager from -proposed you will not see
  these messages when restarting whoopsie.

  [Test Case] (starting after network-manager0
  1) Boot your system
  2) Observe the following in syslog:
  "Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network 
Manager state:
  Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.NetworkManager was not provided by any .service files
  "

  with the version of network-manager in -proposed you will not see the
  "NetworkManager was not provided" messages.

  [Regression Potential]
  Its possible that systems that were not submitting crash reports suddenly 
will and that will use some network bandwidth and Error Tracker resources.

  - Original Description -
  
  On artful crash reports are not uploaded automatically (several .crash files 
in /var/crash and no corresponding upload or .uploaded files)

  ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: whoopsie 0.2.56
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 12 09:39:29 2017
  InstallationDate: Installed on 2013-09-03 (1377 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: apport-noui N/ASourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1704898] [NEW] package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Yuvaraja K]

Public bug reported:

Not installing Wine

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: bsdutils 1:2.29-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Tue Jul 18 06:14:12 2017
DpkgTerminalLog:
 dpkg: error processing package bsdutils (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-14 (64 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: util-linux
Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in util-linux package in Ubuntu:
  New

Bug description:
  Not installing Wine

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Jul 18 06:14:12 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-14 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1704895] [NEW] service output sometimes missing when "User=" used

[Kevin Pulo]

Public bug reported:

This repros on a clean and up-to-date 16.04.2, but not on ubuntu-artful-
daily-amd64-server-20170618, so it looks like this was fixed (possibly
upstream) sometime between 229-4ubuntu17 and 233-6ubuntu3.

Create the test files `/etc/systemd/system/test.service`:
```
[Unit]
Description=test service
After=syslog.target
After=sysinit.target

[Service]
ExecStart=/usr/local/bin/test
User=nobody

[Install]
WantedBy=sysinit.target
```
and `/usr/local/bin/test`:
```bash
#!/bin/sh

echo 'stdout msg'
echo 'stderr msg' 1>&2
# With the next line commented out, rarely see any journal output for the 
failed service (though it still gets forwarded to syslog every time).
# With the line uncommented, will usually see output, and only occasionally see 
partial output (1 out of the 2 lines) or no output at all.
#sleep 0.$RANDOM
exit 11
```
(and remember to `chmod a+x /usr/local/bin/test`).

Now as root try to start the service a few times.  It will always fail,
but the bug is that the `stdout msg` and `stderr msg` lines are absent
from the journal.  The expectation is that all lines output by the
failing service should be present - these lines are often critical for
diagnosing why the service has failed to start.  The lines do, however,
always get forwarded to syslog.

```
root@ip-172-31-6-192:~# cat /etc/systemd/system/test.service
[Unit]
Description=test service
After=syslog.target
After=sysinit.target

[Service]
ExecStart=/usr/local/bin/test
User=nobody

[Install]
WantedBy=sysinit.target

root@ip-172-31-6-192:~# cat /usr/local/bin/test
#!/bin/bash

echo 'stdout msg'
echo 'stderr msg' 1>&2
# With the next line commented out, rarely see any journal output for the 
failed service (though it still gets forwarded to syslog every time).
# With the line uncommented, will usually see output, and only occasionally see 
partial output (1 out of the 2 lines) or no output at all.
#sleep 0.$RANDOM
exit 11

root@ip-172-31-6-192:~# systemctl start test ; sleep 1 ; systemctl status test
● test.service - test service
   Loaded: loaded (/etc/systemd/system/test.service; disabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Tue 2017-07-18 00:45:06 UTC; 1s ago
  Process: 23557 ExecStart=/usr/local/bin/test (code=exited, status=11)
 Main PID: 23557 (code=exited, status=11)

Jul 18 00:45:06 ip-172-31-6-192 systemd[1]: Started test service.
Jul 18 00:45:06 ip-172-31-6-192 systemd[1]: test.service: Main process exited, 
code=exited, status=11/n/a
Jul 18 00:45:06 ip-172-31-6-192 systemd[1]: test.service: Unit entered failed 
state.
Jul 18 00:45:06 ip-172-31-6-192 systemd[1]: test.service: Failed with result 
'exit-code'.
root@ip-172-31-6-192:~# systemctl start test ; sleep 1 ; systemctl status test
● test.service - test service
   Loaded: loaded (/etc/systemd/system/test.service; disabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Tue 2017-07-18 00:45:09 UTC; 1s ago
  Process: 23565 ExecStart=/usr/local/bin/test (code=exited, status=11)
 Main PID: 23565 (code=exited, status=11)

Jul 18 00:45:09 ip-172-31-6-192 systemd[1]: Started test service.
Jul 18 00:45:09 ip-172-31-6-192 systemd[1]: test.service: Main process exited, 
code=exited, status=11/n/a
Jul 18 00:45:09 ip-172-31-6-192 systemd[1]: test.service: Unit entered failed 
state.
Jul 18 00:45:09 ip-172-31-6-192 systemd[1]: test.service: Failed with result 
'exit-code'.
root@ip-172-31-6-192:~# systemctl start test ; sleep 1 ; systemctl status test
● test.service - test service
   Loaded: loaded (/etc/systemd/system/test.service; disabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Tue 2017-07-18 00:45:11 UTC; 1s ago
  Process: 23573 ExecStart=/usr/local/bin/test (code=exited, status=11)
 Main PID: 23573 (code=exited, status=11)

Jul 18 00:45:11 ip-172-31-6-192 systemd[1]: Started test service.
Jul 18 00:45:11 ip-172-31-6-192 systemd[1]: test.service: Main process exited, 
code=exited, status=11/n/a
Jul 18 00:45:11 ip-172-31-6-192 systemd[1]: test.service: Unit entered failed 
state.
Jul 18 00:45:11 ip-172-31-6-192 systemd[1]: test.service: Failed with result 
'exit-code'.
root@ip-172-31-6-192:~# tail /var/log/syslog
Jul 18 00:45:09 ip-172-31-6-192 test[23565]: stderr msg
Jul 18 00:45:09 ip-172-31-6-192 systemd[1]: test.service: Main process exited, 
code=exited, status=11/n/a
Jul 18 00:45:09 ip-172-31-6-192 systemd[1]: test.service: Unit entered failed 
state.
Jul 18 00:45:09 ip-172-31-6-192 systemd[1]: test.service: Failed with result 
'exit-code'.
Jul 18 00:45:11 ip-172-31-6-192 systemd[1]: Started test service.
Jul 18 00:45:11 ip-172-31-6-192 test[23573]: stdout msg
Jul 18 00:45:11 ip-172-31-6-192 test[23573]: stderr msg
Jul 18 00:45:11 ip-172-31-6-192 systemd[1]: test.service: Main process exited, 
code=exited, status=11/n/a
Jul 18 00:45:11 ip-172-31-6-192 systemd[1]: test.service: Unit entered failed 
state.
Jul 18 00:45:11 ip-172-31-6-192 systemd[1]: test.service: Failed with result 

[Touch-packages] [Bug 157690] ☠Fw: Tillerson to make announcement on Iran nuclear deal: White House

[orowitz]

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

Dear,

Under U.S. law, the State Department must notify Congress every 90 days
of Iran's compliance with http://carmelalee.com/coolx.php?fbfa


Best Wishes, mauro gardenal


From: Bug 157690 [mailto:157...@bugs.launchpad.net]
Sent: Monday, July 17, 2017 6:59 PM
To: mauro.garde...@libero.it
Subject: Ii dont even know...

It takes away  the incentive to do the new  content.  I always likely
the karma reward.  Gave  a reason  to do paths like slow and steady and
Picky.   I feel like the 'less content paths'/summer and  winter will be
mostly skipped over  by the average player  base -  whats the point in
dealing with the extra restrictions  if there is no extra reward.



** Attachment added: "D59EAA603BF9AA25DE72ED23388653D7.jpg"
   
https://bugs.launchpad.net/bugs/157690/+attachment/4916443/+files/D59EAA603BF9AA25DE72ED23388653D7.jpg

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

Title:
  update-manager crashed with SIGSEGV in
  gtk_text_view_check_keymap_direction()

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Binary package hint: update-manager

  install and restart

  ProblemType: Crash
  Architecture: i386
  Date: Sat Oct  6 22:36:02 2007
  DistroRelease: Ubuntu 7.10
  ExecutablePath: /usr/bin/update-manager
  InterpreterPath: /usr/bin/python2.5
  NonfreeKernelModules: cdrom
  Package: update-manager 1:0.80
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python2.5 /usr/bin/update-manager
  ProcCwd: /root
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: update-manager
  StacktraceTop:
   gtk_text_view_check_keymap_direction (text_view=0x85f3808)
   gtk_text_view_ensure_layout (text_view=0x85f3808)
   gtk_text_view_update_layout_width (text_view=0x0)
   gtk_text_view_value_changed (adj=0x0, text_view=0x85f3808)
   _gtk_marshal_VOID__OBJECT_OBJECT (closure=0x85f05a0,
  Title: update-manager crashed with SIGSEGV in 
gtk_text_view_check_keymap_direction()
  Uname: Linux Ubuntu710GustyGibbonBeta 2.6.22-13-generic #1 SMP Thu Oct 4 
17:18:44 GMT 2007 i686 GNU/Linux
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse plugdev scanner 
tape

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

-- 
Mailing list: https://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 258050] Re: Real Audio streams play double after pause

[Bug Watch Updater]

** Changed in: gst-plugins-good
   Status: Incomplete => Expired

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

Title:
  Real Audio streams play double after pause

Status in gst-plugins-good:
  Expired
Status in Totem:
  Invalid
Status in gst-plugins-good0.10 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: totem

  When listening to a real audio stream, if the audio is paused, several
  overlapping versions of the audio file will play upon resume. It can
  be tested with this file:

  http://www.cato.org/realaudio/cbfa-10-28-03.ram

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Aug 14 19:36:06 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/totem-gstreamer
  NonfreeKernelModules: nvidia
  Package: totem-gstreamer 2.22.1-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  Uname: Linux 2.6.24-19-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/258050/+subscriptions

-- 
Mailing list: https://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 1641914] Re: Please backport two recent-manager patches

[Martin Wimpress]

** Changed in: gtk+3.0 (Ubuntu Yakkety)
   Status: New => Won't Fix

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

Title:
  Please backport two recent-manager patches

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Yakkety:
  Won't Fix

Bug description:
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=bf560369f2401e2cdd16f962f248e98c890835d0
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=a28022e9161415ef65ae3f21f0c4052f5db8558b

  Please apply/backport these two patches from the 3.22 branch. They fix a 
memory DOS, originally reported against mate-panel here:
  https://github.com/mate-desktop/mate-panel/issues/479

  The GTK+2 version of this bug is bug 1641912

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

-- 
Mailing list: https://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 1704628] Re: CUPS keeps crashing 17.04

[Till Kamppeter]

How did you do this bug report? The automatically generated information
does not contain any stack trace.

When it comes to a crash there is usually a pop-up guiding you to a bug
report or at least submitting information about the crash? Have you seen
such a pop up and accepted sending the information?

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

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

Title:
  CUPS keeps crashing 17.04

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cupsd or cups-browser are systematically crashing at start-up. I tried to 
purge and reinstall cups without success. systemctrl status cups shows:
  cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: core-dump) since Sun 2017-07-16 16:58:10 CST; 45s 
ago
   Docs: man:cupsd(8)
Process: 14474 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=SEGV)
   Main PID: 14474 (code=dumped, signal=SEGV)

  Jul 16 16:58:10 my-desktop systemd[1]: Started CUPS Scheduler.
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Main process exited, 
code=dumped, status=11/SEGV
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Unit entered failed 
state.
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Failed with result 
'core-dump'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: cups 2.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 17:06:10 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-02 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=bf399cdf-9a52-46c0-9d61-daa2bc83cf2f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://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 1704288] Re: Ubuntu 16.04 VPN : DNS information leaking through dnsmasq

[Emmanuel Dupont]

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

Title:
  Ubuntu 16.04 VPN : DNS information leaking  through dnsmasq

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  After connecting the VPN 

  # killall -USR1 dnsmasq

  # tail syslog.log
  ...
  Jul 13 02:18:56 tp dnsmasq[1476]: time 1499905136
  Jul 13 02:18:56 tp dnsmasq[1476]: cache size 0, 0/0 cache insertions re-used 
unexpired cache entries.
  Jul 13 02:18:56 tp dnsmasq[1476]: queries forwarded 154, queries answered 
locally 1
  Jul 13 02:18:56 tp dnsmasq[1476]: queries for authoritative zones 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.1#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.2#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 192.168.0.254#53: queries sent 12, 
retried or failed 0   

  The first two name server are provided by the vpn connection. 
  The last 192.168.0.254 name server is running on my local router and forward 
request to my ISP (this is the default name server when VPN is not activated).

  When I query the DNS, queries are sent to each name server which makes
  a DNS information leaking to my ISP

  I validated that by the mean of tcpdump on eth and tun interfaces and
  also by using  that site: https://www.dnsleaktest.com/

  I tried to force the VPN  DNS server IPs in the VPN configuration (edit Vpn 
connection -> ipv4 - > Automatic Adresses only ..) but the result is the same. 
   
  dnsmasq must not have the local DNS present while VPN connection is 
established.

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

-- 
Mailing list: https://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 1635812] Re: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

[Vlad Orlov]

** No longer affects: poppler

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

Title:
  atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: atril 1.12.2-1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Sat Oct 22 09:43:08 2016
  ExecutablePath: /usr/bin/atril-thumbnailer
  InstallationDate: Installed on 2016-05-14 (160 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: atril-thumbnailer -s 128 
file:///home/username/Documents/jedi_complaint.pdf 
/tmp/.mate_desktop_thumbnail.8JDPPY
  SegvAnalysis:
   Segfault happened at: 0x7fdcb0258990 : mov
0x50(%rdi),%eax
   PC (0x7fdcb0258990) ok
   source "0x50(%rdi)" (0x0050) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: atril
  StacktraceTop:
   cmsGetColorSpace () from /usr/lib/x86_64-linux-gnu/liblcms2.so.2
   GfxICCBasedColorSpace::parse(Array*, OutputDev*, GfxState*, int) () from 
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
   GfxColorSpace::parse(GfxResources*, Object*, OutputDev*, GfxState*, int) () 
from /usr/lib/x86_64-linux-gnu/libpoppler.so.58
   Page::loadThumb(unsigned char**, int*, int*, int*) () from 
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
   poppler_page_get_thumbnail () from 
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
  Title: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark

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

-- 
Mailing list: https://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 1703350] Re: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configurac

[ALEXIS]

Sorry, after Windows 7

2017-07-17 16:18 GMT-03:00 Andreas Hasenack :

> Thanks for getting back to us and letting us know your system is working
> correctly again. I will leave this bug marked as incomplete because
> there is not enough data for us to act on a fix. If you come across more
> information on this issue, or if it happens again, please post back here
> and we can take another look. Otherwise, it will expire in due course
> and automatically close.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1703350
>
> Title:
>   package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
>   está en un estado grave de inconsistencia - debe reinstalarlo  antes
>   de intentar su configuración.
>
> Status in liburcu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   it crashes on sudo apt update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: liburcu4:i386 0.9.1-3
>   ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
>   Uname: Linux 4.4.0-83-generic i686
>   ApportVersion: 2.20.1-0ubuntu2.9
>   Architecture: i386
>   Date: Mon Jul 10 07:44:55 2017
>   Dependencies:
>gcc-6-base 6.0.1-0ubuntu1
>libc6 2.23-0ubuntu9
>libgcc1 1:6.0.1-0ubuntu1
>   ErrorMessage: El paquete está en un estado grave de inconsistencia -
> debe reinstalarlo  antes de intentar su configuración.
>   InstallationDate: Installed on 2017-05-20 (51 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
> (20160719)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.2
>apt  1.2.20
>   SourcePackage: liburcu
>   Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El
> paquete está en un estado grave de inconsistencia - debe reinstalarlo
> antes de intentar su configuración.
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/
> 1703350/+subscriptions
>

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in liburcu package in Ubuntu:
  Incomplete

Bug description:
  it crashes on sudo apt update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liburcu4:i386 0.9.1-3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  Date: Mon Jul 10 07:44:55 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-05-20 (51 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: liburcu
  Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1697375] Re: whoopsie's network-manager state querying is broken

[Brian Murray]

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

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

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

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

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

Title:
  whoopsie's network-manager state querying is broken

Status in whoopsie package in Ubuntu:
  In Progress
Status in whoopsie source package in Xenial:
  Triaged
Status in whoopsie source package in Zesty:
  Triaged
Status in whoopsie source package in Artful:
  In Progress

Bug description:
  [Impact]
  whoopsie's querying of network-manager's state is broken and this results in 
whoopsie only being able to detect if the system is on-line when network 
manager's state changes. Subsequently, if one manually restarts whoopsie then 
whoopsie will stay off-line until an n-m state change. This can result in 
crashes not being uploaded.  Additionally, whoopsie's systemd service file does 
not start after networking which is incorrect since it initially needs to query 
network-manager's state. (However, this ended up allowing crash reports to 
still be submitted because whoopsie would start first then the n-m's state 
would change and whoopsie would detect that.)

  [Test Case] (state detection failure)
  1) Manually restart the whoopsie service
  2) Observe the following two messages:
  "Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] Could not get the Network 
Manager state:
  Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property 'state'"

  with the version of network-manager from -proposed you will not see
  these messages when restarting whoopsie.

  [Test Case] (starting after network-manager0
  1) Boot your system
  2) Observe the following in syslog:
  "Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network 
Manager state:
  Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.NetworkManager was not provided by any .service files
  "

  with the version of network-manager in -proposed you will not see the
  "NetworkManager was not provided" messages.

  [Regression Potential]
  Its possible that systems that were not submitting crash reports suddenly 
will and that will use some network bandwidth and Error Tracker resources.

  - Original Description -
  
  On artful crash reports are not uploaded automatically (several .crash files 
in /var/crash and no corresponding upload or .uploaded files)

  ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: whoopsie 0.2.56
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 12 09:39:29 2017
  InstallationDate: Installed on 2013-09-03 (1377 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: apport-noui N/ASourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1697375] Re: whoopsie's network-manager state querying is broken

[Launchpad Bug Tracker]

** Branch linked: lp:whoopsie

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

Title:
  whoopsie's network-manager state querying is broken

Status in whoopsie package in Ubuntu:
  In Progress
Status in whoopsie source package in Xenial:
  Triaged
Status in whoopsie source package in Zesty:
  Triaged
Status in whoopsie source package in Artful:
  In Progress

Bug description:
  [Impact]
  whoopsie's querying of network-manager's state is broken and this results in 
whoopsie only being able to detect if the system is on-line when network 
manager's state changes. Subsequently, if one manually restarts whoopsie then 
whoopsie will stay off-line until an n-m state change. This can result in 
crashes not being uploaded.  Additionally, whoopsie's systemd service file does 
not start after networking which is incorrect since it initially needs to query 
network-manager's state. (However, this ended up allowing crash reports to 
still be submitted because whoopsie would start first then the n-m's state 
would change and whoopsie would detect that.)

  [Test Case] (state detection failure)
  1) Manually restart the whoopsie service
  2) Observe the following two messages:
  "Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] Could not get the Network 
Manager state:
  Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property 'state'"

  with the version of network-manager from -proposed you will not see
  these messages when restarting whoopsie.

  [Test Case] (starting after network-manager0
  1) Boot your system
  2) Observe the following in syslog:
  "Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network 
Manager state:
  Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.NetworkManager was not provided by any .service files
  "

  with the version of network-manager in -proposed you will not see the
  "NetworkManager was not provided" messages.

  [Regression Potential]
  Its possible that systems that were not submitting crash reports suddenly 
will and that will use some network bandwidth and Error Tracker resources.

  - Original Description -
  
  On artful crash reports are not uploaded automatically (several .crash files 
in /var/crash and no corresponding upload or .uploaded files)

  ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: whoopsie 0.2.56
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 12 09:39:29 2017
  InstallationDate: Installed on 2013-09-03 (1377 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: apport-noui N/ASourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1693900] Re: apt-get update should return exit code != 0 on error

[Julian Andres Klode]

I can only tell you that either python or C++ should give you what you
need at the moment. You could potentially just parse Err lines, but
that's a bit hacky. As you mentioned, the output changed a bit.

Our functions return booleans every in the stack, it's unclear how and
if we can change that to something else in the near future. I was
thinking more about specifying the goal you want (update something,
update all, etc.) and then failing if the goal is not reached.

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

-- 
Mailing list: https://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 1704572] Re: package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package libnl-route-3-200:amd64 is not ready for configuration cannot configur

[K.D.]

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

Title:
  package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
  install/upgrade: package libnl-route-3-200:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in libnl3 package in Ubuntu:
  Incomplete

Bug description:
  System update failed because this package could not be removed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Sat Jul 15 18:24:00 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   libnl-3-200 3.2.27-1ubuntu0.16.04.1
  DuplicateSignature:
   package:libnl-route-3-200:amd64:3.2.27-1ubuntu0.16.04.1
   Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
   dpkg: error processing package libnl-route-3-200:amd64 (--configure):
package libnl-route-3-200:amd64 is not ready for configuration
  ErrorMessage: package libnl-route-3-200:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-10-20 (267 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libnl3
  Title: package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: package libnl-route-3-200:amd64 is not ready for configuration 
 cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1703350] Re: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configurac

[ALEXIS]

Andreas, my english is very poor.
The problem happens before Window 7 checks the hard disck for
inconsistences and I stopped it.
Thank you for your help.

2017-07-17 16:18 GMT-03:00 Andreas Hasenack :

> Thanks for getting back to us and letting us know your system is working
> correctly again. I will leave this bug marked as incomplete because
> there is not enough data for us to act on a fix. If you come across more
> information on this issue, or if it happens again, please post back here
> and we can take another look. Otherwise, it will expire in due course
> and automatically close.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1703350
>
> Title:
>   package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
>   está en un estado grave de inconsistencia - debe reinstalarlo  antes
>   de intentar su configuración.
>
> Status in liburcu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   it crashes on sudo apt update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: liburcu4:i386 0.9.1-3
>   ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
>   Uname: Linux 4.4.0-83-generic i686
>   ApportVersion: 2.20.1-0ubuntu2.9
>   Architecture: i386
>   Date: Mon Jul 10 07:44:55 2017
>   Dependencies:
>gcc-6-base 6.0.1-0ubuntu1
>libc6 2.23-0ubuntu9
>libgcc1 1:6.0.1-0ubuntu1
>   ErrorMessage: El paquete está en un estado grave de inconsistencia -
> debe reinstalarlo  antes de intentar su configuración.
>   InstallationDate: Installed on 2017-05-20 (51 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
> (20160719)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.2
>apt  1.2.20
>   SourcePackage: liburcu
>   Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El
> paquete está en un estado grave de inconsistencia - debe reinstalarlo
> antes de intentar su configuración.
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/
> 1703350/+subscriptions
>

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in liburcu package in Ubuntu:
  Incomplete

Bug description:
  it crashes on sudo apt update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liburcu4:i386 0.9.1-3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  Date: Mon Jul 10 07:44:55 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-05-20 (51 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: liburcu
  Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1693900] Re: apt-get update should return exit code != 0 on error

[Jarno Suni]

juliank, Do you mean ppa-purge should be translated to completely
different programming language, and that I can not even rely on apt-get
outputting something that matches '^Err[ :]' to stdout in such cases?
Sounds difficult.

What do you mean by "Our results are boolean, we might not be able to
really influence the exit status." I do not understand why the "results"
could not be changed to be something else.

You say: "You don't want to prevent the system from being upgraded (in an 
update& type scenario) just because some third party repository 
disappeared."
Something like 
'apt-get update || [ $? -ne "$FATAL_APT_UPDATE_ERROR" ] && apt-get upgrade'
in command line would let upgrade happen even in case of partially successful 
update.

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

-- 
Mailing list: https://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 1697375] Re: crash reports are not uploaded automatically

[Brian Murray]

** Description changed:

- On artful crash reports are not uploaded automatically (several .crash
- files in /var/crash and no corresponding upload or .uploaded files)
+ [Impact]
+ whoopsie's querying of network-manager's state is broken and this results in 
whoopsie only being able to detect if the system is on-line when network 
manager's state changes. Subsequently, if one manually restarts whoopsie then 
whoopsie will stay off-line until an n-m state change. This can result in 
crashes not being uploaded.  Additionally, whoopsie's systemd service file does 
not start after networking which is incorrect since it initially needs to query 
network-manager's state. (However, this ended up allowing crash reports to 
still be submitted because whoopsie would start first then the n-m's state 
would change and whoopsie would detect that.)
  
- ProblemType: Bug
- DistroRelease: Ubuntu 17.10
+ [Test Case] (state detection failure)
+ 1) Manually restart the whoopsie service
+ 2) Observe the following two messages:
+ "Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] Could not get the Network 
Manager state:
+ Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property 'state'"
+ 
+ with the version of network-manager from -proposed you will not see
+ these messages when restarting whoopsie.
+ 
+ [Test Case] (starting after network-manager0
+ 1) Boot your system
+ 2) Observe the following in syslog:
+ "Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network 
Manager state:
+ Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.NetworkManager was not provided by any .service files
+ "
+ 
+ with the version of network-manager in -proposed you will not see the
+ "NetworkManager was not provided" messages.
+ 
+ [Regression Potential]
+ Its possible that systems that were not submitting crash reports suddenly 
will and that will use some network bandwidth and Error Tracker resources.
+ 
+ - Original Description -
+ 
+ On artful crash reports are not uploaded automatically (several .crash files 
in /var/crash and no corresponding upload or .uploaded files)
+ 
+ ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: whoopsie 0.2.56
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 12 09:39:29 2017
  InstallationDate: Installed on 2013-09-03 (1377 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
-  TERM=screen-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
- RelatedPackageVersions: apport-noui N/A
- SourcePackage: whoopsie
+  TERM=screen-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ RelatedPackageVersions: apport-noui N/ASourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- crash reports are not uploaded automatically
+ whoopsie's network-manager state querying is broken

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

Title:
  whoopsie's network-manager state querying is broken

Status in whoopsie package in Ubuntu:
  In Progress
Status in whoopsie source package in Xenial:
  New
Status in whoopsie source package in Zesty:
  New
Status in whoopsie source package in Artful:
  In Progress

Bug description:
  [Impact]
  whoopsie's querying of network-manager's state is broken and this results in 
whoopsie only being able to detect if the system is on-line when network 
manager's state changes. Subsequently, if one manually restarts whoopsie then 
whoopsie will stay off-line until an n-m state change. This can result in 
crashes not being uploaded.  Additionally, whoopsie's systemd service file does 
not start after networking which is incorrect since it initially needs to query 
network-manager's state. (However, this ended up allowing crash reports to 
still be submitted because whoopsie would start first then the n-m's state 
would change and whoopsie would detect that.)

  [Test Case] (state detection failure)
  1) Manually restart the whoopsie service
  2) Observe the following two messages:
  "Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] Could not get the Network 
Manager state:
  Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property 'state'"

  with the version of network-manager from -proposed you will not see
  these messages when restarting whoopsie.

  [Test Case] (starting after network-manager0
  1) Boot your system
  2) Observe the following in syslog:
  "Jul 17 06:46:47 speedy 

[Touch-packages] [Bug 1703350] Re: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración

[Andreas Hasenack]

Thanks for getting back to us and letting us know your system is working
correctly again. I will leave this bug marked as incomplete because
there is not enough data for us to act on a fix. If you come across more
information on this issue, or if it happens again, please post back here
and we can take another look. Otherwise, it will expire in due course
and automatically close.

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in liburcu package in Ubuntu:
  Incomplete

Bug description:
  it crashes on sudo apt update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liburcu4:i386 0.9.1-3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  Date: Mon Jul 10 07:44:55 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-05-20 (51 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: liburcu
  Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1704288] Re: Ubuntu 16.04 VPN : DNS information leaking through dnsmasq

[Andreas Hasenack]

What kind of vpn are you using, is it openvpn? How did you establish it,
was it via the network-manager plugin? Or do you manually bring up an
openvpn client? If it's some other vpn, could you clarify how it is used
please?

Thanks


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

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

Title:
  Ubuntu 16.04 VPN : DNS information leaking  through dnsmasq

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  After connecting the VPN 

  # killall -USR1 dnsmasq

  # tail syslog.log
  ...
  Jul 13 02:18:56 tp dnsmasq[1476]: time 1499905136
  Jul 13 02:18:56 tp dnsmasq[1476]: cache size 0, 0/0 cache insertions re-used 
unexpired cache entries.
  Jul 13 02:18:56 tp dnsmasq[1476]: queries forwarded 154, queries answered 
locally 1
  Jul 13 02:18:56 tp dnsmasq[1476]: queries for authoritative zones 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.1#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.2#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 192.168.0.254#53: queries sent 12, 
retried or failed 0   

  The first two name server are provided by the vpn connection. 
  The last 192.168.0.254 name server is running on my local router and forward 
request to my ISP (this is the default name server when VPN is not activated).

  When I query the DNS, queries are sent to each name server which makes
  a DNS information leaking to my ISP

  I validated that by the mean of tcpdump on eth and tun interfaces and
  also by using  that site: https://www.dnsleaktest.com/

  I tried to force the VPN  DNS server IPs in the VPN configuration (edit Vpn 
connection -> ipv4 - > Automatic Adresses only ..) but the result is the same. 
   
  dnsmasq must not have the local DNS present while VPN connection is 
established.

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

-- 
Mailing list: https://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 1704572] Re: package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package libnl-route-3-200:amd64 is not ready for configuration cannot configure (c

[Andreas Hasenack]

Thanks for filing this bug in Ubuntu.

Could you please try the following commands and see if they resolve the
problem:

sudo apt update
sudo apt install --reinstall libnl-route-3-200

If that doesn't sort it, then please try:

sudo apt -f install

And post back the results. Also, you say you were trying to remove a
package, but the logs don't show removals, could you please clarify
which command exactly failed, or what happened?

Thanks


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

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

Title:
  package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
  install/upgrade: package libnl-route-3-200:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in libnl3 package in Ubuntu:
  Incomplete

Bug description:
  System update failed because this package could not be removed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Sat Jul 15 18:24:00 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   libnl-3-200 3.2.27-1ubuntu0.16.04.1
  DuplicateSignature:
   package:libnl-route-3-200:amd64:3.2.27-1ubuntu0.16.04.1
   Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
   dpkg: error processing package libnl-route-3-200:amd64 (--configure):
package libnl-route-3-200:amd64 is not ready for configuration
  ErrorMessage: package libnl-route-3-200:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-10-20 (267 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libnl3
  Title: package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: package libnl-route-3-200:amd64 is not ready for configuration 
 cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1704803] Re: X11/XCB window resize is broken

[Hans Joachim Desserud]

** Tags added: patch

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

Title:
  X11/XCB window resize is broken

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  This is an upstream bug: https://bugreports.qt.io/browse/QTBUG-57608

  ---[quote]---
  As per the src; Qt assumes that all resize requests will succeed (and in 
turn, apparently, "proactively" resizes child windows for such requests; it's 
not clear if this is because of or even related to the noted issue; it may just 
be how Virtualbox commands Qt5 to behave in this case). This leads to very 
broken behavior and unusable applications where this assumption is invalid; for 
a library like Qt, it's never actually valid (as acknowledged by the FIXME: 
comment).

  This has most recently shown its face with the Virtualbox project, exposed by 
i3 and other window managers, though tiling window managers seem to make use of 
this protocol more than most. The Virtualbox bug report has some good details; 
the i3 report has good details on the compounding effects of such an issue.
  ---[end quote]---

  The attached patch is a backport of the upstream fix. I'm also
  currently maintaining a PPA including this patch:
  https://launchpad.net/~paulo-matias/+archive/ubuntu/qt5-tiling

  It would be nice if the patch was included in the official Ubuntu
  package.

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

-- 
Mailing list: https://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 1704747] Re: package libk5crypto3:amd64 1.15-1ubuntu0.1 failed to install/upgrade: a csomag nagyon rossz, következetlen állapotban van - újra kell telepítenie a beállítási kísér

[Andreas Hasenack]

Thanks for filing this bug in Ubuntu.

Could you please try the following commands and let us know if it fixes
the problem?

sudo apt update
sudo apt install --reinstall libk5crypto3


Thanks!


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

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

Title:
  package libk5crypto3:amd64 1.15-1ubuntu0.1 failed to install/upgrade:
  a csomag nagyon rossz, következetlen állapotban van - újra  kell
  telepítenie a beállítási kísérlet előtt

Status in krb5 package in Ubuntu:
  Incomplete

Bug description:
  I have no more info.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libk5crypto3:amd64 1.15-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jul  5 20:51:19 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
   libkrb5support0 1.15-1ubuntu0.1
  ErrorMessage: a csomag nagyon rossz, következetlen állapotban van - újra  
kell telepítenie a beállítási kísérlet előtt
  InstallationDate: Installed on 2017-05-31 (46 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: krb5
  Title: package libk5crypto3:amd64 1.15-1ubuntu0.1 failed to install/upgrade: 
a csomag nagyon rossz, következetlen állapotban van - újra  kell telepítenie a 
beállítási kísérlet előtt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1704831] Re: package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to install/upgrade: függőségi hibák - e csomag beállítatlan maradt

[Andreas Hasenack]

Thanks for filing this bug in Ubuntu.

Could you please try the following commands and see if they solve the
problem for you:

sudo apt update
sudo apt install --reinstall libgssapi-krb5-2 libk5crypto3


Thanks


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

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

Title:
  package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to
  install/upgrade: függőségi hibák - e csomag beállítatlan maradt

Status in krb5 package in Ubuntu:
  Incomplete

Bug description:
  No info

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libgssapi-krb5-2:amd64 1.15-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  Date: Mon Jul 17 20:08:51 2017
  ErrorMessage: függőségi hibák - e csomag beállítatlan maradt
  InstallationDate: Installed on 2017-05-31 (47 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to 
install/upgrade: függőségi hibák - e csomag beállítatlan maradt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1704843] [NEW] segfault processing very large input list

[Chris Drost]

Public bug reported:

The attached apport file was created from a segfault/core-dump observed
while using wget to try to audit a large number of websites to determine
which ones were online, which were redirects and where they redirected
to, etc.

The exact command-line attempts a considerable amount of obfuscation and
cares nothing at all for the files that are actually downloaded, which
are occasionally harvested for free space. The harvester did not run
anytime near this crash, though.

wget --tries=3 -i /path/to/getlist.txt -U 'Mozilla/5.0 (Windows NT 10.0;
Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115
Safari/537.36' --header="Accept:
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8"
--header="Accept-Encoding: gzip, deflate, br" --header="Accept-Language:
en-US,en;q=0.8" --header="Cache-Control: max-age=0" --header="Referer:
https://www.google.com/; -e robots=off --wait 0.5 --random-wait 2>&1 |
tee /path/to/logfile.txt

The getlist contained 144,551 URLs to process; this happened at the
44,417th URL. Wget successfully downloads the nearby URLs just fine now;
but here is the last several lines of logfile.txt:

- - - - - - - -

--2017-07-15 04:05:13--  http://urlshortener.actorsandcrew.com/
Resolving urlshortener.actorsandcrew.com (urlshortener.actorsandcrew.com)... 
64.13.228.85
Connecting to urlshortener.actorsandcrew.com 
(urlshortener.actorsandcrew.com)|64.13.228.85|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1515 (1.5K) [text/html]
Saving to: ‘index.html.4732’

 0K . 100%
127M=0s

2017-07-15 04:05:19 (127 MB/s) - ‘index.html.4732’ saved [1515/1515]

--2017-07-15 04:05:19--  http://varganess.soclog.se/p
Resolving varganess.soclog.se (varganess.soclog.se)... 83.140.155.4
Connecting to varganess.soclog.se (varganess.soclog.se)|83.140.155.4|:80... 
connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Cookie coming from varganess.soclog.se attempted to set domain to 
bilddagboken.se
Cookie coming from varganess.soclog.se attempted to set domain to 
bilddagboken.se
Cookie coming from varganess.soclog.se attempted to set domain to 
bilddagboken.se
Location: http://dayviews.com [following]
--2017-07-15 04:05:25--  http://dayviews.com/
Connecting to dayviews.com (dayviews.com)|83.140.155.40|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘p’

 0K .. 
115K=0.2s

2017-07-15 04:05:26 (115 KB/s) - ‘p’ saved [19057]

- - - - - - - -

The next site up for audit after this saved event was emitted was
http://drivingrevenue.com/ , which also downloads just fine when I run
it as a one-off.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: wget 1.17.1-1ubuntu1.2
ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
Uname: Linux 4.4.0-75-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
Date: Mon Jul 17 12:40:33 2017
InstallationDate: Installed on 2014-06-23 (1120 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
ProcEnviron:
 LC_CTYPE=en_US.UTF-8
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: wget
UpgradeStatus: Upgraded to xenial on 2016-05-05 (437 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  segfault processing very large input list

Status in wget package in Ubuntu:
  New

Bug description:
  The attached apport file was created from a segfault/core-dump
  observed while using wget to try to audit a large number of websites
  to determine which ones were online, which were redirects and where
  they redirected to, etc.

  The exact command-line attempts a considerable amount of obfuscation
  and cares nothing at all for the files that are actually downloaded,
  which are occasionally harvested for free space. The harvester did not
  run anytime near this crash, though.

  wget --tries=3 -i /path/to/getlist.txt -U 'Mozilla/5.0 (Windows NT
  10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko)
  Chrome/59.0.3071.115 Safari/537.36' --header="Accept:
  
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8"
  --header="Accept-Encoding: gzip, deflate, br" --header="Accept-
  Language: en-US,en;q=0.8" --header="Cache-Control: max-age=0"
  --header="Referer: https://www.google.com/; -e robots=off --wait 0.5
  --random-wait 2>&1 | tee /path/to/logfile.txt

  The getlist contained 144,551 URLs to process; this happened at the
  44,417th URL. Wget successfully downloads the nearby URLs just fine
  now; but here is the last several lines of logfile.txt:

  - - - - - - - -

  

[Touch-packages] [Bug 1436168] Re: systemd-journald crashed with SIGABRT in journal_file_move_to_object()

[mxyzptlk]

This bug was marked as invalid, but I get the error about every other
day. Is there any info I can provide to help verify the bug?

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

Title:
  systemd-journald crashed with SIGABRT in journal_file_move_to_object()

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Crashed over night while recovering backup.

  .

  Xubuntu 15.04 beta1

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu9
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  Date: Tue Mar 24 23:13:27 2015
  ExecutablePath: /lib/systemd/systemd-journald
  ExecutableTimestamp: 1427124595
  InstallationDate: Installed on 2015-03-23 (1 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H
  ProcCmdline: /lib/systemd/systemd-journald
  ProcCwd: /
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=45370e47-0377-4e9d-87fc-81889c091532 ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-journald crashed with SIGABRT
  UpgradeStatus: Upgraded to vivid on 2015-03-24 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 07/08/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7c
  dmi.board.name: GA-MA790GP-UD4H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790GP-UD4H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://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 1702898] Re: package linux-image-extra-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-extra-4.10.0-26-generic 4.10.0-26.30 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-extra-4.10.0-26-generic 4.10.0-26.30
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1452 F pulseaudio
morgan 4306 F pulseaudio
  Date: Sun Jul  2 13:10:33 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=317b6f78-3fd8-4c3c-ac48-0a26d1a42deb
  InstallationDate: Installed on 2016-04-24 (438 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:053a Acer, Inc 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LNV L40-30
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed 
root=UUID=14ac0fee-0d5e-48e8-910c-52b05a0a307d ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.10.0-26-generic 4.10.0-26.30 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to zesty on 2017-06-16 (20 days ago)
  dmi.bios.date: 02/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.vendor: LNV
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: LNV
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd02/28/2015:svnLNV:pnL40-30:pvr1.02:rvnLNV:rn:rvrTobefilledbyO.E.M.:cvnLNV:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: L40-30
  dmi.product.version: 1.02
  dmi.sys.vendor: LNV

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

-- 
Mailing list: https://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 1697375] Re: crash reports are not uploaded automatically

[Brian Murray]

Testing this on Ubuntu 16.04 and Ubuntu 17.04 I've discovered that the
'state' property is also not available, so this will need to be SRU'ed
to both releases.

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

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

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

Title:
  crash reports are not uploaded automatically

Status in whoopsie package in Ubuntu:
  In Progress
Status in whoopsie source package in Xenial:
  New
Status in whoopsie source package in Zesty:
  New
Status in whoopsie source package in Artful:
  In Progress

Bug description:
  On artful crash reports are not uploaded automatically (several .crash
  files in /var/crash and no corresponding upload or .uploaded files)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: whoopsie 0.2.56
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 12 09:39:29 2017
  InstallationDate: Installed on 2013-09-03 (1377 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1693900] Re: apt-get update should return exit code != 0 on error

[Julian Andres Klode]

That's your opinion, and we already know it.

Whether we want to do it that or if it is technically feasible are
different questions. Fact is: Our results are boolean, we might not be
able to really influence the exit status.

I don't want to discuss this with you, I was just giving jarnos a hint
how ppa-purge could possibly be fixed.

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

-- 
Mailing list: https://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 1704831] [NEW] package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to install/upgrade: függőségi hibák - e csomag beállítatlan maradt

[Albert Dezso]

Public bug reported:

No info

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libgssapi-krb5-2:amd64 1.15-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: amd64
Date: Mon Jul 17 20:08:51 2017
ErrorMessage: függőségi hibák - e csomag beállítatlan maradt
InstallationDate: Installed on 2017-05-31 (47 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: krb5
Title: package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to 
install/upgrade: függőségi hibák - e csomag beállítatlan maradt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to
  install/upgrade: függőségi hibák - e csomag beállítatlan maradt

Status in krb5 package in Ubuntu:
  New

Bug description:
  No info

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libgssapi-krb5-2:amd64 1.15-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  Date: Mon Jul 17 20:08:51 2017
  ErrorMessage: függőségi hibák - e csomag beállítatlan maradt
  InstallationDate: Installed on 2017-05-31 (47 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:amd64 1.15-1ubuntu0.1 failed to 
install/upgrade: függőségi hibák - e csomag beállítatlan maradt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1315659] Re: Some widget have black background

[quequotion]

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

** This bug is no longer a duplicate of bug 1367764
   Themes using overlay scrollbars have to set explicitly set backgrounds on 
all scrollable widgets
** This bug has been marked a duplicate of bug 1167079
   GtkScrolledWindow widgets (GTK3) have black or transparent  backgrounds with 
Ayatana overlay-scrollbar

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

Title:
  Some widget have black background

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  You can see the problem in Glade when opening the Menu Editor > Hierarchy tab.
  I am using the default Ambiance theme and the Faenza icon set.

  Overlay scrollbars are on on my system.
  When starting an app from MonoDevelop which disables overlay scrollbars there 
is no issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-themes 14.04+14.04.20140410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  3 14:11:03 2014
  InstallationDate: Installed on 2014-04-18 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1576341] Re: systemd in degraded state on startup in LXD containers

[Christian Reis]

And added a snapd task based on Nish's last comment.

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in nfs-utils package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  Fix Committed
Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1576341] Re: systemd in degraded state on startup in LXD containers

[Christian Reis]

I've also noticed that nfs-common triggers a failure:

root@sendmail:~# systemctl --failed
  UNIT   LOAD   ACTIVE SUBDESCRIPTION
● run-rpc_pipefs.mount   loaded failed failed RPC Pipe File System
● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File 
Systems
● lvm2-lvmetad.socketloaded failed failed LVM2 metadata daemon socket

So I've added a task for nfs-common. The remaining failures I believe
have been handled by this bug and are just unfixed in Xenial (and will
likely remain unfixed right?)

** Also affects: nfs-utils (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in nfs-utils package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  Fix Committed
Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1693900] Re: apt-get update should return exit code != 0 on error

[Jens Elkner]

Actually this is the problem: Users think, their system is up-to-date,
but it is not for sure because a site failed to respond. Therefore only
if _all_ sites answered the request properly, apt-get should return 0.
If not, it should return a specified return code, which lets the callee
know, that there was a problem [and imply, that a subsequent apt-get
upgrade might bring the system to the latest supported state, or not].
If the exit code for such situations is documented properly, the tool
can still decide, whether to run the upgrade or would be bredless art.

BTW: It doesn't really matter, what error (whether temp. DNS, LDAP
lookup, network, etc.) prevented a successful update. Fact is, that
there was an error and this needs to be communicated. CLI tools do that
via exit code.

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

-- 
Mailing list: https://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 1704825] [NEW] package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: el paquete bsdutils no está listo para configurarse no se puede configurar (estado actual `half-inst

[Raymundo Suárez vidaur]

Public bug reported:

Idon't know, it just happened at the star of the system.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: bsdutils 1:2.29-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Tue Jul 11 22:46:10 2017
DpkgTerminalLog:
 dpkg: error al procesar el paquete bsdutils (--configure):
  el paquete bsdutils no está listo para configurarse
  no se puede configurar (estado actual `half-installed')
ErrorMessage: el paquete bsdutils no está listo para configurarse  no se puede 
configurar (estado actual `half-installed')
InstallationDate: Installed on 2017-03-08 (130 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: util-linux
Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: el paquete 
bsdutils no está listo para configurarse  no se puede configurar (estado actual 
`half-installed')
UpgradeStatus: Upgraded to zesty on 2017-05-02 (76 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: el
  paquete bsdutils no está listo para configurarse  no se puede
  configurar (estado actual `half-installed')

Status in util-linux package in Ubuntu:
  New

Bug description:
  Idon't know, it just happened at the star of the system.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Tue Jul 11 22:46:10 2017
  DpkgTerminalLog:
   dpkg: error al procesar el paquete bsdutils (--configure):
el paquete bsdutils no está listo para configurarse
no se puede configurar (estado actual `half-installed')
  ErrorMessage: el paquete bsdutils no está listo para configurarse  no se 
puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2017-03-08 (130 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: el 
paquete bsdutils no está listo para configurarse  no se puede configurar 
(estado actual `half-installed')
  UpgradeStatus: Upgraded to zesty on 2017-05-02 (76 days ago)

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

-- 
Mailing list: https://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 1673860] Re: systemd-resolved unit should run Before=network-online.target

[Dimitri John Ledkov]

systemd (229-4ubuntu19) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generate warnings in the journal. (LP: #1704677)

systemd (229-4ubuntu18) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if resolved
is going to be started, make sure this blocks network-online.target.
(LP: #1673860)
  * networkd: cherry-pick support for setting bridge port's priority
(LP: #1668347)
  * Cherrypick upstream commit to enable system use kernel maximum limit for
RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
  * Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)
  * resolved: fix null pointer dereference crash (LP: #1621396)
  * Cherrypick core/timer downgrade message about random time addition
(LP: #1692136)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved (LP: #1695546)
- CVE-2017-9445
  * Cherry-pick subset of patches to introduce infinity value in logind.conf
for UserTasksMax (LP: #1651518)

Date: Mon, 17 Jul 2017 17:00:42 +0100
Changed-By: Dimitri John Ledkov 
Maintainer: Ubuntu Developers 
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19

==

 OK: systemd_229.orig.tar.gz
 OK: systemd_229-4ubuntu19.debian.tar.xz
 OK: systemd_229-4ubuntu19.dsc
 -> Component: main Section: admin

Upload Warnings:
Redirecting ubuntu xenial to ubuntu xenial-proposed.
This upload awaits approval by a distro manager


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

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

Title:
  systemd-resolved unit should run Before=network-online.target

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

Bug description:
  === Begin SRU Template ===
  [Impact]

  For releases using systemd-resolved (yakkety and zesty); the unit
  configuration does not require that the service be active before
  allowing systemd to reach 'network-online.target' which is a special
  target used to allow other units which require networking access to
  run.  

  In some cases, units which run After=network-online.target may
  encounter DNS failures if systemd-resolved is not yet completely
  active.

  The fix is to add Before=network-online.target to the Unit directives
  for systemd-resolved.service.

  [Test Case]

  1. lxc launch ubuntu-daily:yakkety y1
  2. lxc exec y1 -- journalctl -o short-precise \
 --unit systemd-resolved --unit network-online.target

  3. Check order of units;  If 'Reached target Network is Online' is
 listed before 'Started Network Name Resolution', then DNS may not
 be up.

  Example FAIL output:

  # apt-cache policy systemd
  systemd:
Installed: 231-9ubuntu3
Candidate: 231-9ubuntu3
Version table:
   *** 231-9ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   231-9git1 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages

  # journalctl -o short-precise -u systemd-resolved -u network-online.target 
  -- Logs begin at Thu 2017-03-23 21:22:42 UTC, end at Thu 2017-03-23 21:22:49 
UTC. --
  Mar 23 21:22:47.173454 y1 systemd[1]: Reached target Network is Online.
  Mar 23 21:22:47.197566 y1 systemd[1]: systemd-resolved.service: Failed to 
reset devices.list: Operation not permitted
  Mar 23 21:22:47.198023 y1 systemd[1]: Starting Network Name Resolution...
  Mar 23 21:22:47.207216 y1 systemd-resolved[438]: Positive Trust Anchors:
  Mar 23 21:22:47.207265 y1 systemd-resolved[438]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde3
  Mar 23 21:22:47.207319 y1 systemd-resolved[438]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-add
  Mar 23 21:22:47.216370 y1 systemd-resolved[438]: Using system hostname 'y1'.
  Mar 23 21:22:47.237441 y1 systemd-resolved[438]: Switching to system DNS 
server 10.245.119.1.
  Mar 23 21:22:47.399614 y1 systemd[1]: Started Network Name Resolution.

  
  Example PASS output:
  # journalctl -o short-precise -u systemd-resolved -u network-online.target 
  -- Logs begin at Thu 2017-03-23 21:25:08 UTC, end at Thu 2017-03-23 21:25:11 
UTC. --
  Mar 23 21:25:10.206276 y1 systemd[1]: systemd-resolved.service: Failed to 
reset devices.list: Operation not permitted
  Mar 23 21:25:10.206685 y1 systemd[1]: Starting Network Name Resolution...
  Mar 23 21:25:10.229430 y1 systemd-resolved[445]: Positive Trust Anchors:
  Mar 23 21:25:10.229449 y1 systemd-resolved[445]: . IN DS 19036 8 2 

[Touch-packages] [Bug 1704677] Re: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*=

[Dimitri John Ledkov]

systemd (229-4ubuntu19) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generate warnings in the journal. (LP: #1704677)

systemd (229-4ubuntu18) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if resolved
is going to be started, make sure this blocks network-online.target.
(LP: #1673860)
  * networkd: cherry-pick support for setting bridge port's priority
(LP: #1668347)
  * Cherrypick upstream commit to enable system use kernel maximum limit for
RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
  * Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)
  * resolved: fix null pointer dereference crash (LP: #1621396)
  * Cherrypick core/timer downgrade message about random time addition
(LP: #1692136)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved (LP: #1695546)
- CVE-2017-9445
  * Cherry-pick subset of patches to introduce infinity value in logind.conf
for UserTasksMax (LP: #1651518)

Date: Mon, 17 Jul 2017 17:00:42 +0100
Changed-By: Dimitri John Ledkov 
Maintainer: Ubuntu Developers 
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19

==

 OK: systemd_229.orig.tar.gz
 OK: systemd_229-4ubuntu19.debian.tar.xz
 OK: systemd_229-4ubuntu19.dsc
 -> Component: main Section: admin

Upload Warnings:
Redirecting ubuntu xenial to ubuntu xenial-proposed.
This upload awaits approval by a distro manager


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

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

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

** Changed in: systemd (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.3

** Description changed:

- The systemd version 229-4ubuntu18 from xenial-proposed archive has a
- bug. The '+' prefix (see
- https://www.freedesktop.org/software/systemd/man/systemd.service.html)
- in ExecStart*= and ExecStop*= statements does not work any longer.
+ [Impact]
+ 229-4ubuntu18 included changes irrelevant for xenial, which whilst harmless 
generates a lot of scary journal entries.
+ 
+ [Fix]
+ Drop the cherrypciked ExecStart|StopPost stanzas from the drop in snippet. 
Integration of the resolved stub resolver with resolvconf on xenial is not 
required, because resolved in xenial does not have stub resolver. Also xenial's 
systemd does not support '+' prefix on the Exec* lines.
+ 
+ [Testcase]
+ Upgrade to te new SRU, make sure testcase from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673860 still passes
+ 
+ Check that there is no extra journal warnings/errors about "Executable
+ path is not absolute" from systemd reading /lib/systemd/system/systemd-
+ resolved.service.d/resolvconf.con
+ 
+ [Original Descrption]
+ 
+ 
+ The systemd version 229-4ubuntu18 from xenial-proposed archive has a bug. The 
'+' prefix (see 
https://www.freedesktop.org/software/systemd/man/systemd.service.html) in 
ExecStart*= and ExecStop*= statements does not work any longer.
  
  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':
  
  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target
  
  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'
  
  Those two statements in section [Service] lead to the following two
  error messages in dmesg:
  
  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
- --- 
+ ---
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  

[Touch-packages] [Bug 1429427] Re: Unexplainable time jumps in CRON

[Eric Desrochers]

[ STS SPONSOR REVIEW ]

@Seyeong,

According to your dediff you are only cherry-picking "7a2e247 bugfix:
plug a memleak in imuxsock".

This commit has been introduced upstream starting with
"v7.6.3-158-g7a2e247", thus it seems like this bug is only affecting
Trusty as you previously mentioned.

According to package version Xenial/Zesty and Artful already have the
fix as they are > than "v7.6.3".

# Ubuntu
 rsyslog | 7.4.4-1ubuntu2.6 | trusty-updates   | source, amd64, arm64, armhf, 
i386, powerpc, ppc64el
 rsyslog | 7.4.4-1ubuntu14  | vivid| source, amd64, arm64, armhf, 
i386, powerpc, ppc64el
 rsyslog | 8.16.0-1ubuntu3  | xenial   | source, amd64, arm64, armhf, 
i386, powerpc, ppc64el, s390x
 rsyslog | 8.16.0-1ubuntu5  | yakkety  | source, amd64, arm64, armhf, 
i386, powerpc, ppc64el, s390x
 rsyslog | 8.16.0-1ubuntu5  | zesty| source, amd64, arm64, armhf, 
i386, ppc64el, s390x
 rsyslog | 8.16.0-1ubuntu5  | artful   | source, amd64, arm64, armhf, 
i386, ppc64el, s390x

and also aleady in Debian :

# Debian
 rsyslog| 8.24.0-1| stable | source, amd64, arm64, 
armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
 rsyslog| 8.28.0-1| testing| source, amd64, arm64, 
armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
 rsyslog| 8.28.0-1| unstable   | source, amd64, arm64, 
armel, armhf, i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
 rsyslog| 8.28.0-1| unstable-debug | source


Looking at the upstream project I see 3 commits as follow for the same subject 
: "bugfix: plug a memleak in imuxsock"

$ git log --oneline --grep="plug a memleak in imuxsock"
be45099 bugfix: plug a memleak in imuxsock

#git describe be45099
v7.6.3-159-gbe45099

7a2e247 bugfix: plug a memleak in imuxsock

# git describe 7a2e247
v7.6.3-158-g7a2e247

5a11a1d bugfix: plug a memleak in imuxsock

# git describe 5a11a1d
v7.6.3-119-g5a11a1d


Does the other commits are needed to have a sane rsyslog package ?

I just want to double-check with you that we are not missing anything
before uploading this package in the upload queue.

- Eric

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

Title:
  Unexplainable time jumps in CRON

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Trusty:
  New

Bug description:
  [Impact]

  on Trusty

  logging to syslog via cron causes timestamp abnormals after several
  hours.

  [Test Case]

  1. run below first,
  while true ; do logger "hello syslog" ; sleep 1; done

  2. register below script to crontab
  for i in {1..100} ; do logger "hello syslog via cron" ; sleep 1; done

  3. monitor syslog with below script
  tail -f -n 100 /var/log/syslog

  You can see weird timestamp in several hours.

  [Regression Potential]

  it's ratelimiting turn off code, could be issue with being off rate-
  limit

  [Other Info]

  below commit fixes this issue in my test

  From 7a2e2473476d2b10a775affd9ac6c62b81c450e5 Mon Sep 17 00:00:00 2001
  From: Tomas Heinrich 
  Date: Thu, 24 Jul 2014 13:47:14 +0200
  Subject: [PATCH 1/1] bugfix: plug a memleak in imuxsock

  The hash table for the system socket was allocated twice. The other
  one being in activateListeners().

  This commit practically reverts: 34a77cde2423303da72ab773128a2ddcf41
  The issue seems to be that the hash table is not initialized (to NULL)
  rather then not being allocated.

  #
  ## old description

  On my main server I see unexplainable time jumps backwards in the syslog. 
Those jumps affect CRON.
  Example:

  Feb 10 06:48:01 nostromo CRON[20351]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:49:01 nostromo CRON[20364]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20386]: (root) CMD (
/storage/exec/status-nostromo.sh >/dev/null 2>&1)
  Feb  7 05:40:01 nostromo CRON[20389]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20390]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20391]: (root) CMD (
/storage/exec/checkip.sh 2>/dev/null 1>/dev/null)

  For debugging I did the following:
  Start xclock and watch xclock and tail -f /var/log/syslog in parallel. When 
CRON logged a wrong time, xclock did NOT show any time jump but seemed to 
freeze for a fraction of a second.
  Open a screen and start a script that will once per second read the time (in 
unix seconds) and compare the read time with the time read a second ago. If the 
current time was smaller, the script would send an email with a process list 
from before and after the 

[Touch-packages] [Bug 1704815] [NEW] package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln bin/ls bin/mkdir b

[Herbert Bickmeier]

Public bug reported:

Tried to update Thunderbird

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod 
bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln 
bin/ls bin/mkdir bin/mknod bin/mktemp bin/mv bin/pwd bin/readlink bin/rm 
bin/rmdir bin/sleep bin/stty bin/sync bin/touch bin/true bin/uname bin/vdir 
usr/share/man/man1/id.1.gz usr/share/man/man1/pinky.1.gz 
usr/share/man/man1/printenv.1.gz usr/share/man/man1/sha1sum.1.gz 
usr/share/man/man8/chroot.8.gz]
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Mon Jul 17 17:44:14 2017
DpkgTerminalLog:
 dpkg: error processing package coreutils (--configure):
  package coreutils is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package coreutils is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2016-10-01 (289 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: coreutils
Title: package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod 
bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln 
bin/ls bin/mkdir bin/mknod bin/mktemp bin/mv bin/pwd bin/readlink bin/rm 
bin/rmdir bin/sleep bin/stty bin/sync bin/touch bin/true bin/uname bin/vdir 
usr/share/man/man1/id.1.gz usr/share/man/man1/pinky.1.gz 
usr/share/man/man1/printenv.1.gz usr/share/man/man1/sha1sum.1.gz 
usr/share/man/man8/chroot.8.gz] failed to install/upgrade: package coreutils is 
not ready for configuration  cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod
  bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false
  bin/ln bin/ls bin/mkdir bin/mknod bin/mktemp bin/mv bin/pwd
  bin/readlink bin/rm bin/rmdir bin/sleep bin/stty bin/sync bin/touch
  bin/true bin/uname bin/vdir usr/share/man/man1/id.1.gz
  usr/share/man/man1/pinky.1.gz usr/share/man/man1/printenv.1.gz
  usr/share/man/man1/sha1sum.1.gz usr/share/man/man8/chroot.8.gz] failed
  to install/upgrade: package coreutils is not ready for configuration
  cannot configure (current status 'half-installed')

Status in coreutils package in Ubuntu:
  New

Bug description:
  Tried to update Thunderbird

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod 
bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln 
bin/ls bin/mkdir bin/mknod bin/mktemp bin/mv bin/pwd bin/readlink bin/rm 
bin/rmdir bin/sleep bin/stty bin/sync bin/touch bin/true bin/uname bin/vdir 
usr/share/man/man1/id.1.gz usr/share/man/man1/pinky.1.gz 
usr/share/man/man1/printenv.1.gz usr/share/man/man1/sha1sum.1.gz 
usr/share/man/man8/chroot.8.gz]
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Mon Jul 17 17:44:14 2017
  DpkgTerminalLog:
   dpkg: error processing package coreutils (--configure):
package coreutils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package coreutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-10-01 (289 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: coreutils
  Title: package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod 
bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln 
bin/ls bin/mkdir bin/mknod bin/mktemp bin/mv bin/pwd bin/readlink bin/rm 
bin/rmdir bin/sleep bin/stty bin/sync bin/touch bin/true bin/uname bin/vdir 
usr/share/man/man1/id.1.gz usr/share/man/man1/pinky.1.gz 
usr/share/man/man1/printenv.1.gz usr/share/man/man1/sha1sum.1.gz 
usr/share/man/man8/chroot.8.gz] failed to install/upgrade: package coreutils is 
not ready for configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

[Carlo Lobrano]

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Carlo Lobrano (c-lobrano)

** Changed in: ubuntu-themes
 Assignee: (unassigned) => Carlo Lobrano (c-lobrano)

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

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

-- 
Mailing list: https://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 1704807] [NEW] output doesn't switch automatically to BT speaker when available

[Jean-Baptiste Lallement]

Public bug reported:

artful desktop

Test Case.
1. Pair a BT Speaker and set the output channel to the speaker
2. Play something with vlc or totem (and make sure it uses the speaker with 
pavucontrol for instance)
3. Switch the output to another channel eg internal speaker and turn the BT 
speaker off (do not close the music player)
4. Turn the speaker back on and wait until it connects
5. If the speaker is not selected automatically as the output, select it in the 
sound settings
6. Resume playing in VLC

Expected result
The track plays on the speaker

Actual result
It plays on the internal audio.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jul 17 17:09:17 2017
InstallationDate: Installed on 2013-09-03 (1412 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32VD.214
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32VD
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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX32VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug artful

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

Title:
  output doesn't switch automatically to BT speaker when available

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  artful desktop

  Test Case.
  1. Pair a BT Speaker and set the output channel to the speaker
  2. Play something with vlc or totem (and make sure it uses the speaker with 
pavucontrol for instance)
  3. Switch the output to another channel eg internal speaker and turn the BT 
speaker off (do not close the music player)
  4. Turn the speaker back on and wait until it connects
  5. If the speaker is not selected automatically as the output, select it in 
the sound settings
  6. Resume playing in VLC

  Expected result
  The track plays on the speaker

  Actual result
  It plays on the internal audio.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 17 17:09:17 2017
  InstallationDate: Installed on 2013-09-03 (1412 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/pulseaudio/+bug/1704807/+subscriptions

-- 
Mailing list: https://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 1673817] Re: update-secure-boot-policy behaving badly with unattended-upgrades

[Steve Langasek]

Hello Jeremy, or anyone else affected,

Accepted shim-signed into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.32~14.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

** Changed in: shim-signed (Ubuntu Trusty)
   Status: New => Fix Committed

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

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

Title:
  update-secure-boot-policy behaving badly with unattended-upgrades

Status in shim-signed package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in shim-signed source package in Trusty:
  Fix Committed
Status in unattended-upgrades source package in Trusty:
  Invalid
Status in shim-signed source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Invalid
Status in shim-signed source package in Yakkety:
  Fix Released
Status in unattended-upgrades source package in Yakkety:
  Invalid

Bug description:
  [Impact]
  Any user with unattended upgrades enabled and DKMS packages in a Secure Boot 
environment might be prompted to change Secure Boot policy, which will fail and 
crash in unattended-upgrades.

  [Test case]
  = unattended upgrade =
  1) Create /var/lib/dkms/TEST-DKMS
  2) Install new package
  3) Trigger unattended-upgrades: unattended-upgrades -d

  Upgrade should run smoothly for all the processing but fail to
  complete; shim-signed should end the unattended upgrade with a error
  as unattended change of the Secure Boot policy can not be done.
  Upgrade should not hang in high CPU usage.

  = standard upgrade =
  1) Create /var/lib/dkms/TEST-DKMS
  2) install new package.
  3) Verify that the upgrade completes normally. 

  
  [Regression Potential]
  Any failure to prompt for or change Secure Boot policy in mokutil while in an 
*attended* upgrade scenario would constitute a regression of this SRU.

  Any other issues related to booting in Secure Boot mode should instead
  be directed to bug 1637290 (shim update).

  ---

  Currently, unattended-upgrades will automatically install all updates
  for those running development releases of Ubuntu (LP: #1649709)

  Today, my computer was acting very sluggish. Looking at my process
  list, I saw/ usr/sbin/update-secureboot-policy was using a log of CPU.

  I killed the process. I have a /var/crash/shim-signed.0.crash but
  since it's 750 MB, I didn't bother submitting it or looking at it
  more. Maybe it crashed because I killed the process. Also, I see that
  unattended-upgrades-dpkg.log is 722 MB.

  Today's update included both VirtualBox and the linux kernel.

  I am attaching an excerpt of /var/log/unattended-upgrades/unattended-
  upgrades-dpkg.log

  This message was repeated a very large number of times (but I only
  included it once in the attachment:

  "Invalid password

  The Secure Boot key you've entered is not valid. The password used must be
  between 8 and 16 characters."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: shim-signed 1.23+0.9+1474479173.6c180c6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 17 11:15:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-23 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  SourcePackage: shim-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1704805] [NEW] All titlebars are corrupt

[Barry Warsaw]

Public bug reported:

After today's artful dist-ugprade, all titlebars are corrupted.  The
fonts show only squares.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Jul 17 10:49:00 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2016-11-07 (251 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161107)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=ec4bce78-74fa-43dc-af9e-b26a9a2d562a ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz 1:0.9.13.1+17.10.20170704-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.81-2
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Dec 13 11:21:08 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVMware VMware Virtual USB Mouse MOUSE, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputVirtualPS/2 VMware VMMouse MOUSE, id 9
 inputVirtualPS/2 VMware VMMouse MOUSE, id 10
xserver.errors: No surface to present from.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: OutputVirtual2 
   Virtual3Virtual4Virtual5Virtual6Virtual7 
   Virtual8
xserver.version: 2:1.18.4-1ubuntu7
xserver.video_driver: vmware

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


** Tags: amd64 apport-bug artful corruption regression single-occurrence 
third-party-packages ubuntu

** Attachment added: "titlebars.png"
   
https://bugs.launchpad.net/bugs/1704805/+attachment/4916193/+files/titlebars.png

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

Title:
  All titlebars are corrupt

Status in xorg package in Ubuntu:
  New

Bug description:
  After today's artful dist-ugprade, all titlebars are corrupted.  The
  fonts show only squares.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Jul 17 10:49:00 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2016-11-07 (251 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161107)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 

[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error

[Julian Andres Klode]

No, there are two different use cases here:

1. Did apt-get update (potentially) change something?
2. Did apt-get update (potentially) change everything?

In the general case, 1 is what you need to know. For example, a tool
that runs update and then upgrades your system: You don't want to
prevent the system from being upgraded (in an update& type
scenario) just because some third party repository disappeared.

Then there is the question of fatal vs non-fatal errors. A DNS
resolution error like here is most likely temporary, you don't want to
fail update because of it, this would just confuse users (don't spam me
twice a day with errors just because my machine is offline).

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

-- 
Mailing list: https://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 1704803] [NEW] X11/XCB window resize is broken

[Paulo Matias]

Public bug reported:

This is an upstream bug: https://bugreports.qt.io/browse/QTBUG-57608

---[quote]---
As per the src; Qt assumes that all resize requests will succeed (and in turn, 
apparently, "proactively" resizes child windows for such requests; it's not 
clear if this is because of or even related to the noted issue; it may just be 
how Virtualbox commands Qt5 to behave in this case). This leads to very broken 
behavior and unusable applications where this assumption is invalid; for a 
library like Qt, it's never actually valid (as acknowledged by the FIXME: 
comment).

This has most recently shown its face with the Virtualbox project, exposed by 
i3 and other window managers, though tiling window managers seem to make use of 
this protocol more than most. The Virtualbox bug report has some good details; 
the i3 report has good details on the compounding effects of such an issue.
---[end quote]---

The attached patch is a backport of the upstream fix. I'm also currently
maintaining a PPA including this patch: https://launchpad.net/~paulo-
matias/+archive/ubuntu/qt5-tiling

It would be nice if the patch was included in the official Ubuntu
package.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: patch-accepted-upstream

** Patch added: "Backport of upstream fix"
   
https://bugs.launchpad.net/bugs/1704803/+attachment/4916192/+files/QTBUG-57608.diff

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

Title:
  X11/XCB window resize is broken

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  This is an upstream bug: https://bugreports.qt.io/browse/QTBUG-57608

  ---[quote]---
  As per the src; Qt assumes that all resize requests will succeed (and in 
turn, apparently, "proactively" resizes child windows for such requests; it's 
not clear if this is because of or even related to the noted issue; it may just 
be how Virtualbox commands Qt5 to behave in this case). This leads to very 
broken behavior and unusable applications where this assumption is invalid; for 
a library like Qt, it's never actually valid (as acknowledged by the FIXME: 
comment).

  This has most recently shown its face with the Virtualbox project, exposed by 
i3 and other window managers, though tiling window managers seem to make use of 
this protocol more than most. The Virtualbox bug report has some good details; 
the i3 report has good details on the compounding effects of such an issue.
  ---[end quote]---

  The attached patch is a backport of the upstream fix. I'm also
  currently maintaining a PPA including this patch:
  https://launchpad.net/~paulo-matias/+archive/ubuntu/qt5-tiling

  It would be nice if the patch was included in the official Ubuntu
  package.

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

-- 
Mailing list: https://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 1316830] Re: /usr/lib/accountsservice/accounts-daemon :: memory and CPU time leak

[Christian Et]

Same here, this time on Debian 3.16.43-2+deb8u1 with kernel
3.16.0-4-amd64. I know this is an Ubuntu forum, but this bug ticket is
the closest one for this issue that I could find. Package
accountsservice has version 0.6.37-3+b1.

This machine is running ProFTPd 1.3.5 with a high number of FTP
sessions.

As you can see the wtmp file gets rather large:
-rw--- 1 root utmp  3072 Jul 14 09:53 btmp
-rw--- 1 root utmp  44259072 Jul 17 16:07 wtmp
-rw--- 1 root utmp 119944320 Jul 17 07:49 wtmp.1
-rw--- 1 root utmp 120503424 Jul 16 07:35 wtmp.2
-rw--- 1 root utmp 120549888 Jul 15 07:35 wtmp.3

This is probably the reason why accounts-daemon is eating away most of
by CPU:

  PID USER  PR  NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
  587 root  20   0  481984  98616   2520 R 73.5  9.6   1204:19 
accounts-daemon

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

Title:
  /usr/lib/accountsservice/accounts-daemon :: memory and CPU time leak

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  
  netikras@netikras-netbook ~/received/accountsservice-0.6.20 $ cat 
/etc/lsb-release 
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=16
  DISTRIB_CODENAME=petra
  DISTRIB_DESCRIPTION="Linux Mint 16 Petra"

  uname -a
  Linux netikras-netbook 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:12:00 
UTC 2013 i686 i686 i686 GNU/Linux


  
  Nothing. Using my netbook as usual. Did not really notice when this started 
since earlier today did not feel any significant slowdowns.

  
  That's what happened:
PID   USER  PR  NI  VIRT  RES   SHR   S  %CPU %MEMTIME+  COMMAND
   
  13155 root  20   0 61424  25m 2948 R  99,6  1,3   1:06.01 
accounts-daemon 

  
  netikras@netikras-netbook /tmp $ while :; do ps aux | grep accounts|grep -v 
grep;echo; sleep 2; done
  root 13155 93.6 26.1 555660 519912 pts/0   Sl   01:11   3:15 
/usr/lib/accountsservice/accounts-daemon

  root 13155 92.7 26.1 555660 519912 pts/0   Sl   01:11   3:15
  /usr/lib/accountsservice/accounts-daemon

  root 13155 91.9 26.1 555660 519912 pts/0   Sl   01:11   3:15
  /usr/lib/accountsservice/accounts-daemon

  
  accounts-daemon is using lots o CPU cycles and memory. Stats above are after 
restarting daemon for several times. Before this memory usage was >60%; CPU - 
100%.

  In file attached you should  be able to see there's a loop checking
  for something repeatedly. Not sure this is the cause though, but feels
  like it..

  
  It's the first time I've noticed this problem, but I often leave my computer 
running unattended so I cannot tell if it's really the first time it happened.

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

-- 
Mailing list: https://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 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

[Carlo Lobrano]

Confirmed on Ubuntu 17.04 using Libreoffice 1:5.3.1-0ubuntu2

** Changed in: ubuntu-themes
   Status: New => Confirmed

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

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

-- 
Mailing list: https://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 1700100] Re: Dimmed text is very hard to see

[Carlo Lobrano]

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Carlo Lobrano (c-lobrano)

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

Title:
  Dimmed text is very hard to see

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  To reproduce:
  1- Install gnome-boxes
  2- Start gnome-boxes
  3- Select New -> Enter URL

  There is a dimmed text, which is very hard to see. It starts with
  'Example:...'.

  I believe all GTK text that is styled as "dim-label" are very hard to
  see. This is also apparent in the warning bars in Firefox.

  Here is the line of code of the referred string in gnome-boxes upstream:
  
https://git.gnome.org/browse/gnome-boxes/tree/data/ui/wizard-source.ui?id=f3f581886ead85d5bfcbc71016f37825ed6ee90c#n291

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: light-themes 14.04+16.04.20161024-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 23 16:47:09 2017
  InstallationDate: Installed on 2017-06-21 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1700218] Re: Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

[Carlo Lobrano]

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Carlo Lobrano (c-lobrano)

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

Title:
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  As found by
  https://github.com/gtimelog/gtimelog/issues/81#issuecomment-170923964,
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace. It
  causes issues on some apps. Gitg is affected as well.

  My temporary workaround: https://quan.hoabinh.vn/blog/2017/6/46-fix-
  gitg-doesn-t-use-monospace-font-in-ubuntu

  Please fix it.

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

-- 
Mailing list: https://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 762349] Re: [SRU] Difficult to distinguish which tab is selected

[Nicolas Jungers]

The old fix doesn't work any more because the names of the properties
have changed.

This works for me:

notebook.terminal-notebook tab {
background-color: #a2a1a0;
foreground-color: #ff;
}

notebook.terminal-notebook tab:active {
background-color: #ff;
foreground-color: #010101;
}

I've put the file in ~/.config/gtk-3.0/gtk.css. You may adapt the colors
at your liking. The original definitions are in
/usr/share/themes/Ambiance/gtk-3.0/apps/gnome-terminal.css

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

Title:
  [SRU] Difficult to distinguish which tab is selected

Status in Ayatana Design:
  Fix Committed
Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Released

Bug description:
  [Impact]
   * When a user opens multiple tabs in GNOME terminal all tabs are styled in a 
*very* visually similar manner.  This makes it very hard to distinguish between 
the current active tab and all the others and on a HiDPI screen pretty much 
impossible.

  * This fix has been ack'd by design and was targeted for X but didn't
  get reviewed and OK'd in time.  Design team have approved this
  styling.

  * This bug is fixed by extending the CSS specifically for Terminal
  (i.e. no other applications are affected) giving the active tab a
  darker background colour (using only theme defined colours) and
  reworks the borders around the tabs to remove the graduated image
  borders that only look right on a light coloured background.  Changes
  have been made for both Ambiance and Radiance.

  [Test Case]
   * On a stock 16.04 install open GNOME Terminal (ctrl-alt-t)
   * Open five new tabs (ctrl-shift-t)
   * Click on the tab in the middle
   * Note that it is hard to see at a glance which tab is currently selected
   * Close Terminal and all open tabs.
   * Install the patched theme
   * Open Terminal and open five new tabs
   * Click on the tab in the middle and note that it takes on a light grey 
background compared to the unselected tabs which are dark grey.

  [Regression Potential]
   * The patch only addresses tabs that are placed at the top of the window. 
However this is the only option in Terminal, so should not cause any problems.
   * There is a work-around to match the "actions bar" (the bit with the 
dropdown selector and + button).  This bug is supposed to be fixed in v3.20 and 
could be removed.  This is commented in the CSS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/762349/+subscriptions

-- 
Mailing list: https://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 1429427] Re: Unexplainable time jumps in CRON

[Eric Desrochers]

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

** Changed in: rsyslog (Ubuntu Trusty)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

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

** Tags added: sts-sru-needed

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

Title:
  Unexplainable time jumps in CRON

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Trusty:
  New

Bug description:
  [Impact]

  on Trusty

  logging to syslog via cron causes timestamp abnormals after several
  hours.

  [Test Case]

  1. run below first,
  while true ; do logger "hello syslog" ; sleep 1; done

  2. register below script to crontab
  for i in {1..100} ; do logger "hello syslog via cron" ; sleep 1; done

  3. monitor syslog with below script
  tail -f -n 100 /var/log/syslog

  You can see weird timestamp in several hours.

  [Regression Potential]

  it's ratelimiting turn off code, could be issue with being off rate-
  limit

  [Other Info]

  below commit fixes this issue in my test

  From 7a2e2473476d2b10a775affd9ac6c62b81c450e5 Mon Sep 17 00:00:00 2001
  From: Tomas Heinrich 
  Date: Thu, 24 Jul 2014 13:47:14 +0200
  Subject: [PATCH 1/1] bugfix: plug a memleak in imuxsock

  The hash table for the system socket was allocated twice. The other
  one being in activateListeners().

  This commit practically reverts: 34a77cde2423303da72ab773128a2ddcf41
  The issue seems to be that the hash table is not initialized (to NULL)
  rather then not being allocated.

  #
  ## old description

  On my main server I see unexplainable time jumps backwards in the syslog. 
Those jumps affect CRON.
  Example:

  Feb 10 06:48:01 nostromo CRON[20351]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:49:01 nostromo CRON[20364]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20386]: (root) CMD (
/storage/exec/status-nostromo.sh >/dev/null 2>&1)
  Feb  7 05:40:01 nostromo CRON[20389]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20390]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20391]: (root) CMD (
/storage/exec/checkip.sh 2>/dev/null 1>/dev/null)

  For debugging I did the following:
  Start xclock and watch xclock and tail -f /var/log/syslog in parallel. When 
CRON logged a wrong time, xclock did NOT show any time jump but seemed to 
freeze for a fraction of a second.
  Open a screen and start a script that will once per second read the time (in 
unix seconds) and compare the read time with the time read a second ago. If the 
current time was smaller, the script would send an email with a process list 
from before and after the jump. The script also never detected any time jump.

  In summary, my current impression is that there might be a bug in CRON 
because no other programm seems to be able to see the "wrong" time. The server 
in question is syslog server for 4 servers and 3 network devices. The time 
jumps exclusively show in syslog entries from the local CRON instance. Not in 
any remote syslog entry and not in any other local syslog entry, e.g. from 
DHCPD, bind, tftpd, etc. etc.
  Also, after a reboot, things work ok for several days upto about 2 or 3 
weeks. Then the "time jumps" start to occur with increasing frequency.

  I don't use user crontabs but maintain all jobs in /etc/crontab. I
  have number of jobs which are triggered every minute and another
  number of jobs which are triggered every 5 minutes (maybe some CRON
  internal counter overflow problem?).

  Hardware:
  Asus P9D-V
  Intel Xeon E3-1240L V3
  16GB ECC RAM
  128GB SSD System
  3x3TB ZFS RaidZ2 storage
  1x3TB Misc. data

  CMOS battery already changed and board inspected.

  nostromo:~ # lsb_release -rd
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  nostromo:~ # apt-cache policy cron
  cron:
    Installed: 3.0pl1-124ubuntu2
    Candidate: 3.0pl1-124ubuntu2
    Version table:
   *** 3.0pl1-124ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://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 1693900] Re: apt-get update should return exit code != 0 on error

[Jens Elkner]

The bug/subject here is, that apt-get doesn't return a proper exit code,
not, what else one could use to workaround the bug.

Saying, that update from one of all (i.e. 1+) sites is sufficient is
like going to fly with a jet, where one of two engines is already broken
before it starts. Making this decision for yourself is ok, but making it
for all other passengers is IMHO irresponsible.

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

-- 
Mailing list: https://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 1696499] Re: dhclient segfaults on ubuntu 17.04

[Launchpad Bug Tracker]

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

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

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

Title:
  dhclient segfaults on ubuntu 17.04

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  After upgrading, network-manager stopped running DHCP, after trying to
  run dhclient myself I found out it segfaults. Attached is its strace
  output.

  I can connect to the internet by stopping network-manager and using
  ifconfig + route + /etc/resolv.conf.

  Output:
  guy@golem4:~$ dhclient
  Segmentation fault (core dumped)

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

-- 
Mailing list: https://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 1598300] Re: CUPS web interface stops responding after a while

[KWAndi]

It took me a day to find out why our Java App stop printing after a
while and cupsd is gone without a notification at all. Could please
someone explain why the "cupsd -l" should be useful at all?

Thanks

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Triaged

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

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

-- 
Mailing list: https://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 1548486] Sleep hook in a subdirectory ignored but causes double execution of previous hook

[Dirk F]

On 2017-07-14 09:58, Christian Ehrhardt wrote:
> I revisit dormant bugs on a regular scheduling following our triaging policy.
> It seems nothing happened upstream still.
> 
> For the Debian reporting you can do so through the mail interface - you don't 
> need a Debian system.
> Usually it is preferred that the reporter does so, but if you need help or 
> want me to do that please ping here and I'll do so.

Happy for you to do that, as Debian still seems to be interested in 
pm-utils. Not sure what stops Debian package maintainers from checking 
the upstream bug tracker, however.

/df

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

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

Status in pm-utils:
  Unknown
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548486/+subscriptions

-- 
Mailing list: https://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 1702741] Re: QtCreator crashes when opening a filechooser under wayland

[Jean-Baptiste Lallement]

** Tags removed: wayland-session

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

Title:
  QtCreator crashes when opening a filechooser under wayland

Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in qtbase-opensource-src source package in Zesty:
  Fix Committed
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  The file chooser dialog app for Qt apps will crash the app when trying to use 
the file chooser from a Wayland session such as GNOME on Wayland. GNOME on 
Wayland is included by default in Ubuntu GNOME.

  Test Case
  =
  1) Install Ubuntu 17.04 GNOME
  2) On the login screen, click the gear button and choose GNOME on Wayland and 
log in.
  3) Install qtcreator
  4) Launch qtcreator
  5) Try to do File -> Open File or Project

  The file chooser should open without crashing the app

  Regression Potential
  
  This fix was included in Qt 5.8. This patch was applied in Debian stretch in 
January as part of qtbase-opensource-src 5.7.1+dfsg-3

  
  == Upstream ==

  There is a qt bug here "GTK+ dialogs crash on Wayland" - 
https://bugreports.qt.io/browse/QTBUG-55583
  With what looks like a simple code change that Ubuntu could carry as a patch? 
https://codereview.qt-project.org/#/c/179124/

  Fedora appear to have fixed the bug in Fedora 25 -
  https://bugzilla.redhat.com/show_bug.cgi?id=1403500

  == Debug output ==

  When this occurs in the console you see the following:
  (qtcreator:16534): Gdk-WARNING **: 
/build/gtk+3.0-qPyWJl/gtk+3.0-3.22.11/./gdk/x11/gdkwindow-x11.c:5573 drawable 
is not a native X11 window
  Segmentation fault (core dumped)

  When running under GDB: http://pastebin.ubuntu.com/25033921/

  $ apt-cache policy qtcreator
  qtcreator:
    Installed: 4.1.0-3ubuntu1
    Candidate: 4.1.0-3ubuntu1
    Version table:
   *** 4.1.0-3ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  100 /var/lib/dpkg/status
  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

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

-- 
Mailing list: https://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 1704297] Re: Parrot Zik headphones stuck in A2DP profile

[Jean-Baptiste Lallement]

** Tags removed: wayland-session

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

Title:
  Parrot Zik headphones stuck in A2DP profile

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I've got a pair of Parot Zik bluetooth headphones, with inbuilt
  microphones and such.

  The Sound control panel offers a “Profile” dropdown, with choice of
  A2DP and HSP profiles, but selecting the HSP profile (a) doesn't add
  an input source to the “Inputs” tab, and (b) doesn't stop the
  headphones playing stereo sound, indicating that it hasn't actually
  been switched to HSP profile (which is, AFAIK, mono).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chris  7755 F pulseaudio
   /dev/snd/controlC1:  chris  7755 F pulseaudio
   /dev/snd/pcmC0D0c:   chris  7755 F...m pulseaudio
   /dev/snd/controlC0:  chris  7755 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Jul 14 16:27:09 2017
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA1 02/20/2017
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

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

-- 
Mailing list: https://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 1067434] Re: Sound output device keeps changing when using headphones

[Rada Florin-Daniel]

If someone reaches this page again with this problem, try this:
Install alsamixer if you don't have it installed.
Open a terminal and execute the command below:
alsamixer -c0
this will run the alsamixer, use the left/right arrows and find "loopback" 
option(Usually it's on the right side). When you find it make sure it's 
disabled, if it's enabled, press the "down" arrow to change it to disabled. 
When you did this, press ctrl+c to exit alsamixer. 
Check and see if the problem is gone or it's still there. It should be solved.

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

Title:
  Sound output device keeps changing when using headphones

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Recently upgraded to 12.10. Having issues with sound when using
  headphones plugged into the front ports. Something that doesn't happen
  when booting to windows - so fairly confident it's an Ubuntu issue.

  When listening to any sound, music, video etc the sound levels jump up
  and down and click. If I open "sound" from the settings menu when
  playing videos or music and viewing the "output" tab I can see
  "headphone - built-in audio disappear and reappear (very quickly) so
  I'm guessing the system is jumping back to the "analogue output" and
  back again which is why the sound volume changes and clicks.

  Worth noting I never used my headphones when 12.04 was installed so
  not sure if it's this OS or Ubuntu hates my hardware generally. Booted
  from live cd (usb) to 12.04 and there wasnt any issue.

  Anyone seen this before? any advice?

  Sound is built in to motherboard. I have the Gigabyte GA-X58A-UD5.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu19
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 16 18:07:44 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to quantal on 2012-09-29 (17 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu4
   deja-dup24.0-0ubuntu1
   gnome-control-center-signon 0.0.18-0ubuntu1
   indicator-datetime  12.10.2-0ubuntu3

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

-- 
Mailing list: https://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 1674304] Re: PRIME synchronization not working with xserver-1.19.x in Ubuntu

[Doug McMahon]

Is now working but users need to set up themselves, instructions here
https://ubuntuforums.org/showthread.php?t=2365449=13663158=1#post13663158

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

** Changed in: nvidia-prime (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  PRIME synchronization not working with xserver-1.19.x in Ubuntu

Status in lightdm package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released

Bug description:
  xserver-1.19.x is being proposed for 17.04, currently available in test ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
  FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799

  On 2 separate Optimus laptops there is no sign of it actually working, 
tearing while using nvidia drivers (375.x) is rampart.
  Testing with both current  4.10.0-13 & previous 4.9.0-11 kernels.

  Shows this in kern.log so support is enabled

  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] 
Supports vblank timestamp caching Rev 2 (21.10.2013).
  Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver 
supports precise vblank timestamp

  But in Xorg.0.log -
  randr: falling back to unsynchronized pixmap sharing

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nvidia-prime 0.8.4
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 20 07:53:12 2017
  InstallationDate: Installed on 2017-03-15 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1704677] Re: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*=

[linuxball]

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

-- 
Mailing list: https://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 1420334] Re: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows)

[Alan Griffiths]

** Changed in: miral
   Status: Incomplete => In Progress

** Changed in: miral
Milestone: None => 1.5

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

Title:
  [enhancement] Missing client API for relative surface movement (e.g.
  dragging client-decorated windows)

Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Mir needs a client API to allow surfaces to move themselves
  relatively. This is required to support full client-side decorations
  (bug 1398849), and also other apps like Google Chrome and Gnome
  Nautilus which can be dragged using part of their client areas.

  Later additions that are so similar I think they are part of the same
  bug: there need to be client APIs for "always on top" and "client
  initiate resize".

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

-- 
Mailing list: https://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 1693900] Re: apt-get update should return exit code != 0 on error

[Julian Andres Klode]

You should probably use an API for that (like python-apt), rather than
the command-line tools. We will have to rework error handling if we ever
want to retry automatic updates on failures, but it's not entirely clear
how this will happen yet.

In any case, I do consider an update where not all repositories were
updated a success. But I think some repository should update.

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

-- 
Mailing list: https://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 1429427] Re: Unexplainable time jumps in CRON

[Seyeong Kim]

** Patch added: "lp1429427_trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1429427/+attachment/4916080/+files/lp1429427_trusty.debdiff

** Description changed:

  [Impact]
  
  on Trusty
  
  logging to syslog via cron causes timestamp abnormals after several
  hours.
  
  [Test Case]
  
  1. run below first,
  while true ; do logger "hello syslog" ; sleep 1; done
  
  2. register below script to crontab
  for i in {1..100} ; do logger "hello syslog via cron" ; sleep 1; done
  
  3. monitor syslog with below script
  tail -f -n 100 /var/log/syslog
  
  You can see weird timestamp in several hours.
  
  [Regression Potential]
  
  it's ratelimiting turn off code, could be issue with being off rate-
  limit
  
  [Other Info]
  
- commit
+ below commit fixes this issue in my test
  
  From 7a2e2473476d2b10a775affd9ac6c62b81c450e5 Mon Sep 17 00:00:00 2001
  From: Tomas Heinrich 
  Date: Thu, 24 Jul 2014 13:47:14 +0200
  Subject: [PATCH 1/1] bugfix: plug a memleak in imuxsock
  
  The hash table for the system socket was allocated twice. The other
  one being in activateListeners().
  
  This commit practically reverts: 34a77cde2423303da72ab773128a2ddcf41
  The issue seems to be that the hash table is not initialized (to NULL)
  rather then not being allocated.
- 
  
  #
  ## old description
  
  On my main server I see unexplainable time jumps backwards in the syslog. 
Those jumps affect CRON.
  Example:
  
  Feb 10 06:48:01 nostromo CRON[20351]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:49:01 nostromo CRON[20364]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20386]: (root) CMD (
/storage/exec/status-nostromo.sh >/dev/null 2>&1)
  Feb  7 05:40:01 nostromo CRON[20389]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20390]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20391]: (root) CMD (
/storage/exec/checkip.sh 2>/dev/null 1>/dev/null)
  
  For debugging I did the following:
  Start xclock and watch xclock and tail -f /var/log/syslog in parallel. When 
CRON logged a wrong time, xclock did NOT show any time jump but seemed to 
freeze for a fraction of a second.
  Open a screen and start a script that will once per second read the time (in 
unix seconds) and compare the read time with the time read a second ago. If the 
current time was smaller, the script would send an email with a process list 
from before and after the jump. The script also never detected any time jump.
  
  In summary, my current impression is that there might be a bug in CRON 
because no other programm seems to be able to see the "wrong" time. The server 
in question is syslog server for 4 servers and 3 network devices. The time 
jumps exclusively show in syslog entries from the local CRON instance. Not in 
any remote syslog entry and not in any other local syslog entry, e.g. from 
DHCPD, bind, tftpd, etc. etc.
  Also, after a reboot, things work ok for several days upto about 2 or 3 
weeks. Then the "time jumps" start to occur with increasing frequency.
  
  I don't use user crontabs but maintain all jobs in /etc/crontab. I have
  number of jobs which are triggered every minute and another number of
  jobs which are triggered every 5 minutes (maybe some CRON internal
  counter overflow problem?).
  
  Hardware:
  Asus P9D-V
  Intel Xeon E3-1240L V3
  16GB ECC RAM
  128GB SSD System
  3x3TB ZFS RaidZ2 storage
  1x3TB Misc. data
  
  CMOS battery already changed and board inspected.
  
  nostromo:~ # lsb_release -rd
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  
  nostromo:~ # apt-cache policy cron
  cron:
    Installed: 3.0pl1-124ubuntu2
    Candidate: 3.0pl1-124ubuntu2
    Version table:
   *** 3.0pl1-124ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

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

** Tags added: sts

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

Title:
  Unexplainable time jumps in CRON

Status in rsyslog package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  on Trusty

  logging to syslog via cron causes timestamp abnormals after several
  hours.

  [Test Case]

  1. run below first,
  while true ; do logger "hello syslog" ; sleep 1; done

  2. register below script to crontab
  for i in {1..100} ; do logger "hello syslog via cron" ; sleep 1; done

  3. monitor syslog with below script
  tail -f -n 100 /var/log/syslog

  You can see weird timestamp in several hours.

  [Regression Potential]

  it's ratelimiting turn off 

[Touch-packages] [Bug 1429427] Re: Unexplainable time jumps in CRON

[Seyeong Kim]

** Description changed:

+ [Impact]
+ 
+ on Trusty
+ 
+ logging to syslog via cron causes timestamp abnormals after several
+ hours.
+ 
+ [Test Case]
+ 
+ 1. run below first,
+ while true ; do logger "hello syslog" ; sleep 1; done
+ 
+ 2. register below script to crontab
+ for i in {1..100} ; do logger "hello syslog via cron" ; sleep 1; done
+ 
+ 3. monitor syslog with below script
+ tail -f -n 100 /var/log/syslog
+ 
+ You can see weird timestamp in several hours.
+ 
+ [Regression Potential]
+ 
+ it's ratelimiting turn off code, could be issue with being off rate-
+ limit
+ 
+ [Other Info]
+ 
+ commit
+ 
+ From 7a2e2473476d2b10a775affd9ac6c62b81c450e5 Mon Sep 17 00:00:00 2001
+ From: Tomas Heinrich 
+ Date: Thu, 24 Jul 2014 13:47:14 +0200
+ Subject: [PATCH 1/1] bugfix: plug a memleak in imuxsock
+ 
+ The hash table for the system socket was allocated twice. The other
+ one being in activateListeners().
+ 
+ This commit practically reverts: 34a77cde2423303da72ab773128a2ddcf41
+ The issue seems to be that the hash table is not initialized (to NULL)
+ rather then not being allocated.
+ 
+ 
+ #
+ ## old description
+ 
  On my main server I see unexplainable time jumps backwards in the syslog. 
Those jumps affect CRON.
  Example:
  
  Feb 10 06:48:01 nostromo CRON[20351]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:49:01 nostromo CRON[20364]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20386]: (root) CMD (
/storage/exec/status-nostromo.sh >/dev/null 2>&1)
  Feb  7 05:40:01 nostromo CRON[20389]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20390]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20391]: (root) CMD (
/storage/exec/checkip.sh 2>/dev/null 1>/dev/null)
  
  For debugging I did the following:
  Start xclock and watch xclock and tail -f /var/log/syslog in parallel. When 
CRON logged a wrong time, xclock did NOT show any time jump but seemed to 
freeze for a fraction of a second.
  Open a screen and start a script that will once per second read the time (in 
unix seconds) and compare the read time with the time read a second ago. If the 
current time was smaller, the script would send an email with a process list 
from before and after the jump. The script also never detected any time jump.
  
  In summary, my current impression is that there might be a bug in CRON 
because no other programm seems to be able to see the "wrong" time. The server 
in question is syslog server for 4 servers and 3 network devices. The time 
jumps exclusively show in syslog entries from the local CRON instance. Not in 
any remote syslog entry and not in any other local syslog entry, e.g. from 
DHCPD, bind, tftpd, etc. etc.
  Also, after a reboot, things work ok for several days upto about 2 or 3 
weeks. Then the "time jumps" start to occur with increasing frequency.
  
  I don't use user crontabs but maintain all jobs in /etc/crontab. I have
  number of jobs which are triggered every minute and another number of
  jobs which are triggered every 5 minutes (maybe some CRON internal
  counter overflow problem?).
  
  Hardware:
  Asus P9D-V
  Intel Xeon E3-1240L V3
  16GB ECC RAM
  128GB SSD System
  3x3TB ZFS RaidZ2 storage
  1x3TB Misc. data
  
  CMOS battery already changed and board inspected.
  
  nostromo:~ # lsb_release -rd
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  
  nostromo:~ # apt-cache policy cron
  cron:
-   Installed: 3.0pl1-124ubuntu2
-   Candidate: 3.0pl1-124ubuntu2
-   Version table:
-  *** 3.0pl1-124ubuntu2 0
- 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.0pl1-124ubuntu2
+   Candidate: 3.0pl1-124ubuntu2
+   Version table:
+  *** 3.0pl1-124ubuntu2 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
+ 100 /var/lib/dpkg/status

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

Title:
  Unexplainable time jumps in CRON

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  on Trusty

  logging to syslog via cron causes timestamp abnormals after several
  hours.

  [Test Case]

  1. run below first,
  while true ; do logger "hello syslog" ; sleep 1; done

  2. register below script to crontab
  for i in {1..100} ; do logger "hello syslog via cron" ; sleep 1; done

  3. monitor syslog with below script
  tail -f -n 100 /var/log/syslog

  You can see weird timestamp in several hours.

  [Regression Potential]

  it's ratelimiting turn off code, could be issue with being off rate-
  limit

  [Other Info]

  commit

  

[Touch-packages] [Bug 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

[Claude Champagne]

By the way, I think that a mix of Pop!_OS GTK theme (from Adapta) and
United-Gnome Ubuntu shell theme would do a great job. See attachements
for an example. The United-Gnome GTK theme would be nice too.

** Attachment added: "Capture du 2017-07-17 04-25-31.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1704745/+attachment/4916074/+files/Capture%20du%202017-07-17%2004-25-31.png

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

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

-- 
Mailing list: https://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 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

[Daniel van Vugt]

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

** Package changed: light-themes (Ubuntu) => ubuntu-themes (Ubuntu)

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

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

-- 
Mailing list: https://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 1704747] [NEW] package libk5crypto3:amd64 1.15-1ubuntu0.1 failed to install/upgrade: a csomag nagyon rossz, következetlen állapotban van - újra kell telepítenie a beállítási kís

[Albert Dezso]

Public bug reported:

I have no more info.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libk5crypto3:amd64 1.15-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Wed Jul  5 20:51:19 2017
Dependencies:
 gcc-6-base 6.3.0-12ubuntu2
 libc6 2.24-9ubuntu2.2
 libgcc1 1:6.3.0-12ubuntu2
 libkrb5support0 1.15-1ubuntu0.1
ErrorMessage: a csomag nagyon rossz, következetlen állapotban van - újra  kell 
telepítenie a beállítási kísérlet előtt
InstallationDate: Installed on 2017-05-31 (46 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: krb5
Title: package libk5crypto3:amd64 1.15-1ubuntu0.1 failed to install/upgrade: a 
csomag nagyon rossz, következetlen állapotban van - újra  kell telepítenie a 
beállítási kísérlet előtt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package libk5crypto3:amd64 1.15-1ubuntu0.1 failed to install/upgrade:
  a csomag nagyon rossz, következetlen állapotban van - újra  kell
  telepítenie a beállítási kísérlet előtt

Status in krb5 package in Ubuntu:
  New

Bug description:
  I have no more info.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libk5crypto3:amd64 1.15-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jul  5 20:51:19 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
   libkrb5support0 1.15-1ubuntu0.1
  ErrorMessage: a csomag nagyon rossz, következetlen állapotban van - újra  
kell telepítenie a beállítási kísérlet előtt
  InstallationDate: Installed on 2017-05-31 (46 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: krb5
  Title: package libk5crypto3:amd64 1.15-1ubuntu0.1 failed to install/upgrade: 
a csomag nagyon rossz, következetlen állapotban van - újra  kell telepítenie a 
beállítási kísérlet előtt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1704745] [NEW] Ambiance light-themes - LibreOffice has a white square top right

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In LibreOffice, there's a white square that appears in the top right.
It's a CSS problem. You could check how the guys from Adapta and United-
Gnome managed to solve it.

I posted the same issue at the Github of United-Gnome theme :
https://github.com/godlyranchdressing/United-GNOME/issues/135

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Ambiance light-themes - LibreOffice has a white square top right
https://bugs.launchpad.net/bugs/1704745
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-themes 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 1704677] SystemdDelta.txt

[linuxball]

apport information

** Attachment added: "SystemdDelta.txt"
   
https://bugs.launchpad.net/bugs/1704677/+attachment/4916018/+files/SystemdDelta.txt

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

-- 
Mailing list: https://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 1704677] ProcEnviron.txt

[linuxball]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1704677/+attachment/4916015/+files/ProcEnviron.txt

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

-- 
Mailing list: https://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 1704677] ProcInterrupts.txt

[linuxball]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1704677/+attachment/4916016/+files/ProcInterrupts.txt

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

-- 
Mailing list: https://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 1704677] modified.conffile..etc.pam.d.systemd-user.txt

[linuxball]

apport information

** Attachment added: "modified.conffile..etc.pam.d.systemd-user.txt"
   
https://bugs.launchpad.net/bugs/1704677/+attachment/4916020/+files/modified.conffile..etc.pam.d.systemd-user.txt

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

-- 
Mailing list: https://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 1704677] UdevDb.txt

[linuxball]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1704677/+attachment/4916019/+files/UdevDb.txt

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

-- 
Mailing list: https://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 1704677] JournalErrors.txt

[linuxball]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1704677/+attachment/4916010/+files/JournalErrors.txt

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

-- 
Mailing list: https://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 1704677] ProcCpuinfo.txt

[linuxball]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1704677/+attachment/4916013/+files/ProcCpuinfo.txt

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

-- 
Mailing list: https://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 1704677] ProcCpuinfoMinimal.txt

[linuxball]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1704677/+attachment/4916014/+files/ProcCpuinfoMinimal.txt

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

-- 
Mailing list: https://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 1704677] ProcModules.txt

[linuxball]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1704677/+attachment/4916017/+files/ProcModules.txt

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

-- 
Mailing list: https://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 1704677] Lsusb.txt

[linuxball]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1704677/+attachment/4916012/+files/Lsusb.txt

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

-- 
Mailing list: https://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 1704677] Dependencies.txt

[linuxball]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1704677/+attachment/4916009/+files/Dependencies.txt

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

-- 
Mailing list: https://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 1704677] Lspci.txt

[linuxball]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1704677/+attachment/4916011/+files/Lspci.txt

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

-- 
Mailing list: https://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 1704677] Re: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*=

[linuxball]

apport information

** Tags added: apport-collected package-from-proposed third-party-
packages

** Description changed:

  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.
  
  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':
  
  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target
  
  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'
  
  Those two statements in section [Service] lead to the following two
  error messages in dmesg:
  
  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.9
+ Architecture: amd64
+ CurrentDesktop: LXDE
+ DistroRelease: Ubuntu 16.04
+ MachineType: LENOVO 42406AG
+ Package: systemd 229-4ubuntu18
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
+ ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
+ Tags: xenial package-from-proposed third-party-packages
+ Uname: Linux 4.4.0-85-lowlatency x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 09/20/2016
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: 8AET66WW (1.46 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 42406AG
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Available
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Not Available
+ dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
+ dmi.product.name: 42406AG
+ dmi.product.version: ThinkPad T520
+ dmi.sys.vendor: LENOVO
+ mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1704677/+attachment/4916008/+files/CurrentDmesg.txt

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a
  bug. The '+' prefix (see
  https://www.freedesktop.org/software/systemd/man/systemd.service.html)
  in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] 

[Touch-packages] [Bug 1539995] Re: apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

[Launchpad Bug Tracker]

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

Status in apport package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Partial Upgrade failed (crash)
  Ubuntu Mate 16 Alpha install testing on different machines.
  This machine Dell Optiplex 960

  linuxpusher@linuxpusher-OptiPlex-960:~$ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  
  linuxpusher@linuxpusher-OptiPlex-960:~$ sudo lshw
  [sudo] password for linuxpusher: 
  linuxpusher-optiplex-960  
  description: Computer
  width: 64 bits
  capabilities: smbios-2.5 vsyscall32
*-core
 description: Motherboard
 physical id: 0
   *-memory
description: System memory
physical id: 0
size: 7819MiB
   *-cpu
product: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
vendor: Intel Corp.
physical id: 1
bus info: cpu@0
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl 
aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 xsave lahf_lm dtherm tpr_shadow vnmi flexpriority
   *-pci
description: Host bridge
product: 4 Series Chipset DRAM Controller
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 03
width: 32 bits
clock: 33MHz
configuration: driver=agpgart-intel
resources: irq:0
  *-display:0
   description: VGA compatible controller
   product: 4 Series Chipset Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:33 memory:fe80-febf 
memory:d000-dfff ioport:ecb0(size=8)
  *-display:1 UNCLAIMED
   description: Display controller
   product: 4 Series Chipset Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2.1
   bus info: pci@:00:02.1
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: pm bus_master cap_list
   configuration: latency=0
   resources: memory:fe70-fe7f
  *-communication:0
   description: Communication controller
   product: 4 Series Chipset HECI Controller
   vendor: Intel Corporation
   physical id: 3
   bus info: pci@:00:03.0
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi bus_master cap_list
   configuration: driver=mei_me latency=0
   resources: irq:34 memory:feda6000-feda600f
  *-ide
   description: IDE interface
   product: 4 Series Chipset PT IDER Controller
   vendor: Intel Corporation
   physical id: 3.2
   bus info: pci@:00:03.2
   version: 03
   width: 32 bits
   clock: 66MHz
   capabilities: ide pm msi bus_master cap_list
   configuration: driver=ata_generic latency=0
   resources: irq:18 ioport:fe80(size=8) ioport:fe90(size=4) 
ioport:fea0(size=8) ioport:feb0(size=4) ioport:fef0(size=16)
  *-communication:1
   description: Serial controller
   product: 4 Series Chipset Serial KT Controller
   vendor: Intel Corporation
   physical id: 3.3
   bus info: pci@:00:03.3
   version: 03
   width: 32 bits
   clock: 66MHz
   capabilities: pm msi 16550 bus_master cap_list
   configuration: driver=serial latency=0
   resources: irq:17 ioport:ecb8(size=8) memory:fe6d8000-fe6d8fff
  *-network
   description: Ethernet interface
   product: 82567LM-3 Gigabit Network Connection
   vendor: Intel Corporation
   physical id: 19
   bus info: 

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Kai-Heng Feng]

Please try latest mainline kernel - Carlo's patches are included.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

-- 
Mailing list: https://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 1704726] Re: Please merge openldap 2.4.44+dfsg-8 (main) from Debian unstable (main)

[Ryan Tandy]

** Attachment added: "openldap_2.4.44+dfsg-8ubuntu1.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1704726/+attachment/4915950/+files/openldap_2.4.44+dfsg-8ubuntu1.debian.tar.xz

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

** Changed in: openldap (Ubuntu)
 Assignee: Ryan Tandy (rtandy) => (unassigned)

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

Title:
  Please merge openldap 2.4.44+dfsg-8 (main) from Debian unstable (main)

Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I just uploaded openldap 2.4.44+dfsg-8 in response to the new Heimdal
  upload. It includes the following fixes:

  - fixed FTBFS on ppc64el with kernel 4.9 and newer
  - fixed FTBFS with Heimdal 7.2.0 and newer

  Please consider sponsoring this merge, thanks!

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

-- 
Mailing list: https://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 1704726] Re: Please merge openldap 2.4.44+dfsg-8 (main) from Debian unstable (main)

[Ryan Tandy]

** Attachment added: "openldap_2.4.44+dfsg-8ubuntu1.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1704726/+attachment/4915949/+files/openldap_2.4.44+dfsg-8ubuntu1.dsc

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

Title:
  Please merge openldap 2.4.44+dfsg-8 (main) from Debian unstable (main)

Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I just uploaded openldap 2.4.44+dfsg-8 in response to the new Heimdal
  upload. It includes the following fixes:

  - fixed FTBFS on ppc64el with kernel 4.9 and newer
  - fixed FTBFS with Heimdal 7.2.0 and newer

  Please consider sponsoring this merge, thanks!

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

-- 
Mailing list: https://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 1704726] Re: Please merge openldap 2.4.44+dfsg-8 (main) from Debian unstable (main)

[Ryan Tandy]

** Patch added: "openldap_2.4.44+dfsg-8ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1704726/+attachment/4915948/+files/openldap_2.4.44+dfsg-8ubuntu1.debdiff

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

Title:
  Please merge openldap 2.4.44+dfsg-8 (main) from Debian unstable (main)

Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I just uploaded openldap 2.4.44+dfsg-8 in response to the new Heimdal
  upload. It includes the following fixes:

  - fixed FTBFS on ppc64el with kernel 4.9 and newer
  - fixed FTBFS with Heimdal 7.2.0 and newer

  Please consider sponsoring this merge, thanks!

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

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