date:20180903

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

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  New
Status in console-setup source package in Bionic:
  Fix Released
Status in ubiquity source package in Bionic:
  New

Bug description:
  [ SRU Justification ]
  Due to my brain being in the wrong language, a function was exiting the 
script instead of returning.  Derp.

  [ Regression Potential ]
  N'much.

  [ Test Case ]
  Build a new ubiquity and see if we can haz keyboard again.

  [ Original Bug ]
  Since this version of console-setup in bionic ubiquity now skips the Keyboard 
and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

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

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

[Touch-packages] [Bug 1788597] Update Released

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

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  New
Status in console-setup source package in Bionic:
  Fix Released
Status in ubiquity source package in Bionic:
  New

Bug description:
  [ SRU Justification ]
  Due to my brain being in the wrong language, a function was exiting the 
script instead of returning.  Derp.

  [ Regression Potential ]
  N'much.

  [ Test Case ]
  Build a new ubiquity and see if we can haz keyboard again.

  [ Original Bug ]
  Since this version of console-setup in bionic ubiquity now skips the Keyboard 
and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

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

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

[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5

This bug was fixed in the package console-setup - 1.178ubuntu2.7

---
console-setup (1.178ubuntu2.7) bionic; urgency=medium

  * keyboard-configuration.config: Fix exit/return thinko (LP: #1788597)

 -- Adam Conrad   Thu, 23 Aug 2018 16:32:45 -0600

** Changed in: console-setup (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  New
Status in console-setup source package in Bionic:
  Fix Released
Status in ubiquity source package in Bionic:
  New

Bug description:
  [ SRU Justification ]
  Due to my brain being in the wrong language, a function was exiting the 
script instead of returning.  Derp.

  [ Regression Potential ]
  N'much.

  [ Test Case ]
  Build a new ubiquity and see if we can haz keyboard again.

  [ Original Bug ]
  Since this version of console-setup in bionic ubiquity now skips the Keyboard 
and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

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

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

[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5

I guess we need an ubiquity rebuild with the new console-setup now.

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  New
Status in console-setup source package in Bionic:
  Fix Released
Status in ubiquity source package in Bionic:
  New

Bug description:
  [ SRU Justification ]
  Due to my brain being in the wrong language, a function was exiting the 
script instead of returning.  Derp.

  [ Regression Potential ]
  N'much.

  [ Test Case ]
  Build a new ubiquity and see if we can haz keyboard again.

  [ Original Bug ]
  Since this version of console-setup in bionic ubiquity now skips the Keyboard 
and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

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

-- 
Mailing list: https://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 1244285] Re: Date/time sometimes doesn’t appear in menu bar, settings greyed out

2018-09-03 Thread Jarosław Bartkowiak

No, it doesn't. I don't remember when I saw it last.

W dniu 2018-08-28 o 18:01, Colin Law pisze:
> Does this bug still manifest itself?  It is years old. I have not seen
> the problem since several Ubuntu versions ago.
>

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

Title:
  Date/time sometimes doesn’t appear in menu bar, settings greyed out

Status in One Hundred Papercuts:
  Triaged
Status in Indicator Date and Time:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  it does not happen often, and when it happens, just a log out and re-
  log in is enough to restore it.

  http://askubuntu.com/questions/357266/how-to-show-time-in-
  ubuntu-13-10/357280

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

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

[Touch-packages] [Bug 1762384] Update Released

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

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

Title:
  libgpgme-dev installs libgpgme-pthread.so in
  /usr/lib/${DEB_HOST_MULTIARCH}, literally

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  In Bionic, libgpgme-pthread.so it is installed in 
/usr/lib/${DEB_HOST_MULTIARCH} instead of /usr/lib/x86_64-linux-gnu (the 
variable is not replaced)

  [Test case]
  Check that package installs to correct location

  [Regression potential]
  Packages looking for libgpgme-pthread find it now and might enable gpgme when 
they did not.

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

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

[Touch-packages] [Bug 1762384] Re: libgpgme-dev installs libgpgme-pthread.so in /usr/lib/${DEB_HOST_MULTIARCH}, literally

This bug was fixed in the package gpgme1.0 - 1.10.0-1ubuntu2

---
gpgme1.0 (1.10.0-1ubuntu2) bionic; urgency=medium

  * Make debian/libgpgme-dev.links executable, it uses dh-exec (LP: #1762384)
  * Drop python3.5 test since python3.5 is not supported (fixes autopkgtest)

 -- Julian Andres Klode   Tue, 14 Aug 2018 16:53:39
+0200

** Changed in: gpgme1.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  libgpgme-dev installs libgpgme-pthread.so in
  /usr/lib/${DEB_HOST_MULTIARCH}, literally

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  In Bionic, libgpgme-pthread.so it is installed in 
/usr/lib/${DEB_HOST_MULTIARCH} instead of /usr/lib/x86_64-linux-gnu (the 
variable is not replaced)

  [Test case]
  Check that package installs to correct location

  [Regression potential]
  Packages looking for libgpgme-pthread find it now and might enable gpgme when 
they did not.

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

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

[Touch-packages] [Bug 1722185] Re: Crash installing packages using debconf

This bug was fixed in the package packagekit - 1.1.9-1ubuntu2.18.04.1

---
packagekit (1.1.9-1ubuntu2.18.04.1) bionic; urgency=medium

  * debian/patches/0001-De-register-callbacks-on-PkClientHelper-finalize.patch:
  * debian/patches/0001-Fix-issues-with-debconf-helper-not-working.patch:
- Fix debconf interaction (LP: #1722185)

 -- Robert Ancell   Mon, 21 May 2018
14:39:14 +1200

** Changed in: packagekit (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Crash installing packages using debconf

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Installing .deb package via PackageKit (e.g. using GNOME Software) don't work 
reliably when the packages use debconf. This is due to a faulty implementation 
of debconf handling in PackageKit.

  [Test Case]
  1. Download opera deb file from opera.com
  2. Run the file to launch gnome-software
  3. Install it
  4. Proceed with the debconf prompt

  Expected result:
  A debconf dialog appears asking if you want to "update Opera with the rest of 
the system?". The dialog closes when completed and the package is installed.

  Actual result:
  The dialog shows, but never closes and becomes unresponsive. Force closing 
the dialog causes a crash.

  [Regression Potential]
  The change is quite large, so there is a reasonable chance of introducing new 
bugs in debconf handling. However, the existing code has some obviously wrong 
codepaths, so the new code is probably a lower risk than the existing code.

  Crash reports:
  https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad

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

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

[Touch-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]

** Summary changed:

- Xwayland crashed with SIGABRT in st_renderbuffer_delete()
+ Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running 
Skype or Slack snaps]

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

Title:
  Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when
  running Skype or Slack snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 16 18:18:18 2017
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  x

[Touch-packages] [Bug 1722185] Update Released

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

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

Title:
  Crash installing packages using debconf

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Installing .deb package via PackageKit (e.g. using GNOME Software) don't work 
reliably when the packages use debconf. This is due to a faulty implementation 
of debconf handling in PackageKit.

  [Test Case]
  1. Download opera deb file from opera.com
  2. Run the file to launch gnome-software
  3. Install it
  4. Proceed with the debconf prompt

  Expected result:
  A debconf dialog appears asking if you want to "update Opera with the rest of 
the system?". The dialog closes when completed and the package is installed.

  Actual result:
  The dialog shows, but never closes and becomes unresponsive. Force closing 
the dialog causes a crash.

  [Regression Potential]
  The change is quite large, so there is a reasonable chance of introducing new 
bugs in debconf handling. However, the existing code has some obviously wrong 
codepaths, so the new code is probably a lower risk than the existing code.

  Crash reports:
  https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad

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

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

[Touch-packages] [Bug 1790458] [NEW] Update gnome-online-accounts to 3.30.0

2018-09-03 Thread Andrea Azzarone

Public bug reported:

Update gnome-online-accounts to 3.30.0

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Wishlist
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress


** Tags: upgrade-software-version

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

** Changed in: gnome-online-accounts (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  Update gnome-online-accounts to 3.30.0

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  Update gnome-online-accounts to 3.30.0

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

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

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

2018-09-03 Thread Roman Fiedler

This is the failing "swapon" sequence from updated Xenial i386 on
vmware:

3915  open("/dev/sda2", O_RDONLY|O_LARGEFILE) = 3
3915  uname({sysname="Linux", nodename="v3ls1717", ...}) = 0
3915  ioctl(3, BLKGETSIZE64, [535822336]) = 0
3915  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
 65536) = 65536
3915  close(3)  = 0
3915  swapon("/dev/sda2", 0)= -1 EINVAL (Invalid argument)

Sequence is identical to other, native/amd64 system with same kernel
version but without the problem where swapon() will return 0.

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

Title:
  swapon failed: invalid argument

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

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

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

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

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

  Regards.

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

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

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

2018-09-03 Thread Trent Lloyd

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

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  Fix Released
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid
Status in avahi source package in Bionic:
  Fix Committed
Status in bind9 source package in Bionic:
  Confirmed
Status in avahi source package in Cosmic:
  Fix Released
Status in bind9 source package in Cosmic:
  Confirmed
Status in avahi package in Debian:
  New

Bug description:
  [Impact]

   * Network connections for some users fail (in some cases a direct
  interface, in others when connecting a VPN) because the 'host' command
  to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-
  check-dns.sh never times out like it should - leaving the script
  hanging indefinitely blocking interface up and start-up. This appears
  to be a bug in host caused in some circumstances however we implement
  a workaround to call it under 'timeout' as the issue with 'host' has
  not easily been identified, and in any case acts as a fall-back.

  [Test Case]

   * Multiple people have been unable to create a reproducer on a
  generic machine (e.g. it does not occur in a VM), I have a specific
  machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM)
  by simply "ifdown br0; ifup br0" and there are clearly 10s of other
  users affected in varying circumstances that all involve the same
  symptoms but no clear test case exists. Best I can suggest is that I
  test the patch on my system to ensure it works as expected, and the
  change is only 1 line which is fairly easily auditible and
  understandable.

  [Regression Potential]

   * The change is a single line change to the shell script to call host with 
"timeout". When tested on working and non-working system this appears to 
function as expected. I believe the regression potential for this is 
subsequently low.
   * In attempt to anticipate possible issues, I checked that the timeout 
command is in the same path (/usr/bin) as the host command that is already 
called without a path, and the coreutils package (which contains timeout) is an 
Essential package. I also checked that timeout is not a built-in in bash, for 
those that have changed /bin/sh to bash (just in case).

  [Other Info]
   
   * N/A

  [Original Bug Description]

  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:11:33 2018
  InstallationDate: Installed on 2017-06-15 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: openconnect
  UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago)

To manage notifications about

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

2018-09-03 Thread Trent Lloyd

Confirmed the fix works on my affected system, after upgrade to
0.7-3.1ubuntu1.1 from bionic-proposed and a system reboot the boot works
(relatively) quickly as expected and doesn't get stuck.

Verified the file in place is the original from the package (and not one
modified by me).

Lastly to further verify it was the timeout and not some other change, I
changed the timeout from 5 to 17 (to make the time taken more obvious)
and rebooted and compared the time spent in network.service with
systemd-analyze which changed from 18 seconds (with timeout=5) to
30.368s (with timeout=17). Which is roughly an additional 12 seconds as
expected. And also observed the time before SSH was ready to take that
much extra.

Looks good to me, changed the bionic verification tag to done but left
'verification-needed'.

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

** Changed in: avahi (Ubuntu Bionic)
 Assignee: (unassigned) => Trent Lloyd (lathiat)

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  Fix Released
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid
Status in avahi source package in Bionic:
  Fix Committed
Status in bind9 source package in Bionic:
  Confirmed
Status in avahi source package in Cosmic:
  Fix Released
Status in bind9 source package in Cosmic:
  Confirmed
Status in avahi package in Debian:
  New

Bug description:
  [Impact]

   * Network connections for some users fail (in some cases a direct
  interface, in others when connecting a VPN) because the 'host' command
  to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-
  check-dns.sh never times out like it should - leaving the script
  hanging indefinitely blocking interface up and start-up. This appears
  to be a bug in host caused in some circumstances however we implement
  a workaround to call it under 'timeout' as the issue with 'host' has
  not easily been identified, and in any case acts as a fall-back.

  [Test Case]

   * Multiple people have been unable to create a reproducer on a
  generic machine (e.g. it does not occur in a VM), I have a specific
  machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM)
  by simply "ifdown br0; ifup br0" and there are clearly 10s of other
  users affected in varying circumstances that all involve the same
  symptoms but no clear test case exists. Best I can suggest is that I
  test the patch on my system to ensure it works as expected, and the
  change is only 1 line which is fairly easily auditible and
  understandable.

  [Regression Potential]

   * The change is a single line change to the shell script to call host with 
"timeout". When tested on working and non-working system this appears to 
function as expected. I believe the regression potential for this is 
subsequently low.
   * In attempt to anticipate possible issues, I checked that the timeout 
command is in the same path (/usr/bin) as the host command that is already 
called without a path, and the coreutils package (which contains timeout) is an 
Essential package. I also checked that timeout is not a built-in in bash, for 
those that have changed /bin/sh to bash (just in case).

  [Other Info]
   
   * N/A

  [Original Bug Description]

  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.2

[Touch-packages] [Bug 1790466] [NEW] package python3-protobuf 3.0.0-9.1ubuntu1 failed to install/upgrade: installed python3-protobuf package post-installation script subprocess returned error exit sta

2018-09-03 Thread Greg Scanlon

Public bug reported:

failed to install on upgrade to 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3-protobuf 3.0.0-9.1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sun Sep  2 19:32:46 2018
ErrorMessage: installed python3-protobuf package post-installation script 
subprocess returned error exit status 139
InstallationDate: Installed on 2015-11-02 (1035 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: protobuf
Title: package python3-protobuf 3.0.0-9.1ubuntu1 failed to install/upgrade: 
installed python3-protobuf package post-installation script subprocess returned 
error exit status 139
UpgradeStatus: Upgraded to bionic on 2018-09-02 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package python3-protobuf 3.0.0-9.1ubuntu1 failed to install/upgrade:
  installed python3-protobuf package post-installation script subprocess
  returned error exit status 139

Status in protobuf package in Ubuntu:
  New

Bug description:
  failed to install on upgrade to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-protobuf 3.0.0-9.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Sep  2 19:32:46 2018
  ErrorMessage: installed python3-protobuf package post-installation script 
subprocess returned error exit status 139
  InstallationDate: Installed on 2015-11-02 (1035 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: protobuf
  Title: package python3-protobuf 3.0.0-9.1ubuntu1 failed to install/upgrade: 
installed python3-protobuf package post-installation script subprocess returned 
error exit status 139
  UpgradeStatus: Upgraded to bionic on 2018-09-02 (0 days ago)

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

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

[Touch-packages] [Bug 1790466] Re: package python3-protobuf 3.0.0-9.1ubuntu1 failed to install/upgrade: installed python3-protobuf package post-installation script subprocess returned error exit statu

2018-09-03 Thread Greg Scanlon

Is my laptop at risk?

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

Title:
  package python3-protobuf 3.0.0-9.1ubuntu1 failed to install/upgrade:
  installed python3-protobuf package post-installation script subprocess
  returned error exit status 139

Status in protobuf package in Ubuntu:
  New

Bug description:
  failed to install on upgrade to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-protobuf 3.0.0-9.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Sep  2 19:32:46 2018
  ErrorMessage: installed python3-protobuf package post-installation script 
subprocess returned error exit status 139
  InstallationDate: Installed on 2015-11-02 (1035 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: protobuf
  Title: package python3-protobuf 3.0.0-9.1ubuntu1 failed to install/upgrade: 
installed python3-protobuf package post-installation script subprocess returned 
error exit status 139
  UpgradeStatus: Upgraded to bionic on 2018-09-02 (0 days ago)

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

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

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

2018-09-03 Thread Dave Jones

** Changed in: landscape-client (Ubuntu)
   Status: In Progress => Fix Committed

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

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

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Incomplete
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Incomplete

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

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

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

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

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

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

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

[Touch-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

** Tags added: cosmic

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

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1790458] Re: Update gnome-online-accounts to 3.30.0

2018-09-03 Thread Andrea Azzarone

** Merge proposal linked:
   
https://code.launchpad.net/~azzar1/ubuntu/+source/gnome-online-accounts/+git/gnome-online-accounts/+merge/354176

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

Title:
  Update gnome-online-accounts to 3.30.0

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  Update gnome-online-accounts to 3.30.0

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

-- 
Mailing list: https://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 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5

2018-09-03 Thread Michael Hudson-Doyle

On Mon, 3 Sep 2018 at 20:01, Łukasz Zemczak <1788...@bugs.launchpad.net>
wrote:

> I guess we need an ubiquity rebuild with the new console-setup now.
>

 The version in bionic-proposed has the fix (seems the ubiquity build
process includes packages from -proposed)

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  New
Status in console-setup source package in Bionic:
  Fix Released
Status in ubiquity source package in Bionic:
  New

Bug description:
  [ SRU Justification ]
  Due to my brain being in the wrong language, a function was exiting the 
script instead of returning.  Derp.

  [ Regression Potential ]
  N'much.

  [ Test Case ]
  Build a new ubiquity and see if we can haz keyboard again.

  [ Original Bug ]
  Since this version of console-setup in bionic ubiquity now skips the Keyboard 
and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

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

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

[Touch-packages] [Bug 1790476] [NEW] package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-09-03 Thread Otto Weichsler

Public bug reported:

I cannot declare something

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Mon Sep  3 12:07:29 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
InstallationDate: Installed on 2016-12-07 (634 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: systemd
Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
UpgradeStatus: Upgraded to bionic on 2018-09-03 (0 days ago)

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


** Tags: amd64 apport-package bionic third-party-packages

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

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  I cannot declare something

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Sep  3 12:07:29 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2016-12-07 (634 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-09-03 (0 days ago)

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

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

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

2018-09-03 Thread Dimitri John Ledkov

In general, scheduling with shutdown command should work. E.g. tested in
lxd container that `$ sudo shutdown +4` works correctly.

I wonder if landscape is affected by:
"""
If the time argument is used, 5 minutes before the system goes down the
/run/nologin file is created to ensure that further logins shall not be
allowed.
"""

Also, I see that 'halt' is used, instead of 'poweroff' in landscape, why
is that? I would have thought 'poweroff' is more appropriate (shutdown
-P +4, or just shutdown +4)

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

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

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Incomplete
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Incomplete

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

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

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

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

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

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

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

[Touch-packages] [Bug 1638634] Re: Print Job with Authentication is postponed until queue is opened manually

2018-09-03 Thread brandon211

Yes, all print jobs cause the problem.
I print for example from evince, Okular, LibreOffice
I print all kinds of files you mention.

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

Title:
  Print Job with Authentication is postponed until queue is opened
  manually

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I am connected to a print host requiring authentication. The authentication 
data is already stored in CUPS. I can issue a new print job and the printer 
icon in the panel appears, but the job isn't started, until I open the queue of 
the respective printer.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CupsErrorLog:
   E [10/Aug/2018:07:14:50 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
   E [10/Aug/2018:08:42:31 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
   E [11/Aug/2018:09:58:10 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
   E [14/Aug/2018:10:30:32 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
   E [28/Aug/2018:07:21:07 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-09-15 (1077 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lpstat:
   device for 0_prost: lpd://prost.uni-koblenz.de/
   device for 0_ricoh14: ipp://printhost.uni-koblenz.de:631/printers/ricoh14
   device for MFC9332CDW: 
dnssd://Brother%20MFC-9332CDW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af424f390
  MachineType: LENOVO 20BX000XGE
  Package: cups 2.1.3-4ubuntu0.5
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MFC9332CDW.ppd', 
'/etc/cups/ppd/0_prost.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/MFC9332CDW.ppd: Permission denied
   grep: /etc/cups/ppd/0_prost.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18
  Tags:  xenial
  Uname: Linux 4.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (857 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX000XGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BX000XGE
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1790458] Re: Update gnome-online-accounts to 3.30.0

2018-09-03 Thread Sebastien Bacher

** Changed in: gnome-online-accounts (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Update gnome-online-accounts to 3.30.0

Status in gnome-online-accounts package in Ubuntu:
  Fix Committed

Bug description:
  Update gnome-online-accounts to 3.30.0

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

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

[Touch-packages] [Bug 1790478] [NEW] gdm3 in cosmic fails to start fully in autopkgtest

2018-09-03 Thread Dimitri John Ledkov

Public bug reported:

In systemd package for a while, there is a boot-and-services test case,
which tries to install common/typical things and ensure they continue to
operate with new systemd.

One of the test cases is gdm3. The test case dependencies are:

Tests: boot-and-services
Depends: systemd-sysv,
  systemd,
  udev,
  systemd-container,
  systemd-coredump,
  libpam-systemd,
  xserver-xorg-video-dummy,
  xserver-xorg,
  gdm3 [!s390x],
  cron,
  network-manager,
  busybox-static,
  apparmor,
  pkg-config,
  python3

The test does following:
out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session'])   
   
self.assertIn(b'gdm-x-session gnome-session', out)  
   
out = subprocess.check_output(['ps', 'u', '-C', 'Xorg'])
   
self.assertIn(b'Xorg vt1', out) 
   
self.active_unit('gdm')

However, this now errors out upon the first command, meaning gdm-x-session is 
not running anymore.
On bionic, this test case continues to operate correctly in the autopkgtest 
cloud.

test_gdm3 (__main__.ServicesTest) ... ERROR

==
ERROR: test_gdm3 (__main__.ServicesTest)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.RNx2A1/build.2Wy/src/debian/tests/boot-and-services", 
line 66, in test_gdm3
out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session'])
  File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
**kwargs).stdout
  File "/usr/lib/python3.6/subprocess.py", line 418, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['ps', 'u', '-C', 'gdm-x-session']' 
returned non-zero exit status 1.

--
Ran 24 tests in 18.974s

FAILED (errors=1)

>From http://autopkgtest.ubuntu.com/packages/systemd/cosmic/i386

Thus it looks like there is a regression or a change of behavior of gdm3
in the cloud in cosmic; since bionic continues to work correctly.

I will mark this test as an expected failure for now, and monitor it
separately, as currently, this is blocking many migrations.

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

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


** Tags: autopkgtest

** Also 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/1790478

Title:
  gdm3 in cosmic fails to start fully in autopkgtest

Status in gdm3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In systemd package for a while, there is a boot-and-services test
  case, which tries to install common/typical things and ensure they
  continue to operate with new systemd.

  One of the test cases is gdm3. The test case dependencies are:

  Tests: boot-and-services
  Depends: systemd-sysv,
systemd,
udev,
systemd-container,
systemd-coredump,
libpam-systemd,
xserver-xorg-video-dummy,
xserver-xorg,
gdm3 [!s390x],
cron,
network-manager,
busybox-static,
apparmor,
pkg-config,
python3

  The test does following:
  out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session']) 
 
  self.assertIn(b'gdm-x-session gnome-session', out)
 
  out = subprocess.check_output(['ps', 'u', '-C', 'Xorg'])  
 
  self.assertIn(b'Xorg vt1', out)   
 
  self.active_unit('gdm')

  However, this now errors out upon the first command, meaning gdm-x-session is 
not running anymore.
  On bionic, this test case continues to operate correctly in the autopkgtest 
cloud.

  test_gdm3 (__main__.ServicesTest) ... ERROR

  ==
  ERROR: test_gdm3 (__main__.ServicesTest)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.RNx2A1/build.2Wy/src/debian/tests/boot-and-services", line 
66, in test_gdm3
  out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session'])
File "/usr/lib/py

[Touch-packages] [Bug 1790478] Re: gdm3 in cosmic fails to start fully in autopkgtest

I have found this to be locally reproducible with:
$ autopkgtest --shell-fail --apt-upgrade --no-built-binaries 
--testname=boot-and-services 
--apt-pocket=proposed=src:systemd,src:dbus,src:iproute2,src:glibc 
systemd_239-7ubuntu6.dsc -- qemu --qemu-options='-cpu host' 
--qemu-command=qemu-system-i386 --cpus 8 --ram-size=4096 
~/autopkgtest-cosmic-i386.img

What I see is that it really is failing.
There are plenty of crashes in journal but those seem to be a swarm of red 
herring.

The first start of gdm ends with X11 initializing and giving up like:
/usr/lib/gdm3/gdm-x-session[pid]: dbus-daemon[1112]: [session uid=119 pid=1112] 
Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=119 
pid=1053 comm="/usr/lib/gdm3/gdm-x-session gnome-session --autost" 
label="unconfined")
/usr/lib/gdm3/gdm-x-session[pid]: dbus-daemon[1112]: [session uid=119 pid=1112] 
Activated service 'org.freedesktop.systemd1' failed: Process 
org.freedesktop.systemd1 exited with status 1
/usr/lib/gdm3/gdm-x-session[pid]: Unable to register display with display 
manager


But if you log in later and run "systemctl restart gdm" then all initializes as 
it is supposed to.
It seems something yet unknown isn't available at early boot.

I compared the X11 init of good/bad case but there is no difference
(e.g. in detected HW), the first things that fails/differs is the
org.freedesktop.systemd1 activation.

But the boot start of gdm seems to be really (too early?) as halfway through I 
see:
  "Reached target Basic System"

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

Title:
  gdm3 in cosmic fails to start fully in autopkgtest

Status in gdm3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In systemd package for a while, there is a boot-and-services test
  case, which tries to install common/typical things and ensure they
  continue to operate with new systemd.

  One of the test cases is gdm3. The test case dependencies are:

  Tests: boot-and-services
  Depends: systemd-sysv,
systemd,
udev,
systemd-container,
systemd-coredump,
libpam-systemd,
xserver-xorg-video-dummy,
xserver-xorg,
gdm3 [!s390x],
cron,
network-manager,
busybox-static,
apparmor,
pkg-config,
python3

  The test does following:
  out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session']) 
 
  self.assertIn(b'gdm-x-session gnome-session', out)
 
  out = subprocess.check_output(['ps', 'u', '-C', 'Xorg'])  
 
  self.assertIn(b'Xorg vt1', out)   
 
  self.active_unit('gdm')

  However, this now errors out upon the first command, meaning gdm-x-session is 
not running anymore.
  On bionic, this test case continues to operate correctly in the autopkgtest 
cloud.

  test_gdm3 (__main__.ServicesTest) ... ERROR

  ==
  ERROR: test_gdm3 (__main__.ServicesTest)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.RNx2A1/build.2Wy/src/debian/tests/boot-and-services", line 
66, in test_gdm3
  out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session'])
File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
  **kwargs).stdout
File "/usr/lib/python3.6/subprocess.py", line 418, in run
  output=stdout, stderr=stderr)
  subprocess.CalledProcessError: Command '['ps', 'u', '-C', 'gdm-x-session']' 
returned non-zero exit status 1.

  --
  Ran 24 tests in 18.974s

  FAILED (errors=1)

  From http://autopkgtest.ubuntu.com/packages/systemd/cosmic/i386

  Thus it looks like there is a regression or a change of behavior of
  gdm3 in the cloud in cosmic; since bionic continues to work correctly.

  I will mark this test as an expected failure for now, and monitor it
  separately, as currently, this is blocking many migrations.

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

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

[Touch-packages] [Bug 1790478] Re: gdm3 in cosmic fails to start fully in autopkgtest

I just found that further calls to
  $ sudo systemctl restart gdm

Seem to alternate between good/bad state.

Here is the log of one such bad restarts:
http://paste.ubuntu.com/p/Dx7Sk3wDyx/

OTOH, the service could just in general not be restarable - so take this
with a grain of salt

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

Title:
  gdm3 in cosmic fails to start fully in autopkgtest

Status in gdm3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In systemd package for a while, there is a boot-and-services test
  case, which tries to install common/typical things and ensure they
  continue to operate with new systemd.

  One of the test cases is gdm3. The test case dependencies are:

  Tests: boot-and-services
  Depends: systemd-sysv,
systemd,
udev,
systemd-container,
systemd-coredump,
libpam-systemd,
xserver-xorg-video-dummy,
xserver-xorg,
gdm3 [!s390x],
cron,
network-manager,
busybox-static,
apparmor,
pkg-config,
python3

  The test does following:
  out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session']) 
 
  self.assertIn(b'gdm-x-session gnome-session', out)
 
  out = subprocess.check_output(['ps', 'u', '-C', 'Xorg'])  
 
  self.assertIn(b'Xorg vt1', out)   
 
  self.active_unit('gdm')

  However, this now errors out upon the first command, meaning gdm-x-session is 
not running anymore.
  On bionic, this test case continues to operate correctly in the autopkgtest 
cloud.

  test_gdm3 (__main__.ServicesTest) ... ERROR

  ==
  ERROR: test_gdm3 (__main__.ServicesTest)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.RNx2A1/build.2Wy/src/debian/tests/boot-and-services", line 
66, in test_gdm3
  out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session'])
File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
  **kwargs).stdout
File "/usr/lib/python3.6/subprocess.py", line 418, in run
  output=stdout, stderr=stderr)
  subprocess.CalledProcessError: Command '['ps', 'u', '-C', 'gdm-x-session']' 
returned non-zero exit status 1.

  --
  Ran 24 tests in 18.974s

  FAILED (errors=1)

  From http://autopkgtest.ubuntu.com/packages/systemd/cosmic/i386

  Thus it looks like there is a regression or a change of behavior of
  gdm3 in the cloud in cosmic; since bionic continues to work correctly.

  I will mark this test as an expected failure for now, and monitor it
  separately, as currently, this is blocking many migrations.

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

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

[Touch-packages] [Bug 1697692] Re: package libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a

2018-09-03 Thread Bernard Moreton

I tried to install Qpdfview, but failed with the error message
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/pool/universe/p/poppler/libpoppler-qt5-1_0.62.0-2ubuntu2.1_amd64.deb
  404  Not Found [IP: 91.189.88.149 80]

Ubuntu 18.04.1

Now I can't either install libpoppler-qt5, or un-install qpdfview from Synaptic.
The inconsistency needs urgent attention, I think.

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

Title:
  package libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting a removal

Status in poppler package in Ubuntu:
  New

Bug description:
  I have no further details since I don't know the precise thing that
  has failed. I hope the logs are enough for you, sorry not to be more
  helpful.

  Thank you a lot!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun 13 14:23:13 2017
  DpkgTerminalLog:
   dpkg: error processing package libpoppler-qt5-1:amd64 (--remove):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2017-06-01 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: poppler
  Title: package libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1790482] [NEW] [X550CC, Realtek ALC270, Speaker, Internal] No sound at all

2018-09-03 Thread fabio di bartolo

Public bug reported:

i can't listen any Sound from the speakers. 
if i use headphones i don't have any problem to hear music or anything, but 
without i can't neither choose the option speaker.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dibo   1094 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep  1 18:13:45 2018
InstallationDate: Installed on 2018-09-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   dibo   1094 F...m pulseaudio
 /dev/snd/controlC0:  dibo   1094 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [X550CC, Realtek ALC270, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550CC.212
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550CC
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X550CC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [X550CC, Realtek ALC270, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  i can't listen any Sound from the speakers. 
  if i use headphones i don't have any problem to hear music or anything, but 
without i can't neither choose the option speaker.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dibo   1094 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  1 18:13:45 2018
  InstallationDate: Installed on 2018-09-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dibo   1094 F...m pulseaudio
   /dev/snd/controlC0:  dibo   1094 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [X550CC, Realtek ALC270, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CC.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550CC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1784474] Re: canonical-livepatch failing to enable

2018-09-03 Thread Jeremy Bicha

** Package changed: software-properties (Ubuntu) => canonical-livepatch-
client

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

Title:
  canonical-livepatch failing to enable

Status in Canonical Live Patch Client:
  New

Bug description:
  I'm trying to enable canonical-livepatch but I keep getting an error
  about the freezer cgroup. See below:

  $ uname -a
  Linux laptop-ubuntu 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

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

  $ sudo snap remove canonical-livepatch
  canonical-livepatch removed

  $ sudo snap install canonical-livepatch
  canonical-livepatch 8.0.2 from 'canonical' installed

  $ sudo canonical-livepatch enable REDACTED
  cannot open freezer cgroup (/sys/fs/cgroup/freezer): No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-livepatch-client/+bug/1784474/+subscriptions

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

[Touch-packages] [Bug 1790458] Re: Update gnome-online-accounts to 3.30.0

This bug was fixed in the package gnome-online-accounts -
3.30.0-1ubuntu1

---
gnome-online-accounts (3.30.0-1ubuntu1) cosmic; urgency=medium

  * Merge from Debian unstable (LP: #1790458). Remaining changes:
+ debian/rules:
  - Make sure that gnome-online-accounts.pot is refreshed so the
strings from 0001-ubuntu-sso-provider.patch are included (LP: #1759251).
  - Build with --enable-ubuntu-sso
+ debian/control.*:
  - Add b-d on libsnapd-glib-dev
  - depends on python3 and python3-macaroonbakery for the ubuntu sso
provider.
+ debian/gbp.conf:
  - Set the upstream branch to upstream/latest.
+ debian/gnome-online-accounts.install:
  install usr/share/goa-1.0/scripts/lpa_helper.py
+ debian/libgoa-backend-1.0-1.symbols:
  Add goa_ubuntu_sso_provider_get_type
+ debian/source/include-binaries:
  Add debian/patches/0001-Add-Ubuntu-Single-Sign-on-icons.patch to properly
  deal with new binary images.
+ Ubuntu-specific patches:
  - debian/patches/0001-Add-Ubuntu-Single-Sign-on-icons.patch
  - debian/patches/0001-ubuntu-sso-provider.patch
  - debian/patches/0002-livepatch-auth.patch
  * debian/patches/0001-ubuntu-sso-provider.patch:
  * debian/patches/0001-Add-Ubuntu-Single-Sign-on-icons.patch:
- Split the patch in order to separate the binary files from the non-binary
  ones.

gnome-online-accounts (3.30.0-1) unstable; urgency=medium

  * New upstream release
  * Release to unstable

 -- Andrea Azzarone   Mon, 03 Sep 2018
10:35:24 +0200

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-online-accounts to 3.30.0

Status in gnome-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  Update gnome-online-accounts to 3.30.0

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

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

[Touch-packages] [Bug 48734] Re: Home permissions too open

2018-09-03 Thread Victor

In the server edition this should not be enabled.

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

Title:
  Home permissions too open

Status in adduser package in Ubuntu:
  Opinion
Status in Ubuntu RTM:
  New

Bug description:
  Binary package hint: debian-installer

  On a fresh dapper install i noticed that the file permissons for the
  home directory for the user created by the installer is set to 755,
  giving read access to everyone on the system.

  Surely this is a bad idea? If your set on the idea can we atleast have
  a option during the boot proccess?

  Also new files that are created via the console ('touch' etc.) are
  done so with '644' permissons, is there anything that can be done
  here? nautlius seems to create files at '600', which is a better
  setting.

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

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

[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2018-09-03 Thread Leandro Britez

#84: That's because inside a VM running on Virtualbox/VMWare Player/etc,
the sound chip is being emulated. If it is not working on the host
machine, it will not work on the guest machine.

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

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

2018-09-03 Thread Dave Jones

@xnox Scheduling with /sbin/shutdown normally does work ... however,
what we're dealing with here is the anomalous situation of an instance
which starts off as trusty and is upgraded to xenial. During the upgrade
process, the /sbin/shutdown implementation is changed from the upstart
one to the systemd one. At the end of the process, /sbin/shutdown is
(unsurprisingly) a link to systemctl ... but it doesn't work because
it's expecting to be able to talk to systemd which isn't fully
operational until a reboot. As Landscape is expecting to be able to
reboot via /sbin/shutdown the user relying on Landscape in such a
scenario finds themselves in a bit of a bind (having to have some other
means of dealing with the server, like SSH).

However, /sbin/reboot and /sbin/poweroff *do* work in this (admittedly
rare) scenario, hence the patches committed for this issue leave the
system using /sbin/shutdown by default but if/when it fails, they fall
back to trying /sbin/reboot or /sbin/poweroff (as appropriate) instead.

As to why -h is used instead of -P, in systemd's implementation of
/sbin/shutdown they're exactly the same thing. In the upstart
implementation it's more vague; quoting from the man-page: "Requests
that the system be either halted or powered off after it has been
brought down, with the choice as to which left up to the system". I'm
not sure what that means in practice though!

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

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

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Incomplete
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Incomplete

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

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

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

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

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

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

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

[Touch-packages] [Bug 1790509] [NEW] netplan doesn't configure renamed device

2018-09-03 Thread my balzitch

Public bug reported:

configured yaml file per documentation, ran netplan generate, netplan
apply. Interfaces are configured at this point.

Upon reboot the system renames ens18 to mainlink per config, but stops
after that point. System has no connectivity. mainif shows as DOWN in ip
addr list, networkctl shows mainif setup as unmanaged

Logging in via tty and running "sudo netplan apply" restores
connectivity.

Description:Ubuntu 18.04.1 LTS
Release:18.04

yaml file:

# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
mainif:
  match:
macaddress: "d2:a0:b9:2b:73:c4"
  set-name: mainif
  dhcp4: false
  dhcp6: false
  vlans:
  vlan5:
id: 5
link: mainif
addresses: [ 10.0.69.15/24 ]
gateway4: 10.0.69.1
nameservers:
  search: [ mydomain.com ]
  addresses:
  - "10.0.69.2"

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Mon Sep  3 09:42:57 2018
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=62ef2837-fce8-4133-ba14-07a7d5eab911 ro splash quiet net.ifnames=0 
vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.11
dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.11
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-bug bionic

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

Title:
  netplan doesn't configure renamed device

Status in systemd package in Ubuntu:
  New

Bug description:
  configured yaml file per documentation, ran netplan generate, netplan
  apply. Interfaces are configured at this point.

  Upon reboot the system renames ens18 to mainlink per config, but stops
  after that point. System has no connectivity. mainif shows as DOWN in
  ip addr list, networkctl shows mainif setup as unmanaged

  Logging in via tty and running "sudo netplan apply" restores
  connectivity.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  yaml file:

  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  mainif:
match:
  macaddress: "d2:a0:b9:2b:73:c4"
set-name: mainif
dhcp4: false
dhcp6: false
vlans:
vlan5:
  id: 5
  link: mainif
  addresses: [ 10.0.69.15/24 ]
  gateway4: 10.0.69.1
  nameservers:
search: [ mydomain.com ]
addresses:
- "10.0.69.2"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Sep  3 09:42:57 2018
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=62ef2837-fce8-4133-ba14-07a7d5eab911 ro splash quiet net.ifnames=0 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.11
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.11
  dmi.sys.vendor: QEMU

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

-- 
Mailing

[Touch-packages] [Bug 1790509] Re: netplan doesn't configure renamed device

2018-09-03 Thread my balzitch

-- Reboot --
Sep 03 09:48:42 ubuntu systemd-networkd[317]: Enumeration completed
Sep 03 09:48:42 ubuntu systemd[1]: Started Network Service.
Sep 03 09:48:42 ubuntu systemd-networkd[317]: eth0: Interface name change 
detected, eth0 has been renamed to mainif.
Sep 03 09:50:53 ubuntu systemd[1]: Stopping Network Service...
Sep 03 09:50:53 ubuntu systemd[1]: Stopped Network Service.
Sep 03 09:50:54 ubuntu systemd[1]: Starting Network Service...
Sep 03 09:50:54 ubuntu systemd-networkd[627]: Enumeration completed
Sep 03 09:50:54 ubuntu systemd[1]: Started Network Service.
Sep 03 09:50:54 ubuntu systemd-networkd[627]: lo: Link is not managed by us
Sep 03 09:50:54 ubuntu systemd-networkd[627]: vlan5: netdev ready
Sep 03 09:50:54 ubuntu systemd-networkd[627]: mainif: IPv6 successfully enabled
Sep 03 09:50:54 ubuntu systemd-networkd[627]: vlan5: Gained carrier
Sep 03 09:50:54 ubuntu systemd-networkd[627]: lo: Link is not managed by us
Sep 03 09:50:54 ubuntu systemd-networkd[627]: mainif: Gained carrier
Sep 03 09:50:54 ubuntu systemd-networkd[627]: vlan5: Gained IPv6LL
Sep 03 09:50:54 ubuntu systemd-networkd[627]: vlan5: Configured
Sep 03 09:50:56 ubuntu systemd-networkd[627]: mainif: Gained IPv6LL
Sep 03 09:50:56 ubuntu systemd-networkd[627]: mainif: Configured

In this log I logged in 2 minutes later and ran sudo netplan apply

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

Title:
  netplan doesn't configure renamed device

Status in systemd package in Ubuntu:
  New

Bug description:
  configured yaml file per documentation, ran netplan generate, netplan
  apply. Interfaces are configured at this point.

  Upon reboot the system renames ens18 to mainlink per config, but stops
  after that point. System has no connectivity. mainif shows as DOWN in
  ip addr list, networkctl shows mainif setup as unmanaged

  Logging in via tty and running "sudo netplan apply" restores
  connectivity.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  yaml file:

  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  mainif:
match:
  macaddress: "d2:a0:b9:2b:73:c4"
set-name: mainif
dhcp4: false
dhcp6: false
vlans:
vlan5:
  id: 5
  link: mainif
  addresses: [ 10.0.69.15/24 ]
  gateway4: 10.0.69.1
  nameservers:
search: [ mydomain.com ]
addresses:
- "10.0.69.2"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Sep  3 09:42:57 2018
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=62ef2837-fce8-4133-ba14-07a7d5eab911 ro splash quiet net.ifnames=0 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.11
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.11
  dmi.sys.vendor: QEMU

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

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

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

2018-09-03 Thread Dimitri John Ledkov

/sbin/shutdown, post upgrade not working, imho is a severe bug. I'll
investigate that. I suspect that because we cannot restart dbus things
don't show up there, but /sbin/shutdown should be smart enough to do
something. I guess the scheduling of timeout is failing, but
/sbin/shutdown now works?

Re differences between halt & poweroff, in systemd, eventually it
results in:

case ACTION_HALT:
(void) reboot(RB_HALT_SYSTEM);

case ACTION_POWEROFF:
(void) reboot(RB_POWER_OFF);

For completeness reboot typically is:
(void) reboot(RB_AUTOBOOT);

of if parameter was specified (aka androidish - reboot recovery):
(void) raw_reboot(LINUX_REBOOT_CMD_RESTART2, parameter);


This is the same as with upstart's implementation:

case REBOOT:
   
reboot (RB_AUTOBOOT);   
   

 
case HALT:  
   
reboot (RB_HALT_SYSTEM);
   

  
case POWEROFF:  
   
reboot (RB_POWER_OFF);  
   

case REBOOTCOMMAND: 
   
syscall (SYS_reboot,
   
   LINUX_REBOOT_MAGIC1, 
 
   LINUX_REBOOT_MAGIC2, 
 
   LINUX_REBOOT_CMD_RESTART2,   
 
   rebootcommand);   

Differences between RB_HALT_SYSTEM and RB_POWER_OFF can be read in the
linux manpage here:
http://manpages.ubuntu.com/manpages/bionic/en/man2/reboot.2.html

I have not read kernel code in a while for this, but if i'm not mistaken
poweroff fallsback to halt, in the kernel, if there is no hardware
support to kill power.

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

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

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Incomplete
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Incomplete

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

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

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

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

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

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

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

[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2018-09-03 Thread Mohammad Hassan

I see. Is there still no solution to this?

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2018-09-03 Thread Mohammad Hassan

I tried every combination in HDAjackretask, tried all pins, all
different kind of combinations with the pins. I even wrote down on paper
all the possible combinations for my 3 output pins, 0x14, 0x17 and 0x1b,
none of them solved this. They all just bring more sound settings up,
but none of them do anything at all.

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1790518] [NEW] PCI/internal sound card not detected

2018-09-03 Thread mhammad

Public bug reported:

sem som.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
Uname: Linux 4.4.0-134-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Mon Sep  3 14:16:04 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2017-05-18 (473 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/03/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.7
dmi.board.name: 0P1MTV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/03/2017:svnDellInc.:pnInspiron5566:pvr:rvnDellInc.:rn0P1MTV:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: Inspiron 5566
dmi.sys.vendor: Dell Inc.

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  sem som.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Sep  3 14:16:04 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-05-18 (473 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0P1MTV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/03/2017:svnDellInc.:pnInspiron5566:pvr:rvnDellInc.:rn0P1MTV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5566
  dmi.sys.vendor: Dell Inc.

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

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

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

2018-09-03 Thread Till Kamppeter

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Triaged

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

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

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged

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

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

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

  Note the un-reaped gs process.

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

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

2018-09-03 Thread Christian Zettel

For me it looks like, that steve's patch got lost in version 3.3 of 
initramfs-tools:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/0.130ubuntu3.3

When will this patch be released?

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

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

2018-09-03 Thread Till Kamppeter

The attached patch fixes the bug.

If the GTK print dialog finds a choice for a print option (Page Size,
Media Type, Resolution, Print Quality, ...) which is not under the
currently available choices (according to the PPD file in
/etc/cups/ppd/) it checks whether the option supports custom values and
if so, it considers the value a custom value and prefixes it with
"Custom." regardless of whether this is a valid custom value. This
usually works, if the user types in a custom value in the print dialog,
as the dialog provides the correct interface for a custom value for this
option.

Now there is a case where this easily breaks:

The dialog saves the last settings (printer selection and option
settings) which the user has used for printing so that the next time the
app is opened and the document printed, the saved settings are used by
default. Now let us choose a certain not that common paper size and
print. Then we close the app and do a system update. The update contains
a new version of our printer driver and one of the changes is that some
paper sizes in the PPD get renamed. So the paper size name we have used
for our last print job is not contained in the new PPD any more. Now we
open the app again and print the document right away, without going
through the options tabs of the print dialog and also not changing to
another printer. The print dialog recovers the saved options including
the (old) page size name. As the name does not match any page size name
of the new PPD, the dialog prefixes it with "Custom." and sends off the
job. The CUPS filters are not able to identify the paper size name and
the job errors.

Reproducer:

- Create a print queue with a PPD.
- evince an arbitrary PDF file
- Click the print icon
- In the print dialog choose the newly created queue and choose some uncommon
paper size (not custom). Click "Print".
- Check /var/log/cups/error_log, the page size gets correctly received.
- Close evince.
- Stop CUPS, edit the PPD file removing the paper size you have selected for
your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines.
- Start CUPS.
- Open the same PDF file again with evince, click Print and then select "Print"
in the print dialog without changing anything.
- The job fails, in /var/log/cups/error_log you see that the page size is
prefixed with "Custom.".

With the attached patch the print dialog checks the syntax of the
unknown option value and only if the syntax is correct for the
particular option, "Custom." is added. In the case of a page size name
this does not happen as a custom page size has to be specified as
"Custom.XXXxYYY[unit]", like "Custom.21x29.7cm".

** Patch added: "check-cups-custom-options.patch"

https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1763520/+attachment/5184169/+files/check-cups-custom-options.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/1763520

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

Status in cups-filters package in Ubuntu:
Invalid
Status in gtk+3.0 package in Ubuntu:
Triaged

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

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

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

[Touch-packages] [Bug 1770686] Re: Hide livepatch widgets in flavors without an online account panel in gnome-control-center

2018-09-03 Thread Andrea Azzarone

Tested in xubuntu.

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

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

Title:
  Hide livepatch widgets in flavors without an online account panel in
  gnome-control-center

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Committed

Bug description:
  
  [Impact]
  Some distributions ship software-properties-gtk but not gnome-control-center. 
Considering that Livepatch strictly depends on the online account panel in 
gnome-control-center we should not show the option to enable Livepatch if those 
distributions, otherwise enabling Livepatch will fail and it will seem buggy.

  [Test Case]
  1. Start xubuntu (Bionic)
  2. Open software-properties-gtk
  3. Go to "Updates" tab
  4. Make sure no Livepatch UI is displayed

  [Regression Potential] 
  Please make sure the Livepatch UI is correctly displayed in vanilla Bionic.

  [Original Bug Report]

  Unfortunately Livepatch strictly depends on the online account panel
  in gnome-control-center. We should hide the checkbutton in flavors
  (e.g. Xubuntu) that do not ship gnome-control-center and/or the online
  account panel.

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

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-09-03 Thread siyman

I am affected by this bug, too. Using an nVidia GTX 660 with legacy
nvidia-340 (both mainline as well as graphics-driver ppa) my system is
working as before. Switching to 390 or even 396 leaves me at a blinking
cursor DM both on sddm and gdm3. The only DM I could use has been
lightdm but only after I chowned the .Xauthority file of my user home
dir whilst it was running (sadly this is a no go for me as I rely on
multi user sessions which do not work anymore since the upgrade to
bionic).

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Touch-packages] [Bug 1782274] Re: resolvconf package needs dependency on ifupdown

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

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

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

Title:
  resolvconf package needs dependency on ifupdown

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  When I install resolvconf on a minimal install of Ubuntu 18.04
  (bionic), I see this:

  # apt-get install resolvconf
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following NEW packages will be installed:
resolvconf
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/48.2 kB of archives.
  After this operation, 187 kB of additional disk space will be used.
  Preconfiguring packages ...
  /tmp/resolvconf.config.XleExb: 13: /tmp/resolvconf.config.XleExb: ifquery: 
not found
  /tmp/resolvconf.config.XleExb: 13: /tmp/resolvconf.config.XleExb: ifquery: 
not found
  Selecting previously unselected package resolvconf.
  (Reading database ... 90542 files and directories currently installed.)
  Preparing to unpack .../resolvconf_1.79ubuntu10_all.deb ...
  Unpacking resolvconf (1.79ubuntu10) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for man-db (2.8.3-2) ...
  Setting up resolvconf (1.79ubuntu10) ...
  /var/lib/dpkg/info/resolvconf.config: 13: 
/var/lib/dpkg/info/resolvconf.config: ifquery: not found
  /var/lib/dpkg/info/resolvconf.config: 13: 
/var/lib/dpkg/info/resolvconf.config: ifquery: not found
  Created symlink /etc/systemd/system/sysinit.target.wants/resolvconf.service → 
/lib/systemd/system/resolvconf.service.
  Created symlink 
/etc/systemd/system/systemd-resolved.service.wants/resolvconf-pull-resolved.path
 → /lib/systemd/system/resolvconf-pull-resolved.path.
  resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
  resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for resolvconf (1.79ubuntu10) ...

  
  The "ifquery" program is provided by the ifupdown package. Therefore, 
resolvconf needs to include ifupdown in its Depends: clause. (Currently, 
ifupdown is mentioned in Enhances:)

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

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

[Touch-packages] [Bug 1782274] Re: resolvconf package needs dependency on ifupdown

2018-09-03 Thread Parakram Majumdar

I see the same problem while trying to upgrade to ubuntu 18.04. The upgrade 
seems stuck after the line
Processing triggers for resolvconf (1.79ubuntu10) ...

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

Title:
  resolvconf package needs dependency on ifupdown

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  When I install resolvconf on a minimal install of Ubuntu 18.04
  (bionic), I see this:

  # apt-get install resolvconf
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following NEW packages will be installed:
resolvconf
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/48.2 kB of archives.
  After this operation, 187 kB of additional disk space will be used.
  Preconfiguring packages ...
  /tmp/resolvconf.config.XleExb: 13: /tmp/resolvconf.config.XleExb: ifquery: 
not found
  /tmp/resolvconf.config.XleExb: 13: /tmp/resolvconf.config.XleExb: ifquery: 
not found
  Selecting previously unselected package resolvconf.
  (Reading database ... 90542 files and directories currently installed.)
  Preparing to unpack .../resolvconf_1.79ubuntu10_all.deb ...
  Unpacking resolvconf (1.79ubuntu10) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for man-db (2.8.3-2) ...
  Setting up resolvconf (1.79ubuntu10) ...
  /var/lib/dpkg/info/resolvconf.config: 13: 
/var/lib/dpkg/info/resolvconf.config: ifquery: not found
  /var/lib/dpkg/info/resolvconf.config: 13: 
/var/lib/dpkg/info/resolvconf.config: ifquery: not found
  Created symlink /etc/systemd/system/sysinit.target.wants/resolvconf.service → 
/lib/systemd/system/resolvconf.service.
  Created symlink 
/etc/systemd/system/systemd-resolved.service.wants/resolvconf-pull-resolved.path
 → /lib/systemd/system/resolvconf-pull-resolved.path.
  resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
  resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for resolvconf (1.79ubuntu10) ...

  
  The "ifquery" program is provided by the ifupdown package. Therefore, 
resolvconf needs to include ifupdown in its Depends: clause. (Currently, 
ifupdown is mentioned in Enhances:)

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

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

[Touch-packages] [Bug 1357529] Re: Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

apport information

** Tags added: apport-collected bionic

** Description changed:

  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.
  
  package=cups
  
  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 
  
  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ CupsErrorLog:
+  
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-05-21 (105 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
+ MachineType: System manufacturer System Product Name
+ Package: cups 2.2.7-1ubuntu2.1
+ PackageArchitecture: amd64
+ Papersize: letter
+ PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
+ ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
+ Tags:  bionic
+ Uname: Linux 4.15.0-29-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/07/2012
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 3402
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: P8Z68-V GEN3
+ dmi.board.vendor: ASUSTeK Computer INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Asset-1234567890
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Chassis Manufacture
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: System Product Name
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1357529/+attachment/5184181/+files/CurrentDmesg.txt

-- 
You recei

[Touch-packages] [Bug 1357529] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1357529/+attachment/5184182/+files/Dependencies.txt

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-21 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8

[Touch-packages] [Bug 1357529] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1357529/+attachment/5184185/+files/Lspci.txt

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-21 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRe

[Touch-packages] [Bug 1357529] Locale.txt

apport information

** Attachment added: "Locale.txt"
   https://bugs.launchpad.net/bugs/1357529/+attachment/5184184/+files/Locale.txt

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-21 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvr

[Touch-packages] [Bug 1357529] PrintingPackages.txt

apport information

** Attachment added: "PrintingPackages.txt"
   
https://bugs.launchpad.net/bugs/1357529/+attachment/5184187/+files/PrintingPackages.txt

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-21 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerI

[Touch-packages] [Bug 1357529] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1357529/+attachment/5184186/+files/Lsusb.txt

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-21 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRe

[Touch-packages] [Bug 1357529] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1357529/+attachment/5184188/+files/ProcCpuinfo.txt

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-21 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z6

[Touch-packages] [Bug 1357529] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1357529/+attachment/5184192/+files/ProcModules.txt

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-21 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z6

[Touch-packages] [Bug 1357529] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1357529/+attachment/5184193/+files/UdevDb.txt

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-21 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvr

[Touch-packages] [Bug 1357529] KernLog.txt

apport information

** Attachment added: "KernLog.txt"
   
https://bugs.launchpad.net/bugs/1357529/+attachment/5184183/+files/KernLog.txt

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-21 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:

[Touch-packages] [Bug 1357529] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1357529/+attachment/5184189/+files/ProcCpuinfoMinimal.txt

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-21 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCompu

[Touch-packages] [Bug 1357529] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1357529/+attachment/5184190/+files/ProcEnviron.txt

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-21 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z6

[Touch-packages] [Bug 1357529] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1357529/+attachment/5184191/+files/ProcInterrupts.txt

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-21 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:

[Touch-packages] [Bug 1766932] Re: packagekit daemon crashed from Discover. Requires a manual 'dpkg --configure -a' to correct.

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

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

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

Title:
  packagekit daemon crashed from Discover. Requires a manual 'dpkg
  --configure -a' to correct.

Status in packagekit package in Ubuntu:
  Confirmed

Bug description:
  The packagekit package has just been updated by discover (Kubuntu) from 
1.1.7-1 to 1.1.7-1ubuntu0.1.
  Discover reported that the packagekit daemon had crashed.

  The resulting dpkg status is:

  [parent]: dpkg-query -l 'packagekit*'
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  iF  packagekit 1.1.7-1ubunt amd64Provides a package management ser
  un  packagekit-bac   (no description available)
  un  packagekit-bac   (no description available)
  un  packagekit-bac   (no description available)
  un  packagekit-off   (no description available)
  un  packagekit-plu   (no description available)
  iU  packagekit-too 1.1.7-1ubunt amd64Provides PackageKit command-line 

  and apt-get upgrade reports:

  root@parent:~# apt-get upgrade
  E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to 
correct the problem. 

  Running that command does tidy things up, but the daemon should not
  crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: packagekit 1.1.7-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 25 17:47:49 2018
  InstallationDate: Installed on 2017-11-19 (157 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1357529] Re: Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Good day, I re-ran the test and the error remains! Keep in mind this fix
is simply the interchange of two pointers and it hasn't been done in
over four years ... sad ... but I'm not surprised. I ran the command for
you and uploaded the results.

Cordially, Robert

On Wednesday, August 22, 2018 4:55 PM, gf <1357...@bugs.launchpad.net> 
wrote:
 

 No problem, Robert. Take your time 
Hope you love the new version of Ubuntu
:) 
G

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1357529

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:    Ubuntu 14.04.1 LTS
  Release:    14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
    Installed: 1.7.2-0ubuntu1.1
    Candidate: 1.7.2-0ubuntu1.1
    Version table:
  *** 1.7.2-0ubuntu1.1 0
          500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
          500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
          100 /var/lib/dpkg/status
      1.7.2-0ubuntu1 0
          500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
  
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ub

[Touch-packages] [Bug 1766932] Re: packagekit daemon crashed from Discover. Requires a manual 'dpkg --configure -a' to correct.

2018-09-03 Thread Gordon Lack

Happened again last night when:

gir1.2-packagekitglib-1.0
libpackagekit-glib2-18
packagekit
packagekit-tools

went from 1.1.9-1ubuntu2 to 1.1.9-1ubuntu2.18.04.1.

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

Title:
  packagekit daemon crashed from Discover. Requires a manual 'dpkg
  --configure -a' to correct.

Status in packagekit package in Ubuntu:
  Confirmed

Bug description:
  The packagekit package has just been updated by discover (Kubuntu) from 
1.1.7-1 to 1.1.7-1ubuntu0.1.
  Discover reported that the packagekit daemon had crashed.

  The resulting dpkg status is:

  [parent]: dpkg-query -l 'packagekit*'
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  iF  packagekit 1.1.7-1ubunt amd64Provides a package management ser
  un  packagekit-bac   (no description available)
  un  packagekit-bac   (no description available)
  un  packagekit-bac   (no description available)
  un  packagekit-off   (no description available)
  un  packagekit-plu   (no description available)
  iU  packagekit-too 1.1.7-1ubunt amd64Provides PackageKit command-line 

  and apt-get upgrade reports:

  root@parent:~# apt-get upgrade
  E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to 
correct the problem. 

  Running that command does tidy things up, but the daemon should not
  crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: packagekit 1.1.7-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 25 17:47:49 2018
  InstallationDate: Installed on 2017-11-19 (157 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1357529] Re: Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

2018-09-03 Thread gf

Hi Robert. Thanks for the update and the apport info. I'll look at next steps.
Take care
:)
G

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

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-21 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-3070CW.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChas

[Touch-packages] [Bug 1638634] Re: Print Job with Authentication is postponed until queue is opened manually

2018-09-03 Thread gf

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

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

Title:
  Print Job with Authentication is postponed until queue is opened
  manually

Status in cups package in Ubuntu:
  New

Bug description:
  I am connected to a print host requiring authentication. The authentication 
data is already stored in CUPS. I can issue a new print job and the printer 
icon in the panel appears, but the job isn't started, until I open the queue of 
the respective printer.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CupsErrorLog:
   E [10/Aug/2018:07:14:50 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
   E [10/Aug/2018:08:42:31 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
   E [11/Aug/2018:09:58:10 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
   E [14/Aug/2018:10:30:32 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
   E [28/Aug/2018:07:21:07 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-09-15 (1077 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lpstat:
   device for 0_prost: lpd://prost.uni-koblenz.de/
   device for 0_ricoh14: ipp://printhost.uni-koblenz.de:631/printers/ricoh14
   device for MFC9332CDW: 
dnssd://Brother%20MFC-9332CDW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af424f390
  MachineType: LENOVO 20BX000XGE
  Package: cups 2.1.3-4ubuntu0.5
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MFC9332CDW.ppd', 
'/etc/cups/ppd/0_prost.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/MFC9332CDW.ppd: Permission denied
   grep: /etc/cups/ppd/0_prost.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18
  Tags:  xenial
  Uname: Linux 4.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (857 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX000XGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BX000XGE
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

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

2018-09-03 Thread Ubuntu Foundations Team Bug Bot

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

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

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged

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

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

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

  Note the un-reaped gs process.

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

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

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

[Touch-packages] [Bug 1638634] Re: Print Job with Authentication is postponed until queue is opened manually

2018-09-03 Thread gf

Thanks for the information, Brandon. More questions...

Did this work in a previous version of Ubuntu?

You mention a print host. Is it another computer with Ubuntu on it? If
so, what is the version of cups on the print host?

And when you open the print queue, are you opening it on your local
computer or on the print host?

And just to confirm, it is a Brother MFC-9332CDW - ricoh14 printer?

Can you give me the exact steps you take to produce the problem?

Thanks
G

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

Title:
  Print Job with Authentication is postponed until queue is opened
  manually

Status in cups package in Ubuntu:
  New

Bug description:
  I am connected to a print host requiring authentication. The authentication 
data is already stored in CUPS. I can issue a new print job and the printer 
icon in the panel appears, but the job isn't started, until I open the queue of 
the respective printer.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CupsErrorLog:
   E [10/Aug/2018:07:14:50 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
   E [10/Aug/2018:08:42:31 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
   E [11/Aug/2018:09:58:10 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
   E [14/Aug/2018:10:30:32 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
   E [28/Aug/2018:07:21:07 +0200] Missing value on line 2137 of 
/var/cache/cups/job.cache.
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-09-15 (1077 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lpstat:
   device for 0_prost: lpd://prost.uni-koblenz.de/
   device for 0_ricoh14: ipp://printhost.uni-koblenz.de:631/printers/ricoh14
   device for MFC9332CDW: 
dnssd://Brother%20MFC-9332CDW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af424f390
  MachineType: LENOVO 20BX000XGE
  Package: cups 2.1.3-4ubuntu0.5
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MFC9332CDW.ppd', 
'/etc/cups/ppd/0_prost.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/MFC9332CDW.ppd: Permission denied
   grep: /etc/cups/ppd/0_prost.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18
  Tags:  xenial
  Uname: Linux 4.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (857 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX000XGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BX000XGE
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

2018-09-03 Thread Nate Graham

This *is* 520546 :)

Happened again with console-setup 1.178ubuntu2.7 and keyboard-
configuration 1.178ubuntu2.7. Seems like it happens with every update to
these packages...

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 1789502] Re: Update to 0.6.50

2018-09-03 Thread Robert Ancell

I have all the patches updated except for 0010-set-language.patch

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

Title:
  Update to 0.6.50

Status in accountsservice package in Ubuntu:
  In Progress

Bug description:
  The upstream changes are non trivial and there is work to update the
  patches but that would be useful to do

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

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

[Touch-packages] [Bug 1789502] Re: Update to 0.6.50

2018-09-03 Thread Robert Ancell

Gunnar - could you perhaps have a look at 0010-set-language.patch? In
particular I'm not sure how we want to do the fallback language property
handling in src/user.c - the new code uses autogenerated property
handling so we can't intercept it as easily. I guess we could just set
the fallback values on initialization?

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

Title:
  Update to 0.6.50

Status in accountsservice package in Ubuntu:
  In Progress

Bug description:
  The upstream changes are non trivial and there is work to update the
  patches but that would be useful to do

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

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

[Touch-packages] [Bug 1764779] Re: Nautilus crashed open Windows-partition

2018-09-03 Thread Treviño

No need to perform full verification as per GNOME exception
(https://wiki.ubuntu.com/StableReleaseUpdates/GNOME)

And this bug is fixed in an upstream commit.

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

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

Title:
  Nautilus crashed open Windows-partition

Status in glib2.0 package in Ubuntu:
  In Progress
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  if I open a new partition from the Hard-drive (Windows in this case)
  Nautilus crash, report him self and after reopen it, the partition is
  normal available as nothing would be

  [ Test case ]

  * Open nautilus and select an external hd that is not mounted from the sidebar
  * Nautilus sould not crash (in case showing an error message)

  [ Regression potential ]

  Partitions that have been actually mounted, are not shown or an error
  is prompted.

  -

  Issue from the log:

  Apr 17 16:45:29 hostname udisksd[1014]: Failed to setup systemd-based mount 
point cleanup: Process reported exit code 5: Failed to start 
clean-mount-point@media-username-12F6CC77F6CC5D1B.service: Unit 
media-username-12F6CC77F6CC5D1B.mount not found.
  Apr 17 16:45:29 hostname nautilus[11486]: g_mount_get_default_location: 
assertion 'G_IS_MOUNT (mount)' failed
  Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: **
  Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: 
ERROR:../src/nautilus-file.c:721:nautilus_file_get_internal: assertion failed: 
(location != NULL)

  -

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 16:45:30 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' 
b'show-move-to-trash-shortcut-changed-dialog' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'927x1011+926+27'"
  InstallationDate: Installed on 2018-03-16 (32 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180315)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=de_DE.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Touch-packages] [Bug 1789472] Re: SRU 2.56.2 to bionic

2018-09-03 Thread Treviño

No need to perform full verification as per GNOME exception
(https://wiki.ubuntu.com/StableReleaseUpdates/GNOME)

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

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

Title:
  SRU 2.56.2 to bionic

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  The second stable release in the 2.56 series.

  [ QA ]

  Upstream release, so QA already performed by maintainers

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

  [ Regresison potential ]

  Various fixes in multiple places (see
  https://gitlab.gnome.org/GNOME/glib/blob/d4b603/NEWS) so various apps
  could be affected.

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

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

[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed

2018-09-03 Thread Robert Ancell

** Description changed:

- Using gnome software (or another PackageKit or aptdaemon based UI) to
- install an application - removal of that package leaves behind
- dependencies
+ [Impact]
+ Installing an application them removing it leaves dependencies behind.
  
- Installing an application with ubuntu software centre only leaves behind
- config files (seen in synaptic labelled for complete removal).
+ [Test Case]
+ 1. Ensure that GNOME Sudoku is not installed:
+ $ sudo apt remove gnome-sudoku libqqwing2v5
+ 2. Check if you have any packages that need autoremoval:
+ $ sudo apt autoremove --no-act
+ 3. Open GNOME Software.
+ 4. Search for and install GNOME Sudoku (make sure to install the .deb, not 
the snap).
+ 5. Uninstall GNOME Sudoku.
+ 6. Check if you have any packages that need autoremoval:
+ $ sudo apt autoremove --no-act
  
- After installing and then removing alarm clock with USC -
+ Expected result:
+ The packages in step 6 are the same as in step 2 (which might be none).
  
- sudo apt-get autoremove
- [sudo] password for wolf:
- Reading package lists... Done
- Building dependency tree
- Reading state information... Done
- 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
+ Observed result:
+ The packages in step 6 includes libqqwing2v5, which is a dependency of 
gnome-sudoku and not useful without the game installed.
  
- After cleaning up and then reinstalling with gnome software, followed by
- the removal
- 
- sudo apt-get autoremove
- Reading package lists... Done
- Building dependency tree
- Reading state information... Done
- The following packages will be REMOVED
-   libappindicator1 libindicator7
- 0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade.
- After this operation, 184 kB disk space will be freed.
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
- Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1
- ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
- Uname: Linux 4.4.0-10-generic x86_64
- ApportVersion: 2.20-0ubuntu3
- Architecture: amd64
- CurrentDesktop: XFCE
- Date: Thu Mar  3 16:23:45 2016
- InstallationDate: Installed on 2015-10-29 (126 days ago)
- InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
- SourcePackage: gnome-software
- UpgradeStatus: No upgrade log present (probably fresh install)
+ [Regression Potential]
+ This requires a fix to PackageKit which used to autoremove all packages (too 
aggressive), not just the ones related to the current transaction. A bug in the 
code could cause more packages to be removed than is suitable. GNOME Software 
previously didn't use this autoremove functionality, so by enabling it we could 
trigger a problem in either the existing code or the new fix.

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: Triaged => In Progress

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

Title:
  gnome software leaves dependencies installed

Status in GNOME Software:
  Invalid
Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in packagekit package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Bionic:
  Triaged
Status in packagekit source package in Bionic:
  Triaged
Status in gnome-software source package in Cosmic:
  Fix Committed
Status in packagekit source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Installing an application them removing it leaves dependencies behind.

  [Test Case]
  1. Ensure that GNOME Sudoku is not installed:
  $ sudo apt remove gnome-sudoku libqqwing2v5
  2. Check if you have any packages that need autoremoval:
  $ sudo apt autoremove --no-act
  3. Open GNOME Software.
  4. Search for and install GNOME Sudoku (make sure to install the .deb, not 
the snap).
  5. Uninstall GNOME Sudoku.
  6. Check if you have any packages that need autoremoval:
  $ sudo apt autoremove --no-act

  Expected result:
  The packages in step 6 are the same as in step 2 (which might be none).

  Observed result:
  The packages in step 6 includes libqqwing2v5, which is a dependency of 
gnome-sudoku and not useful without the game installed.

  [Regression Potential]
  This requires a fix to PackageKit which used to autoremove all packages (too 
aggressive), not just the ones related to the current transaction. A bug in the 
code could cause more packages to be removed than is suitable. GNOME Software 
previously didn't use this autoremove functionality, so by enabling it we could 
trigger a problem in either the existing code or the new fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions

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

[Touch-packages] [Bug 1790553] [NEW] Update to 2.58.0

2018-09-03 Thread Treviño

Public bug reported:

Just copy from debian please.

** Affects: glib2.0 (Ubuntu)
 Importance: Wishlist
 Assignee: Iain Lane (laney)
 Status: Triaged


** Tags: upgrade-software-version

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

Title:
  Update to 2.58.0

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Just copy from debian please.

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

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

[Touch-packages] [Bug 1790556] [NEW] package keyboard-configuration 1.108ubuntu15.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2018-09-03 Thread Gabriela Felix Solano

Public bug reported:

subprocess installed post-installation script returned error exit status
127

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: keyboard-configuration 1.108ubuntu15.4
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
Uname: Linux 4.4.0-134-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Mon Sep  3 21:30:20 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 127
InstallationDate: Installed on 2016-10-11 (692 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.27
SourcePackage: console-setup
Title: package keyboard-configuration 1.108ubuntu15.4 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 127
UpgradeStatus: Upgraded to xenial on 2018-09-04 (0 days ago)
modified.conffile..etc.init.d.keyboard-setup: [deleted]

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package keyboard-configuration 1.108ubuntu15.4 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 127

Status in console-setup package in Ubuntu:
  New

Bug description:
  subprocess installed post-installation script returned error exit
  status 127

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: keyboard-configuration 1.108ubuntu15.4
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Sep  3 21:30:20 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2016-10-11 (692 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.108ubuntu15.4 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 127
  UpgradeStatus: Upgraded to xenial on 2018-09-04 (0 days ago)
  modified.conffile..etc.init.d.keyboard-setup: [deleted]

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

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

[Touch-packages] [Bug 1790556] Re: package keyboard-configuration 1.108ubuntu15.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2018-09-03 Thread 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 console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1790556

Title:
  package keyboard-configuration 1.108ubuntu15.4 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 127

Status in console-setup package in Ubuntu:
  New

Bug description:
  subprocess installed post-installation script returned error exit
  status 127

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: keyboard-configuration 1.108ubuntu15.4
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Sep  3 21:30:20 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2016-10-11 (692 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.108ubuntu15.4 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 127
  UpgradeStatus: Upgraded to xenial on 2018-09-04 (0 days ago)
  modified.conffile..etc.init.d.keyboard-setup: [deleted]

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

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

[Touch-packages] [Bug 1790553] Re: Update to 2.58.0

2018-09-03 Thread Jeremy Bicha

This is blocked on https://gitlab.gnome.org/GNOME/glib/issues/1509

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

Title:
  Update to 2.58.0

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Just copy from debian please.

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

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

[Touch-packages] [Bug 1790478] Re: gdm3 in cosmic fails to start fully in autopkgtest

Try gdm version 3.29.92, which has a fix for some rather serious issues:

https://bugs.launchpad.net/ubuntu/+source/gdm3/+bugs?field.tag=fixed-in-
gdm-3.29.92

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

Title:
  gdm3 in cosmic fails to start fully in autopkgtest

Status in gdm3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In systemd package for a while, there is a boot-and-services test
  case, which tries to install common/typical things and ensure they
  continue to operate with new systemd.

  One of the test cases is gdm3. The test case dependencies are:

  Tests: boot-and-services
  Depends: systemd-sysv,
systemd,
udev,
systemd-container,
systemd-coredump,
libpam-systemd,
xserver-xorg-video-dummy,
xserver-xorg,
gdm3 [!s390x],
cron,
network-manager,
busybox-static,
apparmor,
pkg-config,
python3

  The test does following:
  out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session']) 
 
  self.assertIn(b'gdm-x-session gnome-session', out)
 
  out = subprocess.check_output(['ps', 'u', '-C', 'Xorg'])  
 
  self.assertIn(b'Xorg vt1', out)   
 
  self.active_unit('gdm')

  However, this now errors out upon the first command, meaning gdm-x-session is 
not running anymore.
  On bionic, this test case continues to operate correctly in the autopkgtest 
cloud.

  test_gdm3 (__main__.ServicesTest) ... ERROR

  ==
  ERROR: test_gdm3 (__main__.ServicesTest)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.RNx2A1/build.2Wy/src/debian/tests/boot-and-services", line 
66, in test_gdm3
  out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session'])
File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
  **kwargs).stdout
File "/usr/lib/python3.6/subprocess.py", line 418, in run
  output=stdout, stderr=stderr)
  subprocess.CalledProcessError: Command '['ps', 'u', '-C', 'gdm-x-session']' 
returned non-zero exit status 1.

  --
  Ran 24 tests in 18.974s

  FAILED (errors=1)

  From http://autopkgtest.ubuntu.com/packages/systemd/cosmic/i386

  Thus it looks like there is a regression or a change of behavior of
  gdm3 in the cloud in cosmic; since bionic continues to work correctly.

  I will mark this test as an expected failure for now, and monitor it
  separately, as currently, this is blocking many migrations.

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

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

[Touch-packages] [Bug 1743939] Re: Canon MF8380 Wireless Network Not Printing

2018-09-03 Thread Scott Stehno

Yes it was fixed with new driver from Canon.  I upgraded to 18.04 and
one cups driver started printing black pages again.  I just installed
the new driver from Canon on 18.04 with the all the updates installed
and it not printing black pages on PDF pages now.  Not sure if the cups
update or the Canon driver update fixed the problem, just glad it is
working again.  I can run any report you would like to get the
information about my system that you would like.

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

Title:
  Canon MF8380 Wireless Network Not Printing

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  A Canon MF8380CDW printer will not print any thing after upgrading to
  17.10.  I ran all  the steps from this
  https://wiki.ubuntu.com/DebuggingPrintingProblems web site.

  I have attached a lot of log files.  Not sure which one is needed. The
  printer did work back under 15.10 or 16.04 but took a lot to get it
  fixed to work then.  I have tried to print from 18.04 and it has the
  same problem with this printer.





  
  myuseraccount@myuseraccount-System-Product-Name:~$ /usr/lib/cups/backend/snmp
  network socket://192.168.1.100 "Canon MF8300C Series" "Canon MF8300C Series" 
"MFG:Canon;MDL:MF8300C Series;CLS:PRINTER;DES:Canon MF8300
  C Series;CID:;CMD:LIPSLX,CPCA;" ""
  myuseraccount@myuseraccount-System-Product-Name:~$ sudo 
/usr/lib/cups/backend/dnssd
  [sudo] password for myuseraccount:
  DEBUG: sent=0, count=0
  DEBUG: Querying "Canon\032MF8300C\032Series._printer._tcp.local"...
  DEBUG: Querying "Canon\032MF8300C\032Series._pdl-datastream._tcp.local"...
  DEBUG: sent=0, count=2
  DEBUG2: query_callback(browser=0x556cd4f96420, interfaceIndex=2, protocol=0, 
event=0, fullName="Canon\032MF8300C\032Series._printer._tcp.local", rrclass=1, 
rrtype=16, rdata=0x
  556cd4f97854, rdlen=338, flags=5, context=0x556cd4f95900)
  DEBUG2: query_callback: "txtvers=1".
  DEBUG2: query_callback: "note=".
  DEBUG2: query_callback: "qtotal=1".
  DEBUG2: query_callback: "priority=20".
  DEBUG2: query_callback: "ty=Canon MF8300C Series".
  DEBUG2: query_callback: "product=(CNMF8300C Series)".
  DEBUG2: query_callback: "pdl=application/octet-stream".
  DEBUG2: query_callback: 
"adminurl=http://Canon0f2ec4.local/m_network_tcpip.html";.
  DEBUG2: query_callback: "usb_MFG=Canon".
  DEBUG2: query_callback: "usb_MDL=MF8300C Series".
  DEBUG2: query_callback: "Transparent=F".
  DEBUG2: query_callback: "Binary=F".
  DEBUG2: query_callback: "TBCP=F".
  DEBUG2: query_callback: "Color=T".
  DEBUG2: query_callback: "Copies=T".
  DEBUG2: query_callback: "Duplex=T".
  DEBUG2: query_callback: "PaperCustom=T".
  DEBUG2: query_callback: "Bind=F".
  DEBUG2: query_callback: "Collate=T".
  DEBUG2: query_callback: "Sort=T".
  DEBUG2: query_callback: "Staple=F".
  DEBUG2: query_callback: "Punch=0".
  DEBUG2: query_callback: "PaperMax=legal-A4".
  DEBUG2: query_callback(browser=0x556cd4f96420, interfaceIndex=-1, 
protocol=-1, event=2, 
fullName="Canon\032MF8300C\032Series._printer._tcp.local", rrclass=1, 
rrtype=16, rdata=
  (nil), rdlen=0, flags=0, context=0x556cd4f95900)
  DEBUG2: query_callback(browser=0x556cd4f95aa0, interfaceIndex=2, protocol=0, 
event=0, fullName="Canon\032MF8300C\032Series._pdl-datastream._tcp.local", 
rrclass=1, rrtype=16, r
  data=0x556cd4f97a0c, rdlen=338, flags=5, context=0x556cd4f95780)
  DEBUG2: query_callback: "txtvers=1".
  DEBUG2: query_callback: "note=".
  DEBUG2: query_callback: "qtotal=1".
  DEBUG2: query_callback: "priority=10".
  DEBUG2: query_callback: "ty=Canon MF8300C Series".
  DEBUG2: query_callback: "product=(CNMF8300C Series)".
  DEBUG2: query_callback: "pdl=application/octet-stream".
  DEBUG2: query_callback: 
"adminurl=http://Canon0f2ec4.local/m_network_tcpip.html";.
  DEBUG2: query_callback: "usb_MFG=Canon".
  DEBUG2: query_callback: "usb_MDL=MF8300C Series".
  DEBUG2: query_callback: "Transparent=F".
  DEBUG2: query_callback: "Binary=F".
  DEBUG2: query_callback: "TBCP=F".
  DEBUG2: query_callback: "Color=T".
  DEBUG2: query_callback: "Copies=T".
  DEBUG2: query_callback: "Duplex=T".
  DEBUG2: query_callback: "PaperCustom=T".
  DEBUG2: query_callback: "Bind=F".
  DEBUG2: query_callback: "Collate=T".
  DEBUG2: query_callback: "Sort=T".
  DEBUG2: query_callback: "Staple=F".
  DEBUG2: query_callback: "Punch=0".
  DEBUG2: query_callback: "PaperMax=legal-A4".
  network dnssd://Canon%20MF8300C%20Series._pdl-datastream._tcp.local/ "Canon 
MF8300C Series" "Canon MF8300C Series" "MFG:Canon;MDL:MF8300C Series;" ""
  DEBUG: sent=2, count=2
  myuseraccount@myuseraccount-System-Product-Name:~$ /usr/lib/cups/backend/snmp 
192.168.1.100
  network socket://192.168.1.100 "Canon MF8300C Series" "Canon MF8300C Series" 
"MFG:Canon;MDL:MF8300C Series;CLS:PRINTER;DES:Canon MF8300C 
Series;CID:;CMD:LIPSLX,CPCA;" ""
  myuseraccount@myuseraccount-System-Product-Name:~

[Touch-packages] [Bug 1743939] Re: Canon MF8380 Wireless Network Not Printing

2018-09-03 Thread Scott Stehno

I could not run the command you sent.  I guess close this bug report as
I have upgraded to 18.04 and installed the newest Canon driver and it is
working.  My guess is the Canon driver made the biggest difference, it
might be it works better with the newest cups driver.

I printed two different PDF files and both printed just fine with no all
black pages.

Thank you

I will help if you still wish to test.

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

Title:
  Canon MF8380 Wireless Network Not Printing

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  A Canon MF8380CDW printer will not print any thing after upgrading to
  17.10.  I ran all  the steps from this
  https://wiki.ubuntu.com/DebuggingPrintingProblems web site.

  I have attached a lot of log files.  Not sure which one is needed. The
  printer did work back under 15.10 or 16.04 but took a lot to get it
  fixed to work then.  I have tried to print from 18.04 and it has the
  same problem with this printer.





  
  myuseraccount@myuseraccount-System-Product-Name:~$ /usr/lib/cups/backend/snmp
  network socket://192.168.1.100 "Canon MF8300C Series" "Canon MF8300C Series" 
"MFG:Canon;MDL:MF8300C Series;CLS:PRINTER;DES:Canon MF8300
  C Series;CID:;CMD:LIPSLX,CPCA;" ""
  myuseraccount@myuseraccount-System-Product-Name:~$ sudo 
/usr/lib/cups/backend/dnssd
  [sudo] password for myuseraccount:
  DEBUG: sent=0, count=0
  DEBUG: Querying "Canon\032MF8300C\032Series._printer._tcp.local"...
  DEBUG: Querying "Canon\032MF8300C\032Series._pdl-datastream._tcp.local"...
  DEBUG: sent=0, count=2
  DEBUG2: query_callback(browser=0x556cd4f96420, interfaceIndex=2, protocol=0, 
event=0, fullName="Canon\032MF8300C\032Series._printer._tcp.local", rrclass=1, 
rrtype=16, rdata=0x
  556cd4f97854, rdlen=338, flags=5, context=0x556cd4f95900)
  DEBUG2: query_callback: "txtvers=1".
  DEBUG2: query_callback: "note=".
  DEBUG2: query_callback: "qtotal=1".
  DEBUG2: query_callback: "priority=20".
  DEBUG2: query_callback: "ty=Canon MF8300C Series".
  DEBUG2: query_callback: "product=(CNMF8300C Series)".
  DEBUG2: query_callback: "pdl=application/octet-stream".
  DEBUG2: query_callback: 
"adminurl=http://Canon0f2ec4.local/m_network_tcpip.html";.
  DEBUG2: query_callback: "usb_MFG=Canon".
  DEBUG2: query_callback: "usb_MDL=MF8300C Series".
  DEBUG2: query_callback: "Transparent=F".
  DEBUG2: query_callback: "Binary=F".
  DEBUG2: query_callback: "TBCP=F".
  DEBUG2: query_callback: "Color=T".
  DEBUG2: query_callback: "Copies=T".
  DEBUG2: query_callback: "Duplex=T".
  DEBUG2: query_callback: "PaperCustom=T".
  DEBUG2: query_callback: "Bind=F".
  DEBUG2: query_callback: "Collate=T".
  DEBUG2: query_callback: "Sort=T".
  DEBUG2: query_callback: "Staple=F".
  DEBUG2: query_callback: "Punch=0".
  DEBUG2: query_callback: "PaperMax=legal-A4".
  DEBUG2: query_callback(browser=0x556cd4f96420, interfaceIndex=-1, 
protocol=-1, event=2, 
fullName="Canon\032MF8300C\032Series._printer._tcp.local", rrclass=1, 
rrtype=16, rdata=
  (nil), rdlen=0, flags=0, context=0x556cd4f95900)
  DEBUG2: query_callback(browser=0x556cd4f95aa0, interfaceIndex=2, protocol=0, 
event=0, fullName="Canon\032MF8300C\032Series._pdl-datastream._tcp.local", 
rrclass=1, rrtype=16, r
  data=0x556cd4f97a0c, rdlen=338, flags=5, context=0x556cd4f95780)
  DEBUG2: query_callback: "txtvers=1".
  DEBUG2: query_callback: "note=".
  DEBUG2: query_callback: "qtotal=1".
  DEBUG2: query_callback: "priority=10".
  DEBUG2: query_callback: "ty=Canon MF8300C Series".
  DEBUG2: query_callback: "product=(CNMF8300C Series)".
  DEBUG2: query_callback: "pdl=application/octet-stream".
  DEBUG2: query_callback: 
"adminurl=http://Canon0f2ec4.local/m_network_tcpip.html";.
  DEBUG2: query_callback: "usb_MFG=Canon".
  DEBUG2: query_callback: "usb_MDL=MF8300C Series".
  DEBUG2: query_callback: "Transparent=F".
  DEBUG2: query_callback: "Binary=F".
  DEBUG2: query_callback: "TBCP=F".
  DEBUG2: query_callback: "Color=T".
  DEBUG2: query_callback: "Copies=T".
  DEBUG2: query_callback: "Duplex=T".
  DEBUG2: query_callback: "PaperCustom=T".
  DEBUG2: query_callback: "Bind=F".
  DEBUG2: query_callback: "Collate=T".
  DEBUG2: query_callback: "Sort=T".
  DEBUG2: query_callback: "Staple=F".
  DEBUG2: query_callback: "Punch=0".
  DEBUG2: query_callback: "PaperMax=legal-A4".
  network dnssd://Canon%20MF8300C%20Series._pdl-datastream._tcp.local/ "Canon 
MF8300C Series" "Canon MF8300C Series" "MFG:Canon;MDL:MF8300C Series;" ""
  DEBUG: sent=2, count=2
  myuseraccount@myuseraccount-System-Product-Name:~$ /usr/lib/cups/backend/snmp 
192.168.1.100
  network socket://192.168.1.100 "Canon MF8300C Series" "Canon MF8300C Series" 
"MFG:Canon;MDL:MF8300C Series;CLS:PRINTER;DES:Canon MF8300C 
Series;CID:;CMD:LIPSLX,CPCA;" ""
  myuseraccount@myuseraccount-System-Product-Name:~$ lpinfo -v
  network ipp
  network https
  network ipp

[Touch-packages] [Bug 1096152] Re: ubuntu-bug thunderbird is attaching private network details I don't want in my public bug report

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

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

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

Title:
  ubuntu-bug thunderbird is attaching private network details I don't
  want in my public bug report

Status in apport package in Ubuntu:
  Expired
Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  E.g. when sending a bug reporting using ubuntu-bug for thunderbird
  it's copieing my complete network configuration into a public
  resources, even my bug was only related to some UI thing. Users should
  have the opportunity to select/deselect information which is
  transferred to lauchpad. If not, the user is maybe transffering
  private data e.g. about his network environment which is IMHO a
  security issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: apport 2.6.1-0ubuntu9
  ProcVersionSignature: Ubuntu 3.5.0-22.33-generic 3.5.7.2
  Uname: Linux 3.5.0-22-generic x86_64
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  CrashReports:
   640:1000:110:1261589:2013-01-04 15:19:35.735918000 +0100:2013-01-04 
15:20:18.611922558 +0100:/var/crash/_usr_bin_xfce4-appfinder.1000.crash
   664:1000:110:0:2013-01-04 15:20:17.587918601 +0100:2013-01-04 
15:20:17.587918601 +0100:/var/crash/_usr_bin_xfce4-appfinder.1000.upload
   600:104:110:0:2013-01-04 18:25:35.376977374 +0100:2012-12-15 
10:34:43.593351096 +0100:/var/crash/_usr_bin_xfce4-appfinder.1000.uploaded
  Date: Fri Jan  4 18:42:14 2013
  InstallationDate: Installed on 2012-11-08 (57 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1096152] Re: ubuntu-bug thunderbird is attaching private network details I don't want in my public bug report

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

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

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

Title:
  ubuntu-bug thunderbird is attaching private network details I don't
  want in my public bug report

Status in apport package in Ubuntu:
  Expired
Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  E.g. when sending a bug reporting using ubuntu-bug for thunderbird
  it's copieing my complete network configuration into a public
  resources, even my bug was only related to some UI thing. Users should
  have the opportunity to select/deselect information which is
  transferred to lauchpad. If not, the user is maybe transffering
  private data e.g. about his network environment which is IMHO a
  security issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: apport 2.6.1-0ubuntu9
  ProcVersionSignature: Ubuntu 3.5.0-22.33-generic 3.5.7.2
  Uname: Linux 3.5.0-22-generic x86_64
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  CrashReports:
   640:1000:110:1261589:2013-01-04 15:19:35.735918000 +0100:2013-01-04 
15:20:18.611922558 +0100:/var/crash/_usr_bin_xfce4-appfinder.1000.crash
   664:1000:110:0:2013-01-04 15:20:17.587918601 +0100:2013-01-04 
15:20:17.587918601 +0100:/var/crash/_usr_bin_xfce4-appfinder.1000.upload
   600:104:110:0:2013-01-04 18:25:35.376977374 +0100:2012-12-15 
10:34:43.593351096 +0100:/var/crash/_usr_bin_xfce4-appfinder.1000.uploaded
  Date: Fri Jan  4 18:42:14 2013
  InstallationDate: Installed on 2012-11-08 (57 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1790478] Re: gdm3 in cosmic fails to start fully in autopkgtest

...ubuntu7 completed tonight thanks!
I tested 2 times from proposed in the local tester and working as expected now.

Unfortunately the systemd upload itself failed at some of the flaky
(boot and smoke) tests. But it seemed more like the VM it ran in would
be dead.

I retriggered the 4 tests (systemd, iproute2, cryptsetup, dbus)
currently blocked on i386-systemd with appropriate triggers (currently
triggers need: glibc, dbus, systemd).

So in a few hours we know if those now resolve ...

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

Title:
  gdm3 in cosmic fails to start fully in autopkgtest

Status in gdm3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In systemd package for a while, there is a boot-and-services test
  case, which tries to install common/typical things and ensure they
  continue to operate with new systemd.

  One of the test cases is gdm3. The test case dependencies are:

  Tests: boot-and-services
  Depends: systemd-sysv,
systemd,
udev,
systemd-container,
systemd-coredump,
libpam-systemd,
xserver-xorg-video-dummy,
xserver-xorg,
gdm3 [!s390x],
cron,
network-manager,
busybox-static,
apparmor,
pkg-config,
python3

  The test does following:
  out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session']) 
 
  self.assertIn(b'gdm-x-session gnome-session', out)
 
  out = subprocess.check_output(['ps', 'u', '-C', 'Xorg'])  
 
  self.assertIn(b'Xorg vt1', out)   
 
  self.active_unit('gdm')

  However, this now errors out upon the first command, meaning gdm-x-session is 
not running anymore.
  On bionic, this test case continues to operate correctly in the autopkgtest 
cloud.

  test_gdm3 (__main__.ServicesTest) ... ERROR

  ==
  ERROR: test_gdm3 (__main__.ServicesTest)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.RNx2A1/build.2Wy/src/debian/tests/boot-and-services", line 
66, in test_gdm3
  out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session'])
File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
  **kwargs).stdout
File "/usr/lib/python3.6/subprocess.py", line 418, in run
  output=stdout, stderr=stderr)
  subprocess.CalledProcessError: Command '['ps', 'u', '-C', 'gdm-x-session']' 
returned non-zero exit status 1.

  --
  Ran 24 tests in 18.974s

  FAILED (errors=1)

  From http://autopkgtest.ubuntu.com/packages/systemd/cosmic/i386

  Thus it looks like there is a regression or a change of behavior of
  gdm3 in the cloud in cosmic; since bionic continues to work correctly.

  I will mark this test as an expected failure for now, and monitor it
  separately, as currently, this is blocking many migrations.

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

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

[Touch-packages] [Bug 1790478] Re: gdm3 in cosmic fails to start fully in autopkgtest

@Daniel: the latest gdm even in proposed that Dimitri and I can easily
try is currently 3.29.91-1ubuntu2

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

Title:
  gdm3 in cosmic fails to start fully in autopkgtest

Status in gdm3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In systemd package for a while, there is a boot-and-services test
  case, which tries to install common/typical things and ensure they
  continue to operate with new systemd.

  One of the test cases is gdm3. The test case dependencies are:

  Tests: boot-and-services
  Depends: systemd-sysv,
systemd,
udev,
systemd-container,
systemd-coredump,
libpam-systemd,
xserver-xorg-video-dummy,
xserver-xorg,
gdm3 [!s390x],
cron,
network-manager,
busybox-static,
apparmor,
pkg-config,
python3

  The test does following:
  out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session']) 
 
  self.assertIn(b'gdm-x-session gnome-session', out)
 
  out = subprocess.check_output(['ps', 'u', '-C', 'Xorg'])  
 
  self.assertIn(b'Xorg vt1', out)   
 
  self.active_unit('gdm')

  However, this now errors out upon the first command, meaning gdm-x-session is 
not running anymore.
  On bionic, this test case continues to operate correctly in the autopkgtest 
cloud.

  test_gdm3 (__main__.ServicesTest) ... ERROR

  ==
  ERROR: test_gdm3 (__main__.ServicesTest)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.RNx2A1/build.2Wy/src/debian/tests/boot-and-services", line 
66, in test_gdm3
  out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session'])
File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
  **kwargs).stdout
File "/usr/lib/python3.6/subprocess.py", line 418, in run
  output=stdout, stderr=stderr)
  subprocess.CalledProcessError: Command '['ps', 'u', '-C', 'gdm-x-session']' 
returned non-zero exit status 1.

  --
  Ran 24 tests in 18.974s

  FAILED (errors=1)

  From http://autopkgtest.ubuntu.com/packages/systemd/cosmic/i386

  Thus it looks like there is a regression or a change of behavior of
  gdm3 in the cloud in cosmic; since bionic continues to work correctly.

  I will mark this test as an expected failure for now, and monitor it
  separately, as currently, this is blocking many migrations.

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

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

[Touch-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices

2018-09-03 Thread Christopher Berner

I seems that HSP/HFP doesn't work at all on 18.04. I've tried a variety
of different Pulseaudio modules/settings, and also ofono. @vanvugt do
you know if a different issue tracks that?

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

Title:
  Annoying "call from" message when connecting Bose devices

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

2018-09-03 Thread Manuel Rösel

I had the same problem after the update from 16.04 to 18.04. I was able
to solve this with RESUME = none and sudo update-initramfs -u.

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

[Touch-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices

Yes, see bug 1768625.

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

Title:
  Annoying "call from" message when connecting Bose devices

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

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

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

[Touch-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices