[Touch-packages] [Bug 1714628] Re: package udev 229-4ubuntu19 failed to install/upgrade: 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1714628

Title:
  package udev 229-4ubuntu19 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  I get the error of system crashed when i boot the system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu19
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CustomUdevRuleFiles: 60-vboxdrv.rules 11-longcheer-Datacard.rules
  Date: Fri Sep  1 19:38:40 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-08-05 (27 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Hewlett-Packard HP 240 G3 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=UUID=af558641-ca54-46c1-b5df-b60f7e3be534 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: systemd
  Title: package udev 229-4ubuntu19 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 220D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP240G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn220D:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 240 G3 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1714628] [NEW] package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[karan Sarvaiya]

Public bug reported:

I get the error of system crashed when i boot the system

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu19
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CustomUdevRuleFiles: 60-vboxdrv.rules 11-longcheer-Datacard.rules
Date: Fri Sep  1 19:38:40 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-08-05 (27 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Hewlett-Packard HP 240 G3 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=UUID=af558641-ca54-46c1-b5df-b60f7e3be534 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: systemd
Title: package udev 229-4ubuntu19 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.18
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 220D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 86.28
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP240G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn220D:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 240 G3 Notebook PC
dmi.product.version: 0991100600087
dmi.sys.vendor: Hewlett-Packard

** Affects: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1714628

Title:
  package udev 229-4ubuntu19 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  I get the error of system crashed when i boot the system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu19
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CustomUdevRuleFiles: 60-vboxdrv.rules 11-longcheer-Datacard.rules
  Date: Fri Sep  1 19:38:40 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-08-05 (27 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Hewlett-Packard HP 240 G3 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=UUID=af558641-ca54-46c1-b5df-b60f7e3be534 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: systemd
  Title: package udev 229-4ubuntu19 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 220D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP240G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn220D:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 240 G3 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1701816] Re: Annoying beeps on Lubuntu 16.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Annoying beeps on Lubuntu 16.04

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I have a fresh install of Lubuntu 16.04 on my old Vaio VGN-FS730F and there 
are some annoying beeps that sound always in a randomly way. They have no 
defined pattern.
  I thought it was the pc speaker so I disabled from BIOS but it doesn't change 
anything. I realized that the beeps are  emitted by the soundcard because when 
I can listen it by headphones when I connect them. Sometimes the sound tray 
icon blinks at the sound of the beeps.

  The patterns of beeps changes randomly at every machine restart.
  -Not beep at all.
  -Beep every minute
  -Beep every second.
  -Sometimes the beeps lower their frequency when I play some video in firefox.

  Seems to be worst when the battery is low, but this is not a ruler.

  If you have problems figuring my situation, check this video of the
  issue https://youtu.be/GetcRSn2OJ4

  For me, it's enough to find a way to mute these annoying beeps.

  Model : Vaio VGN-FS730F

  >lsb_release -rd
  Description:   Ubuntu 16.0.4.2 LTS
  Release:   16.04
  --- 
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  flor   1013 F pulseaudio
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-05-01 (63 days ago)
  InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170216)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  xenial
  Uname: Linux 4.8.0-58-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/02/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0084J1
  dmi.chassis.asset.tag: Reserved
  dmi.chassis.type: 10
  dmi.chassis.vendor: Reserved
  dmi.chassis.version: Reserved
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0084J1:bd06/02/2006:svnSonyCorporation:pnVGN-FS730F:pvrC300QPZM:cvnReserved:ct10:cvrReserved:
  dmi.product.name: VGN-FS730F
  dmi.product.version: C300QPZM
  dmi.sys.vendor: Sony Corporation
  --- 
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  flor   1013 F pulseaudio
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-05-01 (63 days ago)
  InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170216)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  xenial
  Uname: Linux 4.8.0-58-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/02/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0084J1
  dmi.chassis.asset.tag: Reserved
  dmi.chassis.type: 10
  dmi.chassis.vendor: Reserved
  dmi.chassis.version: Reserved
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0084J1:bd06/02/2006:svnSonyCorporation:pnVGN-FS730F:pvrC300QPZM:cvnReserved:ct10:cvrReserved:
  dmi.product.name: VGN-FS730F
  dmi.product.version: C300QPZM
  dmi.sys.vendor: Sony Corporation

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

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

[Touch-packages] [Bug 1714596] Re: PDF images are blank

[Bryan Quigley]

Looks like enabling openjpeg2 would need an old MIR approved first.  Got many 
negative security reviews in the past.
https://bugs.launchpad.net/ubuntu/+source/openjpeg2/+bug/711061

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  1. Download this PDF - 
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

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

[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

[Simon Quigley]

The Lubuntu Software Center has not been updated for several cycles and
we don't even ship with it by default any more.

On behalf of the Lubuntu Team, I'd like to request that src:lubuntu-
software-center be removed from Artful. Subscribing the Archive
Administrators Team.

Reverse depends:
$ reverse-depends src:lubuntu-software-center
No reverse dependencies found

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  New
Status in mythbuntu-control-centre package in Ubuntu:
  New
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port-
  from-aptdaemon-to-packagekit

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

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

[Touch-packages] [Bug 1714596] Re: PDF images are blank

[Bryan Quigley]

Rebuilding with openjpeg enabled fixed it - which is similar to this
bug- https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/710412.

I don't understand why this is a regression if it was already
disabled...

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  1. Download this PDF - 
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

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

[Touch-packages] [Bug 1714596] Re: PDF images are blank

[Launchpad Bug Tracker]

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

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

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  1. Download this PDF - 
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

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

[Touch-packages] [Bug 1714596] Re: PDF images are blank

[Simon Quigley]

It doesn't seem like Fedora Rawhide has any (new) patches modifying
poppler at all: https://src.fedoraproject.org/rpms/poppler/tree/f27

There also doesn't seem to be any relevant patches in the Ubuntu
packaging...

Otherwise, I can reproduce.

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  1. Download this PDF - 
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

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

[Touch-packages] [Bug 1714596] Re: PDF images are blank

[Bryan Quigley]

Downgrading* to poppler on zesty-updates fixed the issue, looks like
it's an Ubuntu specific poppler regression.

*get and install zesty versions and it's fixed
http://mirrors.kernel.org/ubuntu/pool/main/p/poppler/libpoppler-cpp0v5_0.48.0-2ubuntu2.1_amd64.deb
 
http://mirrors.kernel.org/ubuntu/pool/main/p/poppler/libpoppler-glib8_0.48.0-2ubuntu2.1_amd64.deb
  
http://mirrors.kernel.org/ubuntu/pool/main/p/poppler/libpoppler64_0.48.0-2ubuntu2.1_amd64.deb
 
http://mirrors.kernel.org/ubuntu/pool/main/p/poppler/poppler-utils_0.48.0-2ubuntu2.1_amd64.deb

** Package changed: evince (Ubuntu) => poppler (Ubuntu)

** Description changed:

  1. Download this PDF - 
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  2. Open in Evince, note how first page is blank
  
  Open with Firefox and note how it displays a nice intro page.
  
  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not
  
  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.
  
- My planned next steps
- 1. Rule out Evince (test other version) or find something else that uses 
poppler to confirm
- 2. Rule it being an Ubuntu specific issue
- 2. Ideally bisect if a poppler bug a bit more
- 3. Report an upstream bug
+ Given my testing in Fedora (C#2) which worked fine with same version of
+ poppler and by downgrading the packages I believe this a Ubuntu specific
+ poppler bug.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  New

Bug description:
  1. Download this PDF - 
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

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

[Touch-packages] [Bug 1714596] [NEW] PDF images are blank

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

1. Download this PDF - 
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
2. Open in Evince, note how first page is blank

Open with Firefox and note how it displays a nice intro page.

Ubuntu 17.04 LiveCD works fine
Ubuntu 17.10 LiveCD does not

For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in poppler.

My planned next steps
1. Rule out Evince (test other version) or find something else that uses 
poppler to confirm
2. Rule it being an Ubuntu specific issue
2. Ideally bisect if a poppler bug a bit more
3. Report an upstream bug

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evince 3.24.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Sep  1 17:22:35 2017
SourcePackage: evince
UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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


** Tags: amd64 apport-bug artful third-party-packages
-- 
PDF images are blank
https://bugs.launchpad.net/bugs/1714596
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to poppler 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 1714618] Re: No password necessary for login to admin account

[Scott Emmons]

Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We appreciate the difficulties you
are facing, but it would make more sense to raise problems you are
having in the support tracker at https://answers.launchpad.net/ubuntu if
you are uncertain if they are bugs. For help on reporting bugs, see
https://help.ubuntu.com/community/ReportingBugs.

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/lightdm/+question/657253

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

Title:
  No password necessary for login to admin account

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  Having changed the language of Ubuntu from french to english, and have set 
the admin to login without a password, I have added a password to the admin 
account. However, at the login page, I am not prompted a password when logging 
in. 
  I am prompted for one on other non admin accounts, and I am also prompted it 
when accessing root privileges or when the admin password is needed for other 
reasons on the whole of ubuntu. 
  I have checked and I cannot find a light.dm file with any auto-login data. I 
cannot understand how I can disable auto-login.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep  2 01:19:46 2017
  InstallationDate: Installed on 2016-10-07 (329 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1580394] Re: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power

[spm2011]

** No longer affects: libmatemixer (Ubuntu)

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

Title:
  [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery
  Power

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1714618] [NEW] No password necessary for login to admin account

[Matthew]

Public bug reported:

Having changed the language of Ubuntu from french to english, and have set the 
admin to login without a password, I have added a password to the admin 
account. However, at the login page, I am not prompted a password when logging 
in. 
I am prompted for one on other non admin accounts, and I am also prompted it 
when accessing root privileges or when the admin password is needed for other 
reasons on the whole of ubuntu. 
I have checked and I cannot find a light.dm file with any auto-login data. I 
cannot understand how I can disable auto-login.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Sep  2 01:19:46 2017
InstallationDate: Installed on 2016-10-07 (329 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lightdm (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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1714618

Title:
  No password necessary for login to admin account

Status in lightdm package in Ubuntu:
  New

Bug description:
  Having changed the language of Ubuntu from french to english, and have set 
the admin to login without a password, I have added a password to the admin 
account. However, at the login page, I am not prompted a password when logging 
in. 
  I am prompted for one on other non admin accounts, and I am also prompted it 
when accessing root privileges or when the admin password is needed for other 
reasons on the whole of ubuntu. 
  I have checked and I cannot find a light.dm file with any auto-login data. I 
cannot understand how I can disable auto-login.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep  2 01:19:46 2017
  InstallationDate: Installed on 2016-10-07 (329 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 940145] Re: USB analog only devices sometimes show up with digital profile as well

[Lucas Magasweran]

Does anyone know what the root cause of this digital in/out appearing?
Is it within ALSA or is there something wrong with the USB AudioControl
interface descriptor being returned by the USB audio device? I ask
because I have a custom USB audio device with this issue.

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

Title:
  USB analog only devices sometimes show up with digital profile as well

Status in alsa-lib package in Ubuntu:
  Fix Released

Bug description:
  Sometimes, (I have yet to figure out when!) 
  USB headsets and mics which are analog only show up with a digital profile as 
well. While this is probably not a 12.04 regression, with the revamp of the 
sound settings UI this becomes annoying, as seen in the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu10
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.93-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david 10269 F pulseaudio
   /dev/snd/controlC0:  david 10269 F pulseaudio
   /dev/snd/pcmC0D0c:   david 10269 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd490 irq 48'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:111d7605,103c1413,00100402 
HDA:80862804,80860101,0010'
 Controls  : 23
 Simple ctrls  : 11
  Card1.Amixer.info:
   Card hw:1 'Headset'/'Logitech Logitech USB Headset at usb-:00:1a.0-1.4, 
full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0a0c'
 Controls  : 6
 Simple ctrls  : 2
  Date: Fri Feb 24 10:06:13 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120103)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68AZZ Ver. F.08
  dmi.board.name: 1413
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 57.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68AZZVer.F.08:bd06/29/2010:svnHewlett-Packard:pnHPProBook4520s:pvr:rvnHewlett-Packard:rn1413:rvrKBCVersion57.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4520s
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2012-02-09T11:15:19.592182

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

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

[Touch-packages] [Bug 1002952] Re: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards

[Lucas Magasweran]

I'm curious what the root cause of this bug is because I have a custom
USB audio device with this issue. Is it within ALSA or is something
wrong with the USB audio device's AudioControl Interface descriptor?

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

Title:
  [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards

Status in alsa-lib package in Ubuntu:
  Confirmed

Bug description:
  === Read me first ===

  = Symptom =

  If you have a USB headset, or other USB device that does not have any
  S/PDIF output, but yet sometimes there is an extra device called
  "Digital Output (S/PDIF)" for that device, you're suffering from this
  bug.

  This bug is only for USB devices - if you have an invalid digital
  output for some other type of device, please file a separate bug
  instead.

  = Workaround =

  If you're affected, please try this workaround:

  first check the output of "aplay -l" (lowercase L), or "arecord -l" if
  it's an input device, and grab the first of two name in brackets:

  Example:
  card 3: Headset [Sennheiser USB Headset], device 0: USB Audio [USB Audio]
  here grab the name "Sennheiser USB Headset". Now edit the file 
/usr/share/alsa/cards/USB-Audio.conf (requires root permissions)
  Around line 40, you will find a line saying "Logitech USB Headset" 999
  Add a new line after this line, so that there is now a new line called
  "Sennheiser USB Headset" 999
  (including quotes, and replace "Sennheiser USB Headset" with whatever your 
particular card was named.)

  Save the file and reboot your computer for the changes to take effect.

  = Already known devices =

  These card names are already in 12.04:

  "Blue Snowball"
  "Logitech USB Headset"
  "Logitech Web Camera"

  These card names are on their way into 12.04:

  "Logitech Speaker Lapdesk N700"
  "Logitech Wireless Headset"
  "Plantronics USB Headset"
  "Sennheiser USB headset"

  If you have one of the above four, please help out by testing the
  proposed repository and report back in bug 987163.

  If your name is not listed above, please add a comment to this bug,
  including your alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo -
  they will be collected for a SRU later on, or at least make it into
  the next release of Ubuntu.

  Thanks!

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

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

[Touch-packages] [Bug 1540353] Re: xargs: invalid number for -s option

[Bug Watch Updater]

** Changed in: python3.5 (Debian)
   Status: Unknown => Fix Released

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

Title:
  xargs: invalid number for -s option

Status in One Hundred Papercuts:
  Confirmed
Status in python3.4 package in Ubuntu:
  Confirmed
Status in python3.5 package in Debian:
  Fix Released

Bug description:
  I ran "sudo apt-get autoremove" and when python3.4 and
  libpython3.4-minimal:amd64 were removed, the following error was shown
  on the screen:

  Removing python3.4-minimal (3.4.4-1) ...
  Unlinking and removing bytecode for runtime python3.4
  Removing libpython3.4-minimal:amd64 (3.4.4-1) ...
  xargs: invalid number for -s option
  Usage: xargs [OPTION]... COMMAND [INITIAL-ARGS]...
  Run COMMAND with arguments INITIAL-ARGS and more arguments read from input.

  ...followed by instructions on how to use xargs properly.

  Probably some maintainer scripting errors?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libpython3.4-minimal (not installed)
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  1 13:46:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-28 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  SourcePackage: python3.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1275210] Re: gdbtui does not give input and show cyrillic symbols

[Launchpad Bug Tracker]

This bug was fixed in the package gdb - 8.0-0ubuntu6

---
gdb (8.0-0ubuntu6) artful; urgency=medium

  * Fix build dependencies for the gdb64 build.

 -- Matthias Klose   Fri, 01 Sep 2017 09:00:04 +0200

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

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

Title:
  gdbtui does not give input and show cyrillic symbols

Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  
┌──main.c┐
     │1   #include 
   │
     │2 
   │
     │3   int main()
   │
     │4   { 
   │
     │5   printf("M-P~_M-Q~@M-PM-8M-PM-2M-PM-5M-Q~B 
M-P~\M-PM-8M-Q~@\n");  │
     │6   return 0; 
   │
     │7   } 
   │
     │8 


   │
     
└─┘
  exec No process In:   
  Line: ??   PC: ??
  GNU gdb (GDB) 7.6.1-ubuntu
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  For bug reporting instructions, please see:
  ...
  Reading symbols from /home/eldar/hello...done.
  (gdb) M-Q~GM-Q~BM-PM-> M-Q~BM-PM-0M-PM-:M-PM->M-PM-5

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

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

[Touch-packages] [Bug 1540353] Re: xargs: invalid number for -s option

[Scott Emmons]

Xenial currently has python 3.5 (not python 3.4) and at a version where
the upstream bug[1] should be fixed.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809079


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

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

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

Title:
  xargs: invalid number for -s option

Status in One Hundred Papercuts:
  Confirmed
Status in python3.4 package in Ubuntu:
  Confirmed
Status in python3.5 package in Debian:
  Unknown

Bug description:
  I ran "sudo apt-get autoremove" and when python3.4 and
  libpython3.4-minimal:amd64 were removed, the following error was shown
  on the screen:

  Removing python3.4-minimal (3.4.4-1) ...
  Unlinking and removing bytecode for runtime python3.4
  Removing libpython3.4-minimal:amd64 (3.4.4-1) ...
  xargs: invalid number for -s option
  Usage: xargs [OPTION]... COMMAND [INITIAL-ARGS]...
  Run COMMAND with arguments INITIAL-ARGS and more arguments read from input.

  ...followed by instructions on how to use xargs properly.

  Probably some maintainer scripting errors?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libpython3.4-minimal (not installed)
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  1 13:46:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-28 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  SourcePackage: python3.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dan Streetman]

yep, having up to 3 seconds worth of stale system data is too much time.
Also, I think the builtins can just validate themselves - for example
the kmod builtin can trivially call kmod_validate_resource(ctx) every
time it's asked to load a module, and I think the other builtins that
implement .validate probably also can self-validate too, and remove the
udev_builtin_validate() call entirely.

I have a small draft patch just to the kmod builtin that I'm testing:
https://code.launchpad.net/~ddstreet/+git/systemd/+ref/sf149300

I'll take another look next week to see if it can be expanded to cover
all the builtins that do validation, and submit something upstream for
discussion.

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Scott Emmons]

The commit for this in upstream Debian (0.123 version of initramfs-
tools) is here: https://anonscm.debian.org/cgit/kernel/initramfs-
tools.git/commit/?id=ac6d31fc2c707b72ff8af9944c9b4f8af303a6a3 - I would
be happy to make a patch for this commit to xenial (zesty and later has
0.125+, so should already include the fix).

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Scott Emmons]

Sorry, my previous comment was for another initramfs-tools related bug.
Please disregard #18.

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1597661] Re: When /boot is full, repeated mkinitramfs runs can fill up /

[Scott Emmons]

The commit for this in upstream Debian (0.123 version of initramfs-
tools) is here: https://anonscm.debian.org/cgit/kernel/initramfs-
tools.git/commit/?id=ac6d31fc2c707b72ff8af9944c9b4f8af303a6a3 - I would
be happy to make a patch for this commit to xenial (zesty and later has
0.125+, so should already include the fix).

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

Title:
  When /boot is full, repeated mkinitramfs runs can fill up /

Status in One Hundred Papercuts:
  Confirmed
Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  My /boot partition filled up so when I (or unattended upgrades) next
  attempted to install a kernel, it failed.  On failure, mkinitramfs
  leaves a temporary directory in /var/tmp.

  If you (or unattended upgrades) do this enough times, you can end up
  with substantial, non-obvious disk usage.

  (I believe that this is fixed in Debian: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=814345)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun 30 09:12:45 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-30 (700 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to xenial on 2016-03-07 (114 days ago)

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

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

[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Rafael David Tinoco]

Unrelated to systemd. Related to open-iscsi systemd unit files and
kernel iscsi transport logout during shutdown.

** Changed in: open-iscsi (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: open-iscsi (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: open-iscsi (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: open-iscsi (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: open-iscsi (Ubuntu Artful)
   Importance: Undecided => Medium

** Changed in: open-iscsi (Ubuntu Artful)
   Status: New => In Progress

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

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => In Progress

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

** Changed in: linux (Ubuntu Zesty)
   Status: Incomplete => In Progress

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

** Changed in: linux (Ubuntu Artful)
   Status: Incomplete => In Progress

** No longer affects: systemd (Ubuntu)

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

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in open-iscsi source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  In Progress

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Rafael David Tinoco]

## SUMMARY 1

Affects open-iscsi (NOT systemd):

* ISCSID NEEDS TO BE UP & RUNNING (AND LOGGED TO PORTAL) FOR THE LOGOUT
TO WORK

https://pastebin.canonical.com/197359/

Daemon shutdown documentation in iscsiadm command says (about stopping iscsid 
daemon with iscsiadm -k): 
""" ... This will immediately stop all iscsid operations and shutdown iscsid. 
It does not logout any sessions. Running this command is the same as doing 
"killall iscsid". Neither should normally be used, because if iscsid is doing 
error recovery or if there is an error while iscsid is not running, the system 
may not be able to recover. This command and iscsid's SIGTERM handling are 
experimental. """

Basically meaning you're not able to shutdown the daemon in a clean
manner if you have connected sessions. And basically, checking the
pastebin, you see the need for running iscsid daemon to logout through
iscsiadm command.

So from:
 
(systemctl edit --full open-iscsi.service)
...
Wants=network-online.target remote-fs-pre.target iscsid.service
After=network-online.target iscsid.service
Before=remote-fs-pre.target
...
ExecStartPre=/bin/systemctl --quiet is-active iscsid.service
ExecStart=/sbin/iscsiadm -m node --loginall=automatic
ExecStart=/lib/open-iscsi/activate-storage.sh
ExecStop=/lib/open-iscsi/umountiscsi.sh
ExecStop=/bin/sync
ExecStop=/lib/open-iscsi/logout-all.sh
...

and

(systemctl edit --full iscsid.service)
...
Wants=network-online.target remote-fs-pre.target
Before=remote-fs-pre.target
After=network.target network-online.target
...
ExecStartPre=/lib/open-iscsi/startup-checks.sh
ExecStart=/sbin/iscsid
ExecStop=/sbin/iscsiadm -k 0 2
...

If umountiscsi.sh (it doesn't kill applications using a mount point)
can't umount a mount point (from fstab generator or a mount unit) that
is still being used, the logout-all.sh will fail for logging out the
session of the disk being used. But this service unit would be
considered stopped, allowing "iscsid.service" unit to also be shutdown
(killing the iscsid daemon and leaving an opened iscsi session).

This would be problematic for iscsi root disks AND for the kernel issue
(comment #73), and this is being taken care by Francis Ginther
(fginther) in the next iscsi SRU: https://pastebin.canonical.com/196463/
by creating an iscsi-cleanup.service that will run a script that logs
out all remaining iscsi sessions (including /) right before kernel
shutdown is called by systemd-shutdown like showed in comment #73.

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in open-iscsi source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  In Progress

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  

[Touch-packages] [Bug 1713086] Re: systemd fails to generate .device units inside LXD containers

[Dimitri John Ledkov]

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

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

Title:
  systemd fails to generate .device units inside LXD containers

Status in systemd package in Ubuntu:
  New

Bug description:
  See LXD issue here for more context:
  https://github.com/lxc/lxd/issues/3638

  After attaching a block device (in my case /dev/sdc3) to a LXD
  container, the dev-sdc3.device unit is not generated. However, the
  dev-sdc3.mount unit is generated correctly.

  Steps to reproduce (from GitHub issue):

  stgraber@castiana:~$ truncate -s 10G test.img
  stgraber@castiana:~$ sudo losetup -f test.img
  stgraber@castiana:~$ sudo losetup -a
  /dev/loop1: [0022]:169383 (/var/lib/snapd/snaps/core_2381.snap)
  /dev/loop2: [0022]:770242 (/var/lib/snapd/snaps/core_2312.snap)
  /dev/loop0: [0022]:1170310 (/var/lib/snapd/snaps/core_2462.snap)
  /dev/loop3: [0045]:309158 (/home/stgraber/test.img)
  stgraber@castiana:~$ lxc launch ubuntu:16.04 issue3638
  Creating issue3638
  Starting issue3638
  stgraber@castiana:~$ lxc config device add issue3638 sda unix-block 
source=/dev/loop3 path=/dev/sda
  Device sda added to issue3638
  stgraber@castiana:~$ lxc exec issue3638 -- mkfs.ext4 /dev/sda
  mke2fs 1.42.13 (17-May-2015)
  Discarding device blocks: done
  Creating filesystem with 2621440 4k blocks and 655360 inodes
  Filesystem UUID: 77832ca2-b16d-4b94-8f7d-9ea08c5e6913
  Superblock backups stored on blocks:
   32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

  Allocating group tables: done
  Writing inode tables: done
  Creating journal (32768 blocks): done
  Writing superblocks and filesystem accounting information: done

  stgraber@castiana:~$ echo Y | sudo tee 
/sys/module/ext4/parameters/userns_mounts
  Y
  stgraber@castiana:~$ lxc exec issue3638 -- mount /dev/sda /mnt
  stgraber@castiana:~$ lxc exec issue3638 bash
  root@issue3638:~# echo "/dev/sda /mnt ext4 defaults 0 0" >> /etc/fstab
  root@issue3638:~# cat /etc/fstab
  LABEL=cloudimg-rootfs /ext4   defaults0 0
  /dev/sda /mnt ext4 defaults 0 0
  root@issue3638:~# exit
  stgraber@castiana:~$ lxc exec issue3638 -- umount /mnt
  stgraber@castiana:~$ lxc exec issue3638 -- mount /mnt
  stgraber@castiana:~$ lxc stop issue3638
  stgraber@castiana:~$ lxc start issue3638
  stgraber@castiana:~$ lxc exec issue3638 -- mount | grep mnt
  stgraber@castiana:~$ lxc exec issue3638 -- systemctl -a | grep mnt
    mnt.mount  loadedinactive dead  
start /mnt
  stgraber@castiana:~$ lxc exec issue3638 -- systemctl -a | grep sda
    dev-sda.device loadedinactive dead  
start dev-sda.device
    dev-sda.mount  loadedactive   mounted   
  /dev/sda
  stgraber@castiana:~$ lxc exec issue3638 -- ps aux | grep udev
  root54  0.0  0.0  41720  1864 ?Ss   16:55   0:00 
/lib/systemd/systemd-udevd
  stgraber@castiana:~$

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

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

[Touch-packages] [Bug 1714169] Re: systemd /etc/resolv.conf setup on new installation breaks in-target package installation.

[Dimitri John Ledkov]

I believe debian-installer has resolvconf integration which used to fake
this for us, and this must be extended to fake things for resolved too.

** Package changed: systemd (Ubuntu) => netcfg (Ubuntu)

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

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

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

Title:
  systemd /etc/resolv.conf setup on new installation breaks in-target
  package installation.

Status in netcfg package in Ubuntu:
  Confirmed

Bug description:
  This Ubuntu systemd commit breaks in-target package installation on
  netboot installs.

  https://git.launchpad.net/~usd-import-
  
team/ubuntu/+source/systemd/commit/?id=76e5adfa6d1fb60e9622ca4b0d03a5b4f130885a

  The netboot initrd does not use systemd. /etc/resolv.conf is an actual
  generated file and there is no /run/systemd/resolve/stub-resolv.conf.

  Package installation in /target is done through in-target. in-target bind 
mounts the initrd /run to /target/run. After base-installer installs the 
systemd deb in /target, any subsequent in-target invocation to install a 
package fails. The repository containing the package cannot be resolved because 
/target/etc.resolv.conf will be a symlink to the bind mounted
  non-existent /target/run/systemd/resolve/stub-resolv.conf from the initrd.

  # chroot /target ls -l /etc/resolv.conf
  lrwxrwxrwx 1 root root 39 Aug 29 22:32 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  # chroot /target ls -l /run/systemd/resolve/
  total 4
  -rw-r--r-- 1 root root 89 Aug 29 22:32 stub-resolv.conf

  # chroot /target cat /etc/resolv.conf
  search 
  nameserver 

  # chroot /target ls -l /run
  total 12
  drwxrwxrwt 2 root root 4096 Aug 29 22:30 lock
  drwxr-xr-x 2 root root 4096 Aug 29 22:30 mount
  drwxr-xr-x 3 root root 4096 Aug 29 22:32 systemd
  -rw-rw-r-- 1 root utmp 0 Aug 29 22:30 utmp

  # in-target ls -l /etc/resolv.conf
  Aug 29 22:37:04 in-target: lrwxrwxrwx 1 root root 39 Aug 29 22:32 
/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

  # in-target ls -l /run/systemd/resolve/
  Aug 29 22:40:27 in-target: ls: cannot access '/run/systemd/resolve/'
  Aug 29 22:40:27 in-target: : No such file or directory

  # in-target cat /etc/resolv.conf
  Aug 29 22:41:48 in-target: cat: /etc/resolv.conf
  Aug 29 22:41:48 in-target: : No such file or directory

  # in-target ls -l /run/
  Aug 29 22:44:32 in-target: total 0
  Aug 29 22:44:32 in-target: drwxr-xr-x 2 root root 40 Aug 29 22:26 lock
  Aug 29 22:44:32 in-target: drwxr-xr-x 2 root root 60 Aug 29 22:26 mount
  Aug 29 22:44:32 in-target: drwxr-xr-x 4 root root 100 Aug 29 22:30 udev

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

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

[Touch-packages] [Bug 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable

[Jeremy LaCroix]

I run into this problem every now and then. I am not sure what causes
it. At the moment, this is not happening. I press ALT+Left/Right with no
issue. But at some point this bug seems to appear. It's frustrating
because ALT+Left in Firefox, for example, is a keyboard shortcut I use
to go back a page.

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

Title:
  alt + left/right arrows switch between tty consoles, cannot disable

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dimitri John Ledkov]

I guess this is related to the fact that udevd main loop re-reads
configs at most every 3 seconds. I find that 3 seconds is a really long
time these days.

I wonder if the 3s timeout around manager_reload(manager) should be
removed in udevd.

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1714431] Re: Can not login after switch to runlevel 3 from 1

[Dimitri John Ledkov]

What is a runlevel?

Ubuntu pretty much never had any concepts of runlevels. And even more so
since switch to upstart in 9.10.

I am confused as to what you are trying to do. Could you please describe
what you are trying to achieve?

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

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

Title:
  Can not login after switch to runlevel 3 from 1

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  No login prompt or anything on console after switch to runlevel 3/5
  from 1

  Step to reproduce
  1) Make sure root password is set
  2) login as root on console
  3) `init 1` switch to runlevel 1
  4) login again as root
  5) `init 3` or `init 5` and no login or prompt

  root@D05-2:~# init 1
  root@D05-2:~# 
  Ubuntu 16.04.3 LTS D05-2 ttyAMA0

  D05-2 login: root 
  System is going down.

  Password: 
  Last login: Fri Sep  1 07:28:04 UTC 2017 on ttyAMA0
  Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.10.0-33-generic aarch64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

Get cloud support with Ubuntu Advantage Cloud Guest:
  http://www.ubuntu.com/business/services/cloud

  0 packages can be updated.
  0 updates are security updates.

  
  root@D05-2:~# init 5
  [  103.499358] cloud-init[4497]: Cloud-init v. 0.7.9 running 'init-local' at 
Fri, 01 Sep 2017 07:28:40 +. Up 103.12 seconds.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1569925

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

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

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

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

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

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

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  Incomplete
Status in open-iscsi package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Incomplete
Status in open-iscsi source package in Xenial:
  New
Status in systemd source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Incomplete
Status in open-iscsi source package in Zesty:
  New
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Incomplete
Status in open-iscsi source package in Artful:
  New
Status in systemd source package in Artful:
  Confirmed

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Eric Desrochers]

** Also affects: open-iscsi (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

** Also affects: systemd (Ubuntu Artful)
   Importance: High
 Assignee: Nish Aravamudan (nacc)
   Status: Confirmed

** Also affects: open-iscsi (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

** Also affects: systemd (Ubuntu Zesty)
   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/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in open-iscsi source package in Xenial:
  New
Status in systemd source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  New
Status in open-iscsi source package in Zesty:
  New
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  New
Status in open-iscsi source package in Artful:
  New
Status in systemd source package in Artful:
  Confirmed

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Rafael David Tinoco]

** Also affects: open-iscsi (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in open-iscsi source package in Xenial:
  New
Status in systemd source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  New
Status in open-iscsi source package in Zesty:
  New
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  New
Status in open-iscsi source package in Artful:
  New
Status in systemd source package in Artful:
  Confirmed

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Touch-packages] [Bug 1610517] Re: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping

[Bob Luby]

I attempted to reinstall the Ubuntu Software Centre after upgrading my
graphics card and installing a new driver.  I then found that Software
Centre no longer did anything when clicked.  So I removed it and
reinstalled it.  Below is a capture of my terminal window when the
install failed.



Selecting previously unselected package libgrilo-0.2-1:amd64.
Preparing to unpack .../libgrilo-0.2-1_0.2.15-1_amd64.deb ...
Unpacking libgrilo-0.2-1:amd64 (0.2.15-1) ...
Selecting previously unselected package adwaita-icon-theme.
Preparing to unpack .../adwaita-icon-theme_3.18.0-2ubuntu3.1_all.deb ...
Unpacking adwaita-icon-theme (3.18.0-2ubuntu3.1) ...
Preparing to unpack .../libgtk-3-common_3.18.9-1ubuntu3.3_all.deb ...
Unpacking libgtk-3-common (3.18.9-1ubuntu3.3) over (3.10.8-0ubuntu1.6) ...
Selecting previously unselected package libcolord2:amd64.
Preparing to unpack .../libcolord2_1.2.12-1ubuntu1_amd64.deb ...
Unpacking libcolord2:amd64 (1.2.12-1ubuntu1) ...
Selecting previously unselected package libepoxy0:amd64.
Preparing to unpack .../libepoxy0_1.3.1-1ubuntu0.16.04.2_amd64.deb ...
Unpacking libepoxy0:amd64 (1.3.1-1ubuntu0.16.04.2) ...
Selecting previously unselected package libcapnp-0.5.3:amd64.
Preparing to unpack .../libcapnp-0.5.3_0.5.3-2ubuntu1_amd64.deb ...
Unpacking libcapnp-0.5.3:amd64 (0.5.3-2ubuntu1) ...
Selecting previously unselected package libboost-filesystem1.58.0:amd64.
Preparing to unpack 
.../libboost-filesystem1.58.0_1.58.0+dfsg-5ubuntu3.1_amd64.deb ...
Unpacking libboost-filesystem1.58.0:amd64 (1.58.0+dfsg-5ubuntu3.1) ...
Selecting previously unselected package libmircore1:amd64.
Preparing to unpack .../libmircore1_0.26.3+16.04.20170605-0ubuntu1_amd64.deb ...
Unpacking libmircore1:amd64 (0.26.3+16.04.20170605-0ubuntu1) ...
Selecting previously unselected package libmircommon7:amd64.
Preparing to unpack .../libmircommon7_0.26.3+16.04.20170605-0ubuntu1_amd64.deb 
...
Unpacking libmircommon7:amd64 (0.26.3+16.04.20170605-0ubuntu1) ...
Selecting previously unselected package libprotobuf-lite9v5:amd64.
Preparing to unpack .../libprotobuf-lite9v5_2.6.1-1.3_amd64.deb ...
Unpacking libprotobuf-lite9v5:amd64 (2.6.1-1.3) ...
Selecting previously unselected package libmirprotobuf3:amd64.
Preparing to unpack 
.../libmirprotobuf3_0.26.3+16.04.20170605-0ubuntu1_amd64.deb ...
Unpacking libmirprotobuf3:amd64 (0.26.3+16.04.20170605-0ubuntu1) ...
Selecting previously unselected package libmirclient9:amd64.
Preparing to unpack .../libmirclient9_0.26.3+16.04.20170605-0ubuntu1_amd64.deb 
...
Unpacking libmirclient9:amd64 (0.26.3+16.04.20170605-0ubuntu1) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
(Reading database ... 370003 files and directories currently installed.)
Removing overlay-scrollbar-gtk3:amd64 (0.2.16+r359+14.04.20131129-0ubuntu1) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
(Reading database ... 37 files and directories currently installed.)
Preparing to unpack 
.../overlay-scrollbar_0.2.17.1+16.04.20151117-0ubuntu1.16.04.1_all.deb ...
Unpacking overlay-scrollbar (0.2.17.1+16.04.20151117-0ubuntu1.16.04.1) over 
(0.2.16+r359+14.04.20131129-0ubuntu1) ...
Preparing to unpack .../libgail-3-0_3.18.9-1ubuntu3.3_amd64.deb ...
Unpacking libgail-3-0:amd64 (3.18.9-1ubuntu3.3) over (3.10.8-0ubuntu1.6) ...
Preparing to unpack .../libgtk-3-0_3.18.9-1ubuntu3.3_amd64.deb ...
Unpacking libgtk-3-0:amd64 (3.18.9-1ubuntu3.3) over (3.10.8-0ubuntu1.6) ...
Selecting previously unselected package libjavascriptcoregtk-4.0-18:amd64.
Preparing to unpack 
.../libjavascriptcoregtk-4.0-18_2.16.6-0ubuntu0.16.04.1_amd64.deb ...
Unpacking libjavascriptcoregtk-4.0-18:amd64 (2.16.6-0ubuntu0.16.04.1) ...
Selecting previously unselected package libass5:amd64.
Preparing to unpack .../libass5_0.13.1-1_amd64.deb ...
Unpacking libass5:amd64 (0.13.1-1) ...
Selecting previously unselected package libbs2b0:amd64.
Preparing to unpack .../libbs2b0_3.1.0+dfsg-2.2_amd64.deb ...
Unpacking libbs2b0:amd64 (3.1.0+dfsg-2.2) ...
Selecting previously unselected package libde265-0:amd64.
Preparing to unpack .../libde265-0_1.0.2-2_amd64.deb ...
Unpacking libde265-0:amd64 (1.0.2-2) ...
Preparing to unpack 
.../gstreamer1.0-plugins-bad-videoparsers_1.8.3-1ubuntu0.2_amd64.deb ...
Unpacking gstreamer1.0-plugins-bad-videoparsers:amd64 (1.8.3-1ubuntu0.2) over 
(1.2.4-1~ubuntu1.1) ...
Preparing to unpack 
.../gstreamer1.0-plugins-bad-faad_1.8.3-1ubuntu0.2_amd64.deb ...
Unpacking gstreamer1.0-plugins-bad-faad:amd64 (1.8.3-1ubuntu0.2) over 
(1.2.4-1~ubuntu1.1) ...
Preparing to unpack 

[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE network shares in file chooser

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
  GTK+3 doesn't show FUSE network shares in file chooser

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day. 
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares. 
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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

[Touch-packages] [Bug 1707048] Re: bsdutils conflict

[Phillip Susi]

Please provide the command you were running when you got this error and
attach /var/log/dpkg.log and /var/log/apt/history.log and
/var/log/apt/term.log.


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

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

Title:
  bsdutils conflict

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  dpkg: error al procesar el paquete bsdutils (--configure):
   el paquete bsdutils no está listo para configurarse
   no se puede configurar (estado actual `half-installed')
  Se encontraron errores al procesar:
   bsdutils
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dan Streetman]

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

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1523985] Re: evolution-source-registery needs a restart to pick newly activated uoa accounts

[Bug Watch Updater]

** Changed in: evolution-data-server
   Status: Incomplete => Won't Fix

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

Title:
  evolution-source-registery needs a restart to pick newly activated uoa
  accounts

Status in evolution-data-server:
  Won't Fix
Status in evolution-data-server package in Ubuntu:
  Triaged
Status in evolution-data-server source package in Xenial:
  Triaged

Bug description:
  Using current xenial version
  - go to the uoa settings
  - add a google account

  - > you get a notification that there is an auth issue (that's a weird
  workflow but needed because the application needs to auth but e-d-s
  can't do UI prompting)

  - auth e-d-s in the settings

  -> the new account should be active/listed in the indicator or gnome-
  calendar but is not

  
  The issue is probably that e-d-s connect to the "account-created" signal on a 
AgManager object and adds the account correctly, but at this point the 
authentification/confirmation is not done yet so the account fails to active, 
and there is no following callback after the authentification is done. 

  It seems that AgManager doesn't provide an appropriate signal that can
  be used there so some work might be needed on the signon side

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1523985/+subscriptions

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

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Graham Bosworth]

The failure had not recurred until today.  My slightly amended version
of the script provided above by Steve Chadsey (schadsey), 2017-07-19,
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/comments/18
did not rectify the problem.  I have since modified it more and hope
that it can provide useful diagnostics next time there is a similar
failure.

The connection was active until after 00:49:01.  It was restored
manually by 08:11:59.  Unfortunately, I cannot be certain whether I
reactivated the interface or whether an automated script did so.

yoyo ~ # ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14  
  inet6 addr: fe80::c1e6:4b25:5c64:f669/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:65340342 errors:0 dropped:0 overruns:0 frame:0
  TX packets:26833432 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:21650436815 (21.6 GB)  TX bytes:140523812727 (140.5 GB)
  Interrupt:18 

yoyo ~ # ifconfig eth0 down
yoyo ~ # ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14  
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:65340378 errors:0 dropped:0 overruns:0 frame:0
---^
  TX packets:26833625 errors:0 dropped:0 overruns:0 carrier:0
---^
  collisions:0 txqueuelen:1000 
  RX bytes:21650441164 (21.6 GB)  TX bytes:140523828704 (140.5 GB)
---^^^-
  Interrupt:18 

Notice that the counts of packets and bytes had been increasing, and
that no packets had been dropped.

yoyo ~ # ip a add 192.168.42.187 dev eth0

yoyo ~ # ip a s eth0
2: eth0:  mtu 1500 qdisc pfifo_fast state DOWN group
default qlen 1000
link/ether 00:25:64:72:72:14 brd ff:ff:ff:ff:ff:ff
inet 192.168.42.187/32 scope global eth0
   valid_lft forever preferred_lft forever

yoyo ~ # ip a del 192.168.42.187 dev eth0
Warning: Executing wildcard deletion to stay compatible with old scripts.
 Explicitly specify the prefix length (192.168.42.187/32) to avoid 
 this warning.
 This special behaviour is likely to disappear in further releases,
 fix your scripts!

yoyo ~ # ip a s eth0
2: eth0:  mtu 1500 qdisc pfifo_fast state DOWN group
default qlen 1000
link/ether 00:25:64:72:72:14 brd ff:ff:ff:ff:ff:ff

yoyo ~ # ip a add 192.168.42.187/24 dev eth0

yoyo ~ # ip a s eth0
2: eth0:  mtu 1500 qdisc pfifo_fast state DOWN group
default qlen 1000
link/ether 00:25:64:72:72:14 brd ff:ff:ff:ff:ff:ff
inet 192.168.42.187/24 scope global eth0
   valid_lft forever preferred_lft forever

yoyo ~ # ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14
  inet addr:192.168.42.187  Bcast:0.0.0.0  Mask:255.255.255.0yoyo ~ # 
ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14
  inet addr:192.168.42.187  Bcast:0.0.0.0  Mask:255.255.255.0
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:65340544 errors:0 dropped:357 overruns:0 frame:0
---^^^
  TX packets:26834217 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:21650460079 (21.6 GB)  TX bytes:140523878283 (140.5 GB)
  Interrupt:18 

Now there are dropped packets.

yoyo ~ # ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14
  inet addr:192.168.42.187  Bcast:0.0.0.0  Mask:255.255.255.0
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:65340544 errors:0 dropped:638 overruns:0 frame:0
---^^^
  TX packets:26834217 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:21650460079 (21.6 GB)  TX bytes:140523878283 (140.5 GB)
  Interrupt:18 

More packets have been dropped.

yoyo ~ # ifconfig eth0 down
yoyo ~ # ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14
  inet addr:192.168.42.187  Bcast:0.0.0.0  Mask:255.255.255.0
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:65340544 errors:0 dropped:687 overruns:0 frame:0
  TX packets:26834217 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:21650460079 (21.6 GB)  TX bytes:140523878283 (140.5 GB)
  Interrupt:18 

Oops.  My memory let me down:-

yoyo ~ # ifconfig eth0 up dhcp
dhcp: Unknown host
ifconfig: `--help' gives usage information.
yoyo ~ # ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14
  inet addr:192.168.42.187  Bcast:0.0.0.0  Mask:255.255.255.0
  inet6 addr: fe80::225:64ff:fe72:7214/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  

[Touch-packages] [Bug 1714519] Re: Typo Todoist

[Jeremy Bicha]

It's for the Todoist service:

https://en.todoist.com/

Therefore, I am closing this bug.

Thank you for taking the time to report this issue. Please feel free to
report any other bugs you find.

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Invalid

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

Title:
  Typo Todoist

Status in gnome-online-accounts package in Ubuntu:
  Invalid

Bug description:
  https://translations.launchpad.net/ubuntu/artful/+source/gnome-online-
  accounts/+pots/gnome-online-accounts/fr/112/+translate

  I think it's Todolist and not Todoist

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

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

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dan Streetman]

slight update to test script, add a check to make sure the nvme module
was unloaded - if any nvme partitions are mounted it would cause a false
positive result.

#!/bin/bash
MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
modprobe -rq nvme
mv $MOD_DIR/nvme.ko .
depmod -a
sleep 3
udevadm trigger
sleep 1
mv nvme.ko $MOD_DIR/
depmod -a
grep -q nvme /proc/partitions && echo FAIL nvme driver still loaded unmount all 
nvme partitions && exit 1
udevadm trigger
sleep 3
grep -q nvme /proc/partitions && echo PASS || echo FAIL

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dan Streetman]

grr, please note line wrap in above comment; script should be:

#!/bin/bash
MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
modprobe -rq nvme
mv $MOD_DIR/nvme.ko .
depmod -a
sleep 3
udevadm trigger
sleep 1
mv nvme.ko $MOD_DIR/
depmod -a
grep -q nvme /proc/partitions \
  && echo FAIL nvme driver still loaded unmount all nvme partitions \
  && exit 1
udevadm trigger
sleep 3
grep -q nvme /proc/partitions && echo PASS || echo FAIL

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1714531] [NEW] package libssl1.0.0 1.0.2g-1ubuntu11.2 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libssl1.0.0/changelog.Debian.gz« zu überschreiben, w

[Tobias Wagner]

Public bug reported:

Not sure what happened

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libssl1.0.0 1.0.2g-1ubuntu11.2
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Fri Sep  1 16:05:27 2017
DpkgTerminalLog:
 Vorbereitung zum Entpacken von .../0-libssl1.0.0_1.0.2g-1ubuntu11.2_amd64.deb 
...
 Entpacken von libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) über (1.0.1t-1+deb8u6) ...
 dpkg: Fehler beim Bearbeiten des Archivs 
/tmp/apt-dpkg-install-XPPUMK/0-libssl1.0.0_1.0.2g-1ubuntu11.2_amd64.deb 
(--unpack):
  Versuch, gemeinsam benutztes »/usr/share/doc/libssl1.0.0/changelog.Debian.gz« 
zu überschreiben, welches verschieden von anderen Instanzen des Paketes 
libssl1.0.0:amd64 ist
ErrorMessage: Versuch, gemeinsam benutztes 
»/usr/share/doc/libssl1.0.0/changelog.Debian.gz« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libssl1.0.0:amd64 ist
InstallationDate: Installed on 2017-09-01 (0 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: openssl
Title: package libssl1.0.0 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
Versuch, gemeinsam benutztes »/usr/share/doc/libssl1.0.0/changelog.Debian.gz« 
zu überschreiben, welches verschieden von anderen Instanzen des Paketes 
libssl1.0.0:amd64 ist
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssl (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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1714531

Title:
  package libssl1.0.0 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  Versuch, gemeinsam benutztes
  »/usr/share/doc/libssl1.0.0/changelog.Debian.gz« zu überschreiben,
  welches verschieden von anderen Instanzen des Paketes
  libssl1.0.0:amd64 ist

Status in openssl package in Ubuntu:
  New

Bug description:
  Not sure what happened

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libssl1.0.0 1.0.2g-1ubuntu11.2
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Sep  1 16:05:27 2017
  DpkgTerminalLog:
   Vorbereitung zum Entpacken von 
.../0-libssl1.0.0_1.0.2g-1ubuntu11.2_amd64.deb ...
   Entpacken von libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) über (1.0.1t-1+deb8u6) 
...
   dpkg: Fehler beim Bearbeiten des Archivs 
/tmp/apt-dpkg-install-XPPUMK/0-libssl1.0.0_1.0.2g-1ubuntu11.2_amd64.deb 
(--unpack):
Versuch, gemeinsam benutztes 
»/usr/share/doc/libssl1.0.0/changelog.Debian.gz« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libssl1.0.0:amd64 ist
  ErrorMessage: Versuch, gemeinsam benutztes 
»/usr/share/doc/libssl1.0.0/changelog.Debian.gz« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libssl1.0.0:amd64 ist
  InstallationDate: Installed on 2017-09-01 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: openssl
  Title: package libssl1.0.0 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
Versuch, gemeinsam benutztes »/usr/share/doc/libssl1.0.0/changelog.Debian.gz« 
zu überschreiben, welches verschieden von anderen Instanzen des Paketes 
libssl1.0.0:amd64 ist
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dan Streetman]

note that the test script in the description must be run as root on a
system that does have a nvme drive that isn't in use (because the nvme
module can't be removed if any nvme drive is in use).


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

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dan Streetman]

https://github.com/systemd/systemd/issues/6723

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1714431] Re: Can not login after switch to runlevel 3 from 1

[dann frazier]

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

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

** Changed in: systemd (Ubuntu Xenial)
   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/1714431

Title:
  Can not login after switch to runlevel 3 from 1

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed

Bug description:
  No login prompt or anything on console after switch to runlevel 3/5
  from 1

  Step to reproduce
  1) Make sure root password is set
  2) login as root on console
  3) `init 1` switch to runlevel 1
  4) login again as root
  5) `init 3` or `init 5` and no login or prompt

  root@D05-2:~# init 1
  root@D05-2:~# 
  Ubuntu 16.04.3 LTS D05-2 ttyAMA0

  D05-2 login: root 
  System is going down.

  Password: 
  Last login: Fri Sep  1 07:28:04 UTC 2017 on ttyAMA0
  Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.10.0-33-generic aarch64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

Get cloud support with Ubuntu Advantage Cloud Guest:
  http://www.ubuntu.com/business/services/cloud

  0 packages can be updated.
  0 updates are security updates.

  
  root@D05-2:~# init 5
  [  103.499358] cloud-init[4497]: Cloud-init v. 0.7.9 running 'init-local' at 
Fri, 01 Sep 2017 07:28:40 +. Up 103.12 seconds.

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

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

[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE network shares in file chooser

[Colin Leroy]

** Description changed:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do it.
  
  In the mean time, every user of every application switching to GTK+3 --
  including Chromium, at some point between 58 and 60 -- (a change which
  happened in 16.04 LTS!!), loses the functionality to open or save
  directly to a network share.
  
- I had chosen 16.04 LTS for deploying our workstations at work, and my
- users have been suddenly unable to do a simple operation they have to do
- dozens of times a day.
+ I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day. 
+ They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares. 
+ They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.
  
  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3 package.
  
  Thanks in advance.
  
  Colin

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

Title:
  GTK+3 doesn't show FUSE network shares in file chooser

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day. 
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares. 
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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

[Touch-packages] [Bug 1714518] [NEW] GTK+3 doesn't show FUSE network shares in file chooser

[Colin Leroy]

Public bug reported:

GTK+3 doesn't show FUSE network shares in file chooser - it used to do
so in GTK+2, and the GTK+3 documentation still mentions it should do it.

In the mean time, every user of every application switching to GTK+3 --
including Chromium, at some point between 58 and 60 -- (a change which
happened in 16.04 LTS!!), loses the functionality to open or save
directly to a network share.

I had chosen 16.04 LTS for deploying our workstations at work, and my
users have been suddenly unable to do a simple operation they have to do
dozens of times a day.

I have reported the bug upstream and provided a patch to fix this. I
hope you'll be able and willing to include it to Ubuntu's GTK+3 package.

Thanks in advance.

Colin

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

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

Title:
  GTK+3 doesn't show FUSE network shares in file chooser

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my
  users have been suddenly unable to do a simple operation they have to
  do dozens of times a day.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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

[Touch-packages] [Bug 1714519] [NEW] Typo Todoist

[Olivier Febwin]

Public bug reported:

https://translations.launchpad.net/ubuntu/artful/+source/gnome-online-
accounts/+pots/gnome-online-accounts/fr/112/+translate

I think it's Todolist and not Todoist

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Typo Todoist

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  https://translations.launchpad.net/ubuntu/artful/+source/gnome-online-
  accounts/+pots/gnome-online-accounts/fr/112/+translate

  I think it's Todolist and not Todoist

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

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

[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE network shares in file chooser

[Colin Leroy]

Here's the patch.
It's also been provided upstream at 
https://bugzilla.gnome.org/show_bug.cgi?id=787128


** Patch added: "gtk_3_fix_fuse_mounts.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1714518/+attachment/4942427/+files/gtk_3_fix_fuse_mounts.patch

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

Title:
  GTK+3 doesn't show FUSE network shares in file chooser

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my
  users have been suddenly unable to do a simple operation they have to
  do dozens of times a day.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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

[Touch-packages] [Bug 1714505] [NEW] systemd kmod builtin uses out of date kmod context

[Dan Streetman]

Public bug reported:

[Impact]

udev's rules use a built-in 'kmod' instead of the system
modprobe/insmod, and this built-in kmod only validates/refreshes its
kmod 'context' every 3 seconds (or longer) during event processing.

However, because other parts of the system rely on udev to load modules
correctly, it is not acceptable for it to use an out of date module
context.  For example, during a system installation:

-the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
-udevd starts, and creates its kmod module context, which does not include nvme 
module
-system installer adds 'block-modules' udeb, which adds nvme module to system
-system installer immediately calls hw-detect->update-dev->udevadm trigger
-udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
-udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
-udevd kmod builtin does not find NVMe pci modalias because its context is out 
of date

this results in the system installer complaining to the user that it
found no disks, even though there is a NVMe drive in the system, and the
nvme module is installed in the system.

[Test Case]

This is reproducable when trying to install using debian-installer and a
preseed file that skips all questions, although not on all systems,
since other events can cause udevd to reload all its builtins, or the
installer may take longer than 3 seconds to call udevadm trigger after
installing the nvme module udeb.

However, the bug is easily reproducable on any system with a nvme drive
using this script:

#!/bin/bash
MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
modprobe -rq nvme
mv $MOD_DIR/nvme.ko .
depmod -a
sleep 3
udevadm trigger
sleep 1
mv nvme.ko $MOD_DIR/
depmod -a
udevadm trigger
sleep 3
grep -q nvme /proc/partitions && echo PASS || echo FAIL

that script does:
1) remove nvme module from the system, reproducing situation where nvme module 
had not yet been installed
2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
6) wait 3 seconds for udev trigger to finish (plenty of time), and check if the 
nvme module was loaded

this script reproduces the error every time, due to the stale kmod
context.  With a fixed udev, this should succeed in loading the nvme
module.

[Regression Potential]

The most potential for regression with a fix to this involves slowing
down udev due to validating the kmod context for every kmod load call.
However, slightly higher performance does not make up for broken
operation.

[Other Info]

This needs fixing upstream, which I'm in progress on.

** Affects: systemd (Ubuntu)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

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

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable 

[Touch-packages] [Bug 1714019] Re: Please merge unattended-upgrades 0.96 (main) from Debian unstable (main)

[Balint Reczey]

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Please merge unattended-upgrades 0.96 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I'm also asking for a Feature Freeze Exception following the rules for
  new upstream version per
  https://wiki.ubuntu.com/FreezeExceptionProcess.

  [Reason]
  Unattended-upgrades is planned to be enabled by default but the versions 
present in Ubuntu can break the system by not protecting the upgrade process 
from termination during shutdown (see LP: #1690980).
  The newer version in Debian fixes the shutdown-related issue and contains 
several additional reliability and debuggability fixes.

  [Logs]
  They are attached to this bug.

  [Testing]
  The autopkgtest log is attached and I also tested the version in Debian 
several times while preparing the fixes for various bugs.

  Note that the package in the PPA does not close this bug from the
  changelog while the patches attaches do.

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

-- 
Mailing list: https://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 1714019] Re: Please merge unattended-upgrades 0.96 (main) from Debian unstable (main)

[Balint Reczey]

On Fri, Sep 1, 2017 at 2:07 AM, Steve Langasek
 wrote:
> https://bugs.launchpad.net/ubuntu/+source/unattended-
> upgrades/+bug/1714019/+attachment/4942097/+files/unattended-
> upgrades_0.93.1ubuntu8-to-0.96ubuntu1.patch appears to be a reversed
> patch, and doesn't have a changelog entry for 0.96ubuntu1.

I have fixed the patch it was reversed indeed, but contains the
changelog, just not at the beginning like it is usual for diffs.

>
> Which parts of this change is it that you believe violate feature freeze
> and require an FFe?  (Bugfixes do not require an FFe.)

There are some changes which don't fix bugs but can be seen as
improvements, like:
   * Update the signal used to SIGTERM in the documentation
   * Fix incorrect example for Update-Days.
   * add pep484 type hints
  ...

I also prefer being cautious and asking for such permissions even they
may not be strictly required.

>
> If an FFe is required for the merge, why do a merge rather than cherry-
> picking of the specific bugfix changes?

The part which would be cherry-picked is like ~90% of the changes if
we want to have u-u be in a reasonably good shape in Ubuntu and having
the big delta was painful enough to maintain already.

I aimed at having a sync but dropping/integrating LP: #1649709 needs
more discussion at least with infinity, it seems.
See: https://irclogs.ubuntu.com/2017/08/01/%23ubuntu-devel.html ,
starting from 11:06

>
> >From NEWS.Debian, I understand that a key change is to turn on the
> minimal steps handling by default.  What is the impact of this change on
> the time it takes to do a typical update?  Are we in any way increasing

I have not tested the additional time because without enabling minimal
steps u-u can't be stopped gracefully after it started the actual
upgrade.
Thus i saw no decision point here.
It is worth measuring the impact and checking if we can speed u-u up
in that area, but IMO this optimization should not delay the
acceptance of this upload.

> the risk of an unclean shutdown due to a laptop running out of battery
> during the upgrade, where this wouldn't have happened if we weren't
> doing minimal steps?

When InstallOnShutdown not set apt-daily-upgrade.service does not run
u-u when running on battery:
http://sources.debian.net/src/apt/1.5%7Ebeta2/debian/apt-daily-upgrade.service/#L4

When InstallOnShutdown is set this is a valid concern and thank you
for raising it.
I've just prepared a fix to mitigate this risk:
https://github.com/mvo5/unattended-upgrades/pull/75/commits/fd65bb54556624aacac5212d9d21e3a66df251c3
>
> debian/postinst changes the minimum version at which installinit upgrade
> handling is applied, and will be reapplied to systems which have the
> existing artful package installed.  Could this be a problem?  E.g., does
> this forcibly override the user's preference on upgrade if they have
> disabled the service in systemd?

I have not changed the version check compared to 0.93.1ubuntu8, thus I
see no problem in this area related to FFe.

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

Title:
  Please merge unattended-upgrades 0.96 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  I'm also asking for a Feature Freeze Exception following the rules for
  new upstream version per
  https://wiki.ubuntu.com/FreezeExceptionProcess.

  [Reason]
  Unattended-upgrades is planned to be enabled by default but the versions 
present in Ubuntu can break the system by not protecting the upgrade process 
from termination during shutdown (see LP: #1690980).
  The newer version in Debian fixes the shutdown-related issue and contains 
several additional reliability and debuggability fixes.

  [Logs]
  They are attached to this bug.

  [Testing]
  The autopkgtest log is attached and I also tested the version in Debian 
several times while preparing the fixes for various bugs.

  Note that the package in the PPA does not close this bug from the
  changelog while the patches attaches do.

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

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

[Touch-packages] [Bug 1714493] [NEW] package util-linux 2.29-1ubuntu2 failed to install/upgrade: Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie przed próbą jego skonfigurowania.

[Artur]

Public bug reported:

not working

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: util-linux 2.29-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering:
 util-linux:amd64: Configure
 python3-jwt:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Sep  1 14:01:58 2017
DpkgHistoryLog:
 Start-Date: 2017-09-01  14:01:56
 Commandline: /usr/bin/unattended-upgrade
 Upgrade: python3-jwt:amd64 (1.4.2-1, 1.4.2-1ubuntu0.1)
DpkgTerminalLog:
 dpkg: błąd przetwarzania pakietu util-linux (--configure):
  Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie
  przed próbą jego skonfigurowania.
ErrorMessage: Pakiet jest w złym stanie - powinien zostać zainstalowany 
ponownie  przed próbą jego skonfigurowania.
InstallationDate: Installed on 2017-02-23 (190 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 util-linux 2.29-1ubuntu2 failed to install/upgrade: Pakiet jest 
w złym stanie - powinien zostać zainstalowany ponownie  przed próbą jego 
skonfigurowania.
UpgradeStatus: Upgraded to zesty on 2017-04-18 (136 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/1714493

Title:
  package util-linux 2.29-1ubuntu2 failed to install/upgrade: Pakiet
  jest w złym stanie - powinien zostać zainstalowany ponownie  przed
  próbą jego skonfigurowania.

Status in util-linux package in Ubuntu:
  New

Bug description:
  not working

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   util-linux:amd64: Configure
   python3-jwt:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Sep  1 14:01:58 2017
  DpkgHistoryLog:
   Start-Date: 2017-09-01  14:01:56
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: python3-jwt:amd64 (1.4.2-1, 1.4.2-1ubuntu0.1)
  DpkgTerminalLog:
   dpkg: błąd przetwarzania pakietu util-linux (--configure):
Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie
przed próbą jego skonfigurowania.
  ErrorMessage: Pakiet jest w złym stanie - powinien zostać zainstalowany 
ponownie  przed próbą jego skonfigurowania.
  InstallationDate: Installed on 2017-02-23 (190 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 util-linux 2.29-1ubuntu2 failed to install/upgrade: Pakiet 
jest w złym stanie - powinien zostać zainstalowany ponownie  przed próbą jego 
skonfigurowania.
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (136 days ago)

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

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

[Touch-packages] [Bug 1714282] Re: Sorry something went wrong GDBus:

[bravoure]

** Description changed:

  After applying the latest update the Software-center now opens but still
  has a problem.
  
  For the Launch pad, software center, in Ubuntu 17.10 it reports this error 
when trying to open it.
  "Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown 
Method: No such
  interface` org.gnome.Shell.Extensions on object at path /org/gnome/shell".
+ 
+ Some of the links to the software doesn't work.
+ Some of the buttons of categories doesn't work.
+ Updates never show "software to be updated" anymore

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

Title:
  Sorry something went wrong GDBus:

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After applying the latest update the Software-center now opens but
  still has a problem.

  For the Launch pad, software center, in Ubuntu 17.10 it reports this error 
when trying to open it.
  "Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown 
Method: No such
  interface` org.gnome.Shell.Extensions on object at path /org/gnome/shell".

  Some of the links to the software doesn't work.
  Some of the buttons of categories doesn't work.
  Updates never show "software to be updated" anymore

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

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

[Touch-packages] [Bug 1714019] Re: Please merge unattended-upgrades 0.96 (main) from Debian unstable (main)

[Balint Reczey]

** Patch added: "Proper forward debdiff from 0.93.1ubuntu8"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1714019/+attachment/4942314/+files/unattended-upgrades_0.93.1ubuntu8-to-0.96ubuntu1-proper.patch

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

Title:
  Please merge unattended-upgrades 0.96 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  I'm also asking for a Feature Freeze Exception following the rules for
  new upstream version per
  https://wiki.ubuntu.com/FreezeExceptionProcess.

  [Reason]
  Unattended-upgrades is planned to be enabled by default but the versions 
present in Ubuntu can break the system by not protecting the upgrade process 
from termination during shutdown (see LP: #1690980).
  The newer version in Debian fixes the shutdown-related issue and contains 
several additional reliability and debuggability fixes.

  [Logs]
  They are attached to this bug.

  [Testing]
  The autopkgtest log is attached and I also tested the version in Debian 
several times while preparing the fixes for various bugs.

  Note that the package in the PPA does not close this bug from the
  changelog while the patches attaches do.

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

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

[Touch-packages] [Bug 413846] Re: gnome-appearance-properties crashed with SIGSEGV in pango_context_get_matrix()

[Bug Watch Updater]

** Changed in: pango
   Status: New => Expired

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

Title:
  gnome-appearance-properties crashed with SIGSEGV in
  pango_context_get_matrix()

Status in Pango:
  Expired
Status in pango1.0 package in Ubuntu:
  Incomplete

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

  I dragged a .tar.gz archive containing a theme from a nautilus window
  to the gnome-appearence-manager to install it. It installed just fine
  when I tried to install it by clicking the "Install" button
  afterwards.

  ProblemType: Crash
  Architecture: i386
  Date: Sat Aug 15 01:28:32 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gnome-appearance-properties
  Package: gnome-control-center 1:2.27.5-0ubuntu1
  ProcCmdline: gnome-appearance-properties
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_DK.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
  SegvAnalysis:
   Segfault happened at: 0x1933df :mov
(%esi),%edx
   PC (0x001933df) ok
   source "(%esi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   pango_context_get_matrix () from /usr/lib/libpango-1.0.so.0
   gdk_draw_layout_with_colors ()
   gdk_draw_layout () from /usr/lib/libgdk-x11-2.0.so.0
   ?? () from /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so
   gtk_paint_layout () from /usr/lib/libgtk-x11-2.0.so.0
  Title: gnome-appearance-properties crashed with SIGSEGV in 
pango_context_get_matrix()
  Uname: Linux 2.6.31-3-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

[Celberune]

It's working ! It's working ! Great Thx to Robert Joynt's fix !
so many hours spent on this creepy sound...
Linux is a pain to configure...
And after it's magic to use.
Windows is magic to configure... and after a pain to use ;-)

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

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

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

[Touch-packages] [Bug 1714458] [NEW] [HP Spectre x360 Convertible 13-ac0XX, Realtek ALC295, Speaker, Internal] Underruns, dropouts or crackling sound

[BENOIT COURTILLY]

Public bug reported:

creepy sound, not so much, but quiet poor quality and some underruns
occur

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  benoit10519 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Fri Sep  1 11:28:38 2017
InstallationDate: Installed on 2017-08-06 (25 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Audio interne - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [HP Spectre x360 Convertible 13-ac0XX, Realtek ALC295, Speaker, 
Internal] Underruns, dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.34
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 827E
dmi.board.vendor: HP
dmi.board.version: 94.60
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.34:bd06/26/2017:svnHP:pnHPSpectrex360Convertible13-ac0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion:
dmi.product.name: HP Spectre x360 Convertible 13-ac0XX
dmi.sys.vendor: HP

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
  [HP Spectre x360 Convertible 13-ac0XX, Realtek ALC295, Speaker,
  Internal] Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  creepy sound, not so much, but quiet poor quality and some underruns
  occur

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benoit10519 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Sep  1 11:28:38 2017
  InstallationDate: Installed on 2017-08-06 (25 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [HP Spectre x360 Convertible 13-ac0XX, Realtek ALC295, Speaker, 
Internal] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.34
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.60
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.34:bd06/26/2017:svnHP:pnHPSpectrex360Convertible13-ac0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion:
  dmi.product.name: HP Spectre x360 Convertible 13-ac0XX
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1714282] Re: Sorry something went wrong GDBus:

[Launchpad Bug Tracker]

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

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

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

Title:
  Sorry something went wrong GDBus:

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After applying the latest update the Software-center now opens but
  still has a problem.

  For the Launch pad, software center, in Ubuntu 17.10 it reports this error 
when trying to open it.
  "Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown 
Method: No such
  interface` org.gnome.Shell.Extensions on object at path /org/gnome/shell".

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

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

[Touch-packages] [Bug 1714282] Re: Sorry something went wrong GDBus:

[L Anthonis]

** Description changed:

  After applying the latest update the Software-center now opens but still
  has a problem.
  
  For the Launch pad, software center, in Ubuntu 17.10 it reports this error 
when trying to open it.
  "Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown 
Method: No such
- interface` org.gnome.Shell.Extension on object at path /org/gnome/shell".
+ interface` org.gnome.Shell.Extensions on object at path /org/gnome/shell".

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

Title:
  Sorry something went wrong GDBus:

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After applying the latest update the Software-center now opens but
  still has a problem.

  For the Launch pad, software center, in Ubuntu 17.10 it reports this error 
when trying to open it.
  "Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown 
Method: No such
  interface` org.gnome.Shell.Extensions on object at path /org/gnome/shell".

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

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

[Touch-packages] [Bug 1706558] Re: Japanese Input Method doesn't work by default in Ubuntu 17.10 daily build.

[allstars]

Can we know when the decision will be made?
Or is there a bug tracking this (using ibus or fcitx)?

Thanks

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

Title:
  Japanese Input Method doesn't work by default in Ubuntu 17.10 daily
  build.

Status in ibus package in Ubuntu:
  Invalid
Status in mozc package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I installed Ubuntu Desktop 17.10 daily build (selected Japanese
  Language), but ibus-mozc (Japanese Input Method) is not installed when
  installing Ubuntu 17.10 daily build.

  Fcitx and fcitx-mozc are installed when installing Ubuntu 17.10 daily build.
  But the default is ibus.

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

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

[Touch-packages] [Bug 1714442] [NEW] “Are you sure you want to proceed?” message at login

[Matpen]

Public bug reported:

Right after logging in to the Ubuntu desktop environment, a message like
the one in the attached screenshot appears. I researched the cause and
found several links (see [1] and [2] below) pointing to the cause: a
command in either .bashrc, .profile or /etc/profile.d outputs to stdout.
The solution is then to silence the command by redirecting its output.

However, this bug report is about the "unhelpfulness" of the popup
message. As you can see, the window has no border, and at that stage,
the system is not fully logged in yet, so there is no way to interact
with it. Moreover, the message reads "are you sure you want to proceed?"
but the only possible answer is "OK".

That leaves the user with no clue about how to fix the annoying message,
that will appear at every login. I think it should be improved by
providing pointers to the problem cause.

Note that this bug was reported in [3] already, but since it was filed
against the wrong package, it was marked as invalid. Therefore it still
persist in 16.04, although being found at least in 14.04.

Additional info:
1) OS: Ubuntu 16.04.3 LTS
2) lightdm: 1.18.3-0ubuntu1.1 

Reference links:
[1] 
https://askubuntu.com/questions/587868/are-you-sure-you-want-to-proceed-message-on-login
[2] 
https://askubuntu.com/questions/603328/are-you-sure-you-want-to-proceed-on-login
[3] https://bugs.launchpad.net/fuel/+bug/1428341

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Sep  1 10:07:59 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-12-02 (638 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: lightdm
UpgradeStatus: Upgraded to xenial on 2016-06-05 (452 days ago)

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


** Tags: amd64 apport-bug third-party-packages xenial

** Attachment added: "Pop-up window"
   
https://bugs.launchpad.net/bugs/1714442/+attachment/4942231/+files/message.jpg

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

Title:
  “Are you sure you want to proceed?” message at login

Status in lightdm package in Ubuntu:
  New

Bug description:
  Right after logging in to the Ubuntu desktop environment, a message
  like the one in the attached screenshot appears. I researched the
  cause and found several links (see [1] and [2] below) pointing to the
  cause: a command in either .bashrc, .profile or /etc/profile.d outputs
  to stdout. The solution is then to silence the command by redirecting
  its output.

  However, this bug report is about the "unhelpfulness" of the popup
  message. As you can see, the window has no border, and at that stage,
  the system is not fully logged in yet, so there is no way to interact
  with it. Moreover, the message reads "are you sure you want to
  proceed?" but the only possible answer is "OK".

  That leaves the user with no clue about how to fix the annoying
  message, that will appear at every login. I think it should be
  improved by providing pointers to the problem cause.

  Note that this bug was reported in [3] already, but since it was filed
  against the wrong package, it was marked as invalid. Therefore it
  still persist in 16.04, although being found at least in 14.04.

  Additional info:
  1) OS: Ubuntu 16.04.3 LTS
  2) lightdm: 1.18.3-0ubuntu1.1 

  Reference links:
  [1] 
https://askubuntu.com/questions/587868/are-you-sure-you-want-to-proceed-message-on-login
  [2] 
https://askubuntu.com/questions/603328/are-you-sure-you-want-to-proceed-on-login
  [3] https://bugs.launchpad.net/fuel/+bug/1428341

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep  1 10:07:59 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-02 (638 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. 

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Markus Ketterl]

I have the problem too. After the dhcp lease is expired the avahi-daemon
or something else doesn't renew the dhcp lease. It helps to request an
ip address manually:

# sudo dhclient 
sudo dhclient enp3s0

Configure the lease time on your dhcp server to 86400 seconds (one day)
and it should help the most of us to work without problems for a day.
But it doesn't solve the problem.

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

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

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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

[Touch-packages] [Bug 1714431] [NEW] Can not login after switch to runlevel 3 from 1

[Ike Panhc]

Public bug reported:

No login prompt or anything on console after switch to runlevel 3/5 from
1

Step to reproduce
1) Make sure root password is set
2) login as root on console
3) `init 1` switch to runlevel 1
4) login again as root
5) `init 3` or `init 5` and no login or prompt

root@D05-2:~# init 1
root@D05-2:~# 
Ubuntu 16.04.3 LTS D05-2 ttyAMA0

D05-2 login: root 
System is going down.

Password: 
Last login: Fri Sep  1 07:28:04 UTC 2017 on ttyAMA0
Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.10.0-33-generic aarch64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

  Get cloud support with Ubuntu Advantage Cloud Guest:
http://www.ubuntu.com/business/services/cloud

0 packages can be updated.
0 updates are security updates.


root@D05-2:~# init 5
[  103.499358] cloud-init[4497]: Cloud-init v. 0.7.9 running 'init-local' at 
Fri, 01 Sep 2017 07:28:40 +. Up 103.12 seconds.

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

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

Title:
  Can not login after switch to runlevel 3 from 1

Status in systemd package in Ubuntu:
  New

Bug description:
  No login prompt or anything on console after switch to runlevel 3/5
  from 1

  Step to reproduce
  1) Make sure root password is set
  2) login as root on console
  3) `init 1` switch to runlevel 1
  4) login again as root
  5) `init 3` or `init 5` and no login or prompt

  root@D05-2:~# init 1
  root@D05-2:~# 
  Ubuntu 16.04.3 LTS D05-2 ttyAMA0

  D05-2 login: root 
  System is going down.

  Password: 
  Last login: Fri Sep  1 07:28:04 UTC 2017 on ttyAMA0
  Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.10.0-33-generic aarch64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

Get cloud support with Ubuntu Advantage Cloud Guest:
  http://www.ubuntu.com/business/services/cloud

  0 packages can be updated.
  0 updates are security updates.

  
  root@D05-2:~# init 5
  [  103.499358] cloud-init[4497]: Cloud-init v. 0.7.9 running 'init-local' at 
Fri, 01 Sep 2017 07:28:40 +. Up 103.12 seconds.

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

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

[Touch-packages] [Bug 1714429] [NEW] hang on shutdown with static network configuration

[Aaron Brülisauer]

Public bug reported:

Hi Folks


Problem:

system doesn't reboot/shutdown but *only* when the network configuration
is static (described below). When I change the network configuration to
dhcp, the bug doesn't occur.


The network configuration is set to static:

iface eth0 inet static
  address my_ip
  netmask 255.255.255.224
  gateway router_ip
  dns-nameservers primary_dns secondary_dns 8.8.8.8 8.8.4.4
(I have masked some configuration values)


lsb_release -rd
Release:16.04


apt-cache policy unattended-upgrades
Installed: 0.90ubuntu0.7
Candidate: 0.90ubuntu0.7


symptoms:

a python3 process appears ~2sec after the shutdown command: 2005 python3
/usr/share/unattended-upgrades/unattended-upgrade-shutdown

Screenshot of the VM virtual display output as attachment.

only / is mounted, all other file systems are unmounted already: /boot,
/var, /tmp, /var/log, /var/tmp


other informations:

The network still works. I can ping different addresses like google.com,
debian.org, and other stuff.

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

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1714429/+attachment/4942217/+files/Screenshot_20170901_085822.png

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

Title:
  hang on shutdown with static network configuration

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Hi Folks


  Problem:

  system doesn't reboot/shutdown but *only* when the network
  configuration is static (described below). When I change the network
  configuration to dhcp, the bug doesn't occur.


  The network configuration is set to static:

  iface eth0 inet static
address my_ip
netmask 255.255.255.224
gateway router_ip
dns-nameservers primary_dns secondary_dns 8.8.8.8 8.8.4.4
  (I have masked some configuration values)


  lsb_release -rd
  Release:16.04


  apt-cache policy unattended-upgrades
  Installed: 0.90ubuntu0.7
  Candidate: 0.90ubuntu0.7


  symptoms:

  a python3 process appears ~2sec after the shutdown command: 2005
  python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown

  Screenshot of the VM virtual display output as attachment.

  only / is mounted, all other file systems are unmounted already:
  /boot, /var, /tmp, /var/log, /var/tmp


  other informations:

  The network still works. I can ping different addresses like
  google.com, debian.org, and other stuff.

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

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

[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot

[Paul Gear]

@Robie The ntpdate command has a test mode that does not attempt to set
the clock, which the sntp command lacks.

I've confirmed on multiple systems that the installation of ntpdate
prevents ntp from starting on boot, which IMO is worthy of fixing.

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

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

Title:
  mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race
  leaving ntp dead on reboot

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  New
Status in ntp package in Debian:
  Fix Released

Bug description:
  ntpdate and ntp conflict on the NTP well-known-socket. If ntp and
  ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there
  are 2 static interfaces configured, most often we find that ntpd is
  not running after a reboot.

  When the ntp service is started by systemd, ntp fails to bind the NTP
  socket because ntpdate is running in the background. It's intended
  that ntp and ntpdate try to avoid this conflict with a lock file, but
  the locking mechanism was changed in ntpdate.if-up (from lockfile to
  flock), but it was not changed in ntp.init. Previously the file
  locking prevented ntp from trying to start when ntpdate was running.
  Not any more.

  Having multiple interfaces causes a much longer period of the socket
  being unavailable, because the 2 ntpdate processes will get serialized
  by the lock, while the ntp service is looking for a different lock, so
  it just plows right in.  Attempts by netdate.if-up to stop and start
  ntp seem to overlap and when the final start is invoked, systemd seems
  to thing ntp is already running, though it has failed.

  In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made:
debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock 
now.
  Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream.

  This change diverged locking between ntpdate.if-up and ntp.init. This
  was rectified in rev 451 of ntp.init, to use compatible locking, but
  that doesn't appear in the Ubuntu version.

  
  System Information:

   lsb_release -rd:
 Description:Ubuntu 16.04.2 LTS
 Release:16.04

  
   apt-cache policy ntpdate:

 ntpdate:
   Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
   Version table:
  *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
 100 /var/lib/dpkg/status

   apt-cache policy ntp:

 ntp:
   Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
   Version table:
  *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
 100 /var/lib/dpkg/status

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

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